Playbooks for a twin that does one job well.
The docs explain what everything is. These are the recipes: what to build, in what order, and — the part most guides skip — what each one will not do for you.
- Support twinabout 20 minutes to set up
A support agent that answers from your docs
Turn the help centre you already wrote into a twin that answers your users, cites the passage, and hands off what it doesn't know.
- Cited answers
- An inbox handoff for every gap
- A gap queue you can answer once
- Public twinabout 30 minutes to set up
Turn repeat questions into booked calls
Let the twenty questions you answer every week answer themselves — and hand you the people worth talking to.
- Cited answers in your tone
- Captured leads with the question attached
- Booking-link clicks
- Team twinabout 20 minutes to set up
A team twin for the questions colleagues keep asking you
Answer your colleagues from internal material — without the twin ever deciding anything on your behalf.
- Answers from internal material
- Fewer repeat interruptions
Every playbook is written against what has actually shipped. Where a step needs something we do not have yet, it says so rather than quietly leaving it out — see the roadmap for what is still being built, or the docs for how a particular feature works.