LensReading which lens this session carries.
The catalogueSalesDemand QualificationTransactional

Service SL3A

Lead-to-Meeting

Runs transactional. Starts when a scheduled window opens. It runs 5,786 times a week across 7 stations. One of those stations stops for a person and 6 are done by an agent, 2 of them on the shared spine.

Runs a week

5,786

196 in flight right now.

Stations

7

1 person · 4 agent · 2 spine

Agent share of steps

86%

Autonomy on this service is set at 83% against a ceiling of 90%.

Decisions a person makes

1

Held by Director, Demand Development.

Touchless

83%

Share of runs that complete without anybody opening them.

Timetable against actual

17.3h

Actual 19.5h, 2.2h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 33% of the dwellAgent4 stations and 38% of the dwellShared spine2 stations and 29% of the dwell2 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Customer Relationship Management
Customer Relationship Management
Customer Relationship Management
Contract Lifecycle Management
Configure, Price and Quote
Customer Relationship Management
Contract Lifecycle 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.

Operations

Every station in order

The same stations as a list, with the dwell the estate records against each one and the system a station of that shape would touch.

#StationLaneWhoLayerDwellTargetIn flightSystem
1

Ingest lead

GBSLead Enrichment Agentgbs1h 38m3h 4m41Customer Relationship Management
2

Enrich

GBSLead Enrichment Agentgbs2h 14m3h 49m46Customer Relationship Management
3

Score fit

AgentIntent Signal Agentworkflow35m1h 9m16Customer Relationship Management
4

Sequence outreach

AgentOutreach Sequencing Agentworkflow1h 56m3h 9m40Contract Lifecycle Management
5

Book meeting

AgentMeeting Booking Agentworkflow2h 13m4h 27m38Configure, Price and Quote
6

Route to seller

AgentDisqualification Agentworkflow13m30m6Customer Relationship Management
7

Accept

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

HumanDirector, Demand Developmentpolicy4h 20m7h 55m9Contract Lifecycle Management

Operations

Run it

Change the volume, move the autonomy line, release a gate, and watch what happens to the hours in each lane and to the time it takes one run to get through.

Move something
Demand100%
5,786 a week is what the estate records.
Decisions handed to agents0 of 0
This service has at most one gate, so there is nothing to hand over without removing the last human decision.
People on the gates717 people
Each one is assumed to have 2,100 productive minutes a week, which is 35 hours.
Agent speed100%
100% is the dwell the estate records today.
Person time a week
25,072.7h
5,786 items at 260 minutes of decision each.
Agent time a week
51,013.2h
529 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 22.3h of headroom.
Stations without a person
86%
1 gate left on 7 stations.
Where an item spends its time
33% waiting on a person
67% in the agent lane
An item now takes 789 minutes of worked time end to end against 789 in the recorded estate, a change of +0%. This is worked time, not calendar time: nothing here models a queue or a weekend.
What this model is, on Lead-to-Meeting

The simulation is arithmetic on the estate, not a queueing model.

How it runs

Run it again, going wrong

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

7 stations, walked twice

Once clean, once with the categories the estate counts

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

7 stations, nothing waiting, nothing sent back

0 min of 13 hrs

now Ingest lead · Lead Enrichment Agent · 1.6 hrs

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 33 hrs

now Ingest lead · Lead Enrichment Agent · 1.6 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 …

Live observability

Systems this service would touch

Attributed by rule from the function's system list.

3 systems attributed

0 of 3 returning records

The system register

Customer Relationship Management

Salesforce Sales Cloud · crm · bidirectional · critical

modeled

4 of 7 stations attributed here · would write back

Contract Lifecycle Management

Icertis · legal · bidirectional · high

modeled

2 of 7 stations attributed here · would write back

Configure, Price and Quote

Salesforce CPQ · crm · inbound · high

modeled

1 of 7 stations attributed here · read only

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Qualification Orchestrator
That orchestrator’s remit
Owns lead work end to end inside Sales. Runs 3 lines across 16 stations, drains the repeatable share into the A2L tower, and holds 1 human gates.
Accountable person
Director, Demand Development
Sub-function
Demand Qualification
Shared spine tower
a2l
Hand-over points
None — this service stays inside its function

Other services in this sub-function

2 alongside this one

Intent Surge ResponseSL3BRecycle & NurtureSL3C

What this page is and is not

This is a catalogue of the modeled estate.