How to Trigger Retention Messages at the Right Time in Braze

Braze retention message timing comes from four layers working together. The trigger starts a journey, the delay spaces it, the exit rule stops it, and the send-time controls fix the final moment. Those controls are quiet hours, frequency caps and Intelligent Timing, and this guide shows where they clash.

‍

Key Takeaways

• Treat the trigger, the delay, the exit rule and the send-time controls as separate decisions, so you can debug one layer at a time.
• A day in a Braze delay is 24 hours from entry, while a calendar day waits until the next time you specify.
• An exit event applies during a Delay step, but the user stays in the delay until it ends, and exit counts only update after that.
• Braze checks frequency caps before quiet hours, and a capped user advances without generating a send event.
• Braze recommends choosing quiet hours or Intelligent Timing rather than both, unless policy or compliance requires it.
• We recommend setting the exit rule first, the delay second and the send-time controls last.

‍

How do you trigger Braze retention messages at the right time?

A retention message reaches a user at the end of a short chain of decisions. The trigger decides who enters, the delay decides how long they wait, and the exit rule decides whether they still qualify. The send-time controls then decide the final minute.

We recommend treating these as separate decisions, because each one is then easier to debug. When a message lands at the wrong moment, you can ask which layer moved it.

‍

Every behaviour described here comes from Braze documentation retrieved on 21 Oct 2026, and the pages are listed at the end.

‍

Which trigger should start a retention journey?

Action-based entry fires when a user does something. Braze documents triggers such as opening your app, making a purchase and triggering a custom event. A journey that starts on a positive action, such as a finished session, begins its clock at a moment you can name.

Absence is harder to catch because action-based triggers are defined by things users do. Our suggestion is to find a lapse another way: a segment filter, or a delay followed by a check. Braze's rate limiting page uses "Last used app more than 7 days ago" as a standard re-engagement segment.

Two settings catch people out. Braze advises against using the trigger as the audience filter as well, because a race condition can leave the user outside the audience when the event arrives. Send event timestamps with the current time, since a backdated timestamp can make Braze treat the delay as already elapsed and send early.

Decide re-entry on purpose too. Entry controls determine whether users can re-enter a Canvas, which matters for any nudge you might repeat.

‍

How long should a retention message wait after the trigger?

Braze's Delay documentation separates a "day" from a "calendar day". A day is 24 hours counted from the moment the user enters the step. A calendar day waits until the next specified time, which could be less than 24 hours.

If you don't specify a time, the user is delayed until midnight the next day in company time. Set the time on purpose. When a user enters after the configured time, Braze appends more hours to the delay, so the message lands on the next occurrence of your chosen hour.

Exact-date delays carry a separate risk. If the selected date and time have already passed when users reach the step, they exit the Canvas.

Braze lists one example. A delay targets a specific time in the user's local time zone, but the profile has no time zone set. The delay then defaults to the company time zone, where that time has already passed.

Gaps like these start in the data feed rather than the Canvas, and we recommend closing them first. Our customer data management service covers schema design and validation rules for how data enters your stack.

For retention journeys we recommend calendar days with a set local time. The message then lands at an hour you chose, not at whatever hour the user last triggered the event. Check first that your audience has time zones on their profiles.

‍

How do you stop a retention message once the user has returned?

Exit criteria remove users who perform a named exception event, and the event applies while they're waiting in a Delay step. Braze records the exit as soon as the event happens. The user stays in the delay until it ends and then leaves without advancing to any later step.

In Braze's example, a user performs the exit event on day one of a 30 day delay. They're marked to exit at once but don't fully leave until 29 days later. The "Total Exits by Exit Criteria" figure only updates after a user has fully exited.

Time-based exit criteria add a wrinkle. In Braze's own example, a user in a 24 hour delay performs the exit event "Last placed an order less than 1 hour ago" at 3 am. Braze evaluates the exit criteria when the delay ends, so that user doesn't exit, because 21 hours have passed.

You can also match the exit to the entry. In Braze's ticket example, a user who buys the ticket they selected exits. A user who buys a different ticket stays in and keeps receiving follow-ups.

