Sales script
Funnel strategyAlso called: call script, phone script, discovery call script, cold call script
A sales script is a planned structure for a sales conversation — the questions to ask, the points to make, and where to go next depending on how the prospect answers — written down so every rep runs the same call and you can tell which version of it actually closes.
The word script makes people picture a telemarketer reading a paragraph aloud, which is why good salespeople resist them. What earns its keep is not the wording but the structure: the order the questions come in, the point at which price is raised, and the branch you take when somebody says the number is too high. Those decisions get made under time pressure on every call, and left unwritten they get made differently every time.
A structure is a tree, not a list. "What made you book this call?" has three or four common answers, and each one deserves a different next move. Written as a linear document, that tree collapses into a wall of prose with parenthetical asides, and the rep scrolls it while the prospect waits. Written as a flow chart, each answer is a branch you take, and the rep only ever looks at the two or three cards that come next.
The reason to write it down at all is comparison. If the call is improvised, a good month and a bad month are indistinguishable — you have no record of what was said. If the path through a script is recorded, you can see that the calls which closed spent time on the budget question early, and the ones that stalled skipped it. That is a claim you can test.
How it works in FrazzleCRM
- ✓A Sales Script is a container on the funnel map — the same canvas as the automations, so the call sits next to the sequences that feed it and follow it.
- ✓Five card types: Question (what the rep asks), Statement (what the rep says), Transition (how the call moves on), Action (what the rep does — share a screen, send a link) and Context (notes for the rep, never spoken).
- ✓Branches are the labels on the arrows between cards: draw an edge from a question, label it "Too expensive", and taking that branch during a call is recorded as the route taken.
- ✓Pressing Run starts a live run attached to a contact. Each card the rep clicks is appended to that run's path with a timestamp and the branch label it arrived by, and a misclick can be undone mid-call.
- ✓Every rep's run is its own record — two people running the same script at the same time never collide — and the finished call appears on the contact with its full path.
- ✓Ending a run fires the "Sales script call ends" automation trigger, so the follow-up sequence starts from the call rather than from someone remembering to tag the contact.
- ✓A script is never bound to an automation: it does not consume your plan's flow allowance, and nothing inside it ever sends anything on its own.
See Sales Scripts in FrazzleCRM →
The full feature page: the five card types, how branches are recorded during a live call, and what the run history does to the contact record afterwards.
Where teams get this wrong
Scripts get abandoned when they are written to be read aloud. Write each card as the shortest thing that reminds a rep what to do — one question, one claim, one action — and put the paragraphs of background in Context cards, which are explicitly not spoken. A card the rep has to read in full during a live call is a card they will start ignoring by the third call.
Common questions
Does a sales script make reps sound robotic?
It does when the script is prose to be read. A branching script does the opposite: because the next move is already decided, the rep can stop planning the call in their head and listen to the answer instead.
How do you tell whether a sales script is working?
Record the route each call actually took, then compare the routes of the calls that closed with the ones that did not. Aggregate close rate tells you the script changed something; the paths tell you which part.
See it on a real map
Free templates where this shows up as an actual node. Clone one and the diagram runs as the automation.
Discovery Call Application
Make them apply, disqualify kindly, and only put booked calls on your calendar.
Lead genSpeed-to-Lead Callback
Text back in 60 seconds, alert the rep, and book the call before the lead cools.
SaaSTrial → Demo (Sales-Assist)
Score trial behaviour, and only put a human in front of the accounts worth a human.
Related terms
No-show
A no-show is a booked appointment the contact never attends. No-show rate is the share of booked appointments lost this way, and for most service businesses it is the single largest recoverable leak between a lead and revenue.
If/Else branch
An If/Else branch evaluates a set of rules about the contact at the moment the run reaches it and sends them down one of two paths, letting a single automation behave differently for different people.
Trigger
A trigger is the event that starts an automation for a contact — a tag being added, a form submitted, a link clicked, a date arriving — deciding both who enters the flow and when.
Goal
A goal is a step that represents the outcome an automation is trying to produce. Contacts anywhere upstream jump straight to it the moment the goal's event happens, skipping whatever remained in between.
Or browse all 25 terms — grouped by what part of the funnel they belong to.
Draw it once, and it runs
In FrazzleCRM the funnel map IS the automation — every node you draw is a real step, and every step you edit redraws the map. Free plan, no credit card.
Start free