Immediate result: A conversation flow for your top intents, with clear exits to a human.
Problem it solvesChatbots trap customers in loops and make simple issues harder.
Intents: where's my order, cancel order, payment failed, change address, talk to agent
Where's my order → ask order number (or show last 3 orders) → show live status + ETA.
If ETA passed: apologise, offer agent.
Handover passes: order ID, status, customer's last message.
Badly designed chatbots trap customers in loops and make simple problems harder. This skill designs a short flow for each of your top intents — greet, identify, collect, resolve or hand over — with bot messages under 30 words. A 'talk to a person' option is never more than one tap away, and it defines exactly what the agent receives on handover so customers never repeat themselves. The flows work for any chatbot builder or as a brief for your engineering team. To use it, paste the skill into your assistant and send your top five support intents and what information a human needs to solve each; the reply opens with “Flow per intent”.
# Skill: Support chatbot flow
You are running the "Support chatbot flow" skill for me. I work as: Support operations. What I need from you: a conversation flow for my top intents, with clear exits to a human.
## When I send you my top five support intents and what information a human needs to solve each
1. Design a short flow per intent: greet, identify, collect, resolve or hand over.
2. Write bot messages under 30 words.
3. Add a 'talk to a person' exit at every step.
4. Define what's passed to the agent on handover.
## Reply in this format
- Flow per intent (numbered steps)
- Bot messages
- Handover rules
- Data passed to agent
## Rules
- The human option is never more than one tap away.
- Use only the facts I give you; mark anything you had to assume with [ASSUMPTION].
- If something essential is missing, ask me one short question, then continue.
- No preamble or filler: start with the result.
Confirm you're ready in one line, then wait for me to send my top five support intents and what information a human needs to solve each.Then sendYour top five support intents and what information a human needs to solve each. For example: Intents: where's my order, cancel order, payment failed, change address, talk to agent
Upload it to Claude, add it to ChatGPT's Codex app, clone it into Claude Code, or download the SKILL.md for any agent. Full guide with screenshots →
Download the ZIP and upload it in Claude. Claude then uses the skill on its own whenever a request matches.
Download ZIP
OpenAI's Codex app reads the same SKILL.md format. Copy the skill into your Codex skills folder:
$ git -c http.version=HTTP/1.1 clone https://scienceofapps.com/skills/ai-skills.git
$ cp -r ai-skills/chatbot-flow-designer ~/.codex/skills/
Clone the library and copy this skill into your Claude Code skills folder.
$ git -c http.version=HTTP/1.1 clone https://scienceofapps.com/skills/ai-skills.git
$ cp -r ai-skills/chatbot-flow-designer ~/.claude/skills/~/.claude/skills/ for all projects, or .claude/skills/ inside one project.Download the skill file and put it in a folder named after the skill.
Download SKILL.md~/.claude/skills/chatbot-flow-designer/SKILL.md.Repositoryscienceofapps.com/skills/ai-skills.git · all 200 skills, one folder each, plain git over HTTPS
Chatbots trap customers in loops and make simple issues harder. The skill fixes that: a conversation flow for your top intents, with clear exits to a human.
Copy the skill and paste it as the first message of a new chat, then send your input. To keep it, paste it into a ChatGPT Project or custom GPT, a Claude Project or a Gemini Gem, or upload the SKILL.md file as a Claude Skill.
Send your top five support intents and what information a human needs to solve each. If something essential is missing, the skill asks you one short question and then continues.
Yes. It's free to copy, use and adapt, with no sign-up, and works in the free versions of ChatGPT, Claude, Gemini and Copilot.
ProblemCustomer bug reports are vague, so engineers can't reproduce them.
'App freezes when I upload a photo for KYC' · Redmi Note 12, Android 14
Title: KYC — app freezes on photo upload — Android 14
Steps: Profile → KYC → Upload → choose gallery photo
Missing: photo size; does the camera option also freeze?
Immediate resultAn engineering-ready bug report with steps, expected vs actual, environment and severity.
ProblemCustomers write in Hindi, Tamil or Hinglish and replies come back in stiff English.
'bhai mera refund abhi tak nahi aaya' · answer: refund sent 20 Oct, 5–7 working days
Detected: Hinglish, casual.
Reply: 'Hi! Aapka refund 20 Oct ko bhej diya gaya hai. Bank mein dikhne mein 5–7 working days lagte hain…'
English: 'Your refund was sent on 20 Oct…'
Immediate resultA natural reply in the customer's language and register, with an English version for the record.
ProblemTicket quality reviews are subjective and feedback to agents is vague.
Thread: 6 messages, refund handled, customer asked twice for timeline
Resolution 5 · Efficiency 3 — timeline only given after the second ask.
Coaching: put the 'when' in the first reply.
Better: 'Refund sent today; it shows in 5–7 working days.'
Immediate resultA scored review of a ticket against a rubric with specific coaching feedback.
All 12 customer support skillsAll 200 skillsRead it in the articleProve it: AI for Customer Support Certification (free test)
60 research-backed principles in 6 categories — what each one means, why it works on the human brain and how to use it on your own screens. Written by Sushant Singh, founder of Science of Apps, who has scaled consumer apps to lacs of users and spent 10+ years leading product across startups and digital businesses in the US, EU & India.
110 real paywalls from top apps, taken apart, rated out of 5 and decoded with the Laws of UX — plus the frameworks, copy and checklists to ship your own. By Sushant Singh, founder of Science of Apps.