For action-based campaigns that send after a delay, an exception event does the same job. You can also re-evaluate segment membership at send time.

‍

When should Action Paths replace a plain delay?

A delay with an exit rule tells you whether the user came back. Action Paths tells you what they did. By default Braze evaluates users within one day, and the maximum evaluation window is 31 days.

We recommend Action Paths when a lapsed user might browse without buying. One group can get a thank-you, another a reminder, and everyone else a final nudge through the default Everyone Else group. A plain delay with an exit rule can't make that split.

Watch the ranking toggle. With ranking on, Braze holds all users until the end of the evaluation window, so a user who acts on day one still waits. With ranking off, the first qualifying action sends them down their route straight away.

Decide the ranking setting before launch. Braze warns against changing it once users are in the step, and the rankings aren't editable after launch.

‍

How do quiet hours change the send moment?

Braze holds a message that would send inside the quiet hours window and delivers it after the window ends. Quiet hours apply in each user's local time zone. For action-based campaigns and Canvases the fallback can be abort message or send at next available time.

Quiet hours aren't the same as aborting, because aborting discards the message and quiet hours hold it. We recommend choosing the fallback by asking whether the message is still true in the morning. A reminder tied to a moment suits abort, and a gentle nudge suits send at next available time.

Plan for the surge. Braze notes that when a large audience is held, all of those messages send at once when the window closes. Quiet hours also don't re-evaluate segment membership for a held send, so test what happens when a user returns during the window before you launch.

Quiet hours can also serve a compliance need, and this post doesn't settle what such rules require in your markets. Braze gives a compliance requirement across all SMS sends as its example for workspace quiet hours, which set a default window per channel. A campaign or Canvas window always takes precedence over the workspace default.

Braze's release notes list workspace quiet hours as early access on 20 Aug 2026. The Quiet hours page says it requires enablement by your Braze account manager and appropriate user permissions.

‍

Should Intelligent Timing choose the moment for retention messages?

Intelligent Timing picks a send time for each user from their past engagement: session times, push opens, email clicks and email opens, with machine opens excluded. Users with no relevant data get a fallback time you set. In-app messages and webhooks are delivered immediately and don't receive optimal times.

In a Canvas, Braze advises a Delay step of at least two calendar days before the Intelligent Timing step, and it recommends calendar days over 24-hour days. With a 24-hour day, the user's optimal time can fall before they enter the step, which adds an extra day to the delay. In Braze's example, a two day delay that starts at 2:01 pm misses a 2:00 pm optimal time, and the message goes out a day later.

Braze notes that Intelligent Timing has limits early in a user's lifecycle, when little data is available. It advises sending at different times of day so it can sample them. A lapsed user has produced little recent activity, so our suggestion is to test Intelligent Timing against a fixed time before you commit.

Braze's documentation doesn't describe how lapsed users behave. We'd treat our reading here as a hypothesis to test.

Braze recommends choosing quiet hours or Intelligent Timing rather than both, unless policy or compliance requires quiet hours alongside it. If an optimal time lands inside quiet hours, the message goes to the nearest edge of the window. The abort fallback isn't available while Intelligent Timing is on.

If both rate limiting and Intelligent Timing are used, Braze gives no guarantee about when the message will be delivered. Intelligent Timing also isn't available for API-triggered campaigns.

‍

How do frequency caps interact with retention timing?

Braze checks the cap when a user reaches a Canvas Message step, before quiet hours. If the user is already at cap, Braze skips the send and doesn't hold it. Caps use the user's local calendar, so a hold that crosses midnight can change whether the user is still under the cap.

This is the layer that's easiest to miss in a retention journey, because a capped user simply advances to the next step. Braze documents that users who are frequency capped don't generate a send event for that step. The planned retention message therefore leaves no send event to look for.

Braze points to Currents for tracking message frequency capped events. A Segment Extension can find users who entered the Canvas but didn't receive the expected message.

Aborted messages don't count toward frequency capping, and new campaigns have capping turned on by default. A low delivery rate limit can also delay a send, and Braze aborts messages delayed 72 hours or more.

‍

What does a worked example look like?

