One AI inbox for every
conversation you sell in
Messenger, Facebook comments, Zalo, Telegram and your website chat land in a single shared queue — answered by an AI agent that knows your products, remembers the customer, and steps aside the moment your team wants the thread.
From a connected Page to a working agent
Three steps, and the first conversation is answered the same day.
Connect a channel
Link a Facebook Page, a Zalo account, a Telegram bot or the website widget. Existing history is backfilled, so the inbox opens with the conversations you already have rather than an empty list.
Put an agent behind it
Choose which agent answers on which channel, give it the documents and tools it needs, and decide whether it replies always, only after hours, or not until a human asks it to draft.
Watch, take over, improve
Every run is logged with its tool calls and cost. Take over the threads that need a person, turn the good replies into quick replies, and feed the rest back into the agent as skills and memory.
Connect a channel
Link a Facebook Page, a Zalo account, a Telegram bot or the website widget. Existing history is backfilled, so the inbox opens with the conversations you already have rather than an empty list.
Put an agent behind it
Choose which agent answers on which channel, give it the documents and tools it needs, and decide whether it replies always, only after hours, or not until a human asks it to draft.
Watch, take over, improve
Every run is logged with its tool calls and cost. Take over the threads that need a person, turn the good replies into quick replies, and feed the rest back into the agent as skills and memory.
Built for teams who actually work the inbox
Not a chatbot bolted to a Page — a shared queue your team and your agents work together.
An agent on the front line
Point one of your agents at a channel and it answers in your voice, using your product catalogue, your documents and everything it remembers about that customer. It has your tools too, so it can look an order up rather than apologise for not knowing.
Handover that is not a fight
Any teammate can take a thread out of the agent mid-conversation and keep typing — same thread, same history, no copy-paste. Agents can also be told to pause and ask a human before acting, so the risky step waits for a person instead of guessing.
One customer, not five threads
Contacts are matched across channels, so the Facebook comment, the Messenger reply and the Zalo message are one person with one history — with their phone numbers, tags and attributes attached.
See the Customer 360 profilePhone numbers, caught and kept
Numbers customers type mid-conversation are detected, deduplicated against the ones you already hold, and pinned to the contact — with the noise (staff numbers, numbers in a forwarded quote) curated out rather than counted.
Care follow-ups that read the thread
Conversations that go quiet get followed up by an agent that has read the history — inside the quiet hours you set, capped at how often one person may be contacted, and never as an identical blast.
Numbers you can act on
Volume, response times, and per-channel breakdowns, precomputed by the hour so the dashboard opens instantly instead of scanning a year of messages every time someone changes the date range.
What it connects to, and what it handles
The list a reader arrives looking for, before deciding whether this fits.
Messaging channels
- Facebook Messenger — direct messages
- Facebook comments, with private reply
- Zalo Official Account
- Personal Zalo, through the bridge
- Telegram bots
- Pancake accounts
Your own surfaces
- Website chat widget, embeddable on any page
- Custom API channel — webhook in, webhook out
- Outbound webhooks on inbox events
- Mobile app for iOS and Android
- Deep links straight to a conversation
What a message can carry
- Photos and albums, files, stickers
- Voice notes, transcribed to searchable text
- Locations, polls, product and ad-referral cards
- Quoted replies and message reactions
- Group chats with per-speaker identity
Working the queue
- Full-text search with the matching snippet
- Filters by channel, tag, type and awaiting-reply
- Quick replies your whole team shares
- Tags, labels and custom attributes
- Conversation summaries on the contact panel
Control
- Channel access per member, role or team
- Human approval gates on sensitive actions
- Guardrails on what an agent may say
- Block a contact, or mute a thread
- Full execution log per reply, with cost
Keeping up
- Backfill of history when a channel is added
- Hourly statistics rollups per channel
- Care follow-ups with quiet hours and caps
- Contact merge across channels
- Publish log and delivery retries
What changes on day one
The difference between a bot on a Page and an inbox your team runs.
A tab per Page, a phone for Zalo, and a spreadsheet to remember who said what
Every channel in one queue, with one history per customer
A bot that answers from a script and hands over the moment it is asked anything real
An agent with your documents, your catalogue and your tools — and a human one click away
Phone numbers scrolled past, retyped by hand, or lost when the thread gets long
Numbers detected, deduplicated and pinned to the contact automatically
Follow-ups that go out as an identical blast, at whatever hour the schedule fires
Care messages written from the thread, inside your quiet hours, capped per person
Voice notes nobody plays and images nobody sees, because the bot only reads text
Voice transcribed, images understood, and everything searchable
Giving a contractor inbox access means giving them the whole workspace
Channel-level access per member, role or team
Questions about the AI inbox
What teams ask before they point their first Page at an agent.
Facebook Messenger (including comments on your Page posts), Zalo Official Account, personal Zalo through the bridge, Telegram, Pancake, and a chat widget you embed on your own website. Anything else connects through the Custom API channel, which is a plain webhook in and a plain webhook out — no new code on our side.
Both, and you choose per channel. An agent can answer every conversation, answer only outside working hours, or stay off entirely while your team works the inbox by hand. A human can take over mid-thread at any point, and an agent can be configured to stop and ask for approval before it does something sensitive.
Yes. Contacts are matched across channels, so someone who comments on a Facebook post and later messages you on Zalo shows up as one customer with one history — including phone numbers detected in the conversation, custom attributes your team fills in, and any profile data pulled from your own systems.
They are stored with the conversation and shown inline — photos, albums, stickers, files, locations, polls and product cards all render as themselves rather than as a broken link. Voice messages are transcribed automatically, so a voice note is searchable text your agent can actually read and answer.
Yes. Channel access is assigned per member, per role, or per team, so an agency can give one client team access to one Page without exposing the rest of the workspace. Everything else in the workspace uses the same permission system.
Yes — that is what Care does. You set the trigger (a conversation idle for N hours, a tag, a filter), the quiet hours it must never send inside, and a cap on how many times one person can be contacted. The follow-up itself is written by an agent using the conversation history, not a fixed template blast.
Put an agent on your busiest channel
Connect a Page, pick an agent, and watch the first conversation get answered. Free to start, no credit card.