Reopening the 24-hour WhatsApp conversation window, or sending an order update, requires a Meta-approved message template. 3650HQ lets you create a template, submit it to Meta, and see its approval status sync back, all in one place, instead of guessing.
3650HQ manages the full template lifecycle (create, submit, sync status, send), but approval itself is Meta's decision, not 3650HQ's. Rejections are usually about category mismatch, promotional language in a utility template, or missing variable examples.
WhatsApp draws a hard line between replying to a customer and contacting one. When someone messages you, a 24-hour window opens in which you can reply freely, in your own words, as many times as the conversation needs. When that window closes, free-form outbound stops working.
Reaching someone outside it requires a template: a message written in advance and approved by Meta before it can ever be sent. That covers most of what a business actually needs to send on its own initiative, from an order update to a delivery notification to a promotion.
This is the mechanism that makes WhatsApp usable as a business channel rather than a spam channel, and it is not optional or negotiable. Any tool that claims to send arbitrary outbound WhatsApp messages to cold recipients is not working around the rule, it is breaking it with your number.
Template management is usually split across Meta's Business Manager and whatever tool actually sends the messages, which means writing a template in one place, waiting without visibility, and discovering the outcome somewhere else. 3650HQ keeps the whole loop together.
Write the template and define its variables where you will eventually use it, rather than in a separate console.
Submission goes from the same screen. There is no exporting or re-entering it into Business Manager.
Approval state is pulled back in, so a template's status is something you can look up rather than something you check by trying to send it and seeing what happens.
A rejected template comes back with the reason attached, which is the difference between fixing it in one attempt and resubmitting variations until something sticks.
An approved template can be sent into a single conversation from the inbox, or used as the payload for a bulk campaign with per-recipient variables.
Meta sorts templates into utility, marketing and authentication, and the category is a claim about what the message is for rather than a label you choose for convenience.
Messages about a transaction that is already happening: an order confirmation, a shipping update, a payment receipt. Tied to something the customer initiated.
Anything promotional. Offers, launches, re-engagement, announcements. Broader in what it allows and priced differently from utility.
One-time passcodes and verification codes, with their own constrained format.
The most common reason a template is rejected is promotional language inside a utility template. A discount mentioned in an order update makes it marketing, and submitting it as utility is asking Meta to accept a claim that does not match the text. Missing variable examples is the other frequent cause: Meta reviews the template filled in, so a variable without a sample is a template it cannot properly assess.
3650HQ manages creation, submission, status and sending. It does not approve templates, cannot accelerate a review, and has no influence over the outcome. Approval is Meta's decision, review times vary, and any tool promising guaranteed or instant approval is describing something it does not control.
What is worth optimising is the number of round trips. Most of the delay in getting a template live is not Meta's review, it is the days lost between a rejection you did not notice and a resubmission that guessed at the cause. Keeping the reason attached to the template is what shortens that.
The most common reasons are a category mismatch (e.g. promotional language in a 'utility' template), unclear or missing variable examples, or wording that reads as spam. 3650HQ shows the status Meta returns so you can see and fix the issue.
It varies by submission, typically from minutes to about a day. 3650HQ syncs the approval status automatically so you don't have to keep checking Meta Business Manager.
Utility templates are for order/account updates, marketing templates are for promotions, and authentication templates are for one-time codes. Meta reviews each category differently, and using the wrong one is a common cause of rejection.
Yes. Once approved, a template can be used for a single reply or a bulk campaign to a CSV list.
When a customer messages you, a 24-hour window opens in which you can reply freely in your own words. Once it closes, reaching them requires a pre-approved template. Templates are what make outbound-outside-the-window possible at all.
No. Creating a template, submitting it for approval, seeing the status come back and sending it all happen in 3650HQ rather than being split between two tools.
Yes. The rejection reason comes back with the template, which is usually the difference between one corrected resubmission and several guesses.
No. Approval is entirely Meta's decision and no tool can speed up or guarantee it. What 3650HQ reduces is the wasted time between a rejection and a corrected resubmission.