Templates & Meta review
What a WhatsApp template is, which ones Wapify ships, and how edits go through Meta's review queue.
COD Confirmation
ApprovedAbandoned Cart
In reviewThe Templates page. It only appears once your own WhatsApp number is connected — on Wapify's shared number there is nothing to submit.
A WhatsApp template is a message whose exact wording Meta approved in advance. It is the only way to message a customer who hasn't written to you first, which makes templates the foundation everything automated in Wapify stands on.
Why templates exist
WhatsApp draws a hard line between two kinds of message. Inside the 24 hours after a customer writes to you, you can send anything. Outside it, you can only send a pre-approved template, and only the variables inside it change per customer.
A template's variables are numbered placeholders — {{1}}, {{2}} — that Wapify fills at send time with your store name, the customer's first name, the order number, the total, and so on. The surrounding words never change.
Which templates Wapify uses
Every automation has its own template, in English and Arabic, and several have more than one because a setting changes the message enough to need a separate approved version.
| Automation | Templates | Category |
|---|---|---|
| COD Confirmation | Four variants — package inspection allowed or not, each with or without the return-policy line — plus a reminder | Utility |
| Fulfillment | Two — one with a tracking button, one for shipments with no tracking link | Utility |
| Ask for review | Two — the request and the follow-up reminder, both with the product's photo | Utility |
| Cancellation reasons | One, with an in-chat feedback form | Utility |
| Upsell | Two — with and without a discount code — as a three-card product carousel | Marketing |
| Back in Stock | One, with the product photo | Marketing |
| Abandoned Cart | Four — first message and reminder, each with and without a discount code | Marketing |
Wapify picks the right variant automatically from your settings. Turning on "Mention your return policy" doesn't edit a template — it selects a different, already-approved one.
The category matters for cost and for your allowance: utility messages are cheap, marketing messages are many times more expensive. See Message limits.
On Wapify's shared number
There is nothing to do. Every template is already approved on the number, and the Templates page isn't even shown, because there would be nothing on it. Turning on an automation is the whole setup.
The one exception is COD Confirmation's Additional Information — your own paragraph and support button appended to the confirmation. That produces a custom template belonging to your store, and it does go through Meta review. While it's pending, COD messages keep going out on the standard template; the moment it's approved, yours takes over.
On your own number
Templates live on your WhatsApp Business Account, so they need Meta's approval there. Wapify handles the submission for you.
At connect time
The moment your number is connected, Wapify submits every template it needs — all automations, both languages — in the background. A banner says so and tells you that you can close the page; the job keeps running and the page updates as Meta responds. There is no "submit all" button to hunt for, because it already happened.
Reading the status
Statuses are read from Meta rather than from Wapify's own record, so the page reflects reality even if something changed on Meta's side.
Editing wording
With your own number you can rewrite any template's body text. Two rules govern it:
- Keep the same variables. The editor tells you which ones the template uses. Removing or renumbering them breaks the send, so it isn't allowed.
- The layout is fixed. Buttons, headers, footers and carousels match Wapify's approved structure — those are what the app's logic hooks into, so they aren't editable.
What happens when you submit an edit
Your change goes to Meta as a new version of the template. Crucially, your currently approved version keeps sending the whole time it's in review, so your automations never pause. When the new version is approved it takes over automatically, and outdated versions are removed from your account.
Because of this, editing a template is safe to do at any time of day. There is no window where messages stop.
Why Meta rejects templates
Rejections almost always come down to one of these:
- Promotional content in a utility template. An order-update template that tries to sell something gets recategorised or rejected.
- Variables at the very start or end of the body, or two variables in a row with no words between them.
- Placeholder-looking sample values. Meta reads the example content you supply too.
- Aggressive urgency — countdowns, "last chance", "act now" — especially in marketing templates.
- Formatting problems, such as unbalanced
*bold*markers or an over-long body.
Edit the wording and resubmit; there's no penalty for a rejection, and no limit on trying again.
WhatsApp Flows
Two of Wapify's templates carry a Flow — a short form that opens inside WhatsApp when the customer taps the button, with no browser and no leaving the chat:
- Review Survey — a star rating, an optional comment, and an optional photo. See Ask for review.
- Cancellation Feedback — a reason picker and an optional comment, used both when a customer cancels a COD order and after an order is cancelled. See Cancellation reasons.
Flows are managed entirely by Wapify. There is nothing to build or configure.
Bold text and emoji
WhatsApp's own markup works inside templates: text wrapped in asterisks renders bold in the customer's chat. Wapify uses it sparingly and deliberately — in the COD confirmation, exactly three things are bolded, because they're the three that cause a delivery to be refused at the door: the address to check, the amount to have ready, and the package-inspection policy. If you edit templates on your own number, that restraint is worth keeping: bold everything and bold stops meaning anything.