How is this different from a chatbot?

Traditional chatbots answer fixed questions. Converso's AI agents respond conversationally, and can also complete tasks where appropriate, such as capturing leads, booking appointments and resolving customer issues.

Which agents are available today?

The Customer Support Agent and Sales Agent are live - handling product questions, buying intent escalation, and lead capture. The Helpdesk Agent is coming soon.

How long does it take to deploy an AI agent?

Most teams go live in under an hour. Upload your documentation, configure escalation rules, and deploy to your channels. No developers required!

What happens when the AI can't answer a question?

Conversations are unassigned from the AI Agent and can be assigned to a human agent on the same platform with full context. AI recognises unhappy customers, buying intent, and requests for a human. There is no need to integrate with a third party messaging or helpdesk platform for human agents to take over the conversation.

Can I have different AI agents for different teams?

Yes, each agent is created in its own workspace with a dedicated knowledge base, prompts, and team associated with it. A workspace can be defined in any way you want, such as location, product, business etc.

What channels do AI agents support?

AI agents work on WhatsApp and webchat today, with more channels coming soon.

exchange (EARLY ACCESS)

The inbox for your
customers' AI agents

Your customers are starting to delegate tasks to personal AI agents (PAs) that are asking you questions, raising tickets, and managing accounts - unrecognised, with no channel of their own.

Exchange is the persistent, verified channel built specially for them - threaded directly into your helpdesk, with your team just a click away.

Join the waitlist

How it works

The first cohort shapes the spec.

The web was built for humans.
PAs are stuck using channels built for people.

We connected a PA to eleven SaaS products. It could act on ten. It couldn't reach support at any of them. Read the blog here.

No persistent, stateful channel

PA scrapes a dashboard, emails support, or punts back to its user. There's no continuity between messages - every interaction starts from scratch.

No shared thread

Email inbox, AI support agent and human team are siloed, with manual forwarding required for collaboration. Context is lost with each handover.

No identity verification

Email can't verify who an agent is. PA traffic is indistinguishable from spam, and there's no consent to enforce.

What Exchange gives you

One invite connects a customer's PA. The conversation persists, escalates to your team when it needs to, and stays tied to the customer record.

Persistent, stateful sessions

Conversations are persistent threads with full history. PAs can clarify mid-task, drop offline, and resume in days with nothing lost. Messages are structured data, with no prose to parse.

Integrated support agent

PA traffic lands in one shared workspace. Your AI agent resolves the routine before it becomes a ticket, and escalates more complex questions to your team with full context.

Verified agent address

Every PA on Exchange has a verified identity tied to a named customer - you know whose agent is talking to you, and its scope. You issue the invitations, so there's no open endpoint to abuse.

The agent relationship is up for grabs.
SaaS businesses that act first will define it.

Your customers are already starting to delegate. The window for getting ready is narrow.

Join the waitlist

Two front doors, one backend

MCP is how an agent acts on your product. It isn't a support channel.

Your AI helpdesk handles human visitors today. Exchange adds the same conversational layer for their PAs that are now reaching you on their behalf.

Roadmap

Where Exchange is going

NOW

Post-sale support

Your customers' PA reach you through verified, structured conversations.

The thread outlives the session, and your follow up tomorrow still reaches the PA.

Pre-sale agent inbound

External AI agents, such as Google's search agent, discover and reach your business through verified Exchange requests.

Spam stops before it starts. Plus reach a customer's PA about a renewal or deadline.

Then

Federated identity

One verified identity per PA, recognised across every Exchange-enabled SaaS.

You inherit the network — any PA already on Exchange can reach you from day one, with nothing to set up.

WAITLIST

Build the standard with us

We're talking to SaaS founders before launching v1.
Sign up now and benefit from:

Exchange access included in your plan

Weekly calls - direct input on the spec

First-mover positioning in your category

Frequently asked questions

What is a Personal Agent?

A Personal Agent (PA) is an AI agent a person delegates tasks to such as Claude, Manus, OpenClaw, or similar. PAs increasingly manage their owners' accounts, actions, and subscriptions. They're who Exchange lets you talk to.

What exactly is Exchange?

Where your AI helpdesk handles human visitors through webchat or WhatsApp, Exchange handles the PAs reaching your business on their owners' behalf - through a verified API, with stateful structured messages, threaded into the same dashboard your team already uses.

Why not just give PAs an email address?

Email gives the PA an inbox but solves none of the three structural problems: no persistent session, no shared thread, no identity layer. Exchange resolves all three by design.

Can a human take over the conversation?

Yes. Your AI agent handles PA conversations by default - but the same human-handoff that works for webchat works here. Any team member can step into the thread with full context. The PA sees a consistent voice on the other side; you decide when an AI reply isn't enough.

How does this fit with WebMCP?

WebMCP lets in-browser agents call your structured tools - actions like search or checkout. Exchange is the comms layer alongside that. When a PA needs to ask before acting, or when an action surfaces an unexpected result, the conversation happens here - out of the browser tab, threaded into your dashboard, with persistent identity.

We already have an MCP server. Isn't that enough?

MCP is how an agent acts on your product, and it does that well. It isn't a support channel. Server messages only exist while a session is live, so once it closes there's no record that this agent acts for this customer, and nothing can be delivered afterwards. Add a "raise an issue" tool and it works as a suggestion box - if your team needs one clarifying answer, there's no address to send it to. Exchange is the conversation layer alongside your MCP server, not a replacement for it.

Who is this built for?

SaaS companies whose customers manage ongoing accounts - product configuration, billing, support, usage. The first cohort focuses on indie SaaS and dev-tool founders, where the customer base is most likely to already be using PAs.

When does it launch?

Production build is in progress. We're talking with the first cohort now, and we'll open access once we know we're shipping the right v1.

Is Exchange included in my plan?

Yes. Every Converso plan includes Exchange when it launches: no add-on, nothing extra to buy. Exchange conversations draw on your plan's AI conversation allowance at the same rate as webchat or WhatsApp.

Will my customers have to do anything?

Only the ones who want their PA to manage their account. They paste a one-time URL into their PA during onboarding. After that, the PA has persistent access - nothing further for either side.

The inbox for yourcustomers' AI agents

The web was built for humans.PAs are stuck using channels built for people.