7.3 Creating custom triggers

When you need one

The seven defaults cover sequence hygiene. Custom triggers add your team's workflow: routing, tagging, alerts. Examples:

• Tag prospects who clicked a pricing link twice — "warming" for prioritized follow-up.
• Alert the account owner when a large-account prospect replies.
• Tag prospects whose auto-reply mentioned a successor so you remember to chase the new contact.

Building one

1. Open Triggers.
2. Choose to create a new trigger.
3. Set the condition — the prospect behavior to watch.
4. Add actions: pause campaign, change status, apply tag, notify.
5. Save, then watch it fire on real events before relying on it.

Design rules

• Never weaken the safety defaults — don't build anything that re-contacts opted-out or bounced prospects.
• Prefer tags over status changes — tags are reversible and don't fight the sequence state machine.
• One behavior per trigger — compound triggers are hard to debug.
• Test with one campaign — enable the trigger, run one small campaign, verify the actions fire as expected before going wide.

[CONFIRM: exact list of available trigger conditions and actions in the current UI]