Email glossary · Practical guide
Unsubscribe: a stop request that must reach the sending workflow
Unsubscribe means the recipient requests an end to the relevant communication. The operational task is to apply that request to the appropriate future sending scope.
Reviewed · Examples are illustrative
Who this helps: Readers checking a term before making an outreach or mailbox decision.
Meaning and common confusion
A clicked link, a reply saying remove me and a saved contact state are different records in the process. Confirm that the request results in effective exclusion rather than relying on a polite acknowledgement. Avoid assuming that one system's update automatically reaches every external list.
Worked example
This is a synthetic illustration, not a customer result or a live configuration to copy.
Request received → recipient identified → stop action applied → pending work reviewed
Failure mode: acknowledge the reply while the sequence remains active
Verification: check the actual saved state and subsequent eligibility.Checks to make
- Use the real recipient identity, not only a display name.
- Preserve the exclusion through re-imports.
- Keep confirmation wording limited to verified actions.
Next step and limits
Use the propagation guide for overlapping campaigns. Applicable requirements can depend on context and jurisdiction; this definition is not a complete legal procedure. Do not ask the person to justify the request before stopping promotional follow-up.
Source: Zintara product context for this operational definition
Source references
Worked examples are illustrative. Editorial procedures are suggested methods, not measured performance claims or promises of additional product features.
Related guides
- Prevent contacting suppressed leads after imports and restarts →
- Respond to 'Remove me' by completing the stop action first →