One inbox: SMS, email and AI reply drafts
Answer texts and email from one inbox, check AI reply drafts, and ask before you promise WhatsApp.
Read the lesson
Goal: Put every customer message in one inbox and give each one an owner. Then set a response target the team can meet.
You need: The client's phone numbers and email set up in ServiceAgent. Carrier approval for texting. Growth suits teams of 3 or more, because Core has 2 users.
Why this matters
A typical service business talks to customers in five places. The office cell. The owner's cell. A shared email. Facebook messages. The website chat. Each place has its own habits, and none has an owner.
Five places become one inbox
- Office cell
- Owner's cell
- Shared email
- Facebook messages
- Website chat
- One list in Conversations
- A named person per block of hours
- Inbox SLA tasks as a safety net
So messages wait. A customer texts the office cell on Friday. The office manager is off. The text sits until Monday. The customer books someone else on Saturday.
Conversations is the fix. It is the ServiceAgent inbox. Texts, emails and chats land in one list. Everyone on the team sees the same list. Every message has a clear history.
Every channel into one inbox
- 1SMS, email and chatSet up once in Settings
- 2ConversationsOne list the whole team sees
- 3Named person repliesFrom the number the customer used
- 4Unread past the thresholdChecked hourly
- 5Inbox SLA taskShows where cover failed
The size of the business changes what the inbox must do:
- Owner-operator. The owner is the inbox. The win is one place to look, on one phone, instead of five.
- Fleet. Several people reply. The risk is that two people reply to the same customer, or nobody does. You need owners and a time target.
- Multi-location. Each location has its own number. The team must know which location a message is for.
Channels, senders and costs
Set up each channel once. Then it flows into Conversations.
| Channel | Where to set it | Credits (Credit Calculator) |
|---|---|---|
| SMS | Settings → Communications → Phone numbers | 2 per segment |
Settings → Communications → Email setup | 0.5 per email | |
| Website chat | Widgets → Chat & phone | 0.5 per AI chat interaction |
Not in Channels today; ask ServiceAgent support | Not listed; check Usage history |
An AI text reply costs 3 credits: 2 for the SMS segment and 1 for the AI message. WhatsApp is not on the Credit Calculator. After the first week, check Billing → Usage history for the real cost.
Also set Default senders. These decide which number and email address a reply comes from. A customer who texted the main line should get the reply from the main line, not from a tech's number.
Rules the inbox enforces for you
Settings → Communications → Messaging defaults holds three rules. Know them before you promise anything.
Quiet Hours. Default 9:00 PM to 8:00 AM. Automated texts respect this window.SMS Compliance. Opt-out is always enforced. A customer who replies STOP gets no more texts.Throttles. At least 10 seconds between texts to the same person.
Rules in Messaging defaults
Messaging Settings
Build it in ServiceAgent
- List every place customers message the business today. Ask the owner and the office. Write each one down.
- Connect the main business number in
Phone numbers. If the business has a number it wants to keep, porting goes through ServiceAgent support. It takes about 1 to 2 weeks, and the number stays active. - Connect the main business email in
Email setup. Channelsmanages SMS and email. If customers use WhatsApp, ask ServiceAgent support how to connect it. Many Spanish-speaking customers prefer it.- Install the chat widget (lesson 2).
- Set
Default sendersfor texts and email. - Invite each person who replies in
Settings→Team & Access→Team members & invites. On Core, only 2 users fit, and your login is one of them. - Set the response target. Go to
Settings→Service Catalog→SLAs→Inbox SLA. SetUnassigned Thread ThresholdandUnread Thread Thresholdin minutes. The app checks hourly. A breach creates a task. - Optional: build an auto-acknowledge workflow. Use
Event Trigger→Inbox Message Received. Add aConditionso it runs only outside business hours. Then addReply In Inbox Threadwith a short note and the booking link.Quiet Hoursstill holds automated texts from 9:00 PM to 8:00 AM. - Send one test message from each channel. Check that each lands in
Conversationswith the right contact. - Turn off the old places one by one. Forward the old email. Put the main number on the Facebook page.
Check it works: one test from each channel lands in Conversations. A test left unread past the threshold creates a task within the hour.
An after-hours note at 7:32 pm
- Customer · 7:32 pmHi, my kitchen breaker keeps tripping. Can someone come tomorrow?
- Volt Pro Electric · 7:32 pmThanks for your message to Volt Pro Electric. Our office opens at 8 am. You can book a time here: [booking link]
- Customer · 7:40 pmBooked 9 am tomorrow.
Choosing the SLA numbers
Pick numbers the team can really meet. A target nobody meets creates noise, and people start to ignore the tasks.
A good start for business hours is 15 minutes unread and 30 minutes unassigned. Because the app checks hourly, a breach can take up to an hour to show. That is fine. The SLA is a safety net, not the main tool. The main tool is people looking at one inbox.
Working the inbox day to day
Setup is one day. The habit is every day. Give the team a simple routine and write it on one page.
- Start of day. Open
Conversations. Reply to anything that came in overnight, oldest first. Night messages are often the most urgent. Reply before you start new work. - During the day. One named person watches the inbox in each block of hours. Lunch breaks get cover. The
Inbox SLAtasks show where cover failed. - End of day. Nothing is left unread. Anything that needs a callback gets a task with an owner and a due time.
- Weekly. You, the Operator, read a sample of 20 threads. Look for slow replies, wrong answers and messages in the wrong place.
A day in the inbox
- Start of dayReply to overnight messages, oldest first
- During the dayOne named person watches each block of hours
- End of dayNothing unread; callbacks get a task with an owner
- WeeklyThe Operator reads 20 threads
For an owner-operator, this routine is shorter. They check Conversations at three set times a day, and the AI and the booking link cover the rest. For a fleet, the routine needs names. Write who covers which hours on the same page. For a multi-location business, add the location to each block. "Maria covers Plymouth texts, 8 am to noon" is a clear rule. "The office covers texts" is not.
Language and channel choice
Customers pick the channel. The business should not force them to switch. Some customers text a photo of a leak or a broken part. The photo lands in the thread, so the tech can see it before the visit. Ask the office to reply with a booking link or a time, not only "thanks". A customer who texts gets a text back. A customer who emails gets an email back. Many Spanish-speaking customers prefer WhatsApp. If the client serves them, ask ServiceAgent support about WhatsApp. Reply in Spanish where staff can.
Worked example: Volt Pro Electric
Volt Pro Electric has 10 electricians on Growth. Two office staff reply to messages. Example inputs for one month:
- 300 inbound texts
- AI text replies to 180 of them, mostly after hours
- 90 outbound emails
Credit math:
- AI text replies: 180 x 3 = 540 credits
- Emails: 90 x 0.5 = 45 credits
- Total: 540 + 45 = 585 credits
Growth includes 6,000 credits a month. 585 is just under 10% of that.
Volt Pro Electric monthly credits
- AI text replies: 180 × 3540
- Emails: 90 × 0.545
Total, under 10% of Growth's 6,000585 credits
Before the change, Volt Pro had messages in 4 places. The office manager checked the owner's cell twice a day. After the change, every message is in Conversations. The Inbox SLA is 15 minutes unread. In the first week, it created 6 tasks. Each one showed a gap in coverage over lunch. The office moved one lunch break, and the tasks stopped.
Common mistakes
- Leaving the old places open. If customers can still text the owner's cell, they will. Move the main number and tell regular customers.
- No owner for messages. "Everyone checks the inbox" means nobody does. Name who replies in which hours.
- Targets the team cannot meet. A 2-minute target creates tasks all day. Start at 15 minutes and tighten later.
- Ignoring WhatsApp costs. WhatsApp is not on the Credit Calculator. Check
Usage historyafter the first week. - Too few users on Core. Core has 2 users, and the Operator takes one. A team of 3 that replies needs Growth.
Do this now
For one roster business, list every place customers message it today. Next to each, write how it reaches Conversations. Then pick an Unread Thread Threshold and an Unassigned Thread Threshold. Write one sentence on why the team can meet them.
Practice the conversation
- Owner My team already answers texts.
- Operator From how many phones?
- Owner The office cell, my cell, and email. Facebook too.
- Operator So when your office manager is off, who reads their phone?
- Owner Nobody, I guess.
- Operator With one inbox, every message lands in one list. Anyone on the team sees it.
- Owner What if nobody answers?
- Operator Past 15 minutes, the next hourly check makes a task for the team. Nothing waits all weekend.
- Owner Do I need to buy new phones?
- Operator No. Your team uses ServiceAgent on the phones and computers they have.
Quick check
- A team of 4 office staff must each reply in `Conversations`. The client is on Core. What do you tell the owner?
- Core is fine, because users are unlimited on every plan
- Core has 2 users and your Operator login is one; the team needs Growth
- The staff can share one login to save money
- Move to Launch, which allows more users than Core
- You set the `Unread Thread Threshold` to 15 minutes. A message sits unread for 20 minutes. When can you expect the task?
- Exactly at 15 minutes
- Never, because 20 minutes is close enough
- Within the hour, because the app checks hourly
- The next morning, after `Quiet Hours` end
- A Growth client's AI replies to 250 texts a month. The team also sends 200 emails. How many credits is that?
- 350 credits
- 600 credits
- 850 credits
- 1,000 credits
ServiceAgent UniversityLearn to run a service business on autopilot. Free courses, Blueprints and certification for Service Operators.