Draw the conversation once: what it asks, what it looks up, which of your systems it calls, and where it hands over. Deploy it to every channel. The inbox your team answers from is included, seats and all.
Most conversations never reach your team. The ones that do arrive ready to answer.
The flow answers, the inbox catches what it hands over, and the drafts help your team finish. One loop, one knowledge base, one price.
UniversalFlow
Design the conversation
Lay out what it asks, what it answers and where it branches, in a visual editor. Intent steps read what someone meant, API steps call your systems, conditions route on the answer. One flow deploys to every channel at once.
UniversalInbox
Hand over cleanly
When the flow reaches the end of what it can do, it pauses and passes the thread to a shared queue. One person owns it, everyone can see it.
SupportBuddy
Answer with help
The reply is drafted before your team starts typing, pulled from your knowledge base.
Conversations that earn, not just conversations that cost.
Capture
A visitor asks about pricing at 2am. The flow answers, qualifies budget and timeline, books the call, and keeps the contact in a table of your own or writes it to your CRM. Someone who comes back next week does not start from zero.
Onboard
A new account signs up and gets walked through setup on WhatsApp, one step at a time, with your docs quoted where they get stuck.
Answer
Routine questions are resolved from your own documentation, and from the lists you keep for it to read: today's prices, what is on the menu, when you are open. Anything unusual goes to a person with the thread attached.
Self-service
A customer wants a balance, an order status, or to change a detail. The flow checks who they are, calls your system, and finishes it in the conversation.
Every channel lands in one inbox.
Your team stops switching between WhatsApp, Messenger, Instagram, Intercom and Telegram. One queue, one thread per customer, and everything the flow already said is right there.
One person owns it
Claiming a conversation takes it off everyone else's queue, so nothing gets answered twice. Reassign it when someone else should pick it up.
The flow steps aside
The moment an agent replies, the flow pauses. Put it back in charge when the conversation is routine again.
One customer, not four
The same person on WhatsApp and Intercom is one contact with one history, however many channels they use to reach you.
The reply is already written
Turn SupportBuddy on and every conversation opens with a draft pulled from your knowledge base. Your agent edits and sends.
AI is a choice, not a default.
Your flow does what you drew it to do. Switch AI on for the steps where it pays for itself, and leave it off everywhere else.
Every path is one you drew
Open the flow and read exactly what a customer will be asked and told. Nothing improvises its way into a promise you can't keep.
AI is a node, not a mode
Understanding what someone meant, answering from your docs, drafting a reply for an agent. Each one is a step you add where you want it.
Its own line on the bill
AI spend is separate from the platform, visible as it accrues, and zero on any flow that doesn't use it.
Already on Intercom? Keep it.
Intercom is just another channel. Your flows run there the same way they run on WhatsApp or your website, so nothing moves and nothing gets migrated.
Nothing to migrate.
Conversations stay in Intercom, and your team keeps the inbox they know.
One design, every channel.
The same flow you built for the website answers in Intercom.
Drafts without leaving Intercom.
The same suggestions your agents would get in UniversalInbox, delivered by a Chrome extension inside the Intercom inbox.
Intercom, with the SupportBuddy extension installed
Every answer comes from one place.
Everything your team knows sits in one knowledge base. Flows answer from it during a conversation, SupportBuddy drafts from it in the inbox, and your customers can read part of it themselves.
Everything in one place
Pages your team writes, PDFs, web pages and plain text. Whatever you add is indexed and searchable as soon as it lands.
Scoped into collections
Group sources by product, region or audience, then point each flow and each buddy at the collection it should be answering from.
One copy, everywhere
The bot, the inbox and your help centre read the same source, so an answer does not drift depending on where a customer asked.
Public when you want it
A wiki can go public as a help centre with its own categories, search and sitemap, or stay unlisted and reachable only by link. Uploaded sources stay internal either way.
Priced for the automation, not the people.
The plan pays for the conversations your flows handle and the AI they use. The inbox and seats for your team are in it, and you can watch every meter as it climbs.
Conversations
Counted when a customer actually talks to you, not per message. Each plan includes a monthly amount and bills past it at a per-conversation rate.
AI usage
Passed through at cost, on its own line, alerted as it climbs. Zero on any flow that does not use it.
Seats, included
Every plan comes with seats for the people who reply. One more is a flat, low monthly price, the same on every paid plan.
See full pricingDon't want to build your flows? We'll build them with you, as a paid add-on.
Tell us what you want to automate.
Four questions, ninety seconds. You'll be using the same kind of flow you'd be deploying, and we'll bring what you told us to the call.
