Quickstart
Train the agent on your business, test it in the playground, connect a channel, and take it live — in that order.
A note on this walkthrough
Knowledge, the six live channels, the inbox, human takeover, and resume all work today. The playground, the onboarding wizard, approval mode, and the go-live controls described below are still being built — they're marked where they appear.
The intended fastest path to a working agent does not start with connecting a channel. It starts with teaching the agent your business, because that's the part that decides whether it's any good.
Train the agent on your business
In Phase 2, an operator adds a website URL or hand-written FAQ and the local pipeline chunks, embeds, and indexes it for retrieval. Live Firecrawl crawling still needs provider acceptance. Automatic persona/FAQ/playbook drafting is future onboarding work.
Progressive homepage-first crawling while the rest of a site ingests is future work.
No website? Phase 2 supports hand-written FAQs. Vertical templates and an interview-driven setup are future onboarding paths.
Uploaded files and documents are future work. See Knowledge for the current source boundary.
Future Phase 3: test it in the playground
Before any customer sees it, talk to the agent yourself. Ask it the questions your customers actually ask — including the ones it shouldn't be able to answer, because that's how you find out whether it invents things.
Two things to check:
- Grounding. Prices, policies, and hours must come from your knowledge base or your business profile. When retrieval turns up nothing, the agent should say so and escalate, not improvise.
- Persona. Tone, length, whether it pushes for the qualification info you want.
Playground conversations are marked as test conversations. They don't count toward analytics or billing.
Future self-service step: connect a channel
Start with the lowest-risk channel available to you.
- Web chat widget — a script tag on your site. No account to link, no platform approval to wait for, and nothing that can get banned.
- Email — forward your support address. Replies go out from your own domain.
- Discord — invite the CoPhrase bot into your server.
- Telegram — a bot token from BotFather.
- Instagram DMs — Instagram Login on a professional account.
- WhatsApp — read the ban-risk warning first. It is the one live channel where the account at risk is yours.
- Everything else — see the channel matrix for the connection method and the caveats.
Future Phase 3: configure handoff before you go live
Decide what the agent does when it's out of its depth, before it's talking to customers:
- Which situations trigger a handoff to a human (pricing disputes, complaints, anything you list).
- Whether the agent replies directly or drafts a reply for a human to approve first. Approval mode is the sane default for a new agent.
- Who gets notified.
See Handoff.
Future deployment flow: go live
The planned product makes activation an explicit action, not a side effect of connecting a channel. That draft/live control is not part of the local Phase 2 prototype.
Once live, inbound messages on the connected channel land in the unified inbox as they're handled. Watch the first few dozen threads. Take over any that go sideways — the AI goes silent on a thread the moment a human replies to it.
After launch
What is CoPhrase
CoPhrase runs one AI sales and support agent across every messaging channel your customers already use, with human takeover built in.
Channels
How CoPhrase connects to messaging channels — the full matrix of connection methods, what each channel supports, and which ones are unofficial.