Sequences let you define the order in which notification channels fire and the conditions that stop the sequence early. Instead of broadcasting the same message across all channels simultaneously, you deliver in a prioritised chain where each step waits for a result before deciding whether to proceed.Documentation Index
Fetch the complete documentation index at: https://www.cometchat.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Why use sequences
- Improve deliverability. Target the channel most likely to reach the user based on their prior engagement pattern.
- Avoid notification fatigue. Stop the chain as soon as the user has seen or acted on the message, rather than hitting them on every channel.
How it works
Sequences are configured at the template level. When you create or edit a template in the Dashboard:- Add two or more channels to the template.
- Enable the Sequence toggle in the template settings.
- Arrange the channels in the desired delivery order. The first channel fires immediately at send time.
- For each subsequent step, configure:
- Stop condition. The engagement signal that halts the sequence. Available conditions depend on the channel:
- In-app:
delivered|read|engaged - Push:
delivered|clicked
- In-app:
- Wait window. How long to wait for the stop condition before moving to the next step: 5, 10, 30, 60, 240, or 1440 minutes.
- Stop condition. The engagement signal that halts the sequence. Available conditions depend on the channel:
Example
A template with two channels configured as a sequence:| Step | Channel | Stop condition | Wait |
|---|---|---|---|
| 1 | In-app | delivered | 30 min |
| 2 | Push | n/a | n/a |
Metrics
When a template uses sequencing, per-step delivery metrics are available through the Dashboard and the analytics API. Which metrics are reported depends on the channel:| Channel | Requested | Delivered | Clicked |
|---|---|---|---|
| In-app | ✓ | ✓ | ✓ |
| Push | ✓ | ✓ | ✓ |