One condition and one action per rule. A rule can create a task, move a client, set a next action or enrol them in a sequence. Rule actions do not trigger other rules. Opening this page does not run quiet-client rules.
Resume this rule for future matching events. Earlier events are not replayed; quiet-client rules are checked at the next sweep.
JavaScript is required for automation commands.
Remove Quiet client check-in
Remove this saved rule. Its recorded runs stay available; this does not undo tasks, client changes or enrolments already created.
JavaScript is required for automation commands.
Create a rule
The saved rule is active immediately for future matching events. Earlier events are not replayed. A quiet-client rule is evaluated by the scheduled sweep or the explicit run below. A sequence enrolment can later create tasks or send email when its due steps run; it is not delivery.
JavaScript is required for protected automation creation. Loaded rules remain readable.
Run counts use the latest 500 account run records, including applied, skipped and failed outcomes. They are not lifetime totals. A zero only means no run appeared in that sample.
Recorded outcomes
Latest 30 runs, newest first, across your account. Filters above apply to rules only. Applied records an action outcome; it does not confirm a message was received. A partial failure can leave work applied before its run was recorded. Review client and sequence records before retrying.
Viewing follow-up
Applied
A viewing was held / 20 Oct 2026, 13:00 Dubai time
A client has gone quiet / 20 Oct 2026, 13:00 Dubai time
Client reference unavailable.
the sequence is paused
Rule absent from loaded list
Failed
A client is added / 20 Oct 2026, 13:00 Dubai time
Client reference unavailable.
the action could not be applied
Review a quiet-client run
This checks all active quiet-client rules against your open clients, regardless of the filters above. It can create tasks, change stages or next actions, and enrol clients in sequences. It does not run sequence due steps or send a message itself. Clients already handled within each rule window are skipped. Concurrent or uncertain runs can repeat work; check recorded outcomes before retrying.