Support macros, escalation flows, and knowledge base — AI-built
Customer Support Framework encodes support operations, customer success, and CX design expertise into prompt sequences that generate complete support systems. From macro libraries to escalation playbooks, every prompt produces support artifacts that reduce handle time, improve CSAT, and scale your support team.
Full Access Unlocked
All 44 prompts · All 5 modules
"The macro library prompts generated better responses than what our team had written over 3 years. CS..."
Leila H. · Support Manager
Need expert implementation?
Hire an OrchestratorConnect with a certified Prompt.Doctor Orchestrator to deploy this framework for you.
No coding required. You will use ChatGPT or Claude as your AI tool. Follow these steps in order — do not skip ahead.
Purchase & download the framework
Click the buy button on this page. After checkout, go to the and hit Download .zip. Unzip it — you'll get a .md file (the full framework) and a .pdf (easy to read reference). Keep both open.
Open your project — new or existing
This dashboard is designed to integrate into any existing project or be built as a standalone app. If you already have a site in Airo (or Cursor, Bolt, etc.), open that project. If you're starting fresh, create a new project. The Orchestrator Prompt handles both cases — it scans what's already there and adds only what's missing.
Paste the Orchestrator Prompt into your builder's chat
Open the on this page. Copy the Orchestrator Prompt and paste it into your AI builder's chat. It will scaffold the full admin system — secure login, email marketing module, booking engine, and CMS — on top of your existing codebase. This takes 2–5 minutes.
Add your API keys as secrets
Critical — Novice UsersIn your builder, go to Settings → Secrets and add the keys your app needs. For this framework: STRIPE_SECRET_KEY (for booking payments — get it from your Stripe dashboard), ANTHROPIC_API_KEY (for AI-assisted content — get it from console.anthropic.com), and DATABASE_URL (your MySQL connection string). No key is needed for the admin login, CMS, or email modules — those run on your existing infrastructure.
Don't have a MySQL server?
You can purchase a shared hosting plan with cPanel and MySQL at host.esgwon.dev. Once your account is set up, follow the step-by-step guide to create your database and connect it to your AI website builder.
How to set up cPanel MySQL & connect to your AI website →Need help with Stripe?
Get your STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY from your Stripe dashboard. The guide covers test keys, webhook setup, and going live.
Need help with Anthropic?
Get your ANTHROPIC_API_KEY from console.anthropic.com. The guide covers model selection, cost management, and troubleshooting.
Prompting Airo after setup — always name the file
When asking Airo to add tables, columns, or features to the admin dashboard, always include src/server/lib/admin-db.ts in your prompt. Without it, Airo may target the wrong database. Example: "Add a bookings table in the admin database (src/server/lib/admin-db.ts) — do not touch any other database connection in this project."
Run the framework prompts inside your live app
Your app is now running in the builder's preview panel. Open the on this page, copy each prompt one at a time, and paste it into your builder's chat. Replace every [BRACKET] with your real data before sending. Work through the stages in order — each stage output feeds the next.
Test end-to-end, then publish or hand off to your client
Walk through the admin as a real user: log in, create a booking, send a test email campaign, update a CMS image, and run the Safe-to-Publish gate. Once everything passes, click Publish in your builder. Because this is a white-label dashboard, your client accesses it at /admin on their own domain — no Prompt.Doctor branding, no third-party login required.
5 modules · 44 prompts · 6 workflow stages
Macro Library System
Generate 50+ support response macros for common scenarios: billing questions, technical issues, feature requests, account management, and onboarding help.
10 promptsEscalation Playbook
Tier 1 → Tier 2 → Engineering escalation criteria, handoff templates, SLA definitions, and VIP customer handling protocols.
8 promptsKnowledge Base System
KB architecture design, article templates (how-to, troubleshooting, FAQ, reference), and content audit prompts for existing documentation.
9 promptsDifficult Conversations
Response frameworks for: angry customers, refund requests, churn prevention conversations, public complaint management, and service outage communication.
9 promptsCSAT & Training System
CSAT score diagnosis prompts, improvement action plans, agent training guide generator, and QA scorecard templates.
8 promptsWrite a support response for an angry customer who sent this message: "[PASTE CUSTOMER MESSAGE]". Context: [DESCRIBE WHAT HAPPENED]. Our policy: [RELEVANT POLICY]. What we can offer: [WHAT WE CAN DO]. The response must: (1) Open with genuine acknowledgment (not "I'm sorry you feel that way"), (2) Take responsibility for what we got wrong (without over-apologizing), (3) Explain what happened briefly (if relevant), (4) State clearly what we're doing to fix it, (5) Offer the resolution, (6) Close warmly. Tone: calm, human, direct. Under 150 words. No corporate language.
Write a knowledge base article for [PRODUCT NAME] on the topic: "[ARTICLE TITLE]". Audience: [DESCRIBE USER — technical level, context]. Article type: [How-to / Troubleshooting / FAQ / Reference]. Include: (1) One-sentence summary of what this article covers, (2) Prerequisites (if any), (3) Step-by-step instructions (numbered, with screenshots noted as [SCREENSHOT: description]), (4) Common issues and solutions, (5) Related articles (3 suggestions). Style: plain language, active voice, second person ("you"). Each step: one action only. Flag any steps that vary by plan or user role.
Write a churn prevention conversation guide for a support agent speaking with a customer who has submitted a cancellation request. Product: [PRODUCT NAME]. Customer context: [DESCRIBE — plan, tenure, usage level, stated reason for cancelling]. Guide structure: (1) Opening (acknowledge their decision without panic), (2) Discovery question (understand the real reason), (3) Response to [STATED REASON] (address it directly), (4) Value reminder (specific to their usage), (5) Offer (what can we offer to keep them?), (6) If they still want to cancel (graceful exit that leaves the door open). Include exact language for each step.
system
10 prompts
workflow
8 prompts
architecture
9 prompts
prompts
9 prompts
templates
8 prompts
"The macro library prompts generated better responses than what our team had written over 3 years. CSAT went from 78% to 91% in 8 weeks."
Leila H.
Support Manager
"The difficult conversation frameworks are the best I've seen. The churn prevention script alone has saved dozens of accounts."
Tom R.
CX Director
All 44 prompts across 5 modules are unlocked for your account.
Lifetime access