A Held back message has not gone out, deliberately, for a reason shown next to it. A Scheduled message will go out later, at the time given. You see them in Automations, in the Latest messages table. Click a row to see the detail, including the relevance score out of 100.
"Scheduled"
The message is waiting for:
- the Send after delay (3 hours after the visit, for example);
- the end of the quiet hours (see The safeguards);
- or the best moment for this customer, close to the time they usually come in.
At the moment of sending, everything is checked again: the message may then become Held back.
"Held back": the reasons
- no consent: the customer has not ticked the Wallet box (for a message on the card) or has not accepted emails. Only they can tick the Wallet box, on their card page. For email, only tick Accepts marketing emails on their customer record if they have clearly asked you to.
- customer paused: the customer has chosen Stop receiving anything. That is to be respected.
- sent recently: the Not twice to the same customer within limit has not run out yet.
- daily cap / weekly cap: the customer has already had their quota, campaigns included. Adjustable in Safeguards → Adjust.
- quiet hours: the sending fell during the silence. Normally it is postponed (Scheduled).
- moment of little relevance: the relevance score is below the threshold of the Sending frequency. It drops, for example, if the customer received a message less than 48 hours ago or has just come in. Switch to Active to send more often.
- no channel available: no Wallet card and no email address, or a channel that is too restrictive (Wallet card only for a customer without a card). Choose Wallet card, otherwise email.
- another message takes priority: several promotional automations were triggering at the same time (after a visit, for example). Only one goes out, the one with the higher priority. Programme messages, on the other hand, all go out.
- already sent once: a message set to Once per customer only (that is the case with Reactivation, Review request and Referral).
- automation switched off: you turned it off before the time it was due.
- customer unavailable: the customer has been deleted or anonymised.
Good to know
- When the conditions of an automation are not met (Almost rewarded, for example, for a customer still far from their reward), nothing is logged: that is normal.
- Error is different from Held back: the sending failed. Fidélitas retries on its own, 3 times at most. If the error persists, contact support (the Help button).
Updated on 5 October 2026