Connect your channels and your data.
An agent is useless if it cannot see your stock and does not speak where your customers write. Here is what it connects to, and the documentation for each.
Channels
Where your customers write.
Answer on the channel your customers already use, with a business number and the history kept.
See the channel
Direct messages and story replies, handled as conversations rather than notifications.
See the channel
Messenger
Your Facebook page wired to the same agent, with the same context as every other channel.
See the channel
Web agent
A widget on your site, one line of script, answering from your catalog and your opening hours.
See the channel
The shared inbox joins the same thread, so nothing is lost between chat and email.
See the channelData sources
What the agent reads to answer correctly.
Airtable
Catalog, stock or pricing read live from your base, with no export step.
Documentation
NocoDB
The same, on a self-hosted base, for when the data has to stay with you.
Documentation
API REST
Your own endpoint: the agent sends the customer query and reads the JSON back.
Documentation
File
A dropped CSV or spreadsheet, to get started without wiring anything up.
DocumentationBefore you pick a channel
Do we have to connect everything at once?
No, and it usually works better the other way: one channel first, whichever carries the most messages, and the rest once that one is running. The agent is the same everywhere, so what you tune on the first applies to the others.
If a customer writes on two channels, is that two conversations?
No. The channels land in the same inbox, and a customer who emails on Monday and messages on Thursday is one conversation, so nobody asks them to explain it twice.
What happens if a data source goes down?
The agent does not guess. What it cannot read, it does not assert: it says so and hands over, which is the behaviour that keeps the other answers trustworthy.
What if the connector we need does not exist?
The REST API covers most cases: you expose an endpoint, the agent sends the customer query and reads the response. For anything else, tell us which one is missing.
Missing a connector?
Tell us which one. The REST API already covers most cases, and the rest is a conversation.
Write to us →