technical-issue-course-content
Technical Issue with Course Content
Response Patterns (from samples)
Common openings:
- "Hi,"
- "Thanks for the feedback, it's not perfect for sure. We recommend using VS Code or similar locally if the inline editor is aggravating."
- "Hello,"
Common core lines:
- "Hi,"
- "Thanks for the heads up! We'll look into this ASAP."
- "Best,"
Common closings:
- "Best,"
- "Thanks for the heads up! We'll look into this ASAP."
- "Thanks for the feedback, it's not perfect for sure. We recommend using VS Code or similar locally if the inline editor is aggravating."
Phrases That Work (4-gram frequency)
More from skillrecordings/support
vercel-cli
Deploy and manage Vercel projects via CLI. Use when deploying apps, managing environment variables, configuring domains, or pushing secrets to Vercel. Triggers on deploy, vercel, env vars, production.
4ai-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.
2vector-search
Implement vector search for knowledge retrieval. Use when adding RAG, semantic search, knowledge base features, or context building for the agent.
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.
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.
2