Write Chatbot Intent Answers with Trigger Phrases and Human Handoff Rules
Get a set of chatbot intents for your top support questions, each with customer-style trigger phrases, a short bot answer, and an exact rule for handing off to a human.
Prompt
You are a support operations lead who designs chatbot flows for help centers.
Your job: turn my top support questions into chatbot intents, each with trigger phrases, a short bot answer, and a clear handoff rule. First ask me these in one message and wait for my answers:
1. What does your company sell, and who contacts support?
2. List your top 5-10 support questions, or paste ticket subjects or FAQ text.
3. What can the bot actually do (look up orders, reset passwords, or only answer)?
4. When are agents available, and how does a handoff work?
Rules:
- Each bot answer is 60 words or fewer and ends with one next step or one question.
- Give 5-8 trigger phrases per intent, written the way customers type, including typos and short fragments.
- Each handoff rule names an exact, checkable condition, such as the customer asking twice, mentioning a charge dispute, legal or safety issue, angry language, or an account the bot cannot verify.
- The bot never promises refunds, dates or policy exceptions it cannot confirm.
- Include one fallback intent: one clarifying question at most, then handoff.
Output format:
For each intent: Intent name, Trigger phrases, Bot answer, Handoff rule, Handoff message to customer.
Then a short Global handoff rules list.
End with one line listing gaps: questions my info did not cover and policies I need to confirm.Example output
Tips and common edits
Why this works
- Customer-style trigger phrases with typos match how people actually type, so the bot misses fewer intents.
- Every intent has a checkable handoff condition, which stops loops and guessing.
- Banning unconfirmed promises keeps the bot from creating refund or policy problems for agents.
Use when setting up or fixing a support bot that loops or guesses. Have your top ticket topics, bot capabilities and agent hours ready. Works well in ChatGPT, Claude or Gemini.
Common edits
- Ask for output as CSV columns to import into your chatbot platform.
- Add a tone line, such as casual and friendly or formal, to match your brand voice.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Audit a Help Center Article for Gaps, Jargon and Outdated Steps
Paste a help center article and get a pass/fail checklist scorecard plus a line-by-line fix list ranked by customer impact, without a full rewrite.
Find Help Center Gaps by Matching Support Tickets to Existing Articles
Get a ticket-to-article match table and a ranked list of new help articles to write, with ticket counts and deflection potential for each.
Turn Feature Notes into a Step-by-Step Help Center How-To Guide
Paste rough notes about a product feature and get a customer-ready how-to guide with one action per step, bold UI labels, expected results and a troubleshooting section.
Turn Support Ticket Topics into a Help Center Category Structure and Article List
Groups your pasted ticket topics into 5-8 customer-language categories, flags duplicates and orphans, and ranks proposed article titles by ticket volume.
Write Help Article Titles and Meta Descriptions in Your Customers' Words
Get help article titles that start with the customer's task verb and meta descriptions within search length limits, each with a character count and the customer phrase it matches.
Turn a Resolved Support Ticket Thread into a Help Center Article
Paste a solved ticket thread and get a ready-to-publish help article with customer details removed, verb-first fix steps, and symptoms written the way customers search.