Send WhatsApp Template Messages from Bitrix24 Workflow Robots

The most valuable WhatsApp message your CRM will ever send is the one that goes out the second a lead arrives — while they're still on your pricing page, phone in hand. Getting that to happen automatically from Bitrix24 takes three pieces: an approved template, a workflow robot, and correct variable mapping. Miss any one and the message either can't be sent or gets rejected by Meta before it leaves.

We build this exact machinery for Bitrix24 teams, so here's the whole path — including the failure modes that fill our support inbox.

Why templates are non-negotiable

WhatsApp's rule is simple: a business may send free-form messages only inside the 24-hour customer-service window that opens when the customer messages you. Outside that window — a new lead from an ad form, a payment reminder three days later, a delivery update — the only thing you're allowed to send is a template that Meta has reviewed and approved.

Automations almost always fire outside the window (that's the point of them). So for workflow robots, templates aren't a nice-to-have; they're the license to speak first.

One consequence people miss: this whole system exists only on the official WhatsApp Business API. If your number is connected by QR code, there's no template layer — automation works differently there. On the fence between the two? We compared them in detail in our connection guide.

Step 1: create a template that survives review

A template is a fixed message with numbered placeholders:

Hi {{1}}, thanks for your interest in {{2}}! I'm sending over the details now. Reply here if you have questions — we answer fast.

You create templates in WhatsApp Manager (or directly from your integration, if it supports submission) and pick a category:

• Utility — order updates, reminders, account notices. Cheapest per conversation, fastest review.
• Marketing — promotions, follow-ups, win-backs. Strictest review, higher price.
• Authentication — one-time codes. Special rules (and, notably, these still require a phone number even as WhatsApp shifts to usernames).

Approval usually lands in minutes. When it doesn't, it's almost always one of these:

• Miscategorized — a "utility" template that reads like a promo. Meta recategorizes or rejects.
• Variable soup — placeholders back-to-back ({{1}} {{2}} with no words between) or a template that's mostly variables. Reviewers can't tell what will be sent, so they reject it.
• Vague examples — you must supply example values; lazy ones ("text", "info") trigger rejections.
• Policy content — shortened URLs (bit.ly is a classic rejection magnet), prohibited industries, or missing opt-out language on marketing templates.

Rejections carry no penalty — fix and resubmit. What does carry a penalty is sending approved templates people report as spam: each template has a quality rating, and Meta will pause a template that annoys enough recipients. Watch that rating; a paused template silently breaks every automation built on it.

Step 2: put the robot in your pipeline

In Bitrix24, open CRM → your pipeline → Automation rules, pick the stage, and add the WhatsApp-template robot your integration registered (WASync registers one called Send WhatsApp template). Configure three things:

1. Which WhatsApp connection sends it (your official-API number).
2. Which approved template to use — you're picking from your real, live template list, so a template still in review simply isn't offered.
3. The variable mapping — the interesting part, below.

Typical placements that earn their keep:

• New lead stage → instant first touch while the lead is warm (works beautifully with Facebook Lead Ads flowing into Bitrix24)
• Invoice sent → payment reminder template, 3 days later, only if the deal hasn't moved
• Deal won → onboarding or delivery-tracking template
• Gone quiet → a re-engagement template when a deal sits in a stage for N days

Step 3: map the variables (where most real-world breakage lives)

Every {{n}} placeholder must be filled from a CRM field: {{1}} ← contact first name, {{2}} ← deal product, and so on. The robot does the merge at send time. Three rules from production experience:

1. Map every variable. A template with an unfilled placeholder is rejected at send time by the API — the automation fails quietly unless your integration surfaces the error.
2. Mind empty fields. If half your contacts have no first name, Hi , thanks for… goes out looking broken. Either ensure the field is always populated, or design templates whose variables come from fields that structurally can't be empty (deal name, product, amount).
3. Match the tone to the examples you submitted. Sending content wildly different from your approval examples is a fast route to a quality downgrade.

A fifteen-minute test protocol

Before pointing any of this at real customers:

1. Create a test lead with your own number, push it through the trigger stage, and read what actually arrives — merged variables and all.
2. Check the message landed on the deal's timeline in Bitrix24, so the team sees what the robot said.
3. Reply to it, and confirm your reply reaches Open Lines — the automation is only half the loop; a human has to catch the answer.

That last step matters more than the first two. An automation that sends but can't receive is how businesses end up ignoring hot replies from their own leads.

---

Templates are step one; the next level is AI-written replies generated from your CRM data, and multi-step chat flows. Both run on the same Bitrix24 robots — see what WASync automates.