# WhatsApp Template Specs — WappCloud

Master list of every WhatsApp template the system sends, matched against the
live WappCloud account (checked 2026-07-23). Templates marked **⏳ CREATE**
do not exist in WappCloud yet — copy the Name / Category / Header / Body
below into **Templates → Create New Template** and submit for approval.
WhatsApp sends for those triggers silently fail ("No approved template
found") until they are approved.

**Rules that apply to every template here:**

- Template **names are lowercase** with underscores (Meta requirement). The
  WappCloud list displays them capitalized — the real name is lowercase.
- **Language:** English (`en`).
- **Header image:** upload the Chotekisan logo when the form asks for sample
  media. File: `public/assets/images/logo/header-logo.png`
  (hosted: `https://chotekisan.ci5.in/assets/images/logo/header-logo.png`).
  Every template uses the logo image header **except `order_delivered_invoice`**,
  which uses a **Document** header (the per-order invoice PDF is attached
  automatically at send time).
- Body variables are positional `{{1}}`, `{{2}}`, … — the count and order
  below must be kept exactly; the code maps parameters via
  `notification_templates.whatsapp_variables` (see `NotificationSeeder`).
- Meta rejects bodies that **start or end with a variable** — keep the
  wording so text surrounds the placeholders.

---

## Order flow (grocery)

### 1. `order_placed_confirmation` — ⏳ CREATE *(currently unused — no code fires order_placed; create it only if you want a placed-stage message later)*

| | |
|---|---|
| **Category** | Utility |
| **Header** | Image — logo |
| **Variables** | {{1}} customer name · {{2}} order no · {{3}} total |

**Body:**
```
Hi {{1}}, your Chotekisan order {{2}} has been placed successfully. Order value: Rs.{{3}}. We will notify you as soon as it is confirmed. Thank you for shopping with us!
```
**Samples:** `Priya S` · `CK-ORD-000101` · `1,041.00`

---

### 2. `order_confirmed_update` — ✅ APPROVED (Marketing)

| | |
|---|---|
| **Header** | Image — logo |
| **Variables** | {{1}} customer name · {{2}} order no · {{3}} delivery date |

Already approved and working — exactly 3 body variables. A **Utility** twin
`order_confirmed_update_clone` is also approved; if its body has the same 3
variables, switch the admin template's WhatsApp name to the clone to get
utility pricing and escape Meta's marketing frequency cap (error #131049,
which silently drops repeated marketing sends to the same number).

---

### 3. `order_out_for_delivery` — ⏳ CREATE

| | |
|---|---|
| **Category** | Utility |
| **Header** | Image — logo |
| **Variables** | {{1}} customer name · {{2}} order no · {{3}} delivery person name · {{4}} delivery person mobile |

**Body:**
```
Hi {{1}}, your Chotekisan order {{2}} is out for delivery! Our delivery partner {{3}} (+{{4}}) will reach you shortly. Please keep your phone reachable.
```
**Samples:** `Priya S` · `CK-ORD-000101` · `Ramesh K` · `918680022555`

---

### 4. `order_delivered_invoice` — ✅ APPROVED (Utility)

| | |
|---|---|
| **Header** | **Document** — invoice PDF, attached automatically per order |
| **Variables** | {{1}} customer name · {{2}} order no |

Already approved and working. This is the **only** template that does not use
the logo header — the order's invoice PDF is injected as the document header
at send time.

---

### 5. `order_cancelled_info` — ⏳ CREATE

| | |
|---|---|
| **Category** | Utility |
| **Header** | Image — logo |
| **Variables** | {{1}} customer name · {{2}} order no |

**Body:**
```
Hi {{1}}, your Chotekisan order {{2}} has been cancelled. If you paid online, your refund will be processed within 3-5 business days. We hope to serve you again soon.
```
**Samples:** `Priya S` · `CK-ORD-000101`

---

## Vital Kitchen (salad) flow

### 6. `salad_order_placed` — ⏳ CREATE

| | |
|---|---|
| **Category** | Utility |
| **Header** | Image — logo |
| **Variables** | {{1}} customer name · {{2}} order no · {{3}} bowl name(s) · {{4}} total |

