Shared SMS Inbox: How to Run Two-Way Business Texting

A customer texts your office number at 4:50 pm to move tomorrow's appointment. One person sees it, means to reply, and goes home. By morning nobody knows the message exists. A shared SMS inbox prevents that: every text to a business number lands in one place the whole team can see, with one owner per conversation and a record of what was said.

The software is the easy part. Two-way business texting works when the team agrees on who answers, how fast and in what voice. Below are those rules, five templates to adapt and a checklist to save.

What is a shared SMS inbox?

A shared SMS inbox is a team inbox for text messages sent to and from your business numbers, so any authorised teammate can read, answer and hand over a conversation. It replaces texting customers from personal mobiles.

Texting from personal phones is quick until something goes wrong:

• Context is trapped on one device. The rep who texted the customer last week is the only person who can see that thread. Anyone else starts from zero.
• There is no handover. When that person is sick, on holiday or leaves the company, the conversation goes with them, and so does the customer's history.
• There is no opt-out record. If a customer replies STOP to a personal number, nothing tells the rest of the team. The next person to text them from another phone ignores a clear request.

A shared inbox moves the conversation from the individual to the business. Texts come from and go to business numbers, everyone with access sees the same thread, and opt-outs are recorded once for the whole account.

How should a team assign, snooze and close texts?

Give every open conversation exactly one owner, and use three actions to keep the queue clean: assign, snooze and close. Without ownership, a shared inbox becomes a room where everyone assumes someone else will reply.

The three actions that keep the inbox clean

• Assign a conversation to the person who will see it through. Default rule: whoever replies first owns it, unless it belongs to an existing account manager.
• Snooze a conversation that is waiting on something, such as a customer sending a photo or a part arriving, so it leaves the queue and comes back when it needs attention.
• Close it when the question is answered. If the customer texts again later, whoever picks it up starts with the full history.

Handover rules

Write these down so nobody has to guess:

• Before a day off, the owner reassigns open conversations or snoozes them with a note.
• If an owner misses the reply-time target, a team lead may reassign the thread.
• Billing questions, complaints and anything legal go to a named person, not whoever happens to be online.

Use internal notes, not side chats

When a teammate needs to pass on context ("she already has a quote, don't send another"), put it in an internal note on the conversation. Notes stay with the thread; a side-chat message is lost to the next person. In Phonify's shared inbox, teammates can assign, snooze, close and add internal notes on each conversation, so the history and the handover sit in one place.

How fast should a business reply to a text?

A practical starting target is a first reply within 15 to 30 minutes during business hours and first thing the next morning after hours. Pick a target your team can hit nearly every day, then tighten it.

These are starting points, not industry benchmarks. Texters expect faster answers than emailers, but "instant" is not realistic for a small team.

Use the unread count as your daily health check

The simplest metric is the number of unread conversations. A useful rule: zero unread at lunch and at close. A rising count signals a staffing or ownership problem, and live unread counts make it an easy number to glance at during the day. If texts arrive after hours, pair the inbox with an after-hours call routing plan so calls and texts get the same treatment.

Five SMS templates that don't sound like a robot

Good SMS templates are short, signed with a real name and use one or two merge fields at most. A text that reads like a form letter gets ignored; write templates the way your best rep talks.

The examples below use a hypothetical business, Northside Plumbing:

1. Missed-call follow-up: "Hi {first name}, sorry we missed your call. This is Dana at Northside Plumbing. What can we help with? Reply here or call us back on this number."
2. Appointment reminder: "Hi {first name}, a reminder that we're booked for {appointment time}. Reply C to confirm or R if you need to reschedule."
3. Quote sent: "Hi {first name}, I've just emailed your quote. Happy to walk through it by phone if that's easier. Any questions, just reply."
4. Payment link: "Hi {first name}, here's the secure link for invoice {invoice number}: {link}. If anything looks off, reply here and we'll sort it."
5. Review request: "Thanks again, {first name}. If you have a minute, a quick review helps a small business like ours a lot: {link}. No worries if not."

Rules that keep templates human:

• Sign with a real name. "This is Dana" reads very differently from "This is a message from the team."
• Give one clear next step per message.
• Read every template aloud before saving it. If it sounds stiff spoken, it reads stiff too.

Phonify supports templates with merge fields, and MMS attaches images, PDFs, audio or video up to 5 MB, which is useful for a photo of a finished job or a PDF quote in the same thread.

Why should texts sit on the same timeline as calls and email?

Because the person replying needs the whole history, not just the text thread. The customer who texts "any update?" may have called yesterday and left a voicemail last week; without that context, your team asks questions the customer already answered.

Before replying, your team should see the last call, the last voicemail and the last email with that contact. That is the difference between "Can you remind me what this is about?" and "Yes, the part arrived this morning, we can come Thursday."

In Phonify, every reply lands next to that contact's calls, voicemail and email on one timeline, as described on the page for two-way SMS and the shared inbox. Agents can also send a text from the call screen without leaving the call. Support teams that want one inbox for calls, texts, voicemail and email get the full picture without switching tabs.

How do you handle opt-outs and consent in a shared SMS inbox?

Record consent before you text, honour STOP immediately for the whole team, answer HELP with your business name and register your numbers. A shared inbox makes this easier because there is one record for everyone instead of one per phone.

• Get consent first, and record how and when each customer agreed.
• Honour STOP immediately. When a customer opts out, nobody on the team should be able to text them again until they opt back in.
• Answer HELP with your business name and how to reach you.
• Register your numbers. Business texting from standard local numbers in the US generally requires 10DLC registration. Our 10DLC registration guide walks through it.

Phonify sends automatic STOP, START and HELP replies, so they are handled the same way every time.

This is general guidance, not legal advice. For the industry rules, read the CTIA Messaging Principles and Best Practices and the FCC's guidance on telemarketing and robocalls, and check with your own counsel.

Your shared SMS inbox checklist

Use this list to set up team texting or to audit the setup you already have:

• All customer texts go to and from business numbers, not personal phones
• Every open conversation has one owner
• Written handover rules for days off and missed targets
• Internal notes used for context instead of side chats
• Reply-time targets for business hours and after hours
• Zero unread at lunch and at close
• Five or so templates, signed with a real name, read aloud before saving
• Texts visible next to calls, voicemail and email
• Consent recorded, STOP honoured, numbers registered