LensReading which lens this session carries.

Standard operating procedure · MK5C · Marketing

Send Incident Response

Transactional procedure owned by Campaign Orchestration in Marketing. 6 numbered steps, 1 of them a person deciding and 5 of them agent work …

Procedure code

MK5C

Transactional

Rule versions in force

v4.7 · v5.5 · v3.5 · v2.3

4 governing rules stacked over it

In force since

2025-04-08

Earliest effective date across those rules

Last reviewed

2026-07-06

Latest review date across those rules

Rules approved by

1

Director, Campaign Operations

Rule health

3/4

1 under review · 0 superseded

There is no document register behind this header. The version, the dates and the approver names are read off the governing rules this procedure runs inside, which is the closest thing the estate holds to a document control record. Nobody wrote these procedures. There is no document library behind this page and no Word file anywhere in the estate. Every procedure below is generated from rows this platform already holds: the line and its ordered stations, the owning team and the person accountable for it, the policy items bound to that team, and the governance gates seeded against the function. The steps, the owners, the gates, the approvers, the dwell times and the volumes are read straight off those rows. The sentences that join them together are generated. Read a procedure as the estate describing itself, not as a document somebody signed.

Purpose and scope

What this procedure is for and where it stops

To run send incident response to one repeatable standard inside Campaign Orchestration, part of Marketing.

Entry condition

Runs transactional. Starts when a threshold is crossed.

Exit condition

The unit clears post-mortem.

In scope

  • Every unit of send incident response raised inside Campaign Orchestration, from the trigger below through to the final step.
  • 5 of the 6 steps, which run without a person present.
  • 1 decision that stops the line until a named person releases it.

Out of scope

  • Anything outside the envelope set by the owning team. It leaves the line at a gate and becomes the named approver's decision.
  • Work that belongs to another function. This line records no handoff, so nothing leaves it mid-flow.
  • The 1 step carried on the shared AI GBS spine. They are done for this line but not by this function.

Who owns it

Runs the line

Campaign Orchestrator

Accountable person

Director, Campaign Operations

The end of the escalation path. Above them sits Marketing Chief of Staff for the function.

That team’s remit

Owns campaign send work end to end inside Marketing.

That remit describes the whole team, not this one procedure, so its counts are larger than the ones on this page.

Autonomy

78% now · ceiling 86%

Orchestration and suppression are fully automated with a hard consent gate the agent cannot override.

The procedure, step by step

6 numbered steps · 1 of them stop for a person

A step is one station on the line.

No.StepWho does itWhat happensSystem of recordTime on the stepIn flight
01

Detect defect

Agentworkflow

Calendar Coordination Agent

Calendar Coordination Agent performs this step unattended at the workflow layer, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Customer Relationship Management2.8 hrsstandard 3.7 hrs21
02

Halt sends

GBSgbs

Calendar Coordination Agent

Calendar Coordination Agent performs this step unattended on the shared AI GBS transaction spine, outside the function, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Customer Relationship Management52 minstandard 1.5 hrs7
03

Assess exposure

Agentworkflow

Audience Suppression Agent

Audience Suppression Agent performs this step unattended at the workflow layer, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Marketing Automation3.1 hrsstandard 6.3 hrs39
04

Notify

HumanpolicyDecision

Director, Campaign Operations

Releases: Director, Campaign Operations

Work stops. Director, Campaign Operations reviews what the line has produced and either releases the unit or sends it back. Nothing downstream of this step runs until that decision is made.Holds until: Held for a named human when the unit exceeds the campaign send decision envelope, when confidence falls below the floor, or when a policy clause is engaged.Customer Relationship Management42 minstandard 1.2 hrs9
05

Remediate

Agentworkflow

Frequency Cap Agent

Frequency Cap Agent performs this step unattended at the workflow layer, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Digital Analytics1.0 hrsstandard 1.9 hrs35
06

Post-mortem

Agentworkflow

Campaign Quality Agent

Campaign Quality Agent performs this step unattended at the workflow layer, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Customer Relationship Management59 minstandard 2.3 hrs29

The swimlane

The same steps, laid out by who is holding the work

Three lanes: a person deciding, an agent working, and the shared services spine.

Person1 station and 7% of the dwellAgent4 stations and 83% of the dwellShared spine1 station and 9% of the dwell4 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Customer Relationship Management
Customer Relationship Management
Marketing Automation
Customer Relationship Management
Digital Analytics
Customer Relationship Management
Click any station to see who does it, what it costs in time, the rule that gates it and the system attributed to it.

