How to create, submit, and send a WhatsApp template in Zoho CRM, from the Template Submission Portal through Meta approval to your first automated send.
You can’t just type a message and hit send on a WhatsApp template in Zoho CRM. Every template goes through Meta’s approval queue first, and the fields you fill in along the way (category, variables, footer, buttons) decide whether that approval takes a day or gets rejected outright. Here’s the process from opening the Template Submission Portal to sending your first approved template, plus the mistakes that get templates bounced back.
A WhatsApp Business Platform rule sits underneath all of this: once more than 24 hours have passed since a customer last messaged you, you can’t just send them a free-form message. Anything outside that window has to be a pre-approved template. Zoho CRM’s WhatsApp channel builds template creation and submission into the CRM itself so you’re not jumping into Meta’s separate WhatsApp Manager to do it, though the template still gets reviewed by Meta on the other end.
That matters for two very different situations: sending an automated “your order shipped” notification the moment a deal record changes stage, and sending a “we haven’t heard from you” nudge to a lead who went quiet three days ago. Neither is possible without an approved template sitting behind it.
WhatsApp needs to already be connected under Settings → Channels → WhatsApp in your Zoho CRM account, with your business verified through Meta Business Manager. If you haven’t done that part yet, our full walkthrough of Zoho’s WhatsApp CRM integration covers connecting the channel from scratch. Everything below assumes that connection already exists.
From Zoho CRM, go to the WhatsApp settings and open the Template Submission Portal. This is the screen Zoho built specifically for creating and submitting templates without leaving the CRM; it talks to Meta’s WhatsApp Manager behind the scenes, so a template you build here is the same one that shows up for review on Meta’s side.
Click Create Template (or + New Template, depending on your Zoho edition) to start a fresh one.
Give the template a name using lowercase letters, numbers, and underscores only; Zoho and Meta both reject spaces or special characters here. Pick the language your customers will actually read it in.
Then choose a category, and this is the choice that decides how strict the review is:
Utility covers transactional, account-related messages a customer would expect because of something they already did: order confirmations, appointment reminders, shipping updates. This is the easiest category to get approved and the one most CRM notifications fall under.
Marketing covers anything promotional or re-engagement focused: a discount code, a “check out our new stock” nudge, a win-back message to a cold lead. Marketing templates get reviewed more strictly and are the category Meta bumps a template into automatically if it decides your content reads as promotional, regardless of what you selected. Since April 2025, a template you submit as Utility that Meta judges to be promotional gets approved as Marketing instead, not rejected outright, so don’t assume tagging something “Utility” guarantees it stays there.
Authentication is narrowest of all, built specifically for one-time passcodes and login verification, with a rigid format Meta enforces closely. Most CRM use cases won’t need this category.
Picking the wrong category on purpose to dodge marketing review is the single fastest way to get a template rejected or recategorized. Pick the one that honestly matches what the message does.
The body is the only required part, and it caps out at 1,024 characters. Everything else is optional but shapes how the message actually looks in a customer’s chat.
Header is a single line above the body: plain text, or an image, video, or document if you want the template to open with media rather than words. Body is the main message text, and this is where variables go if you want the template to pull in a name, order number, or date at send time. Zoho follows Meta’s numbered-placeholder format, so you’d write something like “Hi {{1}}, your order #{{2}} has shipped” and map {{1}} and {{2}} to CRM fields (say, Contact Name and Deal Name) when you actually send it. Footer is a short line of fixed text under the body, commonly used for something like a company name or a one-line disclaimer, and it can’t contain variables. Buttons let you add a call-to-action link, a phone number, or up to a few quick-reply options a customer can tap instead of typing a response.
Keep the variable count reasonable. A template stuffed with five or six placeholders and almost no fixed text reads to Meta’s review system as an attempt to disguise a generic marketing blast as something personalized, and that’s a common rejection reason on its own.
Once the template looks right in the preview pane, submit it. From here it moves out of Zoho’s hands and into Meta’s review queue; Zoho isn’t the one approving or rejecting it, it’s just the interface you used to build and send it in.
Back in the Template Submission Portal, every template sits in one of three states. Pending means it’s still in Meta’s queue; this typically clears within a day, sometimes faster, sometimes slower depending on how backed up review is. Approved means it’s ready to use anywhere in the CRM. Rejected means Meta didn’t approve it as submitted, and Zoho shows the template in this state rather than just deleting it so you can edit and resubmit rather than starting over from a blank template.
If a template comes back rejected, the fastest fix is usually loosening or removing whatever made it read as generic spam: too many variables, a header that doesn’t match the body’s actual purpose, or wording that leans promotional under a Utility category. Rewrite and resubmit rather than trying to appeal a specific rejection, since a straightforward resubmission is usually faster.
Once a template shows Approved, you can send it two ways. From a Contact, Lead, or Deal record, open the WhatsApp panel, pick the template from the list, fill in any variables for that specific record, and send. For anything automated, go to Automation → Workflows (or Blueprints, or CommandCenter, depending on what you’re building), add a WhatsApp Notification action, and select the approved template there; the trigger you set, a status change, a new lead, a scheduled reminder, fires the template automatically with the record’s own field values filling the variables.
Only approved templates show up as selectable in either place. A pending or rejected template simply won’t appear as an option until Meta clears it.
A few patterns account for most rejections. Marketing content submitted under Utility to dodge the stricter review, as covered above. Variables placed at the very start of the body with no other text around them, which reads as a placeholder-only message rather than a real one. Broken or inconsistent variable numbering, like using {{1}} and {{3}} without a {{2}}. And template names or content in a language that doesn’t match the language selected for the template. None of these take long to fix once you know to look for them; they just aren’t obvious the first time through.
Everything above happens because Zoho’s WhatsApp channel runs on the official WhatsApp Business Platform, where Meta’s template rule applies to every message sent outside that 24-hour window. That’s not a Zoho limitation, it’s how the Business Platform works for any CRM connected to it.
The Chat Quotient takes a different route entirely. It’s a standalone WhatsApp CRM built as a Chrome extension that runs directly inside WhatsApp Web, on the number you already use day to day. It is not a Zoho integration, plugin, or add-on, and it does not send messages through Zoho CRM or sync with it in any way. Because it doesn’t connect through the Business Platform, there’s no template category to pick, no Meta review queue to sit in, and no rejected-template loop to debug. Its Campaign tool sends templated messages to a contact list built from a CSV upload, a WhatsApp Label, a group, or a pasted list, spaced out with randomized intervals and a daily send limit rather than gated behind approval, with opt-out contacts automatically excluded from future sends.
That’s a real trade, not a strictly better one. Zoho’s route gets you the official green-tick-eligible Business Platform and delivery through Meta’s own infrastructure, along with the review process that comes with it. The Chat Quotient skips the review process because it isn’t running through that infrastructure at all, which is a fit for a team that finds Meta’s template queue slower than the actual sending it’s trying to do. For the fuller comparison between the two paths, including cost, see our complete guide to Zoho’s WhatsApp CRM integration.
How long does WhatsApp template approval take in Zoho CRM? Most templates clear Meta’s review within a day. It can be faster, and it can take longer if Meta’s review queue is backed up or the template needs a second look after a rejection.
Why was my WhatsApp template rejected in Zoho CRM? The most common reasons are marketing content submitted under the Utility category, too many variables with too little surrounding text, inconsistent variable numbering, or content that doesn’t match the selected language. Zoho keeps rejected templates editable so you can fix the issue and resubmit rather than starting over.
Can I send a WhatsApp template in Zoho CRM without it being approved? No. Only templates showing an Approved status appear as selectable options when sending from a record or setting up a Workflow action. Pending and rejected templates aren’t usable.
Can I edit an approved WhatsApp template later? Editing an approved template typically sends it back through review as a new version, since Meta re-checks any change to the content. It’s not an instant edit the way updating a CRM field is.
Does The Chat Quotient send WhatsApp templates through Zoho CRM? No. The Chat Quotient is a standalone WhatsApp CRM that runs on WhatsApp Web itself. It doesn’t send messages through Zoho, sync with it, or require Meta’s template approval process; its Campaign tool sends templated messages through its own mechanism instead.
Sending a WhatsApp template in Zoho CRM comes down to six steps: connect the channel, open the Template Submission Portal, pick a category honestly, build the header and body within the 1,024-character limit, submit, and wait for Meta’s approval before it’s usable. The category choice and variable count are what most rejections trace back to, so getting those right the first time saves a resubmission cycle. For teams who’d rather skip the approval queue altogether, that’s the specific gap a standalone tool like The Chat Quotient is built to fill.
Install The Chat Quotient and turn that chat into a tracked lead, a faster reply, and — eventually — a closed deal. Free to start, right inside the WhatsApp Web you already use.
