Call Runner

The Call Runner turns a desk into a branching cold-call script — gatekeeper, permission opener, problem-first pitch, a float or calibration fork, diagnose and advise, seventeen objections and honest exits — then runs it on a prospect with the right names, numbers and next step filled in, and writes the outcome back to the record when you hang up.

Pilot note. The Call Runner is currently switched on for the Kolvera team only while the methodology settles. It will roll out to plans once the pilot closes; nothing here costs you credits until it is on for your workspace.

Three surfaces

Frameworks — /call-frameworks/. One framework per desk. Create it, generate a draft from the desk, edit it on the canvas, publish a version.
Runner — the Call Runner button on a prospect’s page and in the desk’s prospect drawer, beside Call. Opens the latest published framework for that prospect’s desk with every value pre-filled.
Write-back — the exit you land on logs the call, moves the prospect’s stage, sets the dated next action and appends a call note (verbatim objections included). The softphone call, if one is live, is linked to the same log.

What a framework is made of

A framework is a graph of nodes. Each node has a line you say, coaching chips, and the responses you might hear — every response routes to the next node. Kinds, in the order a call usually runs:

Gate — the receptionist. State your name and agency plainly and ask for the hiring contact by name; if asked what it concerns, name the role. Get a time rather than a voicemail.
Opener — five scripted beats in order: name and agency, one signal about them, own the cold call, ask for thirty seconds, the hang-up clause. Variants for a stale ad and for a warm contact; a refusal ends the call cleanly, while genuine timing gets one callback offer — there is no menu of reasons to pick from and no second ask.
Pitch — the buyer’s problem first, never the agency. The take-away probe (“if it’s working I’d leave it alone — one question”) is a pitch node.
Fork — motion A names a real candidate on your bench (name → proof → availability → price → one question); motion B is a calibration call that names nobody.
Diagnose / Advise — the must-ask questions, the candidate-call flip, and the honest “you may not be ready” line.
Objection — agree, incentivise, test-drive. Every objection has a recovery path back into the call and a refusal path to an exit.
Exit — booked, email sent, callback, nurture, dead, voicemail, no answer. Each carries the outcome, stage, next action and the referral ask.

How generation works

  1. Research. The AI reads the desk (target titles, pain points, positioning), your business context, documents attached to the desk, and up to fifty of your logged calls. It returns stage bands (headcount ranges with a verdict, ARR and funding read, talking points, a peer comparison and an org chart), personas, seats and only the facts it can source.
  2. Graph. From that research it writes the framework against a fixed skeleton: required nodes, fourteen required objections plus three optional ones (no agencies, PSL, call me back later), seven exits, and the methodology rules below.
  3. Repair. The validator checks the graph; up to two targeted repair passes fix what it flags, then a deterministic wiring pass closes the mechanical gaps (an objection nothing routes to, a missing exit, a stranded required node).
  4. Draft. The result lands as a draft with any remaining issues listed. Nothing publishes until the validator is clean.

Under twenty logged calls the runner shows Objection bank drafted from your desk: the objections are a starting point, not what your market has said. Regenerate once you have twenty logged calls and the bank is rewritten from what was actually heard.

Credits and refunds

5 credits per generation — charged when the run starts.
Refunded — if the framework cannot be built (the model fails, returns nothing usable, or the draft is still invalid after repair), and if the run is interrupted before it finishes. Interrupted runs are swept every five minutes; the draft shows why.
Kept — only when a draft is saved that you can publish, or that needs at most your own edits.
Cached — generating again within seven days with the same desk, documents and calls returns the previous result at no charge. Regenerate in the builder always runs fresh.

Builder, step by step

  1. Create. Name the framework and pick the desk. The desk decides which prospects use it and what the research reads.
  2. Generate. Takes two to five minutes; the builder polls and shows the draft, or the reason it stopped.
  3. Read the validator. Errors block publishing; warnings do not. Click any issue to jump to its node.
  4. Edit. Drag nodes on the canvas, drop a new node from the palette, connect responses to targets. The node panel edits the line, chips, responses (label, intent, match hints, target) and, on exits, the outcome, stage, next action and referral ask.
  5. Entry rules. Which opener a call starts on: by persona, motion, ad age, headcount or whether the bench has a float. The first matching rule wins; the default is the fallback. Only forks carry a node-level motion condition.
  6. Upgrade. A draft written before the current skeleton shows an Upgrade to bd_v1 button: it adds the missing nodes from the reference script, wires them in and leaves your wording untouched.
  7. Test run on a prospect without publishing, then Publish. Each publish is a new version; the runner always opens the latest published version for the prospect’s desk, and editing the draft never changes what callers see until you publish again.

