The Blueprint Workshop: services, staff, booking rules
Run the Blueprint Workshop to collect the services, the staff and the booking rules.
Read the lesson
Goal: Run a 90-minute workshop that captures every fact the build needs, in the team's own words.
You need: A signed client and a booked meeting. The workshop sheet from this lesson. Lesson 1 done.
Why this matters
Most setup errors are not app errors. They are missing facts. Nobody told you the drain service takes 2 hours on old homes. Nobody told you the owner never books past the river.
The workshop collects those facts once, before you build. A missed fact shows up later as a wrong booking, a wrong price or an angry customer. Each one costs the owner money and costs you trust.
A Blueprint is SAU's name for a documented build. There is no Blueprint feature in the app. You rebuild each Blueprint with workflow templates, Build with Emma and the voice agent's Use template. The workshop gives you the client facts that fill the Blueprint.
Who must be in the room
Invite the owner and the person who books jobs today. That is often a dispatcher, an office manager or a spouse.
The owner knows the prices and the rules they want. The scheduler knows the rules they forget. They know which tech will not do crawl spaces. They know that Tuesday is supply-house day.
If the owner says "just the two of us", explain why. Then invite the scheduler anyway. Twenty minutes of their time saves days of rework.
For a fleet, add the lead tech or the service manager. For a multi-location business, add one scheduler from each location.
The six parts of the workshop
The workshop has six parts. Top call reasons take 15 minutes and services take 20. Staff, and area and hours, take 10 minutes each. Booking rules take 15. Words the AI may say take the last 20.
Total: 90 minutes.
The 90-minute workshop
- 0:00Top call reasons: 8 to 10 reasons, one outcome each
- 0:15Services: real door-to-door time, price rule, category
- 0:35Staff: who does what, who is bookable, who takes transfers
- 0:45Area and hours: service area, phone hours, closures
- 0:55Booking rules: Minimum Notice, Maximum Advance, Buffer
- 1:10Words the AI may say: prices, emergency wording, never-say list
- 1:30Close: open questions, date for the written yes
Before the workshop
Send three things two days ahead. First, the agenda with the six parts. Second, the questions below, so nobody has to guess on the spot. Third, a short homework task for the scheduler.
The homework is simple. Ask them to tag the reason for their last 50 to 100 calls. A paper tally is fine. Their tally turns opinions into counts. Without it, the owner guesses, and owners usually guess that emergencies are most of the calls.
Also ask for the current price list and the service area as towns or ZIP codes. Ask for any scripts the office already uses. Read them before the meeting. Mark every line you do not understand.
Send two days before the workshop
- The agenda with the six parts
- The questions for each part
- Scheduler homework: tag the last 50 to 100 calls by reason
- Ask for the current price list
- Ask for the service area as towns or ZIP codes
- Ask for any scripts the office uses
Questions that find the hidden rules
Ask open questions, then ask for examples. "Tell me about the last booking that went wrong."
Services:
- Which 5 to 8 services do customers book most?
- How long does each take, from arrival to leaving? Ask the techs, not the price list.
- Which jobs need a site visit before a price?
Staff:
- Who can do which jobs? Who is new?
- Who takes urgent calls after hours? Is it always the same phone?
Booking rules:
- How soon can a new job start? That is Minimum Notice, in hours.
- How far ahead do you book? That is Maximum Advance, in days.
- How long between jobs for the drive? That is Buffer Between Appointments, in minutes.
Words:
- Which prices may the AI say on a call? Get them in writing, with a date.
- What counts as an emergency? Get the client's own words. Each client writes its own emergency wording.
- What must the AI never promise?
Running the room
Open with the goal in one sentence. "Today we write down how you book jobs. Then the AI books the same way." Then go part by part. Assign one person to watch the time. Then the last part still gets its full 20 minutes. Keep a clock in view.
Write every answer where both people can see it. A shared screen works well. A whiteboard photo works too. What matters is that nobody leaves with a different memory of what was agreed. When the owner and the scheduler disagree, do not pick a side. Ask for the last real example. The example usually settles it.
When the owner and scheduler disagree
- Ask the workshop question
- Do the owner and scheduler agree?YesWrite it where both can see itEnds hereNoAsk for the last real example
- Does the example settle it?YesWrite the rule the example showsNoPut it on the open list with a name and a date
- Build nothing until its open questions close
Park side topics, and do it kindly. Owners like to talk about ads, hiring and last year's slow winter. Write each topic on a "later" list and move on. You can bring it up in the monthly review.
Close with three things. Read back the open questions and who owns each one. Confirm the date for the written yes. Book the next touch point, usually the go-live check in lesson 9.
Size changes the room. An owner-operator workshop may take 60 minutes, because one person holds every answer. A fleet needs the full 90 minutes and the service manager. A multi-location workshop may run as one shared session, then a short session per location.
Build it in ServiceAgent
You do not build during the workshop. You capture. Then you build in this order:
- Hours and closures:
Settings→Brand & Locations→Business hours. - Services:
Settings→Service Catalog→Services→Create Service(lesson 4). - Team:
Settings→Team & Access→Team members & invites(lesson 1). - Booking rules:
Settings→Service Catalog→Booking rules. This opensCalendar Configurations. Edit the booking calendar, then openAvailability→Booking Rules. SetMinimum Notice (hours),Maximum Advance (days)andBuffer Between Appointments (minutes). - Words for the AI:
Voice Agents→BasicsandKnowledge(lesson 5). - Check it works. Read the workshop sheet back to the owner and scheduler. Ask them to sign and date it.
Where Cedar's booking rules live
Booking calendar, Availability tab
Note what the app does not have. There is no travel-time setting, so the buffer stands in for the drive. There is no per-service daily cap. There are no price tiers inside one service.
After the workshop: the build sheet
Within 24 hours, turn your notes into a build sheet. It has one row per decision and one column for where it lives in ServiceAgent. For example, "Buffer 30 minutes" lives in Availability → Booking Rules. "Never quote repair prices" lives in the voice instructions and Quick answers.
Send the build sheet back to the owner and the scheduler. Ask for a written yes. Questions they cannot answer go on an open list with a name and a date. You do not build a part until its open questions are closed.
For a multi-location client, use one build sheet per location. Hours, service area and staff often differ by shop. Shared items, such as brand voice and prices, sit on a common page that every location sheet points to.
Worked example: Cedar HVAC
Cedar HVAC has 9 techs on Growth. The owner and the dispatcher join the workshop.
Top call reasons. The dispatcher tagged 100 recent calls before the meeting:
| Reason | Calls | Outcome |
|---|---|---|
| No cool or no heat | 31 | Book same day, transfer if a safety case on the owner's list |
| Tune-up | 22 | Book |
| Estimate for new system | 14 | Book a site visit |
| Existing job question | 12 | Look up and answer, or task the office |
| Thermostat or noise | 9 | Book |
| Billing | 6 | Task the office |
| Vendor or spam | 6 | End the call politely |
The top 3 reasons cover 31 + 22 + 14 = 67 calls, or 67%. All 7 rows cover 100%. Every reason has one outcome.
Cedar HVAC's 100 tagged calls
- No cool or no heat31
- Tune-up22
- Estimate for new system14
- Four other reasons33
Calls tagged by the dispatcher100
Booking rules agreed:
- Minimum Notice: 2 hours. The dispatcher needs time to route.
- Maximum Advance: 30 days.
- Buffer Between Appointments: 30 minutes. Cedar's homes average 25 minutes apart, plus 5 minutes to load the van.
The owner had said 15 minutes. The dispatcher said 30. You use 30, because they see the late arrivals.
Cedar's buffer, from the dispatcher
Common mistakes
- Meeting the owner alone. You miss the scheduler's rules. Fix: invite the person who books jobs today.
- Using price-list durations. The calendar overbooks. Fix: ask the techs for door-to-door time.
- Writing emergency wording yourself. You take on a risk that is not yours. Fix: the client writes it, and you paste it in.
- Leaving with verbal prices. Fix: get approved prices in writing, with a date.
- Building during the meeting. You lose the thread. Fix: capture now, build after.
Do this now
Copy the six parts into a one-page workshop sheet. Add the questions under each part. Run it with a real client or a friend who runs a trade business. Get the sheet signed.
Practice the conversation
- Operator I'd like 90 minutes with you and whoever books jobs today.
- Owner Can't we just do it, you and me? Tess is busy.
- Operator Tess knows rules you don't think about anymore.
- Owner Like what?
- Operator Which tech skips crawl spaces. How long the drive really is.
- Owner Fair. They do know that stuff.
- Operator I'll send the questions first, so nobody guesses.
- Owner And the prices? I'll tell you on the call.
- Operator Please. Then I'll send them back for you to sign. The AI says only what you approve.
Quick check
- The owner of a 6-person electrical shop wants the workshop to be just you and them. Their dispatcher books every job. What do you do?
- Meet them alone and email them the notes
- Invite the dispatcher too
- Copy the rules from the website
- Skip the workshop and fix bookings after go-live
- In the workshop, a tech says jobs are 25 minutes apart, plus 5 minutes to load. Which setting holds this?
- A travel-time setting on each service
- `Minimum Notice (hours)`
- `Buffer Between Appointments (minutes)` set to 30
- `Maximum Advance (days)`
- You tagged 100 calls. Tune-ups are 22, estimates 14 and no-heat calls 31. What share do these three reasons cover?
- 45%
- 53%
- 31%
- 67%
ServiceAgent UniversityLearn to run a service business on autopilot. Free courses, Blueprints and certification for Service Operators.