L
LoyaltyDocs

Notifications

WhatsApp notifications for credits and debits — the events, the templates, the live details a message can carry, and delivery schedules

Every confirmed earning or redemption can message the customer on WhatsApp. The platform writes the message the moment the transaction completes; your setup decides which template carries it, what it says, exactly when it is allowed to arrive — and whether it goes out by itself or when your till says so.

How It Works

  1. A transaction is confirmed — the platform prepares its message.
  2. The message is sent — automatically as part of the confirmation when Message the member is on, or when your till triggers it (send notification) — or not at all, for moments not worth a message.
  3. The platform delivers on WhatsApp, inside the delivery schedule you configured for that event.

Once, and only for real events

Each message can be sent exactly once, and only for a transaction that actually completed. A repeat trigger is refused; an unconfirmed transaction has nothing to send.

Automatic or Triggered?

Choice

Where

Effect

Tenant default

Settings → Redemption → Message the member

Every confirmation sends its message without a second call

Per call

The auto_send_notification field on the confirm call

Overrides the tenant default for that one transaction

Neither

—

The till triggers the message when it wants to, within the transaction's window

The Moments You Can Configure — Settings → Notifications

Each loyalty event gets its own section, with its own template and delivery schedule. Add an event announces one that is not listed yet; an event with no message sends nothing — the clean way to keep that moment silent.

Event

Fires when

Points earned at the counter

An accrual from a till, the app or your systems is confirmed

Points earned from an uploaded sheet

An accrual loaded from a bulk upload is confirmed

Points redeemed

A redemption is confirmed

Points expiring soon

A scheduled reminder, set up with your account team, finds points approaching their use-by date

Per Event: the Message

  • Message — which approved WhatsApp template goes out: a warm one for earning, a receipt-style one for spending, an urgent one for expiry.
  • Fixed wording can be merged in: your brand name, a store name, a support number — set once, appears in every message of that event.
  • Live details fill in automatically per message — the full list is below. The page warns if a template uses a variable loyalty cannot fill; it would arrive blank.

Per Event: the Delivery Schedule

Option

What you choose

Days it may go out

Each of the seven days individually, or Every day / Weekdays only

Any time of day

On — the message goes out the moment it is triggered, typical for transactional confirmations / off — hold messages to a window so members are not messaged at night

Send between

A From and To time, local time, for each allowed day — 09:00 to 21:00 by default

What happens outside the window: the message is not lost — it is held and delivered when the schedule next opens. A redemption confirmed at 11 PM with a 9 AM–9 PM window arrives at 9 AM the next allowed day. Only if no upcoming slot exists at all is the message dropped.

Different schedules for different tones

Run transactional confirmations any-time, and put business-hours windows on marketing-flavored messages like expiry reminders — each event's schedule is independent.

What the Message Can Say

Templates can weave in live details from the transaction — reference them by these names when your team designs the template.

Variable

Detail

Example use

points_earned

Points earned

“You just earned 120 points!”

points_redeemed

Points spent

“You redeemed 200 points.”

remaining_balance

Balance after

“415 points left.” — looked up live if the transaction did not carry it

bill_no

The bill reference

“…on bill #1001” — the same reference your till used

points_expiring

Points about to expire

“150 points expire soon…”

expiry_date

The expiry date

“…on 30-06-2026”

action_date

Transaction date

Day-month-year, e.g. 11-06-2026

action_time

Transaction time

Date with time, e.g. 11-06-2026 04 32 PM

Putting It Together — an Example Setup

Event

Template

Fixed wording

Schedule

Points earned at the counter

“You earned points!”

Brand name

Any time

Points redeemed

“Redemption receipt”

Store name, support number

Any time

Points earned from an uploaded sheet

“Points added to your account”

Brand name

Mon–Sat, 9:00–21:00

Points expiring soon

“Don't lose your points”

Brand name

Mon–Fri, 10:00–19:00

For developers

Templates are mapped per event with [update notification templates](https://prod.freecustomer.in/api/v2/docs#tag/loyalty/PATCH/api/v2/loyalty/configuration/notifications) — send only the events you are changing; a `null` template removes an event's mapping.

Was this page helpful?

Last updated on

On this page