Skip to content

Area: User guide

How WhatsApp messages work

A WhatsApp message in Releva is a Meta message template: a text (optionally with an image, a button or a set of cards) that Meta reviews before anyone can send it. Releva stores the template, submits it to Meta for approval, tracks its status and sends it to the phone numbers of your profiles when a workflow runs. Templates live under Marketing Channels › WhatsApp Messages; the connection lives under Settings › Facebook & Whatsapp, tab WhatsApp.

Part Where What it does
WhatsApp Business Account (WABA) Settings › Facebook & Whatsapp › WhatsApp The Meta account and phone number Releva sends from. Without one, New Whats App Message and Import templates are disabled and the list shows Connect your WhatsApp Business Account (WABA) to enable the creation of template messages.
Template Marketing Channels › WhatsApp Messages Name, type, texts, image, buttons, merge tags and the daily-limit rule. See Create a WhatsApp template message.
Workflow Workflows, or Send on a saved template Picks the audience and the moment. A WhatsApp template is sent only from a workflow; Send on the template offers Use Existing Workflow or Create New Workflow.

Saving a template submits it to Meta for review but sends nothing to customers. Only a running workflow and Test Message send.

The Connection Method control on the WhatsApp settings tab is shown while no account is connected:

Method How it connects What Releva stores
WhatsApp Manager (default) Connect WhatsApp Business opens Meta’s embedded sign-up in a popup. Releva exchanges the result for an access token, subscribes its app to your WABA so Meta sends it delivery reports, and shows Register Phone Number with a 6-Digit PIN until the number is registered. WABA id, phone number id, token. Shown read-only as WhatsApp Business Account and Phone Number.
Business Solution Provider You paste the Auth Token, WhatsApp Business Account ID and WhatsApp Phone Number ID your provider gave you and select Save. No call to Meta or the provider is made on save. The same three values; the token is shown in clear text afterwards. See Connect WhatsApp through a Business Solution Provider.

Each template remembers the sender it was created with (WhatsApp Manager or BSP badge on the card). A template cannot be test-sent through the other sender. Disconnect WhatsApp removes the whole configuration (for WhatsApp Manager it also unsubscribes Releva from your WABA at Meta) and brings the Connection Method control back.

WhatsApp does not need the Facebook tab of the same settings page; Facebook ads, product sets and audiences do, see Connect your Meta account to Releva.

Type Parts Notes
Text-Based Header (up to 60 characters), Message (up to 1024), Footer (up to 60, no merge tags) The only type with a text header.
Media-Based Image URL (JPEG, JPG or PNG; Browse opens your Files), Message, Footer, optional Button Text with Button URL The image is the header. Button text and URL must be set together.
Carousel Message, 2 to 10 Cards, each with an image, a Card Body (up to 160 characters) and a button The card count is fixed once the template is created. Button text is limited to 25 characters.

Media and carousel templates have a Mode: Static (you provide the image and URL) or Recommender (Releva fills {{product.*}} tags from a Product Feed per recipient; a sample product from the feed is sent to Meta for approval). See How product feeds work. Name, type and mode are locked after the first save.

Saving a new template uploads its media to Meta and creates the template there (through your provider for BSP accounts). Meta answers with the template id, its status and its category (always MARKETING for templates created in Releva). If Meta rejects the request, nothing is saved in Releva.

Status badge Meaning In Releva
PENDING Meta is reviewing the template Buttons, URLs, image and footer are locked; Save is disabled; test sends answer The WhatsApp template message is pending. Please try again later.; workflow sends are skipped.
APPROVED Meta accepted it Can be edited, test-sent and sent by workflows.
REJECTED Meta refused it Can be edited and saved again; the change is sent to Meta.
PAUSED Meta paused it for low quality Can be edited; sends are skipped until Meta approves it again.

Status, quality and category changes reach Releva through a Meta webhook (see How delivery reports and status changes reach Releva). As a safety net Releva also asks Meta for the state of every template once an hour, so a missed webhook corrects itself within the hour. When a quality score is set, it shows as a badge on the card.

Editing an approved template sends the change to Meta again. Deleting one deletes it at Meta too; if Meta does not confirm, Releva answers Deleting was unsuccessful, try again later! and keeps the template.

