SASarah AhmedWhatsApp · Property enquiryAisha
Is the Business Bay unit still available?
Internal note — captured on the lead, never sent to the customer.
Owned by Aisha2m ago
ONE THREAD LIST
Every conversation,
in one place.
Most teams answer customers across three apps on somebody’s personal phone. Nobody can see the history, nobody knows who replied, and when that person is away the thread simply stops.
01 — IN ONE LINE
One shared thread list for every channel, so a conversation belongs to the business rather than to whoever owns the phone.
And, just as usefully, what it is not:
- Not a shared login on one handset. Everyone has their own account, and you can see who said what.
- Not a helpdesk with ticket numbers. It stays a conversation, because that is what the customer thinks it is.
- Not an archive you check afterwards. It is where the work actually happens.
02 — HOW IT ACTUALLY WORKS
Six steps,
in order.
- ArrivesEverything lands in one list
WhatsApp, Instagram and Telegram messages appear in the same place, in the order they arrived, whoever they are for.
- ContextThe history comes with it
Open a thread and you have every previous message, the captured fields and the internal notes, without asking a colleague what happened last time.
- OwnerSomeone owns it
A thread is assigned to a person, not left in a shared pile. The name is visible on the thread, so nobody double-replies and nobody assumes it is handled.
- NotesInternal notes stay internal
Leave a note for the next person on the thread itself. It is attached to the conversation and never visible to the customer.
- HandoverHandover is a click, not a briefing
Reassign and the whole thread goes with it. The person picking it up reads what was said rather than a summary of what someone remembers.
- SearchIt is all searchable afterwards
Find the conversation where you quoted a price, six weeks later, without scrolling one person’s phone.
03 — IN DEPTH
What it does,
and what you decide.
Every channel in one list
WhatsApp, Instagram and Telegram threads sit together instead of in three apps with three notification badges.
You controlYou choose which channels are connected and who can see each one.
Shared, with real accounts
Each person logs in as themselves, so replies are attributable and access can be removed when someone leaves.
You controlRoles decide who sees the whole inbox and who sees only their own threads.
Assignment and ownership
Threads are assigned, manually or by rule, and the owner is visible on the thread.
You controlRouting by language, channel, workload or hour.
Internal notes
Context for colleagues lives on the conversation rather than in a separate chat group.
You controlNotes are never sent to the customer; there is no way to post one by accident.
The record is attached
The lead, its stage and its captured fields sit beside the thread, so replying and updating are the same action.
You controlWhich fields show on the thread panel is configurable.
Search and history
Conversations remain findable after the fact, including ones handled by people who have since left.
You controlRetention is a workspace setting.
04 — SEE IT MOVE
Try the mechanic,
not a video of it.
Switch channel. The list, the history and the owner do not change — only the app the customer happened to use.
One thread listIllustrative sample data
OHOmar HassanInstagram · AppointmentAhmed
Do you have anything tomorrow evening?
Internal note — captured on the lead, never sent to the customer.
Owned by Ahmed18m ago
DKDaniel KhanTelegram · Course enquiryAisha
Are weekend classes available?
Internal note — captured on the lead, never sent to the customer.
Owned by Aisha1h ago
Same list, whichever app the customer used.
05 — WHAT YOU CONTROL
Your settings,
not our defaults.
Connected channels
Which numbers and accounts feed the inbox.
Who sees what
Whole inbox, one team’s threads, or only your own.
Assignment rules
How an unclaimed thread finds an owner, and what happens out of hours.
Reply permissions
Who may reply to a customer, and who may only leave notes.
Saved replies
The answers your team types constantly, kept in one place and edited once.
Retention
How long conversation history is kept.
06 — WHAT IT DOES NOT DO
The honest list.
Every tool has one. Most vendors keep it for the sixth week of the implementation, which is a worse time to read it than now.
- It cannot pull in history from before the number was connected. You start from the day you connect, not from your whole past.
- Each WhatsApp number belongs to one workspace. A number already live in another provider must be migrated, not shared.
- It is not a personal chat app. Staff messaging each other should stay wherever it already lives.
- Voice calls are not part of it. The inbox is messaging.
- If your team keeps replying from personal phones, the inbox will be incomplete and the reporting on top of it will be wrong. This is a habit problem, and the tool cannot solve it for you.
07 — GETTING IT LIVE
What the first
two weeks look like.
- Day 1Connect one channel
Usually the WhatsApp number customers already message. Everything else can wait.
- Day 1Add your people
Real accounts, real names. This is what makes replies attributable.
- Day 2Decide who owns what
Assignment rules, and the fallback for out of hours.
- Week 1Move the team off personal phones
The hardest step, and the one that determines whether any of this works.
- Week 2Add the remaining channels
Instagram and Telegram, once the habit has taken.
08 — WHERE IT SITS
It is one part
of one system.
AI Agents
The agent works these same threads. There is no separate bot conversation to reconcile afterwards.
The CRM
The lead and its fields sit beside the thread, so replying and updating the record are one action.
Automation
Inbound messages are the most common workflow trigger.
Analytics
Response times and per-person volume are measured from what actually happened here.
09 — QUESTIONS
What teams
actually ask.
Do we keep our existing WhatsApp number?
That is the usual goal, and it is worth asking about your specific case in the demo. A number currently on the consumer WhatsApp Business app has to be migrated, which is a one-way step.
Can two people reply to the same customer?
They can, which is exactly why threads are assigned and the owner is shown. The inbox makes a double-reply visible rather than impossible.
Will staff see each other’s conversations?
That is a setting. Some teams want a fully open inbox; others restrict each person to their own threads.
What happens when someone leaves?
You remove their account and reassign their threads. The history stays with the business, which is the main reason not to run this on personal phones.
Can customers tell the difference?
No. It is the same WhatsApp conversation from their side.
Does it work on a phone?
Ask in the demo and we will show you exactly what the mobile experience is today rather than describing it.
LET’S KEEP THE CONVERSATION GOING
Bring us the process
you already run.
We will map it into Unified Inbox live, and tell you honestly which parts fit and which do not.
- 5 minYou show us how the work happens today
- 10 minWe build it in front of you
- 5 minYou keep the diagram, either way
