This covers exactly what merges, what refuses to, when you actually need one, and what to do about the parts that cannot be unified.<\/p>\n\n\n\n
Key takeaways<\/h2>\n\n\n\n\n- A unified inbox unifies the work, not the customer.<\/strong> WhatsApp knows a phone number, Instagram knows an account id, and nothing bridges them.<\/li>\n\n\n
- What genuinely unifies: the queue, the escalation rules, the ownership model and the measurement. That is enough to be worth it.<\/li>\n\n\n
- Capabilities do not unify – AI replies run only on Instagram, TikTok, Telegram and Discord, product cards are not available on TikTok, LinkedIn has no DM sending at all.<\/li>\n\n\n
- Reply windows differ: 24 hours on Meta inboxes, 7 days for a private reply to a comment, 48 hours on TikTok.<\/li>\n\n\n
- Cost does not unify either – the free monthly service allowance is per WhatsApp business number with no equivalent elsewhere.<\/li>\n\n\n
- The decisive signal is coordination happening in a second tool: \u201cdid anyone reply to this?\u201d asked in a group chat.<\/li>\n\n\n
- You can match customers yourself using an email or order number. That is matching you perform, not identity the platform resolves.<\/li>\n\n<\/ul>\n\n<\/div>\n\n\n\n
What Genuinely Merges<\/h2>\n\n\n\n
Four things, and they are worth more than the marketing suggests.<\/p>\n\n\n\n
One Queue<\/h3>\n\n\n\n
The obvious one, and the largest practical gain. Not because switching tabs is hard, but because what is waiting in a tab nobody opened is invisible – and every multi-channel business has one channel that quietly goes unanswered for days.<\/p>\n\n\n\n
A single queue makes neglect visible, which is most of what fixes it.<\/p>\n\n\n\n
One Set of Rules<\/h3>\n\n\n\n
The word refund<\/em> should route to the same person whether it arrived on Instagram or WhatsApp. Without unification each channel develops its own habits, usually shaped by whoever happens to watch it, and the customer experience varies by the channel they picked.<\/p>\n\n\n\nWriting the rules once and applying them everywhere is a quieter benefit than the single queue and arguably a bigger one – see how escalation rules get written<\/a>.<\/p>\n\n\n\nOne Ownership Model<\/h3>\n\n\n\n
A rota that covers all channels, rather than an implicit arrangement where one person watches Instagram because they always have. The ownership question is the same one that decides shared inbox versus helpdesk<\/a>, and unification is what makes a single answer possible.<\/p>\n\n\n\nOne Set of Numbers<\/h3>\n\n\n\n
Response time computed the same way everywhere is what finally lets you compare channels – and the comparison is usually surprising. Most businesses discover they are slowest on the channel they consider most important.<\/p>\n\n\n\n
Without a shared definition, per-channel numbers are not comparable and effort follows habit rather than evidence.<\/p>\n\n\n\n![\"What](\"https:\/\/dmpro.brandid.app\/blog\/wp-content\/uploads\/2026\/10\/unified-social-inbox-what-merges.jpg\")
The work, the rules and the measurement. Not the customer.<\/figcaption><\/figure>\n\n\n\nThe Identity Problem<\/h2>\n\n\n\n
The part vendors are vague about, and the part worth understanding before you buy anything.<\/p>\n\n\n\n
Two Contacts, One Human<\/h3>\n\n\n\n
WhatsApp identifies a person by phone number. Instagram identifies them by an account id. Messenger, Telegram and TikTok each have their own. None of these is exposed to anybody else, and there is no lookup that connects them.<\/p>\n\n\n\n
So a customer who asks about an order on Instagram and follows up on WhatsApp appears as two separate conversations with two separate histories, in every tool, including this one. An inbox can put those conversations next to each other; it cannot know they are the same person.<\/p>\n\n\n\n
What You Can Do Instead<\/h3>\n\n\n\n
Match on something the customer gives you. An order number, an email address, a booking reference – any of those lets you join the records yourself, and a webhook lookup can pull the matching history into the conversation.<\/p>\n\n\n\n
That is matching you perform, deliberately, on data you were given. It is not the platform resolving identity, and it only works where the customer volunteers the key.<\/p>\n\n\n\n
Design Around It<\/h3>\n\n\n\n
Practically: ask for the order number early in support flows, because it is the join key as well as the lookup key. And do not promise customers that you will remember a conversation they had on a different channel, because you will not reliably.<\/p>\n\n\n\n
The order-status pattern in the order-status lookup<\/a> is the same mechanism doing double duty.<\/p>\n\n\n\nThree More Things That Do Not Unify<\/h2>\n\n\n\n
Each one surprises somebody during implementation.<\/p>\n\n\n\n
Capabilities<\/h3>\n\n\n\n
AI replies work on Instagram, TikTok, Telegram and Discord, and not on WhatsApp or Messenger. Product cards work on WhatsApp, and not on TikTok. LinkedIn offers comment triggers and no DM sending at all. Rich sends – locations, contact cards, stickers, invoices – differ channel by channel.<\/p>\n\n\n\n
A flow built once therefore does not behave identically everywhere, and a unified inbox does not change that. What it changes is that you can see it happening in one place.<\/p>\n\n\n\n
Windows<\/h3>\n\n\n\n
Twenty-four hours from the customer’s last message on Meta inboxes, resetting each time they write. Seven days for a private reply to a public comment. Forty-eight hours on TikTok, with a cap of ten consecutive outbound messages.<\/p>\n\n\n\n
Which means \u201creply within 24 hours\u201d is not a single policy you can apply across the inbox – it is the strictest common denominator, and treating it as universal wastes the seven-day window where you have it.<\/p>\n\n\n\n
Cost<\/h3>\n\n\n\n
There is no single meter. WhatsApp’s thousand free monthly service messages are per business phone number and have no equivalent on the other channels, which have their own arrangements.<\/p>\n\n\n\n
So a per-conversation cost across a unified inbox is an average of unlike things. Model each channel separately – the method is in the cost arithmetic<\/a>.<\/p>\n\n\n\n![\"The](\"https:\/\/dmpro.brandid.app\/blog\/wp-content\/uploads\/2026\/10\/unified-social-inbox-when.jpg\")
Two of these are enough. None of them is a follower count.<\/figcaption><\/figure>\n\n\n\nWhat Survives Unification, by Channel<\/h2>\n\n\n\n
Worth having on a wall during implementation, because every one of these catches somebody out.<\/p>\n\n\n\n
What Genuinely Merges<\/h2>\n\n\n\n
Four things, and they are worth more than the marketing suggests.<\/p>\n\n\n\n
One Queue<\/h3>\n\n\n\n
The obvious one, and the largest practical gain. Not because switching tabs is hard, but because what is waiting in a tab nobody opened is invisible – and every multi-channel business has one channel that quietly goes unanswered for days.<\/p>\n\n\n\n
A single queue makes neglect visible, which is most of what fixes it.<\/p>\n\n\n\n
One Set of Rules<\/h3>\n\n\n\n
The word refund<\/em> should route to the same person whether it arrived on Instagram or WhatsApp. Without unification each channel develops its own habits, usually shaped by whoever happens to watch it, and the customer experience varies by the channel they picked.<\/p>\n\n\n\n Writing the rules once and applying them everywhere is a quieter benefit than the single queue and arguably a bigger one – see how escalation rules get written<\/a>.<\/p>\n\n\n\n A rota that covers all channels, rather than an implicit arrangement where one person watches Instagram because they always have. The ownership question is the same one that decides shared inbox versus helpdesk<\/a>, and unification is what makes a single answer possible.<\/p>\n\n\n\n Response time computed the same way everywhere is what finally lets you compare channels – and the comparison is usually surprising. Most businesses discover they are slowest on the channel they consider most important.<\/p>\n\n\n\n Without a shared definition, per-channel numbers are not comparable and effort follows habit rather than evidence.<\/p>\n\n\n\n The part vendors are vague about, and the part worth understanding before you buy anything.<\/p>\n\n\n\n WhatsApp identifies a person by phone number. Instagram identifies them by an account id. Messenger, Telegram and TikTok each have their own. None of these is exposed to anybody else, and there is no lookup that connects them.<\/p>\n\n\n\n So a customer who asks about an order on Instagram and follows up on WhatsApp appears as two separate conversations with two separate histories, in every tool, including this one. An inbox can put those conversations next to each other; it cannot know they are the same person.<\/p>\n\n\n\n Match on something the customer gives you. An order number, an email address, a booking reference – any of those lets you join the records yourself, and a webhook lookup can pull the matching history into the conversation.<\/p>\n\n\n\n That is matching you perform, deliberately, on data you were given. It is not the platform resolving identity, and it only works where the customer volunteers the key.<\/p>\n\n\n\n Practically: ask for the order number early in support flows, because it is the join key as well as the lookup key. And do not promise customers that you will remember a conversation they had on a different channel, because you will not reliably.<\/p>\n\n\n\n The order-status pattern in the order-status lookup<\/a> is the same mechanism doing double duty.<\/p>\n\n\n\n Each one surprises somebody during implementation.<\/p>\n\n\n\n AI replies work on Instagram, TikTok, Telegram and Discord, and not on WhatsApp or Messenger. Product cards work on WhatsApp, and not on TikTok. LinkedIn offers comment triggers and no DM sending at all. Rich sends – locations, contact cards, stickers, invoices – differ channel by channel.<\/p>\n\n\n\n A flow built once therefore does not behave identically everywhere, and a unified inbox does not change that. What it changes is that you can see it happening in one place.<\/p>\n\n\n\n Twenty-four hours from the customer’s last message on Meta inboxes, resetting each time they write. Seven days for a private reply to a public comment. Forty-eight hours on TikTok, with a cap of ten consecutive outbound messages.<\/p>\n\n\n\n Which means \u201creply within 24 hours\u201d is not a single policy you can apply across the inbox – it is the strictest common denominator, and treating it as universal wastes the seven-day window where you have it.<\/p>\n\n\n\n There is no single meter. WhatsApp’s thousand free monthly service messages are per business phone number and have no equivalent on the other channels, which have their own arrangements.<\/p>\n\n\n\n So a per-conversation cost across a unified inbox is an average of unlike things. Model each channel separately – the method is in the cost arithmetic<\/a>.<\/p>\n\n\n\n Worth having on a wall during implementation, because every one of these catches somebody out.<\/p>\n\n\n\nOne Ownership Model<\/h3>\n\n\n\n
One Set of Numbers<\/h3>\n\n\n\n
The Identity Problem<\/h2>\n\n\n\n
Two Contacts, One Human<\/h3>\n\n\n\n
What You Can Do Instead<\/h3>\n\n\n\n
Design Around It<\/h3>\n\n\n\n
Three More Things That Do Not Unify<\/h2>\n\n\n\n
Capabilities<\/h3>\n\n\n\n
Windows<\/h3>\n\n\n\n
Cost<\/h3>\n\n\n\n
What Survives Unification, by Channel<\/h2>\n\n\n\n