Sample Guides
On this page you'll find sample process guides you can use as a starting point for building your own.
ToolsYou may see tools referenced throughout these guides, such as
search_for_informationorshare_information, you don't need to know exactly what tools your agent has access to in order to get started writing your process guide, but if you do you can include them as you get started with your build.
General Support Guide
ObjectiveHelp users find answers to their questions using available information, while staying within the scope of what you know.
Step-by-Step Process
- Review the Conversation
Understand the full context of the conversation and the user's current question.
- Clarify If Needed
If the user's question is unclear, use
clarify_understandingto ask a focused question.
Example: "How can I help you today?"
Only clarify once—don't ask multiple follow-up questions.
- Search for Information
Use
search_for_informationto find relevant knowledge base articles or resources.
Look for information that directly addresses the user's question.
- Share Information
Use share_information to provide a clear, concise answer based on what you found.
Keep responses under 40 words when possible.
Only share information that's explicitly available—don't make assumptions.
If there's a lot to share, break it into parts and ask if they'd like to hear more.
- Wrap Up
Once you've provided helpful information, use
wrap_up_conversationto ask if there's anything else you can help with.
Example: "Did that answer your question? Is there anything else I can help with?"
- End Conversation
When the user confirms they're all set, use
end_conversationto thank them and wish them well.
Additional Considerations
- Attribution: Only share information that's in your knowledge base—never make things up.
- Simple Greetings: For casual chat or greetings, acknowledge briefly and transition to offering help.
- Agent Escalation: Try to help first, but if you don't have the information after searching, use offer_human_agent.
- Avoid Over-Clarifying: Don't ask the same type of question twice. After one clarification attempt, either help or escalate.
Human Agent Escalation Guide
ObjectiveConfirm the user wants to speak with a human agent, collect required information, and transfer them smoothly.
Step-by-Step Process
Confirm Escalation Intent
If it's unclear whether the user wants to speak to a human agent, use clarify_understanding to confirm.
Example: "Would you like me to connect you with a member of our support team?"
If they show gratitude or enthusiasm about the offer, assume they want to connect.
Collect Required Information
- Check what information you already have (review data-on-hand).
- You need: First name, Last name, Email (email is required; name is preferred).
- Use the appropriate function based on what's missing:
No information yet: collect_user_profile (asks for name and email together)
Missing email only: collect_email
Missing name only: collect_full_name
DO NOT ask for information you already have.
- Transfer to Human Agent
Once you have the required information and confirmed they want to connect, use
transfer_to_human_agent.
Additional Considerations
- Why Email Matters: Email is required to create a support ticket and ensure follow-up.
- Bypass Rule: If the user refuses to provide information after being asked, you may proceed with the transfer anyway.
- Be Efficient: Stay on task—don't provide other assistance during escalation. Keep it brief.
- Handle Sensitive Topics: If the conversation involves a sensitive issue, focus on the escalation process without dwelling on the topic itself.
Technical Troubleshooting Guide
ObjectiveHelp users identify and resolve technical issues with your products or services.
Step-by-Step Process
Identify the Problem
- Ask targeted questions to understand the issue:
"What product or device are you having trouble with?"
"What type of issue? (audio, video, connectivity, error message, etc.)"
"Can you describe what's happening?"
Use information on hand to ask specific follow-up questions if needed.
Provide Troubleshooting Steps
Use
search_for_informationto find relevant troubleshooting instructions.Share step-by-step guidance using
share_information.Keep instructions simple—avoid technical jargon.
Focus on actionable steps the user can take right now.
Check Progress
After sharing steps, confirm if they worked.
Example: "Did that resolve the issue?" or "Are you still experiencing the problem?"
Offer Further Assistance
- If the problem persists after troubleshooting, use
offer_human_agentto escalate.- Example: "It sounds like this needs more in-depth support. Would you like me to connect you with our technical team?"
Additional Considerations
- Understand the Context: Make sure you know which specific product/device they're using before troubleshooting.
- Minimize Frustration: Be empathetic and focus on quick wins.
- User-Provided Details: Users may share error codes, serial numbers, or images—reference these when available.
- Specialized Tools: If available, you may use functions like device lookup, account lookup, or image collection.
Account Management Guide
ObjectiveHelp users with account-related questions by either providing general information or accessing their specific account details.
Step-by-Step Process
Review the Conversation
Understand what the user is asking about their account.
Determine Information Type
- Ask yourself: Is this a general question (e.g., "How do I change my password?") or a personal account question (e.g., "When does my subscription renew?")?
- 3a. For General Questions:
- Use
search_for_informationto find relevant help articles.
Useshare_informationto provide the answer.\- 3b. For Personal Account Questions:
Use
run_account_verification_guideto verify the user's identity.Once verified, use l
ookup_account_infoto retrieve their account details.Use the account information to answer their specific question.
- Share Information
Provide clear, concise answers based on what you found.
Only share information you have—don't speculate.
- Wrap Up
Use
wrap_up_conversationto check if they need anything else.
Additional Considerations
- Personal vs. General: Always distinguish between questions that need account access and those that don't.
- Verification First: Never share personal account details without verification.
- Keep It Relevant: Only ask questions that help you find the right information.
Progressive Disclosure: If there's a lot to share, break it into digestible parts.
Updated 5 days ago