PYRSOS LIBRARY · THE PHONES PLAYBOOK

A Phone Script Your Crew Will Actually Use

PUBLISHED APRIL 14, 2026

The phone script that works in a trade shop is a skeleton, not a speech: a standard greeting, four required intake questions, three branch plays, and a booking ask that always gets made. Your crew supplies their own words between the fixed points. That keeps every call complete without making anyone sound like a hostage reading demands.

01

Why scripts fail: written like essays, delivered like hostages

Most service-call scripts die within a week, and they deserve to. Somebody downloads a two-page document with full paragraphs to recite, complete with "I understand how frustrating that must be for you." The crew reads it aloud a few times, sounds exactly like a man reading aloud, hates it, and quietly goes back to winging it.

The diagnosis is simple: the script tried to control the words, and words are the part that has to stay human. Scripts make my people sound like robots is a fair complaint about that kind of script.

But watch what winging it costs. Calls end without an address. Nobody asked whether the water is still running. The caller with a dead furnace hangs up with "somebody will call you back" instead of a Tuesday slot. Your people talking like themselves was never the problem. The calls were ending incomplete, and incomplete calls leak jobs.

So fix what scripts are for. A good one does not standardize the talking. It standardizes what must be true before the call ends.

02

The one-card script: greeting, four intake questions, the booking ask

Everything your phone needs fits on an index card taped next to it.

The greeting, one line, same every time: "Thanks for calling [shop], this is [name], what's going on?"

Four intake questions. Name: "Who am I speaking with?" Address: "Where's the property?" Problem, in the caller's own words, plus the one clarifier your trade needs (is it leaking now, is the unit cooling at all, when did it back up). Urgency: "Is this a today problem or a this-week problem?"

The booking ask, which is the step untrained answerers skip and the whole reason the card exists: "We can have somebody out [day] between [window]. Does that work?" Asked directly, every call, before any goodbye. Not "somebody will call you back." A caller who hangs up without being offered a time is a caller still shopping, and the numbers on what an unbooked call costs are on our Auto-Booking page.

Between those fixed points, your people talk like themselves. The card does not care how they get from question two to question three. It cares that they arrive.

03

Branch points: emergency, price shopper, existing customer

Three kinds of calls need a play of their own, and the card carries one line for each.

The emergency: gas smell, smoke, sparks, sewage rising, water pouring in. The card says: safety first, 911 before scheduling. "I need you to leave the house and call 911 or the gas company's emergency line first. Call us back the minute you're safe and we'll get you first in line." Of everything on the card, this branch alone must be delivered word for word.

The price shopper: "What do you charge to..." deserves a straight answer about how your pricing works and an immediate pivot to value: "The honest answer depends on what we find, which is why the visit comes first. I can have someone out Thursday morning who'll give you the real number on the spot. Want that slot?" The shopper who books stops shopping.

The existing customer: greet the history. "Good to hear from you again, is this about the unit we put in, or something new?" A caller your shop remembers is a caller who stops comparing you to anyone. The record-keeping that makes this possible on every call, not just the ones the owner happens to answer, feeds straight into the Job Brief your tech reads before rolling.

04

Training it in fifteen minutes a week

A card nobody drills is a decoration. The training that sticks is short and constant: fifteen minutes, once a week, same slot.

The format is one role-play and one real call. First, somebody plays the caller for three minutes, using last week's weirdest real call as the material. Everybody hears one person run the card. Then play back a recorded real call from the week and check it against the card: greeting, four questions, right branch, booking ask made or not. No shaming, one tally. Shops that keep the tally watch complete calls climb within a month, and complete calls become booked calls.

Fifteen minutes a week is also about the limit of what a working shop will actually sustain, and staying inside that limit is why it sticks. This whole discipline, the fixed questions, the branches, the ask that always gets made, is exactly what we hard-wired into our AI voice receptionist for the hours when no crew is there to drill. Days, your people run the card in their own voices. Nights, the card should still be running. Either way, nobody hangs up without being offered a time.

QUESTIONS

Common questions

Should my employees use a phone script?

Use a skeleton, not a speech: fixed intake questions and a required booking ask, with their own words in between. Consistency where it counts, humanity everywhere else.

What should a service call script include?

The greeting, four intake questions (name, address, problem, urgency), an emergency branch, and a direct ask for the booking before anybody hangs up.

Twenty minutes. We look at your call volume and tell you straight whether this pays for itself. If the math does not work for your shop, we say so on the call.

Get in Touch

Or email us: [email protected]