**Body:**
```
Hi {{1}}, your Vital Kitchen order {{2}} ({{3}}) has been placed successfully. Order value: Rs.{{4}}. We will notify you once it is confirmed. Stay fresh, stay healthy!
```
**Samples:** `Priya S` · `CK-SO-000040` · `Protein Power Bowl` · `549.60`

---

### 7. `salad_order_confirmed` — ⏳ CREATE

| | |
|---|---|
| **Category** | Utility |
| **Header** | Image — logo |
| **Variables** | {{1}} customer name · {{2}} order no · {{3}} bowl name |

**Body:**
```
Hi {{1}}, your Vital Kitchen order {{2}} ({{3}}) is confirmed and our kitchen has started preparing it fresh for you.
```
**Samples:** `Priya S` · `CK-SO-000040` · `Protein Power Bowl`

---

### 8. `salad_order_out_for_delivery` — ⏳ CREATE

| | |
|---|---|
| **Category** | Utility |
| **Header** | Image — logo |
| **Variables** | {{1}} customer name · {{2}} order no · {{3}} bowl name · {{4}} delivery person name · {{5}} delivery person mobile |

**Body:**
```
Hi {{1}}, your Vital Kitchen order {{2}} ({{3}}) is out for delivery. Our delivery partner {{4}} (+{{5}}) will reach you shortly. Please keep your phone reachable.
```
**Samples:** `Priya S` · `CK-SO-000040` · `Protein Power Bowl` · `Ramesh K` · `919876543210`

---

### 9. `salad_order_delivered` — ⏳ CREATE

| | |
|---|---|
| **Category** | Utility |
| **Header** | Image — logo |
| **Variables** | {{1}} customer name · {{2}} order no · {{3}} bowl name |

**Body:**
```
Hi {{1}}, your Vital Kitchen order {{2}} ({{3}}) has been delivered. Enjoy your fresh salad! We would love to hear your feedback.
```
**Samples:** `Priya S` · `CK-SO-000040` · `Protein Power Bowl`

---

### 10. `salad_order_cancelled` — ⏳ CREATE

| | |
|---|---|
| **Category** | Utility |
| **Header** | Image — logo |
| **Variables** | {{1}} customer name · {{2}} order no · {{3}} bowl name |

**Body:**
```
Hi {{1}}, your Vital Kitchen order {{2}} ({{3}}) has been cancelled. If you paid online, your refund will be processed within 3-5 business days.
```
**Samples:** `Priya S` · `CK-SO-000040` · `Protein Power Bowl`

---

## Account & subscription

### 11. `welcome_new_customer` — ✅ APPROVED (Marketing)

| | |
|---|---|
| **Header** | none (approved without a media header — do not add one in the admin form) |
| **Variables** | {{1}} customer name |

Already approved and verified live.

### 12. `subscription_activated_confirm` — ✅ APPROVED (Marketing)

| | |
|---|---|
| **Header** | Image — logo |
| **Variables** | {{1}} customer name · {{2}} plan name · {{3}} start date · {{4}} end date |

Already approved.

### 13. `subscription_expiry_reminder` — ✅ APPROVED (Marketing)

| | |
|---|---|
| **Header** | Image — logo |
| **Variables** | {{1}} customer name · {{2}} plan name · {{3}} "in 2 days"/"tomorrow" · {{4}} expiry date |

Already approved. Sent by the daily 09:00 scheduler at 2 days and 1 day
before expiry.

### 14. `subscription_expired_renew` — ⏳ CREATE *(currently unused — no code fires subscription_expired yet; create it only when that flow is built)*

| | |
|---|---|
| **Category** | Marketing |
| **Header** | Image — logo |
| **Variables** | {{1}} customer name · {{2}} expiry date |

**Body:**
```
Hi {{1}}, your Chotekisan subscription expired on {{2}}. Renew today to continue enjoying fresh daily deliveries without interruption.
```
**Samples:** `Priya S` · `22 Jul 2026`

---

## Subscription delivery, pause & failure (NEW — create & submit for approval)

These cover the admin actions on **Today's Salad Preparation** and the
**Subscriber** screens for **subscription** deliveries (one-off salad orders use
the `salad_order_*` templates above). Push + Email already fire for all of them;
WhatsApp turns on once each template below is approved in WappCloud and its name
is set on the matching trigger (seeder or Admin → Notification → Templates).

