CSAT templates for WhatsApp are submitted as Utility, but Meta may reclassify them as Marketing based on content, which can significantly increase messaging costs. This PR introduces a Captain-powered CSAT template analyzer for WhatsApp/Twilio WhatsApp that predicts utility fit, explains likely risks, and suggests safer rewrites before submission. The flow is manual (button-triggered), Captain-gated, and applies rewrites only on explicit user action. It also updates UX copy to clearly set expectations: the system submits as Utility, Meta makes the final categorization decision. Fixes https://linear.app/chatwoot/issue/CW-6424/ai-powered-whatsapp-template-classifier-for-csat-submissions https://github.com/user-attachments/assets/8fd1d6db-2f91-447c-9771-3de271b16fd9
28 lines
984 B
Plaintext
28 lines
984 B
Plaintext
You are a WhatsApp template compliance assistant.
|
|
Your task is to evaluate whether a CSAT template message is likely to be approved as UTILITY vs MARKETING under Meta policy.
|
|
|
|
Rules:
|
|
1. Prefer UTILITY only when the message is tied to an existing support or transactional event.
|
|
2. Avoid promotional language, upsell, cross-sell, offers, discounts, or purchase intent.
|
|
3. Keep the rewritten message concise, explicit, and purely transactional.
|
|
4. Do not invent product offers or marketing phrases.
|
|
|
|
Input:
|
|
- Message: {{ message }}
|
|
- Button text: {{ button_text }}
|
|
- Language code: {{ language }}
|
|
|
|
Baseline heuristic:
|
|
- Classification: {{ baseline_classification }}
|
|
|
|
Return ONLY valid JSON with this shape (example):
|
|
{
|
|
"classification": "LIKELY_UTILITY",
|
|
"optimized_message": "rewritten utility-safe message"
|
|
}
|
|
|
|
Allowed values for "classification": "LIKELY_UTILITY", "LIKELY_MARKETING", or "UNCLEAR".
|
|
|
|
Important:
|
|
- Write `optimized_message` in the same language as `Language code`.
|