How to forward text messages to your team (and keep records)

A customer texts your business number at 4:40 PM asking whether you can come out tomorrow. The person holding that phone is on a job site, the person who books jobs is at a desk across town, and the owner wants to see every conversation. The usual fix is to forward the texts to whoever needs them. That works for about a week.

Forwarding gets a message from one phone to another. It does not give you one history of the conversation. It does not keep opt-outs in one place, and it does not make replies come from the business. Those three gaps are where small teams lose leads and take on compliance risk. This post compares the three ways to get customer texts to staff: phone forwarding, a shared inbox and routing rules. For each one we cover what breaks and what you need to keep on record.

The three approaches at a glance

Short version: forwarding is fine for one person with two devices. Once a second person needs to reply, use a shared inbox. Add routing rules when the inbox gets busy enough that "whoever sees it first" stops working.

Option 1: phone forwarding

What it actually does

There are a few versions of this, and they behave differently:

• iPhone Text Message Forwarding sends SMS from your iPhone to your other Apple devices signed in to the same Apple ID, such as a Mac or iPad. It does not send texts to a coworker's phone.
• Carrier call forwarding usually forwards calls only. Plenty of owners set it up and assume texts follow. On most plans they don't.
• Android auto-forward apps watch incoming SMS and resend each one to another number or to email. Each forwarded copy is a new text sent from your phone.
• Text-to-email forwarding, which some virtual number services offer, drops each incoming text into an inbox.

Where it breaks

Forwarding moves a copy of the message to another phone or inbox. The conversation itself stays split:

1. The reply comes from the wrong number. The coworker who gets the forwarded text replies from their own phone. The customer now has two numbers for your business and saves the wrong one.
2. Nobody has the full thread. Part of the conversation sits on the business phone, part on a coworker's phone and part in someone's email.
3. Opt-outs don't travel. Suppose a customer texts STOP to the business number. The coworker texting them from a personal phone has no idea, and every text sent after that STOP is exposure under the TCPA, where statutory damages commonly run $500 to $1,500 per text.
4. Records walk out the door. When the employee leaves, the customer conversations on their personal phone leave with them.

Forwarding is reasonable when one owner wants texts on a phone and a laptop. If that's you, our guide to texting from a computer covers the options. Forwarding stops working once two people are replying to customers.

Option 2: a shared inbox

A shared inbox puts the business number in one place that several people can log in to. Every inbound text lands in a single thread per contact. Whoever answers, the reply goes out from the business number, and the whole team sees the history.

What you get

• One identity. The customer only ever sees one number. Hand-offs between staff don't show up on their end.
• One history. A new hire can open a thread and read the last six months of it before replying.
• Opt-outs applied once. On Ready, an inbound STOP or UNSUBSCRIBE is honored automatically and applies across the account, so that contact can't be texted again from any campaign or any team member's reply.
• Quiet hours enforced. Campaigns outside permitted hours in the recipient's local area are held and go out later; a one-off first text is held only if the window opens within about 6 hours, otherwise it is refused. A reply to someone who texted you in the last 24 hours goes out right away, because they started the conversation.

This is the model in our post on using SMS for customer support, which goes deeper on response times and hand-offs. If your team also texts each other about jobs, keep that separate from customer threads. Group texting for business covers why.

The tradeoff: you have to register

A shared inbox runs on a business number sending application-to-person (A2P) traffic. In the US that means 10DLC registration, and unregistered traffic gets filtered by carriers. On Ready, registration happens in the app. The charge at submit is the first month, $25, and after that the monthly cost is $25/mo for registration + $2 per number. Most approvals take 2 to 7 days. While you wait, an account can send up to 500 texts a month before it registers, at its normal per-text rate. What is 10DLC explains the process if it's new to you.

What it costs to run

Ready bills $0.0075 per segment plus a $0.0045 carrier fee per segment, and that applies to texts you receive as well as texts you send. Budget for both directions.

Here's an example with stated assumptions. A home-services business gets 1,500 customer texts a month and sends about 1,500 replies. Most messages are short, but assume 300 of the replies run longer and split:

• Inbound: 1,500 texts × 1 segment = 1,500 segments
• Outbound: 1,200 replies × 1 segment + 300 replies × 2 segments = 1,800 segments
• Total: 3,300 segments × $0.0075 = $25, plus 3,300 × $0.0045 in carrier fees
• Add registration: $25/mo for registration + $2/mo for one number