All: **Language English (en)**, **Header = Image (logo)**, body must not start/end
with a variable, variable order fixed.

### 15. `subscription_out_for_delivery` — ⏳ CREATE  → trigger `subscription_out_for_delivery`

| | |
|---|---|
| **Category** | Utility |
| **Variables** | {{1}} customer name · {{2}} plan name · {{3}} delivery person name |

**Body:**
```
Hi {{1}}, your Chotekisan {{2}} salad is out for delivery. Our delivery partner {{3}} will reach you shortly. Please keep your phone reachable.
```
**Samples:** `Priya S` · `Daily Fresh Pack` · `Ramesh K`

---

### 16. `subscription_delivered` — ⏳ CREATE  → trigger `subscription_delivered`

| | |
|---|---|
| **Category** | Utility |
| **Variables** | {{1}} customer name · {{2}} plan name |

**Body:**
```
Hi {{1}}, your Chotekisan {{2}} salad has been delivered. Enjoy your fresh, healthy meal! We would love to hear your feedback.
```
**Samples:** `Priya S` · `Daily Fresh Pack`

---

### 17. `subscription_delivery_missed` — ⏳ CREATE  → trigger `subscription_delivery_missed` (not-delivered / skipped)

| | |
|---|---|
| **Category** | Utility |
| **Variables** | {{1}} customer name · {{2}} plan name · {{3}} date |

**Body:**
```
Hi {{1}}, we are sorry — your Chotekisan {{2}} salad delivery on {{3}} could not be completed. Please contact our support team if you need any help.
```
**Samples:** `Priya S` · `Daily Fresh Pack` · `06 Aug 2026`

---

### 18. `subscription_paused_notice` — ⏳ CREATE  → trigger `subscription_paused`

| | |
|---|---|
| **Category** | Utility |
| **Variables** | {{1}} customer name · {{2}} plan name · {{3}} resume date |

**Body:**
```
Hi {{1}}, your Chotekisan {{2}} subscription has been paused until {{3}}. Your deliveries will resume automatically after that date.
```
**Samples:** `Priya S` · `Daily Fresh Pack` · `15 Aug 2026`

---

### 19. `subscription_delivery_failed` — ⏳ CREATE  → trigger `subscription_delivery_failed_company`

| | |
|---|---|
| **Category** | Utility |
| **Variables** | {{1}} customer name · {{2}} date |

**Body:**
```
Hi {{1}}, we are sorry — today's Chotekisan subscription delivery on {{2}} could not be completed due to an operational issue. We have made it right for you and apologise for the inconvenience.
```
**Samples:** `Priya S` · `06 Aug 2026`

---

### 20. `subscription_preparing` — ⏳ CREATE *(OPTIONAL — not recommended)*  → trigger `subscription_preparing`

Kitchen "preparing/prepared" fires several times per order per day. WhatsApp on
every kitchen micro-step is spammy and Meta often rejects generic "status"
templates. **Recommended: keep kitchen status on Push + Email only.** Provided
here only if the client insists.

| | |
|---|---|
| **Category** | Utility |
| **Variables** | {{1}} customer name · {{2}} plan name |

**Body:**
```
Hi {{1}}, good news — your Chotekisan {{2}} salad is now being freshly prepared and will be out for delivery soon.
```
**Samples:** `Priya S` · `Daily Fresh Pack`

---

## Other approved templates on the account (not managed by the seeder)

| Template | Used by |
|---|---|
| `coupon_offer_alert` | `coupons:send-whatsapp` daily scheduler (setting `whatsapp_coupon_template`) — 5 vars: name/code/discount/min-order/expiry, image header |
| `cravings_for_you_clone`, `daily_remainder`, `freshness`, `miss_you`, `more_than_90_daysand3orders`(+clone), `welcome_back_90plus_3ordersandless` | Manual broadcasts from Admin → Notification → Broadcast |
| `purva_blumont_event_final` | Unrelated (another brand on the same WappCloud account) |
| `order_confirmed_update_clone` | Utility twin of `order_confirmed_update` — see #2 |

## After a template gets approved

Nothing to change in code — the seeder already points each trigger at the
names above. Just confirm the approved template's variable count matches this
doc; if WappCloud/Meta altered it during review, update the trigger's
template in Admin → Notification → Templates (or the seeder) accordingly.