Take a hypothetical language-learning app that wants to nudge users who finish a lesson and then go quiet. This is an illustration, not client work, and it uses no real data. We would make the decisions in this order:

1. Entry: action-based, on a custom event for completing a lesson. The audience filter doesn't repeat that event, which avoids the documented race condition.
2. Delay: three calendar days at an early-evening local time, so the nudge lands at an hour the team chose. The team first checks that profiles carry a time zone.
3. Exit criteria: starting a session. A user who returns on day one is marked to exit at once and leaves when the delay ends. The team reads exit counts only after that.
4. Message: a push with quiet hours on and send at next available time, because a lesson reminder still makes sense in the morning.
5. Frequency cap: the workspace cap applies. The team tracks capped users through Currents, because a capped user advances without a send event.
6. Send time: a fixed local time first. Braze advises sampling different times of day before Intelligent Timing can work well, so the team adds it to a later reminder after a delay of at least two calendar days.

‍

The behaviours behind each step are documented. The choices are our judgement, and a real programme would test them against its own audience.

‍

What should you set first?

As a Braze implementation partner, we recommend settling the exit rule first, the delay second and the send-time controls last. A message that's perfectly timed but reaches a user who has already returned is a wasted send. Build the stop before you tune the moment.

Timing controls aren't consent controls. Braze documents subscription settings as applying per step, with no effect on the entry audience. We recommend setting them separately from any delay or quiet hours window.

‍

How does this connect to the rest of the programme?

Timing for push specifically is covered in Optimising Push Notification Timing in Braze for Engagement. Entry design sits in Setting Up Engagement Triggers in Braze: A Practical Guide, and event capture in Tracking User Events for Better Campaigns in Braze.

If the user has already lapsed, see How to Build Effective Win-Back Campaigns in Braze. For the wider plan, read Top 10 Customer Retention Strategies Using Braze. For build mechanics, see How to Automate Mobile Campaigns in Braze Canvas.

Our case study on interactive gamification to re-engage lapsing users covers how a retail programme worked an interactive reward game into its automated lifecycle communication paths.

‍

Frequently Asked Questions
‍

1. How long can a Canvas Delay step last?

Braze documents that you can extend Delay steps up to two years (730 days). Check the Delay documentation for the current limit before you rely on it.

2. What happens if a user returns while sitting in a Delay step?

If the return is your exit event, Braze marks the user to exit at once. They stay in the delay until it ends and then leave without reaching later steps.

3. Does a frequency cap remove a user from a Canvas?

Global frequency capping alone doesn't exit users from a Canvas. On Message steps the user advances, and no send event is generated for the skipped message.

4. Can I use quiet hours and Intelligent Timing together?

Braze recommends choosing one rather than both, unless policy or compliance requirements make quiet hours necessary. If both are on, a send inside the window moves to its nearest edge.

5. Is workspace quiet hours generally available?

Braze's release notes list workspace quiet hours as early access on 20 Aug 2026. Braze's page says it requires enablement by your Braze account manager.

‍

Sources

• Braze, Action-based delivery. Retrieved 21 Oct 2026.
• Braze, Delay. Retrieved 21 Oct 2026.
• Braze, Exit criteria. Retrieved 21 Oct 2026.
• Braze, Matching exit criteria to entry events. Retrieved 21 Oct 2026.
• Braze, Action Paths. Retrieved 21 Oct 2026.
• Braze, Quiet hours. Retrieved 21 Oct 2026.
• Braze, Workspace quiet hours. Retrieved 21 Oct 2026.
• Braze, Intelligent Timing. Retrieved 21 Oct 2026.
• Braze, Create a Canvas. Retrieved 21 Oct 2026.
• Braze, Rate limiting and frequency capping. Retrieved 21 Oct 2026.
• Braze, Release notes. Retrieved 21 Oct 2026.
• Braze limits, defaults and feature status change over time, so check the linked page for the current position before you build.
• Written by CustomerIK, a Braze implementation partner.

‍

CustomerIK is a Braze implementation partner working across onboarding, technical integration, marketing operations and customer data management.

If your retention journeys send at the wrong moment, or you can't tell which control moved a message, let's talk.

‍