These figures exclude the optional compliance surcharge. DNC/litigator scrubbing and landline validation are each $0.003 extra per segment when switched on for an account, and both are off by default.

Watch the segment count on longer replies. A plain reply splits into 153-character segments after 160 characters. A single emoji drops the limit to 70 characters (67 per part), so a friendly 140-character reply ending in 👍 is 3 segments instead of 1. Ready swaps curly quotes and long dashes for plain ones before sending, so those don't change the count.

Ready is not the lowest per-segment price available. Raw carrier APIs and GoHighLevel's LC Phone are priced lower per message. What Ready includes is the inbox, registration handled in-app, opt-out propagation, quiet hours and the rest of the platform on top of the rate.

Option 3: routing rules

Once several people work the inbox, "whoever sees it first" turns into either two people answering the same customer or nobody answering. Routing rules decide who owns a conversation before anyone has to think about it.

Common rules for small teams

• By number dialed. Give each department its own registered number, such as one for scheduling and one for billing. Customers who text the billing number land with billing. This is the simplest rule, needs no software logic, and costs $2/mo per added number.
• By keyword. A customer texting RESCHEDULE or QUOTE gets tagged and handled by the right person. Our post on SMS keywords covers how keywords behave.
• By hours. After closing, an automation can send a short auto-reply saying when someone will respond, and the thread waits for the morning shift. The auto-reply is a fixed message you wrote. It is not AI answering on your behalf.
• By contact owner. Existing customers go to the rep who already handles them.

Where the rules live

If you run on GoHighLevel, Ready connects through OAuth with two-way sync, so inbound texts appear in GHL for each connected sub-account. You can then use GHL's own workflows and assignment to route them. If your team works out of a helpdesk or your own app, Ready has webhooks for inbound messages and a REST API for replies. The messages API docs and the quickstart show the setup.

One caution: a routing rule that forwards a text to someone's personal phone just brings back Option 1's problems. Route conversations to people inside the shared system, never out of it.

What to keep on record, and who keeps it

"Keep records" means three different things, and they live in different places.

1. Message history. Every inbound and outbound text, with timestamps and who sent it. A shared inbox keeps this automatically. On Ready you can download it any time from Settings, Compliance, Export (Messages as CSV or JSON), or pull it through the API (GET /v1/messages, paged with before_id) and archive it on your own schedule.
2. Opt-outs. The list of numbers that said STOP. Ready keeps this per account and refuses sends to opted-out numbers up front, with no charge for the refused text. Download the list from the same Export section, or read it with GET /v1/opt-outs.
3. Consent. This is the one owners get wrong. Ready records the sender's opt-in attestation on each bulk send and each API send that sets consent_attested: who sent it, to how many people and when. That gives you an audit trail of your own promises. It is not a per-contact consent record. Ready does not store when a given customer opted in, what wording they saw or which page they signed up on, and a keyword reply doesn't create one. Your website form, booking tool or CRM has to keep that. If you're building a list from scratch, how to build an SMS marketing list covers capturing consent properly. (A contact who signs up on a Ready-hosted opt-in page is the exception: Ready stores that sign-up, with the time, IP address and exact wording, and support@tryready.com can send you a copy.)

A note for regulated businesses: healthcare, legal and financial teams have retention and privacy rules beyond the TCPA. Moving customer texts off personal phones and into a system the business controls is a step in the right direction. It does not settle your obligations on its own, so check your specific requirements with whoever advises you on compliance. Compliance stays the sender's responsibility. The tools reduce risk; they don't remove it.

Which one to use

• Solo owner, one phone: forward to your own laptop and stop there.
• Two to ten people answering customers: move to a shared inbox on a registered business number. Recovering a single lost lead usually pays for the monthly registration.
• A busy inbox or several departments: add routing, starting with one number per department before building anything clever.

Whichever you pick, make sure replies come from the business, the full thread lives somewhere the business owns, and STOP applies to everyone at once.

Next step

If you want to try the shared-inbox approach, you can create a Ready account. To send, you add a card and get a number, which is $2 a month with the first month charged when you get it. Your first 20 one-to-one texts are free, so use them to test replies from your phone and the inbox before you pay for registration, because the free texts end once registration is paid. When you're ready to register, the in-app flow handles the brand and campaign. Pricing shows the per-segment rate.