Unsubscribe Handling
All outbound emails from Scitor include standard List-Unsubscribe headers. When a customer clicks “Unsubscribe” in their email client, Scitor automatically handles the request.
How it works
- Customer clicks Unsubscribe — their email client sends an email with subject “unsubscribe” to the reply address
- Scitor detects the request — the inbound handler recognizes the unsubscribe subject
- Comment posted — a notification comment is added to the original issue or discussion, so your team is aware
- Label applied — the
unsubscribedlabel is added to the issue - Follow-ups cancelled — any pending scheduled follow-up messages for that ticket are automatically cancelled
What your team sees
When a customer unsubscribes, you’ll see a comment like:
🔕 Unsubscribe Request
John Doe (
john@example.com) has requested to unsubscribe from email notifications on this ticket.Use
/block-senderto block all future emails from this sender, or/followup cancelto stop pending follow-ups.
Behavior details
| Scenario | Action |
|---|---|
| Unsubscribe reply to an existing ticket | Comment + label + cancel follow-ups |
| Unsubscribe email with no ticket context | Silently dropped (no issue to reference) |
Next steps after an unsubscribe
The unsubscribed label helps you filter and track tickets where the customer opted out. From there you can:
- Continue via GitHub only — keep working on the issue without sending emails
- Block the sender — use
/block-senderif you want to prevent future emails entirely - Close the ticket — if the conversation is done