Five steps. Each is small. Each is reversible. Most teams finish in under a week — with a tested, scoped agent that goes live without surprises.
Who are your customers? What do they ask most? What does success look like? Five minutes of context saves hours of tuning.
Print out your last 200 support tickets. Find the 50 you answer most often. That's your knowledge base — for now.
Paste FAQs and policies, save public URLs, publish articles, and add products. The agent answers from your content.
Brand color, greeting, languages, business hours, and handoff behavior. Test with the Training live preview first.
Invite teammates, connect Slack or webhooks, and decide when visitors should request a human.
Pick a north-star metric (resolution rate, deflection, CSAT). Tune everything else against it.
Don't boil the ocean. Begin with the questions your own support history shows are asked most often, then add the rest as you go.
Set guardrails, test, approve. Don't ship an unrestricted model to a real audience.
The knowledge-gap report is your real backlog. Close gaps, the agent gets better.
The time depends on how much source material you add and how thoroughly you test it. You can install the widget immediately, then expand knowledge and guardrails before sending it real traffic.
Yes. Use live chat or email for product and setup questions. Response times vary with issue severity and support volume; no plan promises a dedicated engineer or scheduled onboarding call.
Skipping the guardrails step. They ship an unrestricted model, it says something off-brand, and they pull the widget. Always test-set approve before going live.
Free plan, no credit card. Drop in the script, point it at your site, ship it.
