2pm.spaceOne AI inbox for every
conversation you sell in
Messenger, Telegram, your website chat and personal Zalo 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.
Four channels, one queue
Where your customers already write to you — each with what it does that the others do not.
Messenger
Direct messages and Page comments
- Every Page you connect, in one queue
- Post comments answered in public or by private reply
- Ad-referral and product cards shown in the thread
- Existing history backfilled when the Page is added
Telegram
Your bot, private chats and groups
- Your own bot, answered by the agent you choose
- Group chats with every member kept as their own speaker
- Photos, files and voice notes — voice transcribed to text
Website Widget
A widget on your own site
- One script tag, locked to the domains you allow
- Your colours, greeting, launcher and quick replies
- Pre-chat form, eight languages, placement per device
Personal Zalo
Your own account, by QR code
- Log in with a QR code — no Official Account needed
- One-to-one and group chats in the same queue
- Friend requests by phone number, from the thread
From the first message to the thank-you
A customer writes on any channel. The agent consults, takes the order, books the delivery and says thank you — and when the conversation turns, it knows which way to go.
Customers chat
- Messenger“Is the blue one still in stock?”
- Telegram“Do you ship to Da Nang?”
- Website Widget“How much for two of these?”
- Personal Zalo“Can I pay on delivery?”
2pm AI consults
One agent behind every channel, drawing on everything your workspace knows.
Process
Confirms the items, the phone number and the delivery address back with the customer.
address savedCreate the order
A draft order in your shop's ERP, priced from its catalogue — your team confirms it there.
SAL-ORD-2026-00213Book the COD shipment
Booked with Viettel Post with the amount to collect on delivery, or by your ERP with your own carrier.
COD · tracking codeSay thank you
When the delivery is reported, an event rule sends a thank-you — written from the thread, or from your template.
delivered → thanked
Along the way
Friend them on Zalo
The number is pinned to the contact and your personal Zalo sends a friend request — paced, between 8 a.m. and 8 p.m. When they accept, the Zalo chat joins the same customer.
+84 ••• 412 → ZaloCare follows up
A care agent reads the thread and follows up after the silence you set — inside your quiet hours, capped per person, and within the channel’s messaging window.
quiet 2h → follow-upYour team steps in
The agent sends your team a push alert that opens the thread. Anyone can reply there — or pause AI to keep the thread for themselves.
alert → AI pausedThe agent stops replying
It switches AI and care off for that thread and leaves your team a one-line reason. Anyone can switch it back on from the inbox.
AI off · reason notedFrom 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 and give it the documents and tools it needs. It replies on its own once a customer's burst of messages ends — you set how long it waits, which tagged conversations it leaves to your team, and a sandbox mode that keeps its replies in-app while you test.
Watch, step in, improve
Every reply keeps its run — the tool calls and the cost — behind the execution log. Pause AI on the threads that need a person, and rate or improve a reply: the correction improves the agent now and trains it later.
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 and give it the documents and tools it needs. It replies on its own once a customer's burst of messages ends — you set how long it waits, which tagged conversations it leaves to your team, and a sandbox mode that keeps its replies in-app while you test.
Watch, step in, improve
Every reply keeps its run — the tool calls and the cost — behind the execution log. Pause AI on the threads that need a person, and rate or improve a reply: the correction improves the agent now and trains it later.
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 reply mid-conversation — same thread, same history — and their reply cancels the answer the agent was still writing, without switching it off. Pause AI hands a thread to your team until someone enables it again. Where a person has to decide, the agent leaves it to one: an order it takes waits as a draft in your shop's ERP for your team to submit, and it can send your team a push alert that opens the thread.
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
- Personal Zalo, logged in by QR code
- Zalo Official Account — coming soon
- Telegram bots
- Pancake accounts
Your own surfaces
- Website 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, shown against the message they answer
- 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
- Orders the agent takes held as drafts until staff submit them
- Guardrails on what an agent may say
- Block a contact from the 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
- Channel merge, folding one account’s history into another
- Outbound webhook delivery log
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), Telegram, personal Zalo logged in by QR code, Pancake, and a chat widget you embed on your own website, with Zalo Official Account coming soon. 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. The agent answers each new message on its own, once the customer's burst of messages ends, and your team can reply in the same thread at any time — a teammate's reply cancels the answer the agent was still writing, and the AI stays on. Pause AI hands a thread to your team (it also pauses care follow-ups there) until someone enables it again, and conversations carrying a tag you pick can be left to your team entirely. There is no approval step mid-conversation; for orders, the checkpoint is the order itself — the agent creates a draft in your shop's ERP and your team submits it there.
Yes. Conversations are linked on a shared phone number or email, so someone who comments on a Facebook post and later messages you on Zalo is shown 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.