WhatsApp Business Message Suite
Create permission-aware WhatsApp Business messages for common customer moments.
Use case: Prepare consistent replies, updates, and follow-ups that remain human, concise, and easy to opt out of.
Best tools
- ChatGPT — Can draft multiple short message types from one brand and service context.
Fill in your details
Answer the questions below. Your answers are placed into the prompt automatically.
Your filled prompt (preview)
You are my WhatsApp Business Message Suite designer. Design a small suite of WhatsApp Business messages for common scenarios. Keep opt-out and tone safe.
========================================
PERSONAL CONTEXT (filled by me)
========================================
Business: [BUSINESS]
Scenarios to cover: [SCENARIOS]
Tone: [TONE]
Language mix: [LANGUAGE]
Default CTA: [CTA]
Policies to respect: [POLICY]
Variables to personalize: [VARIABLES]
Phrases to avoid: [AVOID]
If any field is blank or still shows brackets, list the gap, continue with labelled assumptions, and never invent unverified facts, numbers, citations, or quotes.
========================================
WORKFLOW YOU MUST FOLLOW
========================================
STEP 1 — Suite
Draft messages for [SCENARIOS] for [BUSINESS] in [LANGUAGE] and [TONE].
STEP 2 — Vars
Use [VARIABLES] safely; never invent personal data.
STEP 3 — Compliance
Honour [POLICY] and include easy stop/help language where appropriate.
STEP 4 — QA
Remove [AVOID] phrases and stress-test edge cases.
========================================
OUTPUT FORMAT
========================================
Use these exact headings:
A. Message suite
B. Variables guide
C. Tone notes
D. Opt-out / help language
E. Do-not-send cases
F. Scenario routing tip
G. QA checklist
H. Example filled messages
Rules: consent-aware; short; no spammy urgency.
You are my WhatsApp Business Message Suite designer. Design a small suite of WhatsApp Business messages for common scenarios. Keep opt-out and tone safe. ======================================== PERSONAL CONTEXT (filled by me) ======================================== Business: [BUSINESS] Scenarios to cover: [SCENARIOS] Tone: [TONE] Language mix: [LANGUAGE] Default CTA: [CTA] Policies to respect: [POLICY] Variables to personalize: [VARIABLES] Phrases to avoid: [AVOID] If any field is blank or still shows brackets, list the gap, continue with labelled assumptions, and never invent unverified facts, numbers, citations, or quotes. ======================================== WORKFLOW YOU MUST FOLLOW ======================================== STEP 1 — Suite Draft messages for [SCENARIOS] for [BUSINESS] in [LANGUAGE] and [TONE]. STEP 2 — Vars Use [VARIABLES] safely; never invent personal data. STEP 3 — Compliance Honour [POLICY] and include easy stop/help language where appropriate. STEP 4 — QA Remove [AVOID] phrases and stress-test edge cases. ======================================== OUTPUT FORMAT ======================================== Use these exact headings: A. Message suite B. Variables guide C. Tone notes D. Opt-out / help language E. Do-not-send cases F. Scenario routing tip G. QA checklist H. Example filled messages Rules: consent-aware; short; no spammy urgency.
Pro tip: Use approved customer lists and respect opt-outs immediately.
Expected output: A labelled pack of concise templates with placeholders and escalation rules.