Step 7 of 10

Add human escalation path

Build the Path B workflow that hands blocked emails off cleanly to a human owner, with enough context for them to respond without reading the original thread.

Why this matters

Escalation is not a failure state, it is a feature. A well-designed escalation path gives the human responder everything they need in one forwarded message: who sent the email, why the system blocked it, the full normalized content, and the intent classification. Without this context, escalated emails pile up with no information and get missed.

Build instructions

Build the escalation notification email

Step 1
Add a Gmail 'Send Email' action in Path B. Set To: your human owner email address or shared team mailbox.
Step 2
Set Subject: '[ESCALATED] ' + the original email subject from the trigger. The [ESCALATED] prefix makes these easy to filter and prioritize in the recipient's inbox.
Step 3
Build the body with this structure: ESCALATION NOTICE\nFrom: [Sender email]\nOriginal subject: [Email subject]\nTime received: [Timestamp]\n\nBLOCK REASON\n[Block reason from Step 5]\n\nCLASSIFICATION\nDetected intent: [Intent]\nConfidence: [Confidence]\nRisk flag: [Risk flag]\n\nORIGINAL MESSAGE\n[Normalized email body]\n\nPlease reply directly to the sender. Do not reply to this escalation notice.

Label the original Gmail thread

Step 1
Add a Gmail 'Apply Label' action in Path B. Map the Thread ID from the trigger to identify the original email thread.
Step 2
Apply the label 'Needs Human Review'. This label should already exist, create it in Gmail Settings → Labels if it does not.
Step 3
This label gives the human responder a filtered view in Gmail showing only emails that need attention from them.

Confirm no auto-reply goes to the original sender

Step 1
Carefully review Path B. There should be NO Gmail 'Send Email' action that targets the original sender's email address in this path. The only outbound email is the escalation notice to the internal owner.
Step 2
The original sender receives nothing from this workflow in Path B. They may receive a follow-up from the human responder, but that is outside the automation's scope.

Common mistakes

Accidentally including the sender's email in the escalation notification recipient field. Double-check that the To field contains only the internal owner address.
Not including the block reason in the escalation email. Without this, the human responder does not know why the email was escalated and may not understand the urgency.

Pro tips

Add an SLA note to the escalation email footer: 'SLA: Please respond within 4 business hours.' This reminds the responder that escalated emails are time-sensitive.

Before you continue

Trigger a test escalation by sending a billing-related email through the system. Confirm: the internal owner receives the escalation notification with all context sections populated, the original Gmail thread has the 'Needs Human Review' label, and the original sender received no auto-reply.

Step result

Every blocked email is handed off to a human owner with full context, properly labeled in Gmail, and never auto-replied to.