Workflow guide
Support plan for startups
Answer onboarding, feature, and pricing questions from docs that change every week. Pricing promises and bug triage stay with the founders.
What the visitor sees
Questions to test
What the agent answers, and what stays with your team.
Use these questions as test prompts. Each one should be answered from the source under it. Account-specific answers need authentication and a supported connection.
Beta support
Planning sampleAnswer from approved sources
- 01How do I import my contacts?Getting started guide
- 02What’s included in the free plan?Pricing page
- 03What changed in this week’s release?Release notes
Hand to your team
- Pricing promises and discounts
- Bug reports that need triage
- Roadmap commitments
Can I keep the beta pricing after launch?
Handoff rules
Write down where the agent stops.
When it does, your team sees the whole chat, not a summary.
- 01
A bug report
The agent asks for the steps and creates a support ticket for triage.
- 02
A question about the roadmap
The agent shares the release notes and leaves promises to the founders.
- 03
A user who is about to cancel
The agent passes the chat to a founder while the user is still there.
What your team sees
A safer first version
Four steps, one pilot review.
Record a baseline before the test, use the same time window after it, and keep the result tied to your own conversation data.
- 01Choose one support job
- 02Add approved sources
- 03Set action and handoff rules
- 04Run a private test
Sample measurement checklist
Pilot review
Pilot review progress: 0/4Questions before setup
Decide the rules before customers see it.
Test one narrow workflow first.
Start with five real questions, remove sensitive data, and compare every answer with the source your team approved.
No credit card required