Unified Inbox — Why the Seat You Add Costs More Than the Seat You Bought

Quick answer: A unified inbox is the shared screen where humans handle whatever the bot could not. Every vendor demos it, ten of our fifteen reviews document one, and buyers almost never ask the question that decides the bill: what does it cost to put a fourth person in it? Only four of the fifteen attach a dollar figure to a single seat in their own materials: Intercom, Wati, AiSensy and BotPenguin. Where a seat has a published price, the fourth agent is cheap or free. It costs nothing at all on Tidio, BotPenguin and AiSensy, and $29 on Intercom, the platform in this set most often described as the pricey option. Where the seat has no published price it is buried in a tier step, and the same person costs $100 on Manychat, $350 on Chatbase and at least €300 on Landbot. Wati sits in both camps and is the reason the rule needs stating carefully: it publishes $24 and $69 per additional user on its two upper tiers, and its entry tier is hard-capped at three with no add-on path at all, so the fourth person there costs an $80 tier jump before any per-user rate applies.

What it actually is, which takes one paragraph

An inbox becomes unified when a message that arrived on Instagram and a message that arrived on your website sit in the same list, assignable to the same person, with one set of notes and one status model. That is genuinely useful and it is not hard engineering. What it is not is channel unification. Reply to a WhatsApp thread from a unified inbox and the reply travels through the WhatsApp Business Platform with all of that platform's template rules and session windows intact. Our Wati review puts the point more sharply than most vendors would like, describing the omnichannel inbox there as unifying five channels "at the UI layer — not first-class native automation depth across all five." Read every vendor's inbox claim that way and you will be right more often than not.

The inbox is also where a chatbot project stops being a bot project. It is the destination of every human handoff, the place your handoff rules deliver to, and the surface where average handle time is actually spent. A bot with no inbox behind it is a deflection device with nowhere to deflect to.

What our fifteen reviews record

