PTS AI › Academy › Playbooks
Module 3 of 6

Playbooks

Pick the problem you want to fix.

6 lessons · about 18 min · written by the PTS AI team from live deployments

Six plays. Take the one that is yours.

They already bought from you. Talk to them again.

3 min

The list already exists, the trust already exists, and nobody has called it in two years.

Define dormancyRemove who must not be calledOne reason to talkQualifyTransfer

The four decisions that make or break it

Report recovered revenue and cost per recovered customer. Calls made is not a result and it will not get you a second campaign.

Transfer three unqualified calls to a branch manager on day one and nobody picks up again. That is how this play dies, and it is not a technology failure.

"Not now" is not "never"

3 min

Cold leads are not one list, and calling a never-contacted lead with the same script as one you lost to a competitor is why most of these campaigns produce nothing.

Segment first, then rank

"Are you still interested?" is a bad question. It gets a polite yes from people who are not and a polite no from people who are busy. Ask about a fact, and make the yes cost a date or a number.

The real output is not transfers. It is a database more accurate than it was three weeks ago, with the reason for every no written down in the customer's words.

You paid for that call. Somebody should answer it.

3 min

Pull one month from your phone system: unanswered, abandoned in queue, after hours, weekends. Multiply by your close rate and average ticket. It is the cheapest number in this library to produce and usually the most alarming.

Then build it in this order

A transfer to a phone nobody answers is worse than the missed call you were fixing, because now the customer has been told somebody is coming.

Read fifty transcripts in week one. Inbound tells you what your customers actually want, which is often not what your website says you offer.

Your reps should be selling

3 min

Measure two numbers for one week before you change anything: connects per hour, and conversation minutes per rep per day. In most teams the second is under ninety minutes out of eight hours, and that surprises the person who runs the team.

DialVoicemailDialNoteDialOne conversation

What changes

Week one, review every single transfer with the rep who took it. Reps ignoring AI-sourced opportunities because the first three were bad is how this play quietly dies.

Then measure the same two numbers. That comparison is the whole argument.

One company should not run thirty different ways

3 min

Every location will tell you they are special. Some are. Most of the differences are accidents that accumulated because nobody wrote the process down.

Sort every difference into deliberate or accidental

Branch-level reporting from day one. Retrofitting it later means rebuilding the identifier chain, which is the most expensive rework in this whole library.

The most common cause of a failed transfer is not technology. It is that nobody was there at 12:40.

If revenue moved, you should know why

3 min

Attribution is not a report. It is an identifier that survives five system boundaries, and if it breaks anywhere everything downstream is a guess.

SourceContactConversationOpportunitySaleRevenue

Where it breaks, in order of frequency

Three fields, never one

Name the three numbers you will report and the record each lives in, before any dashboard exists. If you cannot name the record, you cannot report the number.

The owner's page is five lines and no scrolling, and the fifth one names the location that is off trend. That line is why it gets opened on Mondays.

Rather not build it yourself?

We already run this across 28 finance branches.

Same system, installed and operated for you — calling, qualifying and handing leads to your team while you focus on closing.

All modules