Request my free trial
Help center

Automations

The safeguards: caps and quiet hours

How many messages a customer can receive each day and each week, the quiet hours, and where to change these settings.

The safeguards keep you from bothering your customers: they limit the number of messages per customer and block sending at night. By default: at most 1 message a day and 3 a week per customer, and quiet hours from 8pm to 9am.

This feature is part of the Pro plan. On the Essential plan, the screen shows "Automatic messages: available with Pro"; the owner can switch from Settings › Subscription › Upgrade to Pro (immediate, prorated).

Changing the settings

  1. Open Automations.
  2. In the Safeguards banner at the top of the page, click Adjust.
  3. In the Anti-spam safeguards window, choose:
  • Per day, at most: 1, 2 or 3 messages;
  • Per week, at most: from 1 to 5 messages, or 7;
  • Quiet from and Until: the hours with no sending.
  1. Click Save. The message Safeguards saved confirms.

The time zone in use is shown at the bottom of the window (for example Europe/Paris).

How the caps are counted

  • Per customer, across all messages: Wallet card and email.
  • "Per day" means over the last 24 hours, "per week" over the last 7 days.
  • Campaigns count: if a customer received a campaign this morning, a promotional automation due in the afternoon will be held back (daily cap).
  • A campaign itself goes out the moment you click Send, without waiting for the quiet hours to end. So choose the time with care.
  • A campaign is never held back by the caps: your messages written in Messages (email or card notification) go to every customer who gave consent, even at night. The only exception, set by Google: at most 3 notifications per card per 24 hours; beyond that, the message shows on the card without an alert.

The quiet hours

A message due during the quiet hours is not deleted: it is postponed to just after they end. In the Latest messages log it appears as Scheduled, with the sending time planned for it.

Programme messages always go out

Messages tied to the programme (labelled "programme", for example Reward unlocked) are not counted towards the caps and are not blocked by the quiet hours. That way the customer learns straight away that a reward is waiting.

The other limits

Each automation also has limits of its own, under Adjust → Limits:

  • Not twice to the same customer within: a number of days;
  • Once per customer only;
  • Sending frequency: Active, Balanced (recommended) or Cautious. The more cautious it is, the fussier Fidélitas is about the timing (customer close to their reward, no message received recently…): messages judged to be of little relevance are held back.

Good to know

A message stopped by a safeguard appears as Held back in the log, with the reason. See Messages held back or scheduled.

Updated on 30 October 2026

Was this article helpful?

In the same section

Can't find the answer?

Already a customer? Click “Aide” in your merchant space: the assistant checks your account, and a human takes over if needed.

Write to us

Your cookies, your choice. Only cookies the site needs, cookie-free audience measurement, no advertising cookies. Privacy policy ·