WhatsApp has one rule that shapes everything else: you may write freely to someone for 24 hours after they message you, and outside that window you may only send a template that Meta has approved. The WhatsApp templates screen is where you get those approvals, and where you tell Finocket what Meta charges you so it can keep an eye on the bill.
Submit a template and watch it get approved
Create the template in Campaigns with the channel set to WhatsApp, then open the WhatsApp templates screen and tap Submit to Meta. Finocket hands it over, records that Meta is reviewing it, and shows the exact time it last asked.
Reviews usually finish within a day. Tap Refresh status to ask again. Meta can answer in five ways, and the screen tells you what each one means for you:
- Approved — ready to send, including to people who haven't messaged you recently.
- Waiting on Meta — submitted, no answer yet.
- Rejected — Meta's own reason is shown word for word. Edit the wording and submit again.
- Paused — Meta paused it after negative feedback from recipients. It cannot send until Meta lifts the pause.
- Disabled — Meta removed it. Create a replacement.
Every one of those states came from Meta. Finocket never marks a template approved on its own, and a template you haven't submitted says “not submitted” rather than pretending to be in a queue.
Write the body the way WhatsApp wants it
WhatsApp only accepts numbered placeholders — {{1}}, {{2}} — not named ones. If your body contains something like {{first_name}}, Finocket refuses the submission and lists the tokens to change. It deliberately doesn't renumber them for you: you should know exactly what went to Meta's reviewers.
You need your own WhatsApp connection
Templates are approved by Meta, not by Finocket, so this screen needs your workspace's own WhatsApp Business connection — Meta Cloud API or 360dialog — set up under Integrations. Until one is connected the screen says so plainly and submits nothing.
Sending inside the 24-hour window still works without any of this: when a customer messages you, you can reply from the app for the next 24 hours.
What WhatsApp costs, and a limit you set
Meta charges per message, and the price depends on the kind of conversation: marketing, utility (order updates and reminders), authentication (one-time passcodes) or service (your replies inside a conversation the customer started).
Finocket does not guess those prices. They differ by country, by category, by provider and by whatever you negotiated, and Meta has re-cut them more than once. Copy the numbers from your own Meta or provider rate card into the cost panel, and from then on every WhatsApp send is costed and added up for the month.
Set a monthly limit and Finocket holds back any send that would take you past it. That refusal is recorded in your message log as blocked, with the reason — the same way a consent block is recorded. Nothing is dropped silently, and blocked messages cost nothing so they never count towards the month.
If you haven't entered rates, nothing is held back: Finocket won't block your messaging over a price it doesn't know.
Delivered, read, and what that changes
When WhatsApp tells Finocket that a message was delivered or read, that now flows all the way through to your message log and to the Engagement report. A WhatsApp read receipt is the most trustworthy engagement signal in the product — unlike an email open, nothing fabricates it: no privacy proxy, no company mail scanner. If your contacts read WhatsApp and ignore email, the heatmap will now show you that.
Consent still decides
An approved template is permission from Meta, not from your customer. Every WhatsApp message still goes through the same consent checkpoint as everything else: someone who replied STOP is not messaged, whatever the template says. See Outreach and consent for how that works.