# How Viber messages work

> What a Viber message is in Releva, Marketing versus Transactional scope, Text versus Multimedia mode, who receives it, merge tags and link shortening, the daily limit, Viber transactional templates per provider, test messages and statistics.

A **Viber message** is a saved piece of content that Releva sends to the phone numbers of your profiles through the Viber provider set up for your shop. The message holds the text, an optional button and image, a scope, and a daily-limit rule. Who gets it and when is decided by the workflow that uses it. Viber messages live under **Marketing Channels › Viber Messages**.

## Three parts: provider, message, workflow

| Part         | Where                                            | What it does                                                                                                                                                                                                                                                                                                       |
| ------------ | ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Provider** | **Settings › Messaging**, tab **Viber Messages** | The gateway Releva sends through: **Mobica**, **Routee** or **Link Mobility**, with your credentials (Routee also asks for a **Viber Sender Id**). Without one, **New Viber Message** is disabled and the list shows *Please fill in your Viber Message credentials because we cannot send messages without them!* |
| **Message**  | **Marketing Channels › Viber Messages**          | Name, **Scope**, **Mode**, text, optional button and image, and **If max viber messages per day is reached**. See [Create a Viber message](https://releva.ai/documentation/guides/viber/create-a-viber-message/).                                                                                                                   |
| **Workflow** | **Workflows**, or **Send** on the message        | Picks the audience and the moment. **Send** opens a window with one tab, **Workflow**, where you pick an existing workflow or create a **One Off**, **Continuous** or **Triggered** one; campaigns are not offered there.                                                                                          |

Saving a message makes no call to the provider. Only a launched workflow and **Test Message** send.

## Scope: Marketing or Transactional

| Scope                   | Use it for                                                    | What changes                                                                                                                                                                                                                                                                                                                                                                                                 |
| ----------------------- | ------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Marketing** (default) | Offers, news, product recommendations                         | **Mode** can be **Text** or **Multimedia**.                                                                                                                                                                                                                                                                                                                                                                  |
| **Transactional**       | Order, booking and account notifications the customer expects | **Mode** is locked to **Text** (*Transactional messages are text-only buttons and images are available only for Marketing messages.*). A **Viber template** row appears when the provider supports templates. The server rejects a transactional message with a button or image: *Transactional Viber messages must be text-only. Remove the button and image - those are available for Marketing messages.* |

The scope is fixed after the first save. To change it, select **Make a copy** and set the scope on the copy.

## Mode: Text or Multimedia

**Text** sends the message body only. **Multimedia** adds **Button Text**, **Button URL** and **Image URL** (JPEG, JPG or PNG; 400x400 recommended; **Browse** picks a file from **Assets**), and a **Type**:

* **Message**: the same content for every recipient. Button text and URL go together: *Button Text is required when Button URL is provided.* and the reverse. The URL must be a full address or a merge tag.
* **Recommender**: one product per recipient from a **Product Feed** (feeds of scope marketing channels; see [How product feeds work](https://releva.ai/documentation/learn/product-feeds/how-product-feeds-work/)). Selecting it pre-fills **Shop Now**, `{{product.url}}`, `{{product.imageUrl}}` and a sample text, and adds product tags such as `{{product.name}}` and `{{formatPrice product "price"}}` to **Merge Tags**. The limit drops to 5000 characters and a feed is required to save. A recipient for whom the feed returns no product is skipped.

The mode and type are fixed after the first save.

## Who receives a Viber message

When a workflow step runs, Releva loads the profiles that match the workflow’s audience and keeps only those that:

* have a phone number;
* are subscribed, when the workflow runs in the marketing scope (see [How consent works in Releva](https://releva.ai/documentation/learn/consent/how-consent-works-in-releva/));
* have no hard bounce recorded for Viber, and no soft bounce in the last 14 days;
* did not receive this message from this workflow step already (the same phone number is never sent twice in one run);
* have an unsubscribe link of their own, on shops that manage subscriptions externally without a fallback link.

Profiles that fail these checks are left out silently.

## Merge tags, links and length

The message is a [Handlebars](https://handlebarsjs.com/) template. **Merge Tags** lists every tag with its **Pattern** and **Label**: profile fields such as `{{firstName}}` and `{{phoneNumber}}`, links such as `{{unsubscribeLink}}`, `{{subscriptionManagementLink}}` and `{{loyaltyLink}}`, your custom profile fields, dynamic coupon lists (see [How dynamic coupons work](https://releva.ai/documentation/learn/dynamic-coupons/how-dynamic-coupons-work/)), survey links, `{{md5 phoneNumber}}` and, in triggered workflows, the trigger event’s fields. The form checks the template as you type: a broken tag shows *Invalid merge tag: …* and disables **Save** and **Test Message**; the server rejects the same text with *Message body is not a valid Handlebars template: …*.

Every `http://` or `https://` link in the text is replaced at send time by a short tracking link, so clicks and purchases are attributed to the message. The **Preview** on the form is fetched from the server and shows the shortened text, which is why its length can differ from what you typed. The limit is 7000 characters (5000 for a Recommender); emojis count.

## The daily limit

Each shop has a maximum number of Viber messages one profile may receive per day (3 by default, 1 to 10, under **Settings › Messaging**, tab **Viber Messages**). The message 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 at least 24 hours later. **Max Reschedules** (1 to 10, default 3) is the number of retries. |
| **Send anyway**          | The limit is ignored for this message.                                                                                                                       |
| **Skip sending**         | The profile is left out; no retry.                                                                                                                           |

The form notes that this setting only applies when the message is used in continuous campaigns or workflows. Rescheduled and skipped profiles are recorded as events on the profile.

## Viber transactional templates

From 15 July 2026 Viber requires an approved template for transactional messages; otherwise they are billed as promotional. Releva still sends a transactional message without an approved template, as plain text, and logs a warning. Once a template is **APPROVED**, sends use the template ID and its variables instead of the raw text.

Before a template is generated or submitted, Releva checks the text (each failure is shown under the **Viber template** row):

* It must start and end with static text, not a variable: *The message must start with static text, not a variable.* / *The message must end with static text, not a variable - add a closing word or sentence after the last variable.*
* At most 1000 characters and at most 8 variables, each with a name of at most 50 characters.
* Only simple fields such as `{{firstName}}`; Handlebars helpers are not allowed.
* No `{{unsubscribeLink}}`, `{{subscribeLink}}`, `{{subscriptionManagementLink}}`, `{{loyaltyLink}}` or `{{unsubscribeLinkOneClick}}`: Viber forbids URLs as variable values.
* Literal links and URL-valued tags become a tracked short-link variable, and a link cannot be the last element.

How the template reaches the provider depends on it:

| Provider                      | On the form                                                                                                                                                                                                                               | Status                                                                                                                             |
| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| **Mobica**                    | **Generate template text** builds the text in Mobica’s `{variable}` syntax (for example `{custom_orderId}` for `{{custom.orderId}}`). You create it in the Mobica portal, enter the numeric **Template ID** and select **Link template**. | Linking asks Mobica for the status. At send time each variable value is cut to 125 characters.                                     |
| **Routee**, **Link Mobility** | A language picker (40 Viber locales, default **English**) and one button, **Save & submit for approval**, which saves and submits in one go.                                                                                              | **PENDING** until the provider’s callback or **Refresh status** reports **APPROVED** or **REJECTED** (with *Rejected: \<reason>*). |

Editing the text or the language of a submitted template clears it, so the message must be submitted again. A **PENDING** or **APPROVED** template locks the **Message** field; use **Make a copy** to write a new version. Deleting a message also deletes its Routee or Link Mobility template. See [Create a transactional Viber message](https://releva.ai/documentation/guides/viber/create-a-transactional-viber-message/).

## Test messages

**Test Message** on the form sends the message for real, through your provider, to one or more numbers in international format (`+359…`), separated by commas; the field is prefilled with your own number. You can pick a **Profile to impersonate** (email, phone number or profile id) so the merge tags render with that profile’s data, and a **Trigger event** for triggered workflows. The button is disabled while the form is invalid. If the provider rejects the message, the form shows *Viber message delivery failed: \<provider text> (code \<n>)*; a Recommender with no product for the impersonated profile shows *No products could be found for this combination of product feed and user to impersonate. …*

## Statistics

Each card on the list shows, for the selected period (30 days by default): **Sent**, **Delivered** (% of sent), **Opened** (% of delivered), **Clicks** (% of opened), **Conversions** (% of clicks), **Purchases** (% of conversions), **Revenue**, **Unsubscribes** (% of sent) and **Bounces**. The people icon next to a number opens a new segment of the profiles behind it. **Statistics** on a card opens the daily chart for one message (7 days by default; *No data available for the selected period* when empty), and **Export** on the list creates a report of all messages. Transactional cards also show the template status badge.

Delivered and Bounces come from the delivery reports your provider posts to Releva.

## Deleting and copying

**Make a copy** opens a new form named **Copy of \<name>** with the same content. **Delete** asks *Are you sure?* and warns: *Please verify that this Viber Message is not part of any workflows or campaigns before proceeding with deletion. This action cannot be undone!* Releva does not check this for you.

## Next steps

* [Create a Viber message](https://releva.ai/documentation/guides/viber/create-a-viber-message/): Write and save a marketing Viber message.
* [Create a transactional Viber message](https://releva.ai/documentation/guides/viber/create-a-transactional-viber-message/): Prepare a message and template that Viber bills as transactional.
* [How consent works in Releva](https://releva.ai/documentation/learn/consent/how-consent-works-in-releva/): Learn which customers can receive marketing messages.
* [How SMS work](https://releva.ai/documentation/learn/sms/how-sms-work/): Compare Viber with SMS for the same audience.