Run the procedure

One unit walked along that swimlane on the happy viable agentified path

Press run and a single unit enters at station 01. Each station takes exactly the dwell this platform records for it and is held by whoever the estate says holds it.

speed
worked clock
00:00
allowance clock
00:00
stations cleared
0/6
the happy path, worked time0 min of 9.4 hrs
the same run against its allowance0 min of 17 hrs
Human
decides · 1
Agent
does the work · 4
GBS
shared spine · 1
run log

Nothing has happened yet.

where the worked time goes9.4 hrs a unit
Person42 min · 7%Agent7.9 hrs · 83%Shared spine52 min · 9%4 crossings between lanes
what makes this path viable
  • The lanes are the recorded lanes. 1 of the 6 stations stop for a person and every one of them still does on this run.
  • Every one of the 1 decision is still taken by the person who holds it. The happy path is that each one is released first time, not that it is skipped.
  • The owning team is held to a 86% autonomy ceiling and this run sits at 93% unattended, inside it.
  • 3 systems are attributed across the stations, and 0 of them are connected. Nothing in this run has been watched executing against a real system of record.
what would have to change

One decision, held by Director, Campaign Operations.

stays with a person
  • 04 Notify — The last decision on the line. Something on every procedure ends with a person, so this one is never offered.
what this run is, and what it is not

This is a run, not a forecast.

Happy means nothing goes wrong: no station raises an exception, no gate sends the unit back, no rework loop fires and nothing sits in a queue between stations.

The second clock is the allowance.

A decision may be handed to the agent lane only if two things hold …

The run reads the station rows only.

What this run does not model: arrival patterns, contention between procedures for the same person, shift patterns, weekends, learning curves, and the cost of anything.

Run it again, going wrong

The same unit, the same stations, broken the way the estate already records breaking

This is the same unit on the same stations, breaking.

No break below was chosen.

One play head, two tracks, the same scale. The clean run stops when it runs out of stations; the other one keeps going.

As written

6 stations, nothing waiting, nothing sent back

0 min of 9.4 hrs

now Detect defect · Calendar Coordination Agent · 2.8 hrs

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 27 hrs

now Detect defect · Calendar Coordination Agent · 2.8 hrs

personagentshared spinework the break addsnobody working it

What breaks, and where it is counted

No break below was chosen.

What the two runs say together

5 counted categories land on this procedure.

What this run cannot claim

These breaks are shown together on one unit so the shape of a bad day fits on one screen.

The separation register records a duty conflict against a sub-function and a named post, not against one procedure.

Two clocks run. Worked time is the sum of the time the work is actually being done …

Roles and responsibilities

6 named parties

The responsibility grid is assigned by a rule, not lifted from a chart.

PartyRACIStepsDutyEscalates to

Campaign Orchestrator

orchestrator

Runs the line0Sequences this line, holds its timetable and decides what has to surface to a person. Raises to Director, Campaign Operations when a unit falls outside the envelope or confidence drops below the floor.

Calendar Coordination Agent

agent

A4% autonomy · ceiling A4%

92% clean · 3% overridden

Responsible2Runs the repeatable portion of campaign orchestration inside the shared transaction spine at spine cost and spine controls.Escalates to Director, Campaign Operations when the unit falls outside the decision envelope or confidence drops below the floor.

Audience Suppression Agent

agent

A4% autonomy · ceiling A4%

92% clean · 7% overridden

Responsible1Executes the campaign orchestration step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Director, Campaign Operations when the unit falls outside the decision envelope or confidence drops below the floor.

Director, Campaign Operations

person

Accountable and responsible1Holds 1 decision on this line. Accountable to Director, Campaign Operations for the decisions held here.

Frequency Cap Agent

agent

A2% autonomy · ceiling A4%

90% clean · 8% overridden

Responsible1Holds the rules that bind every other agent in campaign orchestration. Escalates on any decision that would breach a live policy version, with the clause cited.

Campaign Quality Agent

agent

A4% autonomy · ceiling A4%

97% clean · 9% overridden

Responsible1Watches campaign orchestration continuously. Escalates to Director, Campaign Operations when the unit falls outside the decision envelope or confidence drops below the floor.

Decision points and escalation

1 places this procedure stops

04 · Notify

42 min

