Conversations

Work the inbox without leaving Claude.

The shared inbox and the sales board. The important sequence is take_over → send_reply → hand_to_ai: without the first call the AI will answer over the top of you.

Things you can just ask

Real prompts, not pseudo-code. Claude picks the tools itself.

“Show me every open conversation from the last 24 hours and summarise what each one wants.

“Read conversation X, draft a reply in our tone, and send it once I approve.

“Take over the thread where the customer is asking about a refund — I want to handle that one.

“Which conversations have been pending for more than two days?

“List this week’s signups with an email address and tell me which look like real buyers.

The 16 tools behind it

Tool	Needs	What it does
`list_conversations`	read	The shared inbox. Filter by bot, stage or channel.
`get_conversation`	read	Every message in order, plus the lead details captured on the thread.
`send_reply`	write	Reply as a human. Never metered and never counted against your plan.
`take_over`	write	Stop the AI on a thread so a person can answer.
`hand_to_ai`	write	Give the thread back; the AI resumes answering.
`set_conversation_status`	write	Move a thread between open, pending and closed.
`list_signups`	read	Captured leads — anyone who gave a name, email or phone to a bot.
`get_signup`	read	One lead in full.
`update_signup`	write	Edit a lead record or add a note.
`get_pipeline`	read	Your sales board — who is at which stage, what the open pipeline is worth, and whether the bot or a person moved them.
`list_opportunities`	read	Leads the AI let slip, found twice a day: why, what they said, what to do and a message ready to send.
`update_opportunity`	write	Mark a missed opportunity done or not worth it once the team has replied, called or made an offer.
`scan_opportunities`	write	Read the latest chats for missed opportunities right now instead of waiting for the next scheduled scan.
`move_contact`	write	Move someone to another stage or set what their deal is worth. Unlike the bot, you can move people backwards and close them.
`list_tags`	read	Your tags, how many people carry each, and which ones keep the AI quiet.
`tag_contact`	write	Tag the person in a chat, e.g. Client, or take the tag off. A tag can keep the AI quiet for them: no replies, no follow-ups.

read works with any key. write is refused unless the key allows it — the server checks before the tool runs, so a read-only key genuinely cannot change anything.

What it will not do

Worth knowing before you wire it into something that matters.

send_reply posts to a real customer. Have Claude draft first and approve before it sends.
Call take_over before replying, or the AI keeps answering and the customer gets two voices.
Deleting a conversation is not exposed over MCP at all — that stays in the console on purpose.

Also over MCP

Manage bots

Six tools cover the whole lifecycle of an agent: find it, read it, change it, and check the change before a customer sees it.

Add knowledge

The one that earns its keep is delete_knowledge: when a bot gives a wrong answer, the fix is almost always removing a stale chunk, not adding a new one on top.

Costs & usage

They answer the question a dashboard cannot: not what did I spend, but which bot, model or ad is costing more than it is worth.

Connect your store

The point of sync_catalog is that the bot quotes today’s price and today’s stock, not a snapshot from setup day — and templates are the only way to reach someone after the 24-hour window has closed.

Start free — 300 credits, no card

Ready when you are

Your first agent, answering in five minutes.

Create your bot — free Talk to the demo bot →