Intraday Management sales demo - the evidence-led script for 'when the day goes sideways, how does your duty manager decide?'
Objective. Give sales and CSM a runnable, 5-beat demo script for IDM that lands the control-tower-to-decision story on a live call, cites the exact screens in order, states the execution limit out loud, and answers the discovery questions a WFM buyer actually has.
This is the question -> screen -> evidence -> interpretation -> next-step demo for IDM. The arc is one shortage carried all the way through the loop: the day drifts, you quantify it, locate the gap, simulate two fixes, compare, and show how the decision is logged and reviewed. The discipline that makes it credible is stating the boundary - IDM simulates and recommends; execution happens in the customer's systems - before the prospect asks.
See it in the demo
The story arc (one shortage, carried through the loop)
Do not tour screens. Carry one shortage through the whole decision loop so the prospect feels the before-and-after of deciding blind versus deciding with evidence.
The 5 beats:
- Question - 'When the day goes sideways by mid-morning, how does your duty manager decide between overtime, VTO, a skill move or holding - and how do they know, before committing, which one protects service best?'
- Screen - open the control tower, let the drift show itself, then move into the detail.
- Evidence - quantify the drift on forecast vs actual and locate the gap on staffing.
- Interpretation - simulate two corrective actions in the what-if and compare their projected effect, stating clearly these are projections.
- Next step - show how the chosen action is logged and reviewed at end of day, and agree a pilot on one of the prospect's own volatile queues.
The emotional beat you are selling: the duty manager stops guessing and starts choosing on evidence, with a record.
The exact screens, in order, with the one value point each
- Control tower (https://idm.demo.timechamp.io/#/tower) - value point: 'Your duty manager sees drift as it starts, not at end of day.' Say: this is the detect step, a prompt to look closer, not a verdict.
- Forecast vs actual (https://idm.demo.timechamp.io/#/forecast) - value point: 'This turns a red flag into a real picture - where the day diverged and what the rest of the day now looks like if nobody acts.' Label the reforecast a projection.
- Staffing (https://idm.demo.timechamp.io/#/staffing) - value point: 'It locates the gap precisely, by interval and skill, so you fix the real shortage - not the whole floor.' Make the netting point: a balanced total can hide a severe interval shortage.
- What-if (https://idm.demo.timechamp.io/#/whatif) - value point and centrepiece: 'Before committing, compare two fixes side by side on coverage, backlog and cost.' Simulate overtime, then a skill move, and compare. State the projection and execution limits here.
- Action log + end-of-day review (https://idm.demo.timechamp.io/#/log and https://idm.demo.timechamp.io/#/eod) - value point: 'Every decision is recorded and reviewed against what actually happened, so the operation learns which fixes hold.' This is what makes it auditable, not a one-off clever trick.
The limitation to state out loud
Say this before the prospect asks it - volunteering it is what makes the whole demo credible:
'IDM simulates and recommends. It does not run the day for you. The actual staffing change - opening overtime, moving a skill - executes in your own systems, within your cost and policy rules. And every number in a what-if is a projection on current assumptions, not a delivered result. What IDM gives you is a faster, evidenced, auditable decision - the service outcome is yours to realise, and we would baseline it with you rather than promise it.'
This one paragraph pre-empts the 'so it auto-fixes the day?' objection, separates simulated from executed from achieved, and sets up an honest pilot conversation. Overstating automation is the fastest way to lose a WFM buyer who knows their own floor.
The discovery questions this demo answers
Use the demo to answer the questions a WFM buyer is really asking, and to surface them if they have not:
- 'How long does it take us to notice the day has drifted?' (tower + forecast vs actual = detect faster)
- 'When we react, are we fixing the real gap or over-reacting across the floor?' (staffing by interval and skill)
- 'Can we compare options before we commit, instead of betting on one?' (the what-if - the core value)
- 'Can anyone reconstruct later what we decided and whether it worked?' (action log + end-of-day review)
- 'Does this replace our people or our systems?' (no - it informs the decision; execution stays in their systems)
And the qualifying question back to them: 'How volatile is your intraday - and when it moves, what does a wrong duty-manager call cost you in backlog, overtime or missed SLA?' Their answer sizes the pilot. Keep claims to decision quality and speed; the service number is the customer's own baseline, confirmed with product on what executes where.
Interpretation check
The demo sells a faster, evidenced, auditable decision - not an automated day. State out loud that IDM simulates and recommends while execution happens in the customer's systems, and that every what-if number is a projection, not a delivered result. The engine proposes, the human disposes, and the service outcome is the customer's to baseline.
In the field
OVO (contact centre): run the demo on an afternoon arrival spike - the classic IDM case - and compare 'overtime vs skill move' in the what-if, then ask OVO what a wrong duty-manager call costs them in a volatile hour. KnackGlobal (RCM): run it on a time-sensitive claim queue where 'overtime vs pull a skill vs hold' before a filing deadline protects both cost and compliance - sizing the pilot on their own backlog risk.
Practical task
Prepare and rehearse a 7-minute live IDM demo on the seeded account: carry one shortage through all five beats, show the six screens in order with the one value point each, include two what-if options compared, and state the execution-and-projection limitation out loud before the what-if. End by proposing a pilot scoped to one of a named prospect's own volatile queues, with the decision-quality measures you would baseline (time to detect and respond, action completion) kept separate from any service-number promise.
Self-check
What is the opening question of the IDM demo, and why open with it rather than a screen?
'When the day goes sideways, how does your duty manager decide between overtime, VTO, a skill move or holding - and how do they know, before committing, which protects service best?' It opens with the prospect's real pain so every screen after answers a question they already feel, instead of being a feature tour.
Which screen is the centrepiece of the demo and what is the one value point you make on it?
The what-if. The value point: before committing, you can compare two fixes side by side on coverage, backlog and cost - simulate overtime, then a skill move, and choose on evidence instead of betting on one. State the projection and execution limits right there.
What limitation must you state out loud, and when?
That IDM simulates and recommends while the actual staffing change executes in the customer's own systems within their policy, and that every what-if number is a projection not a delivered result. Say it before the prospect asks - volunteering it is what makes the demo credible.
A prospect asks 'so it auto-fixes the day?' mid-demo. How do you answer, and where in the script should this already have been handled?
'No - it detects, reforecasts, simulates and recommends, and records the decision; the staffing change executes in your systems within your policy. Confirm with product exactly what it can trigger versus hand off.' It should already have been handled by the stated limitation before the what-if.
Why show the action log and end-of-day review rather than ending on the impressive what-if?
Because they make the capability auditable and repeatable - the operation learns which fixes actually held. Ending on the what-if risks selling a clever one-off; the log and review are what turn it into a durable decision loop and an honest pilot.
Verified vs demo. All six screens are live in the demo on seeded data at idm.demo.timechamp.io; every figure is SME-validation-pending and must be presented as illustrative. What IDM can execute directly versus hand off, alerting and Copilot entitlement, and actuals-feed latency are production-dependent - confirm with product. The decision model end to end is what the demo proves, not any specific number.