// PIPELINE HYGIENE · EVENT AGENTS

Attendance Receipts Before Pipeline

Operator thesis: an event agent that treats registration as intent is not creating pipeline. It is laundering passive names into sales work.

NO RECEIPT · NO ROUTE
01A registration is an address. It is not buying intent.
02Agents may follow up only when attendance, attention, and fit are visible.
03The receipt must name the signal, owner, next step, and suppression reason.
04Fake event pipeline makes sales busy while the real buyers go cold.
The growth problem is not event volume. It is evidence-free routing.

The failure mode

Webinar agents look useful because they can email every registrant, score every attendee, and create follow-up tasks before the recording is uploaded. The dashboard says motion. Sales feels noise.

The dangerous jump is simple: registration becomes attendance, attendance becomes intent, intent becomes pipeline. Each jump needs proof.

Attendance receipt matrix

Signal
Agent can do
Agent cannot do
Registered only
No live or replay attendance.
Send low-pressure recap or suppress.
Create sales task or opportunity.
Watched enough
Meaningful live or replay minutes.
Ask for declared problem or route to nurture.
Assume budget or timing.
Engaged
Question, poll, chat, reply, or page visit.
Route with signal, segment, and owner.
Hide evidence in a generic lead score.
Bad fit
Student, vendor, competitor, unsupported segment.
Suppress and explain why.
Let activity pressure override ICP.

Event-to-pipeline control flow

01Capture attendance.
02Match fit.
03Score engagement.
04Name owner.
05Write receipt.
If the agent cannot show what the buyer actually did, it does not get to call it pipeline.

Build the control plane

Give event agents a narrow lane. They can summarize, nurture, and route. They must stop when the evidence is registration-only, the account is bad-fit, or the next step has no owner.

CAPTURE ATTENTION.
Store live minutes, replay minutes, poll, question, reply, and page visit as separate fields.
SEPARATE INTEREST FROM FIT.
A curious bad-fit attendee is not pipeline. It is suppression with a receipt.
NAME THE OWNER.
Every routed attendee gets a human or machine owner and a next step.
WRITE THE RECEIPT.
Attach evidence, reason, route, suppression state, and rollback path before sales sees the task.

Operator action rule

Before an event agent can create pipeline, demand four fields: attendance proof, engagement signal, ICP fit, and routed owner.

If any field is blank, the agent nurtures or suppresses. It does not create an opportunity, assign sales work, or inflate the forecast.

What A Head Of Growth Should Do Next

Take the issue in this piece and turn it into one operating rule. If a machine worker in this lane can touch pipeline, routing, pricing, forecasting, CRM truth, or customer communication, define the permission boundary, evidence requirement, and escalation path before you scale it.

The win is not more activity. The win is more trusted action with less cleanup debt.