Fifteen files match sample-reviews/*-review.md. Searching them for the literal phrases gives three different answers, and the differences are the interesting part:

The union of the first three is smaller than you would guess and the last figure is misleading, which is why phrase counting is not the method here. Reading all fourteen matches, ten of the fifteen document a shared multi-agent inbox as a product feature: AiSensy, Blip, BotPenguin, Chatfuel, Intercom, Landbot, Manychat, SendPulse, Tidio and Wati. Landbot never uses any of the three phrases and still belongs on the list: the review documents the Inbox surface first-hand on a fourteen-day trial of Pro-tier features, which the review is careful to distinguish from full paid Pro, with Chats, Channels and Team tabs visible and a live Messenger conversation routed through it. Note what that does and does not establish. One channel was exercised, not three, and the review's own three-channel sentence is a statement about which buyers the surface suits rather than a record of what was tested.

Four do not belong on it, and the reasons are worth stating because each is a way an inbox count goes wrong:

• Tars contains the word "inbox" zero times. Nothing to interpret.
• Typebot mentions an inbox only as a thing it lacks, noting that handover flows out to Zendesk, Intercom, Slack or a webhook.
• Chatbase matches on "inbox" exactly twice, on two lines. The first is Chatbase's own Help desk beta, which the review records as visible but unpressed on the tested account, with validation scheduled for a later cycle. The second is a handover into a Zendesk inbox through a native integration, and the "Multi-user inbox UX: 4/5" score on that same line is therefore a score for the Zendesk destination; reading it as a Chatbase inbox score is an inference the file does not support. Neither line documents a shipped, tested Chatbase inbox.
• Voiceflow uses the word twice, both on the same line, inside a single handover-scenario description: it asserts "a Voiceflow inbox" exists and adds that routing rules are configurable per team. That is one sentence and no feature documentation, and we are not publishing it as one.

Botpress is the honest borderline case. It ships Botpress Desk, a helpdesk product with a conventional three-pane inbox, but the review documents only one channel feeding it, Webchat, so it fails the "unified" half of the test while passing the "shared" half. Count it and the figure is eleven; we count it out and say so.

The seat-step ratio, which is the number to ask for

Here is the part nobody demos. A unified inbox is priced in one of two shapes, and the shape matters far more than the sticker.

Linear. You pay a stated amount per seat. Our Intercom review records Essential at $29/seat, Advanced at $85/seat and Expert at $132/seat, monthly-billed, with no annual discount recorded. Four people cost four times one person. Nothing surprises you.

Stepped. The tier price includes N seats. Seat N+1 is not for sale. You buy the next tier, and the next tier is priced for its capacity, not for your one extra human.

To compare the two, divide the cost of the seat that forces the upgrade by the cost per seat you were already paying. Call it the seat-step ratio. On a linear plan it is 1.00 by construction. Every figure below comes from the review named, and the arithmetic is one division:

* AiSensy's $45 is the rate on its USD pricing page. Its default INR page prices the same Basic tier at ₹1,500, which our review puts at roughly $17.86 at market FX, a 2.5x spread. On the INR page the cost per included seat falls to about $2.98, which brings AiSensy to within eight cents of Tidio's $2.90 rather than past it: $17.86 ÷ 6 = $2.977, and $29 ÷ 10 = $2.90. Tidio still has the cheapest included seat in the table, by a margin small enough that it disappears the moment either vendor moves a price. Which currency page you land on is not a detail.

Median ratio across the five stepped platforms: 3.48. The seat that breaks your tier costs roughly three and a half times the seat you thought you were buying, and on two platforms it costs seven to nine times.

Four things about that table are load-bearing and all four cut against it:

1. The step buys other things. Chatbase Pro adds 11,000 message credits and four more AI agents on top of the two extra seats. Manychat Advanced adds 17,500 active contacts. The ratio therefore measures what the seat costs you, not what the vendor thinks a seat is worth. That is a buyer-side number by design, because you cannot buy the seat on its own, which is the entire point.
2. Landbot's Business tier is quoted "From €400/mo". A floor, not a price. The 9.00 is a lower bound and the real figure is higher. Landbot also bills in EUR with no currency switcher, so a US buyer takes FX on top.
3. Wati's Growth tier is the strictest case in the set and the one most likely to catch a small team: three users, hard-capped, with no per-user add-on path at all. There is no amount of money that puts a fourth person on Growth. Above the cap Wati does publish per-user rates, $24/user/month on Pro and $69/user/month on Business, so the platform is stepped once and then linear.
4. Three platforms record nothing, and one records an absence. SendPulse, Tars and Voiceflow document no seat count, no cap and no per-seat price; SendPulse gates its teamwork tools to the Pro tier and stops there. Absence of a recorded limit is not evidence of no limit, and this is the first question to put to those three in a sales call. Chatfuel is the different case and the fifteenth platform: its pricing page affirmatively states that there are no team member seat limits, which is the best possible answer to the question this entry asks and comes with its own unknown, since the role permissions behind those unlimited seats are undocumented.

Two of the four seat-price publishers put their figure in an add-on line rather than in a headline rate, which is why they are easy to miss: AiSensy charges $20/mo per agent beyond the five free, and BotPenguin $7/month per team member beyond the tier limit. BotPenguin's is the cheapest marginal human anywhere in our corpus. Neither shows up in a pricing-page comparison that reads only the tier row.

The finding, stated plainly

The reputational ranking and the marginal-cost ranking are close to inverted. Intercom publishes a per-seat price, is routinely called the expensive one, and sells the cheapest fourth seat of any platform in this corpus that charges for one. Four Intercom Essential seats come to $116/month. Four Chatbase seats come to $500/month, and Chatbase never prints a seat price anywhere. The two products are not substitutes and we are not pretending otherwise; the comparison is about pricing shape, not about fit. But a buyer comparing $29 against $150 on a pricing page is comparing the wrong pair of numbers, and every stepped vendor in the table benefits from that.

Ask for the ratio. "What does my fourth agent cost, in dollars, this month" is a question with one right answer, and a vendor who cannot give it in a sentence has told you the answer is a tier.

Related terms

• Chatbot channel strategy — deciding which channels feed the queue in the first place, which is the decision upstream of this one.
• Live chat — the human-staffed channel a unified inbox exists to run.
• Human handoff — the moment a conversation becomes a seat's problem.
• Chatbot handoff rules — what decides which seat, and when.
• Canned response — the main reason a seat handles more conversations than it looks like it should.
• Average handle time — the metric that tells you whether you needed the fourth seat at all.

FAQ

What is a unified inbox?

One screen where a team handles conversations that arrived on different channels. A message from your website widget, one from WhatsApp and one from Instagram appear in the same assignable queue with their own thread histories, so an agent works in a single place. The unification is at the interface layer. Outbound replies still travel through each channel's own rules, which is why a WhatsApp reply from a unified inbox is still bound by WhatsApp's template and session-window requirements.

Is a unified inbox the same as a shared inbox or a team inbox?

In vendor marketing, close enough to treat as synonyms, and our corpus uses all three for the same feature. If you want the distinction: "shared" and "team" describe who can see the queue, and "unified" describes how many channels feed it. A single-channel shared inbox is a real and common product. Our AiSensy review documents exactly that, calling it a unified inbox while recording WhatsApp as the only channel in it.

What does an extra agent seat cost?

It depends on which of two shapes your vendor uses, and the gap is large. Where a per-seat price is published, our corpus records $29, $85 and $132 per seat on Intercom, $24 and $69 per additional user on Wati above its included five, $20 per additional agent on AiSensy above its free five, and $7 per additional team member on BotPenguin. Where no seat price is published, the extra person costs a tier upgrade: $100 on Manychat, $80 on Wati at the Growth cap, $350 on Chatbase, at least €300 on Landbot.

Which platforms include enough seats that I never hit the cap?

On the figures our reviews record, Tidio is the outlier, listing 10 seats on Free, Starter and Growth alike. BotPenguin's Little tier at $29/mo includes five team members and its Emperor tier is unlimited. AiSensy gives one owner plus five free agents on every published paid tier, its Free Forever row recording only "Multi-agent" without a number. Chatfuel's pricing page goes further and states no team member seat limits at all, though its role permissions are undocumented, which is a different kind of unknown.

Do I need a unified inbox if I have a chatbot?

You need one as soon as a human has to finish a conversation the bot started, on more than one channel, with more than one person answering. Below that threshold an email address works. The honest sequence is to size the inbox after you know your escalation rate, not before, which is the argument in our escalation playbook.

Why do vendors hide seat pricing inside tiers?

Because a stepped tier makes the marginal human invisible at the point of purchase and expensive afterwards, and because tiers bundle seats with capacity a buyer is also growing into. There is nothing improper about it. The remedy is arithmetic, not indignation: divide the upgrade cost by the seats you already have, and compare that number across vendors rather than comparing entry prices.

Sources

• Chatbotscape review corpus, searched and read 28 August 2026. Denominator: ls sample-reviews/*-review.md | wc -l returns 15. The four phrase searches printed in the body were executed verbatim from the repository root and return 6, 1, 4 and 14 respectively. Every price, seat count and cap in this entry is quoted from the review that recorded it; each was checked against the source line before publication. The reviews state their own verification dates, which range from May to August 2026, and this entry did not re-verify them against vendor pricing pages.
• Per-seat and per-user figures: sample-reviews/intercom-review.md ($29/$85/$132 per seat, and the note that no annual discount is applied); sample-reviews/wati-review.md (Growth 3 users hard-capped with no add-on path, Pro $24/user/month, Business $69/user/month); sample-reviews/aisensy-review.md (1 owner plus 5 free agents, $20/mo per additional agent); sample-reviews/botpenguin-review.md ($7/month per additional team member beyond 5 or 10).
• Stepped-tier figures: sample-reviews/chatbase-review.md (Free 1 seat, Hobby $40 / 2, Standard $150 / 3, Pro $500 / 5, monthly-billed); sample-reviews/manychat-review.md (inbox seats 1/1/2/3/5 against Free/$17/$39/$99/$199, and the separate "Users" column at 1/2/3/5/10 which is not the same limit); sample-reviews/tidio-review.md (10 seats on Free, Starter $29 and Growth $59); sample-reviews/landbot-review.md (Sandbox 1, Starter €40 / 2, Pro €100 / 3, Business from €400 / 5, EUR-denominated); sample-reviews/typebot-review.md (Personal 1, Starter $39 / 2, Pro $89 / 5, and no annual billing offered).
• Blip is excluded from the ratio table on evidence quality, not on price. sample-reviews/blip-review.md records "$500/user/month" but sources it to a third-party Capterra listing built from vendor questionnaire responses rather than to a Blip pricing page, and the same file states the figure "may differ by ±30-50%". A number with that error bar does not belong in an arithmetic comparison.
• Corpus defects flagged for the manual editorial track and not corrected in this run: the three incompatible Botpress Plus prices ($189, $89, "$150-189") inside sample-reviews/botpress-review.md; the five-versus-seven channel discrepancy in sample-reviews/manychat-review.md; and a cross-review inconsistency in which three other reviews price Wati's Growth tier in euros (€69) while the Wati review itself prices it in dollars ($69).
• Ahrefs Keywords Explorer, US overview and volume-by-country, queried 28 August 2026 — the demand, difficulty, CPC, global-volume and country-split figures in this entry's keyword note, including the checks behind declining 'pms integration', 'property management system', 'channel manager' and 'booking engine'.
• Chatbotscape pricing methodology, including the monthly-billed rule applied to every figure above. /methodology (continuously updated).