customer-facing-clone-requirements.md
Everything to decide before a clone talks to customers or the public: audience, integrations, persona, scope, escalation rules, approved knowledge, test plan and pilot.
Version 1 · updated Nov 15, 2026
# Customer-facing clone requirements: [COMPANY NAME] > How to use this template: fill in what you can before you build a clone that talks to customers, residents, patients or the public. Blank answers are fine; work through them with your team or your Clone onboarding contact. When it's done, upload it to that clone's Knowledge (Clone level) so the clone knows its own rules. ## 1. Purpose and audience - Who will talk to this clone? [customers, prospects, residents, visitors...] - Top 5 reasons they contact you today: 1. [ ] 2. [ ] 3. [ ] 4. [ ] 5. [ ] - What does success look like in 30 days? [e.g. fewer repeat questions, faster replies, fewer hand-offs] ## 2. Integrations Mark what you want and the order to launch them. | Integration | Wanted? | Priority (1 = first) | Notes | |---|---|---|---| | Website (embeddable link or SDK) | | | | | Phone number | | | An existing number can forward to the clone's number | | Microsoft Teams or Slack (staff) | | | | | Clone email address | | | Decide who it replies to: internal only, or everyone | | Voice chat | | | | ## 3. Persona and tone - Name and role: [ ] - Tone: [formal / friendly / concise / warm] - Languages people use (written and spoken): [ ] - Should the clone say it's an AI assistant? [recommended: yes] - Greeting and sign-off: [ ] ## 4. Scope - In scope (the clone may answer): [ ] - Out of scope (hand off to a person): [ ] - Never discuss: [e.g. individual payment details, other people's personal data] ## 5. Escalation rules | Situation | What the clone should do | Hand off to (name or role) | How (email / Teams / phone) | Expected response time | |---|---|---|---|---| | Doesn't know the answer | | | | | | Complaint or upset customer | | | | | | Safety or emergency | | | | | | Request to change a booking, payment or contract | | | | | ## 6. Knowledge sources Approved documents this clone may use (see the Knowledge plan worksheet in this library). | Document | Owner | Language | Current? | |---|---|---|---| | | | | | **Reminder:** keep sensitive internal data off a public-facing clone. Use a separate internal clone for it. ## 7. Test plan - 15 to 20 real past questions with ideal answers - At least 3 tricky ones (unclear, off-topic, or asking for something out of scope) - At least 3 in each language your audience uses ## 8. Launch plan - Pilot group: [who tests it first, and for how long] - Who reviews conversations during the pilot: [name] - Go-live date: [ ]
Customer-facing clone requirements: [COMPANY NAME]
How to use this template: fill in what you can before you build a clone that talks to customers, residents, patients or the public. Blank answers are fine; work through them with your team or your Clone onboarding contact. When it's done, upload it to that clone's Knowledge (Clone level) so the clone knows its own rules.
1. Purpose and audience
- Who will talk to this clone? [customers, prospects, residents, visitors...]
- Top 5 reasons they contact you today:
- [ ]
- [ ]
- [ ]
- [ ]
- [ ]
- What does success look like in 30 days? [e.g. fewer repeat questions, faster replies, fewer hand-offs]
2. Integrations
Mark what you want and the order to launch them.
| Integration | Wanted? | Priority (1 = first) | Notes |
|---|---|---|---|
| Website (embeddable link or SDK) | |||
| Phone number | An existing number can forward to the clone's number | ||
| Microsoft Teams or Slack (staff) | |||
| Clone email address | Decide who it replies to: internal only, or everyone | ||
| Voice chat |
3. Persona and tone
- Name and role: [ ]
- Tone: [formal / friendly / concise / warm]
- Languages people use (written and spoken): [ ]
- Should the clone say it's an AI assistant? [recommended: yes]
- Greeting and sign-off: [ ]
4. Scope
- In scope (the clone may answer): [ ]
- Out of scope (hand off to a person): [ ]
- Never discuss: [e.g. individual payment details, other people's personal data]
5. Escalation rules
| Situation | What the clone should do | Hand off to (name or role) | How (email / Teams / phone) | Expected response time |
|---|---|---|---|---|
| Doesn't know the answer | ||||
| Complaint or upset customer | ||||
| Safety or emergency | ||||
| Request to change a booking, payment or contract |
6. Knowledge sources
Approved documents this clone may use (see the Knowledge plan worksheet in this library).
| Document | Owner | Language | Current? |
|---|---|---|---|
Reminder: keep sensitive internal data off a public-facing clone. Use a separate internal clone for it.
7. Test plan
- 15 to 20 real past questions with ideal answers
- At least 3 tricky ones (unclear, off-topic, or asking for something out of scope)
- At least 3 in each language your audience uses
8. Launch plan
- Pilot group: [who tests it first, and for how long]
- Who reviews conversations during the pilot: [name]
- Go-live date: [ ]
Was this useful?
Thanks!