Messages get missed because they arrive in six places and no single person is responsible for any of them.
TL;DR One inbox, every channel, threaded by customer. Assign every conversation to a named person. Track first-response time as your main metric. Tag automatically, respond manually.
The problem in concrete terms
A typical service business receives enquiries through
- The website form, going to a shared address.
- Direct email to whoever’s address the customer had.
- Text to the owner’s mobile.
- Facebook or Instagram messages.
- Google Business Profile messages.
- WhatsApp.
- Phone, with voicemail somewhere else again.
- The booking platform’s own messaging.
No single view. No ownership. No record of who replied to what. The missed enquiry is not carelessness, it is a structural inevitability.
What a unified inbox does
Threads every channel by customer, so the text from Tuesday and the email from Friday sit in one conversation.
Assigns ownership, so every conversation has a name against it.
Records the history, so anybody picking it up has context.
Measures response time, which is the metric that actually predicts conversion.
Threading by customer, not by channel
This is the feature that matters and not every platform does it well.
Test during a trial: send yourself a message from three channels using the same phone number and email. Do they appear as one conversation or three?
Matching keys
- Phone number, normalised. This is why phone format standardisation matters.
- Email address.
- Social profile ID, linked manually the first time.
Merge duplicates when they appear. A customer who texts from a second number will create a new record, and the merge should be one click.
Assignment and ownership
Every conversation gets an owner. No exceptions.
Rules that work
- Unassigned queue is checked by a named person at set times, not “whenever someone looks”.
- First responder owns it until they hand it over explicitly.
- Handover is a deliberate action, with a note, not a silent reassignment.
- Nobody goes on holiday without reassigning their open conversations.
Avoid round-robin auto-assignment in a small team. It sounds fair and it produces conversations owned by whoever happens to be up a ladder.
Response time as the core metric
First-response time is the number to manage.
Set an internal target and publish it to the team
| Channel | Target during hours |
|---|---|
| Phone | Answered, or called back within 30 minutes |
| SMS and chat | Within 15 minutes |
| Social message | Within 1 hour |
| Email enquiry | Within 1 hour |
| Email, existing customer, non-urgent | Same day |
Measure the median, not the average. One conversation left over a weekend distorts an average badly and hides the typical experience.
An automatic acknowledgement is not a response. Count the first human reply. Acknowledgements are useful and they are not the metric.
Automated tagging
Tag automatically. Respond manually.
Useful tags
- Enquiry type. New job, existing customer, complaint, supplier, spam.
- Urgency. Detected from keywords, with a bias toward over-flagging.
- Service type, for routing to the right person.
- Status. Awaiting us, awaiting customer, closed.
The awaiting-customer tag is quietly valuable. It stops conversations sitting in the queue looking unanswered when the ball is with them, and it lets you chase properly after a few days.
Do not auto-respond with anything substantive. An acknowledgement, yes. An answer, no.
Templates without sounding templated
Save the openings and the facts, not the whole message.
Good snippet
Our standard call-out is $95, which covers the first hour on site. Parts are quoted separately before any work goes ahead.
Then write the rest personally. Snippets for the repeated factual content, human writing around it.
Avoid full canned replies for anything beyond acknowledgement. They are recognisable and they read as dismissive on the receiving end.
Out of hours
- Set expectations in an auto-reply, with the emergency route.
- Do not promise a response time you will not meet. Under-promise here.
- Emergency path must be genuinely monitored. An emergency number nobody answers is worse than not offering one.
- Turn off notifications for the team outside hours, deliberately. Always-on inboxes produce burnout and worse responses.
Choosing a platform
Check
- Which channels are supported natively, especially Google Business Profile messages and WhatsApp, which are commonly missing.
- Threading by customer, tested properly.
- Mobile app quality. Most responses will be sent from a phone.
- Does it connect to your CRM, so conversation history appears on the customer record.
- Number portability. Can you keep your existing business number?
- Export. Your conversation history is a business record.
Many all-in-one platforms include this, which is usually the right answer at small scale rather than a separate tool.
Measure it
- Median first-response time, by channel, weekly.
- Conversations with no owner, which should be zero at end of day.
- Conversations open over 48 hours.
- Enquiry to booking conversion, segmented by response time. This is where you prove the value of the whole exercise internally.
- Messages received per channel, which frequently reveals a channel nobody was monitoring.
Audit where messages currently arrive, listing every channel honestly. Most businesses find at least two nobody is responsible for, and that audit alone is worth doing before you buy anything.
Need a pro to set it up? [BOOK A CALL]