How replies are read
Replies arrive through the connected mailbox and are matched to the enrollment by thread. Each reply is classified into one category, with a confidence score:
The sequence’s primary reply action (finish, continue, or pause for N days) applies to a reply
from the prospect; the secondary reply action applies to a reply from anyone else on the
thread. Reactions in Rules of engagement can override these per
outcome.
Custom reply labels
Under Sequencer › Settings a team can add its own reply labels (“Asked for pricing”, “Referred me to someone”). The built-in categories cannot be edited, because the engine acts on them; custom labels only trigger reactions you define, through the a reply matched one of your labels outcome.Suppression: the do-not-contact list
Sequencer › Suppression holds emails, domains and phone numbers that will never be enrolled. The enrollment preview refuses them with the reason “suppressed”.
Entries carry a reason: unsubscribed, bounced, complained, manual, or do not
call. Unsubscribes, bounces and complaints are added automatically; a do not call disposition
in the dialer also adds the phone. Bulk import a list of addresses or domains with Import.
Auto-send for replies
By default every reply a rep or Ari drafts is a task: someone reads it and sends it. Auto-send lets a team release drafted replies on a timer for specific reply categories, for example an automatic thank-you and scheduling link to an interested reply if nobody has sent one within two hours. Settings under Sequencer › Settings › Auto-send:
Every auto-send is logged on the enrollment as a send with the note that it was released
automatically, and the drafted reply stays visible in the task list until it goes.
Unknown is banned on purpose. If the classifier is unavailable, every reply is categorised as
unknown with zero confidence; banning it means an outage results in nothing being sent rather
than everything.