Import templates on the list opens Import WhatsApp templates from Meta with the templates in your WABA (Name, Lang, Category, Status, Mode). Up to 50 templates per import. Templates that are already imported, have no body or are carousels are marked and skipped. A template with a button URL is not imported as is: Releva creates a copy named <name>_releva with Releva’s click-tracking URL and submits it to Meta for review, and your original stays untouched.

The message is a Handlebars template. Merge Tags lists every tag with its Pattern and Label: profile fields such as {{firstName}}, {{lastName}}, {{email}}, {{phoneNumber}}, links such as {{unsubscribeLink}} and {{subscriptionManagementLink}}, your custom profile fields, dynamic coupon lists (see How dynamic coupons work) and, in recommender mode, {{product.*}} tags.

Meta’s rules apply on top of Releva’s:

  • A body or card body cannot start or end with a merge tag. The form shows Body cannot start or end with a merge tag — Meta rejects this for all template bodies. Add text before/after the tag.
  • {{product.*}} tags are allowed only in recommender mode: Body contains {{product.}} tags but recommender mode is not enabled. Remove them or switch to recommender mode.*
  • No merge tags in the Footer.
  • A broken tag shows Invalid merge tag: Parse error on line 1: … and disables Save.

Each merge tag becomes a numbered {{1}}, {{2}} placeholder in the template Meta approves. Releva fills the placeholders per recipient at send time.

When a workflow step with a WhatsApp message runs, Releva checks that the template is APPROVED and that the shop’s WhatsApp service is not disabled, loads the profiles that match the step’s audience, keeps those with a phone number and dedupes them per phone number so nobody gets the same message twice from one run. Profiles without an unsubscribe link of their own are skipped when the shop runs external subscription management without a fallback link. See How consent works in Releva and How profiles work.

Button links are replaced by Releva’s click-tracking link, which needs the shop’s click-tracking domain (CNAME) to be set up; without it the whole send is quietly refused.

Each shop has a maximum number of WhatsApp messages one profile may receive per day (3 by default, set under Settings › Messaging; the form links to it as shop settings page). The template decides what happens to a profile that already reached it:

Setting What happens
Reschedule (default) The profile is left out of this run and the step is queued again for the next allowed slot at least 24 hours later. Max Reschedules (1 to 10, default 3) caps the retries.
Skip sending The profile is left out; no retry.

There is no Send anyway for WhatsApp. The form notes that the setting applies only when the message is used in continuous campaigns or workflows.

Test Message on the form is enabled once the template is saved and the form is valid. It opens a window with Send to (phone numbers in international format with +<countryCode>, separated by commas, prefilled with your own number), Profile to impersonate and Trigger event, and sends the template for real through your sender. The server refuses templates that are not APPROVED and templates whose sender differs from the connected account.

Each card on the list shows, for the selected period (30 days by default): Sent, Delivered (% of sent), Opened (% of delivered), Clicks (% of delivered), Conversions (% of clicks), Purchases (% of conversions), Revenue and Bounces (% of sent). The people icon next to a number opens a new segment of the profiles behind it. Statistics on the card opens a daily chart for one template.

Delivered, Opened and Bounces come from Meta’s status reports. Opened counts read receipts, which depend on the recipient’s privacy settings, so it undercounts.

How delivery reports and status changes reach Releva

Section titled “How delivery reports and status changes reach Releva”

Meta posts callbacks to Releva’s webhook, POST /api/v0/whatsapp/webhooks. You never call it yourself: Releva subscribes its app to your WABA when you connect through WhatsApp Manager; a BSP forwards Meta’s callbacks for you.

  • A message status (delivered, read, failed, deleted) for a message Releva sent in the last 7 days becomes a delivery, open, bounce or deleted event on the profile and feeds the statistics. Failures with Meta error codes 131009, 131047, 131049 and 131056 are recorded as soft bounces; 131021, 131026 and 131050 as hard bounces. Statuses for messages Releva did not send (for example test messages) are ignored.
  • A template status, quality or category update changes the badge on every shop connected to that WABA.
  • Duplicate callbacks within 24 hours are dropped.