duplicate-purchase
Duplicate Purchase
Response Patterns (from samples)
Common openings:
- "Hi,"
- "Hello,"
- "Hey,"
Common core lines:
- "It may take 5-10 business days for the refunded amount to show up in your account, depending on how quickly it's processed by your financial institution."
- "[EMAIL]"
- "Best,"
Common closings:
- "It may take 5-10 business days for the refunded amount to show up in your account, depending on how quickly it's processed by your financial institution."
- "Best,"
- "Let me know if you have any issues requesting login links using that email address."
Phrases That Work (4-gram frequency)
- "let me know if" — 78 (33.3%)
- "me know if you" — 56 (23.9%)
- "5 10 business days" — 53 (22.6%)
- "if you have any" — 51 (21.8%)
- "take 5 10 business" — 51 (21.8%)
- "it may take 5" — 49 (20.9%)
- "may take 5 10" — 49 (20.9%)
- "10 business days for" — 49 (20.9%)
- "business days for the" — 49 (20.9%)
- "days for the refunded" — 49 (20.9%)
Tone Guidance (observed)
- Openings trend toward: "Hi,"
- Closings often include: "It may take 5-10 business days for the refunded amount to show up in your account, depending on how quickly it's processed by your financial institution."
What NOT To Do
- Don't introduce policy details that are not present in the verified response lines above.
- Don't paraphrase or reframe the customer's question in a way that changes meaning.
- Don't add refund/discount promises unless they appear in the extracted responses for this topic.
Validation
Draft must:
- Include at least one of the required phrases from the validation block
- Stay consistent with the observed response patterns above
- NOT introduce policy details that are not present in the verified response lines above.
More from skillrecordings/support
ai-sdk
Comprehensive guide to AI SDK v6 for agent development, tool definitions, multi-step agentic workflows, and result extraction patterns
2lesson-content-question
Answer lesson-specific content questions. Use when a customer asks about a lesson, code example, or concept in a course.
2email-change
Transfer licenses to a new email address. Use when a customer wants to change account email, move a license, or update access after a job change.
2ops-setup
Guide user through support platform setup. Use when user says "set up", "configure", "I'm on step X", or provides API keys/credentials.
2vector-search
Implement vector search for knowledge retrieval. Use when adding RAG, semantic search, knowledge base features, or context building for the agent.
2course-builder-incident-forensics
Diagnose production incidents for any course-builder app (ai-hero, epic-web, etc.) across Axiom, Vercel logs, source code, and DB preconditions. Use this whenever a course-builder app has 4xx/5xx spikes, `/api/inngest` failures, shortlink/post-linking failures, or someone asks "what account/deploy/path is failing right now?
2