Channels and integrations
Connected to what you already run
Meet customers on the channels they already use, read the databases and files you already keep, and hand off into the tools your team already staffs.
Wherever the questiongets asked
A channel is where a conversation happens. One agent runs across all of them, and every conversation lands in the same shared inbox with its history intact, so a handoff to a person never starts from scratch.
Web widget
One script tag puts Relay on your site, isolated from your styles in a Shadow DOM. Three presentations to pick from, and an allowlist of the domains permitted to embed it.
Connect a WhatsApp Business number through the Meta Cloud API and Relay answers in the thread your customers already message. Live today.
Slack
Relay answers questions asked in a channel, in the thread. ChatPlotDB answers database questions from the same place, posting the table or chart back into the thread. Live today.
Telegram
Runs on a bot token, no app review and no approval queue, so a channel can be live the same afternoon. Live today.
Email, Messenger, and Instagram
Inbound support email and social DMs land in the same shared inbox as every other channel, with the same handoff to a person. In build.
Point it at the datayou already have
ChatPlotDB is database-agnostic. Register a SQL database, a DynamoDB source, or a spreadsheet, or compose several into one conversation and ask a question that spans them.
PostgreSQL and MySQL
Register a SQL database with the SSL mode your setup needs. Credentials are encrypted at rest and never handed back to the browser.
Amazon DynamoDB
Items are flattened into SQL-shaped tables, so a document store answers the same questions a relational one does.
CSV and Excel
Upload a spreadsheet and query it directly, no connection to register and no schema to model.
Several databases at once
A stitched config composes two to five databases into one conversation, so a single question can span all of them.
And into the rest of your stack
Relay learns from the tools your team already writes in, answers from your live commerce and billing data, and escalates into the helpdesk you already staff. WhatsApp, Slack, and Telegram are live today; the rest are in build.
Answers on the WhatsApp Business number your customers already message, right in the thread.
Slack
Answers inside your workspace, so questions get resolved without anyone leaving the channel.
Telegram
Runs on a bot token with no review and no approval queue, live the same afternoon.
Messenger & Instagram
Picks up Facebook Messenger and Instagram DMs alongside every other channel.
Turns inbound support email into conversations Relay can answer or escalate.
WordPress
Drops the widget onto a WordPress site with a plugin instead of a code change.
Shopify
Reads your store's catalogue so Relay answers product questions from live data.
Zendesk
Escalates into Zendesk as a ticket, with the whole conversation attached.
Connection FAQs
A channel is where a conversation happens: the web widget, WhatsApp, Slack, Telegram. An integration is a system the agent reads from or writes back to, like a database, a helpdesk, or a CRM.
Slack is both, which is why the two live on one page: Relay answers questions in a channel there, and it is also where escalations get posted.
The web widget, WhatsApp, Slack, and Telegram. Email, Facebook Messenger, and Instagram are in build.
We flag each one as it lands rather than listing everything as available: if a card here doesn't say live, it isn't yet.
Every conversation lands in one shared inbox regardless of the channel it arrived on, with its full history attached.
That history is what makes handoff work: when Relay isn't confident or the customer asks for a person, your team picks the thread up mid-conversation instead of asking them to start again.
PostgreSQL, MySQL, Amazon DynamoDB, and uploaded CSV or Excel files. A stitched config can compose two to five databases into one conversation, so a single question spans all of them.
Connection credentials are encrypted at rest and never returned to the client: the interface only shows a redacted summary.
Yes, three ways. Hand over an OpenAPI spec and the agent calls your own endpoints mid-conversation; connect any MCP-compliant tool for real-time data and actions; or fire a webhook on every conversation and drive whatever runs next yourself.