Validator codes

unreachable / dead_end / bad_target / no_terminal — nothing routes here / no responses / a response points at a node that does not exist / no path from here reaches an exit.
no_recovery — an objection with no way back into the call.
missing_node / missing_kind / missing_objection — the skeleton requires it and the graph does not have it.
no_referral — an exit without the referral ask.
bad_entry / bad_node_entry — an entry rule or node condition using a key the runner does not know.
bad_exit / bad_token / bad_kind / bad_intent / bad_chip / bad_skeleton — a value outside the vocabulary.
banned_claim — the counter-offer failure statistic. It is not sourced; it does not go in a script.
over_cap — more than 200 nodes, 12 responses on a node, or 512 KB.
Warnings — no_chips, no_hints, single_response, chip_placement (an opener without a tone or silence chip, a fee node without a never chip), too_many_chips.

Running a call

Open the runner from the prospect. The strip across the top shows what the call is being run as, and where each value came from:

Contact and persona — the prospect’s name and title; the persona is matched from the title against the framework’s persona patterns.
Company and stage — headcount on the company record picks the stage band. No headcount on file? A slider lets you set it on the call and the read updates live.
Live ad — the company’s longest-running open job ad and its age, which drives the stale-ad opener and the internal-TA flip.
Seat and motion — the persona’s seat and default motion, or the framework’s first.
Float — the bench candidate linked to this desk (favourites first). No float and motion A demotes to B automatically — the runner never asks you to name someone you do not have, and warns on any line that would.

Every one of those is a picker. Change the persona and the seat and motion follow; change any of them and the call restarts from the right opener. The ACV field is optional and lands in the call note.

Navigate — the line to say, its chips (tone, silence, curiosity, urgency, never), and the responses you might hear. Press 1–9 or click. Back and Restart do what they say.
Brief — the whole framework on one page for a read-through before the call.
On-call mode — the line at reading size, everything else out of the way.
Intel panel — the stage band’s verdict, funding read, the org chart at this headcount (seats you place, their next hire, what does not exist yet), talking points, the peer comparison and the seat benchmarks with their sources.
Must-asks — on diagnose and advise nodes, the seat’s questions as a checklist that survives the whole call.
Missing — a pill lists any value the record could not supply; the line shows the placeholder rather than a guess.
Exit — the referral ask (“Who else in your space is dealing with this?”), a notes box for verbatim objections, and Log call.

The rules the generator keeps

Permission, not small talk — no “did I catch you at a bad time”. Own the cold call, ask for thirty seconds, stop at the question mark.
Problem first — the pitch names the buyer’s pain before anything about you.
No float, no fake float — a candidate is named only when one is on the bench. Otherwise it is a calibration call.
Honest urgency — urgency chips quote sourced facts and the float’s availability, nothing invented. The counter-offer statistic is banned outright.
Never discount — fee objections are answered on shortlist quality and the guarantee, not price.
Fee, then pause — a fee question gets a direct answer in the terms that apply, then silence. It is treated as a buying signal, not a cue to defend the whole industry.
Exclusivity is a defined service, not a demand — the framework offers the engagement that fits the search (a non-exclusive introduction or a scoped, priority-effort engagement) rather than asking for commitment before value is shown.
The flip — if a hiring conversation turns out to be a candidate conversation (or the reverse), the runner asks before changing the purpose and only continues with agreement.
A rude hang-up ends cleanly — no argument, no follow-up card or gift. Rudeness is recorded as a fact, not treated as a reason to try harder.
Referral only after a useful call — the ask is skipped after a refusal, a rushed exit or a request not to be contacted.

Coming next

Adaptive mode: with the softphone transcribing, the runner will hear the buyer’s response and move to the matching node itself — the same event the buttons send today. The objection bank will also rewrite itself from your logged calls once there are twenty.

Related

The dialler places the call the runner scripts. Frameworks are built per desk, and generation costs are listed under credits.