The platform

Three parts, one interface.

Build it once in Studio, serve it everywhere through Channels, and watch what actually happens in Rooms.

Convoy Studio bêta

Build your agentic interface.

Studio is where you decide what an AI is allowed to do with your product. You point it at what you already run, describe the jobs in plain language, and set the rules. No rebuild, no separate agent stack.

See what yours would look like

01ConnectPoint Studio at the API endpoints and data sources you already have. Your catalogue, your bookings, your records — read as they are, not copied somewhere else.

02ConfigurePackage what you exposed into skills and playbooks: the small jobs an agent can do, and the sequences it should follow to do them well.

03GovernSet the limits before anything goes live. What may be read, what may be changed, what needs a human. Every call is checked against them and written down.

Skills

Small, named jobs

One skill does one thing well: search the catalogue, check availability, create a booking. Named so an agent knows when to reach for it.

Playbooks

The order to do them in

Your way of handling a request, written down. Qualify before booking, check stock before promising, offer the alternative before saying no.

Guardrails

The lines it will not cross

Price caps, what stays private, what needs approval. Applied on every call, whoever is asking, without you being in the room.

Convoy Channels

Serve with AI, and serve AIs, everywhere.

Your customers arrive two ways. Some use the AI you give them, inside your own product. Others send the assistant they already use. Channels answers both from the one setup you built in Studio.

See the two directions

01Website CopilotYour site answers in plain language, with your live data and your guardrails behind every reply.

02Micro AI AppA chat-native app your customers can install. Yours end to end, no app store in the way.

03Custom IntegrationsThe same interface wherever you already talk to customers: WhatsApp, Slack, or anything else through the API.

04External assistantsChatGPT, Claude and Grok reach you through the connector each of them speaks. WebMCP when it lands.

One setup

Publish once

A change to a skill reaches every channel at the same time. No per-assistant version to keep in step.

Same rules

Everywhere alike

The guardrails you set in Studio hold on every surface, whether the request came from your own widget or someone else's assistant.

Your voice

Still yours

Answers carry your tone and your name, on channels you do not own as much as on the ones you do.

Convoy Rooms

Monitor what happens inside Rooms.

Every customer gets a Room: their own context, kept between visits, whether they signed in or not. A Room is where you see what was asked, what was served, and where a conversation stopped short.

See a Room in the dashboard

01One context per customerWhat they asked last time is still there this time, so nobody has to repeat themselves. Anonymous or signed in, the Room follows them.

02Events, not guessworkEach call becomes an event: which tool was reached for, what it returned, how long it took, whether a rule stopped it.

03Where intent stallsThe questions that got no useful answer are the most valuable thing in the Room. They tell you what to expose next.

Top tools

What agents reach for

The skills being called most, and the ones nobody touches. A ranking of what your customers actually want done.

Outcomes

What it delivered

Not just traffic. Which conversations ended in something happening, and which ones ran out of road.

Audit trail

Exportable, on request

Every decision traced with its context, ready the day someone asks you to show your working.