Branching pathsObjection handling50+ merge fieldsIn-script actions

A script that keeps up with the conversation.

Printed scripts assume the call goes in a straight line. It never does. This one branches where the conversation branches, and every objection is one click away from wherever the rep happens to be.

Opens automatically the moment a call connects
Branching

The call goes where it goes

Each step offers the paths that make sense from there. The rep clicks what the prospect actually said, and the script follows.

The rep drives

Branches are buttons, not guesses. Your rep heard the call; they click the path it took — and the script is already where it needs to be.

Every path is a real path

Build the shape of the conversation you actually have. When a branch dead-ends, the script says so, rather than leaving a rep stranded mid-sentence.

Opens on connect, pre-filled

The instant the call bridges, the script is on screen with that contact's details already rendered. Through a dialer queue it re-arms for each new contact automatically.

Objection handling

The part that isn't a straight line

Objections don't wait for the right step. "How much is this?" arrives whenever it arrives.

A linear script

The objection comes early. The rep is on step two, the rebuttal lives on step nine, and now they're scrolling while a real person waits on the line. So they wing it — and the thing you spent a quarter refining goes unused.

Persistent objection paths

Mark a node persistent and it's reachable at any moment, from anywhere in the script — in its own panel, beside the main flow rather than replacing it.

The rep handles “too expensive” without losing their place, then carries on exactly where they were. Objection paths branch too — “too expensive” has more than one right answer.

Merge fields

Fifty-odd fields, and one that matters more than the rest

Name, city, lead source, agent details, licensing, and your booking link — all rendered live from the record as the rep reads.

State-matched licensing

For licensed sellers, the script inserts the right license number for the prospect's state automatically. It handles “TX” and “Texas” as the same place, so the correct number is on screen without the rep thinking about it.

No template language to learn

Fields are plain tags like {First Name} — write your script the way you'd say it, and the record fills itself in. The same tags work in your texts and emails.

Gaps stay visible

A field with no value stays on screen as a tag rather than collapsing into a blank. The rep sees what's missing instead of reading a sentence with a hole in it.

Actions

Do the thing without leaving the call

Send a text or email

Fire a template mid-call — preview it first — while they're still on the line to receive it.

Update the record

Capture what you learn as you learn it. It's on the contact before the call ends.

Open a form or a page

Pull up an intake form or a webpage from inside the script. Needs analysis and similar forms are built in.

Take notes, book the follow-up

A notepad and follow-up scheduling live in the script, so nothing waits on the rep's memory after they hang up.

For agencies

Scripts as intellectual property

Your best script is an asset. Treat it like one.

Publish to your downline

Share a script with your agents and let them import it. Your version becomes their starting point, and the link back to your original is kept.

Import from what you already have

Bring in a Sellify export, or upload an existing .docx, .pdf, or .txt script and have it converted into a branching one rather than retyped.

More to explore

Related features

Questions

Common questions

Can the script branch automatically based on the contact's data?

Not today. Branches are chosen by the rep — they click the path the conversation actually took. What is automatic is the content: merge fields render live from that contact's record, so the words on screen are always specific to the person on the phone.

How is this different from a script in a Google Doc?

Three things a document can't do: it opens by itself when the call connects with the right contact's details already in it, objection paths are reachable from any point without losing your place, and it can send a text or update the record from inside the script.

Does the AI coach read from the script?

No — they're separate systems today. The script is a rep-driven tool; live AI coaching listens to the call independently and suggests on its own. Connecting them is an obvious next step, but it isn't there yet, and we'd rather say so.

Can I use my own custom fields in a script?

Custom fields are fully supported in texts and emails, where they render by name. In the on-screen script reader today, the contact, agent, licensing, and scheduling fields resolve. Custom fields and agency fields in script text are on the list to fix.

What happens to scripts I share with my downline?

Publishing marks a script as available to your agents, who import their own copy. The link back to your original is retained, so it's clear where it came from. You can also import an existing .docx, .pdf, or .txt script and have it converted rather than rebuilding it by hand.

Ready to sell smarter?

Sell smarter. Close faster.

Start free today — bring your contacts, fire up the dialer, and let the AI coach do the rest.