Held for a named human when the unit exceeds the campaign send decision envelope, when confidence falls below the floor, or when a policy clause is engaged.

Director, Campaign Operations

Handoffs out of this procedure

Nothing leaves this procedure for another function. It completes inside Campaign Orchestration.

The rules this procedure runs inside

4 governing rules

Campaign Orchestration Decision Envelope

active

MK5-POL-200 · envelope · vv4.7

Agents in this lane may act without a human when the campaign send sits inside the stated value, risk and confidence envelope.

Approved by Director, Campaign Operations · in force 2025-11-27 · reviewed 2026-05-25

Binds Calendar Coordination Agent, Cross-channel Sequencing Agent, Audience Suppression Agent, Send-time Agent

Global

Campaign Orchestration Evidence Standard

active

MK5-POL-201 · evidence · vv5.5

Every autonomous decision writes inputs, the rule version applied, the model and prompt version, the output and a reversal path.

Approved by Director, Campaign Operations · in force 2026-06-26 · reviewed 2026-06-22

Binds Calendar Coordination Agent, Cross-channel Sequencing Agent, Audience Suppression Agent, Send-time Agent

APAC

Campaign Orchestration Escalation Rule

under review

MK5-POL-202 · escalation · vv3.5

Escalation is mandatory when confidence falls below the floor, when two options sit inside the confidence band, or when a break condition on a ratified position fires.

Approved by Director, Campaign Operations · in force 2025-11-15 · reviewed 2026-06-18

Binds Calendar Coordination Agent, Cross-channel Sequencing Agent, Audience Suppression Agent, Send-time Agent

US · Canada

Campaign Orchestration Autonomy Ceiling

active

MK5-POL-203 · ceiling · vv2.3

The ceiling for this lane is 86 on the platform scale.

Approved by Director, Campaign Operations · in force 2025-04-08 · reviewed 2026-07-06

Binds Calendar Coordination Agent, Cross-channel Sequencing Agent, Audience Suppression Agent, Send-time Agent

EU · UK

Systems this procedure touches

3 named · 0 connected

System attribution is a rule, not a reading.

SystemVendorDomainCriticalityStepsConnection
Customer Relationship ManagementSalesforce Sales Cloudcrmcritical4modeled
Marketing AutomationMarketo Engagemarketingmedium1modeled
Digital AnalyticsAdobe Analyticsmarketingmedium1modeled

0 of the 3 systems on this procedure is connected to the platform, and none of the twenty-six in the estate register is. 2 of them are marked as taking a write back, which is a property of the system, not a live path from here.

How it performs

End to end

9.4 hrs

Summed from the time each step sits, standard 16.8 hrs — running at 56% of the standard.

Touchless

90%

Agent share

83%

A week

6,670

In flight

140

Effort a week

42 human minutes · 525 agent minutes

Volume multiplied by the time on each step.

Assurance over this procedure

4 governance gates sit above it

The twenty-four controls and eighteen exception classes in this platform are held at estate level …

GateWhat trips itWho releases itClockWaivable

New or regulated claim

approval

Any performance, comparative or regulated product claim not already substantiatedCMO and General Counsel2 business daysNo

Budget reallocation guardrail

approval

Reallocation above 5% of campaign budget or $100,000CMO1 business dayNo

New personal-data use

approval

Any new data class, inferred attribute or third-party audience sourcePrivacy officer3 business daysNo

Crisis or socially sensitive content

escalation

Public position, crisis response or politically sensitive topicCMO and Communications2 hoursNo

Next to it on the same team

Campaign Orchestration

All of Marketing

What this document is and is not

These procedures describe the modeled estate.

Actions

What is waiting on a person

What one procedure document gives you, and what to check before you treat it as the standard.

Operations

What this desk is allowed to start

A surface that only reports is not operable.

Trigger and bound

A procedure document prints purpose, scope, entry and exit, the numbered steps with the actor on each, the roles and their RACI position, the swimlane, the decision points and escalation, the handoffs, the governing rules with version and approver, the systems by rule and the timings.

Live observability

What the record shows right now

The whole library, by lane, so a single document can be read against the estate it came from.

Current distribution

2,748 steps

Agent, inside the function1,38951%
Agent, on the shared spine85131%
Person deciding at a gate50818%

Is policy and strategy coming to fruition

Whether the written intent is holding here

Half. The document is complete and every actor on it is measured

Not holding on the record

A procedure here carries a version, an approver, an in-force date and a last-review date.