Outcome. A request to bring a contact back to marketing contact status waits for a named approver before the status actually changes, so a reactivation that raises the marketing contacts bill never happens on one person's unchecked click.
flowchart TD
A[Reactivation request status = Requested] --> B[Create approval task]
B --> C[Notify approver]
C --> D{Wait until Approved/Denied, expire 5 biz days}
D -->|Expired| E[Set status = Expired, notify requester]
D -->|Approved| F[Set marketing contact status = Marketing contact]
F --> G[Set reactivation_approved_date]
G --> H[Notify requester: approved]
D -->|Denied| I[Notify requester: denied, no change]

When to use it, when not to
- UseUse when your plan is billed per marketing contact tier and more than one person can flip a contact back to marketing status.
- UseUse when you need an audit trail of who requested a reactivation and who approved it.
- SkipDo not use if a single admin already controls every marketing status change and volume is low. A shared checklist may be enough.
- SkipDo not expect this workflow to physically block a direct edit to marketing contact status outside this request path. It governs one path, not the underlying field permission. See Known pitfalls.
or the marketing ops pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.





