Home/Digital workers/Conversation agent
Conversation agent

Catch every message, pass the serious ones to a person

DMs and comments arrive at all hours, and a person can only answer a slice of them. The Conversation agent answers each one using the persona and knowledge base you configured, builds it into a contact profile, and stops when your handoff conditions are met — passing that contact to sales.

What it delivers

  • Contact profilesOne per contact, filterable by field and exportable
  • Conversation historyFull transcripts across accounts and platforms
  • Handoff queueContacts that met your conditions, waiting for sales
  • Two ratiosReplies sent by AI, and contacts escalated
Why it exists

You've probably run into these

A customer asks about pricing at 2am, I see it when I get in, and they're long gone

The Conversation agent is online during activity hours for the account's region and answers the settled questions from your knowledge base. Anything it can't answer is parked and flagged rather than bluffed.

Five platforms, a dozen accounts, switching between inboxes — I always miss a few

Conversations from 6 platforms land in one inbox, grouped by contact rather than by account. Someone who reached you on two platforms shows up as a single profile.

The AI replies read like a template and customers spot the bot immediately

Personas set the role and tone, phrasing libraries give consistent verbal habits, and scripts govern how a conversation advances. The same question gets a different answer from a different persona.

A salesperson leaves and three months of customer conversations walk out on their personal messenger

Conversations, profiles and tags live on the platform and the accounts belong to the company. During a handover you reassign the accounts and contact groups to someone else, and nothing is lost.

How it works

From one DM to a contact worth working

The handoff conditions and the closing stage are both yours to define. AI catches and organises; anything involving quotes, commitments or the final push goes to a person.

01
Consolidate into one inbox

DMs and comments from every platform account land in one inbox. A contact's conversations across platforms sit in a single profile, so there's no switching.

Automatic
02
Confirm persona, knowledge base and handoff conditions

Pick a persona and activity hours, import your own knowledge base, and spell out which questions must go to a human. This configuration is what decides what the AI can and cannot say on your behalf.

Needs you
03
AI replies in persona

It only answers what the knowledge base supports, advancing along the script. It replies in whatever language the customer uses, translating when needed.

Automatic
04
Build profiles and tags

Requirements, source and stage are pulled from the conversation into profile fields and tags. Long-term memory across sessions means the next conversation picks up where the last one stopped.

Automatic
05
Hand off to sales

Contacts that meet your conditions enter the handoff queue and the AI stops replying. Sales continues in the same inbox with the full history in front of them.

Needs you

A price, a stock commitment or an after-sales condition becomes a promise the moment it's sent, and walking one back costs far more than answering a few minutes later. So the last step goes to a person: the AI asks what needs asking and records what needs recording, and sales just carries the conversation forward.

Capabilities

What it can do

Unified inbox

Conversations from 6 platforms in one place, grouped by contact, filterable by account, tag and status.

AI replies

Answers from your own knowledge base and nothing beyond what it supports. Switch it on or off per account.

Handoff rules

You define the triggers. Once matched, the AI stops and the contact joins the queue for sales.

The persona set

Personas, activity hours, phrasing and scripts. Keep one account on one set over time and its voice stays consistent.

Long-term memory

When a contact returns weeks later it remembers where the conversation stopped and what they asked for, so they don't have to repeat themselves.

Profiles and tags

Profile fields and the tag scheme are yours to define, with bulk tagging, tag filters and profile export.

Canned replies

Save your common lines as snippets and send them in one click after taking over, instead of retyping.

Translation

Read incoming messages in your own language and send in the customer's, with both the original and the translation kept on record.

Prerequisites

What you need before you start

The Conversation agent is software. The accounts, environments and knowledge it works from are yours to provide. We spell that out so you don't plan against the wrong cost.

Platform accounts
Your own accounts. We don't supply accounts and we don't register them for you. For customer conversations, use accounts that have already been warmed and carry a record of ordinary use.
Cloud environment or cloud phone
One isolated environment per account keeps the session stable. Phone-first platforms like WhatsApp and Telegram need a cloud phone. Billed on actual usage.
Proxy network
Set the exit route by each account's target region so account and IP stay paired. Use our proxy pool or connect your own.
Knowledge bases
Product details, how you talk about pricing, common questions, and what must never be promised. If it isn't in the knowledge base the AI won't invent it — it parks the message for a person.
Handoff conditions
Which questions have to go to a person. Leave this unset and the AI speaks for you the whole way through, which is not a state we'd recommend going live in.
Persona and phrasingPreset template available
With no persona of your own, start from a preset. Run a batch of real conversations, then tune the phrasing and scripts against how customers responded.
Works with

Who it works with

FAQ

FAQ

Will the AI get something wrong and lose the customer?

It will get things wrong. The AI answers only from your knowledge base, so if that's vague or self-contradictory the answers will be too. The real safety net is your handoff conditions: put pricing, stock and after-sales — anything that can't afford an error — on the must-escalate list, and the AI stops when it hits them. Before going live, run a batch against real past conversations, read the answers, then scale up.

What's a normal share of replies for the AI to handle?

There's no standard figure — it depends on how much your knowledge base covers and how tight your handoff conditions are. The dashboard shows replies sent by AI and contacts escalated; read them together. A high AI share alongside a low close rate on escalated contacts means things that should have been escalated weren't.

Does the AI keep chiming in after a handoff?

No. Once a contact is handed off, automatic replies for them are switched off and only people speak. Sales takes over in the same inbox with the full history and profile there. When they're done, you can manually hand the contact back to the AI for ongoing follow-up.

What does long-term memory store, and for how long?

Structured information pulled from the conversation — requirements, preferences, the stage reached — rather than a full copy of the transcript. When the same contact returns weeks later, the AI can pick up where it left off. What's remembered is visible in the contact profile, and you can correct or delete it.

Can contact profiles be exported?

Yes. Filter profiles by tag, source or stage and export them into your own CRM. Conversation transcripts can be exported by date range too.

Can we send broadcast messages to contacts?

Technically yes — filter contacts by tag and send in bulk. But platform limits on unsolicited marketing messages vary widely, and WhatsApp is especially strict. Start small, keep the frequency down, and treat broadcasting as a supplement rather than your main channel. The account risk here comes down to your sending strategy.

Start with one platform's conversations

A consultant will put together a concrete configuration recommendation and resource quote around your platforms, contact volume and existing messaging.