ExampleExample scenario. Not a real customer. Figures are modelled from the sources listed.

Case studyCommercial plumbing

Example: a commercial plumbing contractor's service-call desk

A modelled scenario: how a fictional commercial plumbing contractor would route night emergencies, capture PO numbers and site access, and chase quotes.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing9 min read

On this page
  1. Scenario profile
  2. The contractor in this example
  3. Where the calls go wrong in this example
  4. How the SI Employee would be set up
  5. PO numbers, site access and the paper trail
  6. Following up on open quotes
  7. What the numbers would look like
  8. The first 30 days in this example
  9. Lessons from the scenario
  10. Frequently asked questions
  11. References

Scenario profile

Business
Example: Eastgate Commercial Plumbing (14 technicians)
Industry
Commercial plumbing
Size
Owner, operations manager, three field supervisors, two CSR-dispatchers, a billing clerk and 14 technicians
Setting
Restaurants, property management portfolios and facilities (schools, offices, medical office buildings), about 140 on service agreements
Call volume
About 85 calls a weekday, plus 30 to 40 after-hours calls a week

Key takeaways

  • In this example, most of what goes wrong on commercial calls is routing and paperwork: the wrong supervisor paged, no PO number, nobody at the door.
  • The modelled setup gives each book of accounts its own service line, so an urgent call reaches the supervisor who owns that book, with the PO, approver and site contact taken down before anyone drives out.
  • Open quotes would get a text on day 3 and day 10 before anyone calls, since eight in ten Americans say they don't generally answer their cellphone when an unknown number calls[1].
  • Every figure here is modelled from the sources listed or invented for the example, never measured at a real contractor.

The contractor in this example

Eastgate Commercial Plumbing is a fictional contractor, used to show how a commercial shop would run its phones with an SI Employee on the line. In this example it has 14 technicians and three field supervisors, each owning a book of accounts: restaurants, property management companies, and facilities such as schools, offices and two medical office buildings. Around 140 customers are on service agreements with written response windows.

Two CSR-dispatchers answer about 85 calls a weekday in this example. After 5 pm the line rolls to an answering service, which takes 30 to 40 calls a week, writes a message and pages whoever holds the on-call phone that week, whatever the account. Night calls are part of the job on both ends of the line: plumbers are often on call to handle emergencies[2], and facilities managers often are on call to address problems that arise at all hours[3].

Where the calls go wrong in this example

None of the trouble in this scenario is about pipe. It is about what the person answering knows, what they ask and what they write down.

  • The wrong supervisor at night. A restaurant's floor drain gets paged to the property supervisor, who has to find the food-service supervisor before anyone calls the kitchen back. On a priority 1 account, that relay eats the response window.
  • No PO number. Facilities clients here issue a PO for every work order; the night message almost never has one, so invoices bounce and billing spends the morning chasing approvers.
  • Nobody at the door. The message says there is a leak at the school, but not which entrance or who has keys. The technician waits in the parking lot while the clock runs.
  • Quotes that go quiet. Agreement visits turn up repair work, such as a running flushometer or a backflow assembly that failed its test. The quote goes out by email and nobody chases it.
  • Status calls. Is the tech on the way, which PO did we use, can you resend the invoice: each one pulls a CSR off the dispatch board.

Restaurants make most of the night calls in this example, and grease is usually the reason. EPA's food service fact sheet quotes its report to Congress: grease from restaurants, homes and industry is the most common cause of reported sewer blockages, at 47%[4]. The same sheet puts one restaurant's grease trap waste and uncollected grease at 800 to 17,000 pounds a year[4]. Here, kitchen floor drains back up after the last service, when the office is closed.

Before and after: how commercial calls would be handled in this example
SituationBefore (answering service)After (modelled setup)
Restaurant drain backs up at 10:40 pmMessage taken; this week's on-call phone pagedRings the restaurant line and is transferred live to the food-service supervisor
Facilities job that needs a POPO rarely captured; billing chases it the next dayPO, or the approver's name and number, taken down before the transfer
Site accessAddress onlyWho meets the tech, which entrance, and the shutoff location if the caller knows it
Tenant reports a leak in a managed buildingHandled like any other callerChecked against the management company's emergency rules first
Open quote for a backflow repairEmailed once, then forgottenTexts on day 3 and day 10; callbacks answered with the quote details
Daytime call asking where the tech isA CSR leaves the board to look it upAnswered from the job record through the contractor's API, or passed to dispatch with a summary

How the SI Employee would be set up

The setup starts with the account list, not the greeting. Here the operations manager exports every agreement customer from the field-service software with six fields: the account and its sites, the supervisor who owns it, the priority level and response window, whether a PO is required, the not-to-exceed amount, and the after-hours contact tree.

Each book then gets its own service number, printed on the agreement and the equipment stickers. Each line holds only that book's accounts and transfers to the supervisor who owns it, then the backup. Callers in the contacts list are recognized by their number; the main number stays as it is.

Alarm and lockbox codes stay in the field-service app, where the technician already sees them. New jobs reach that software by webhook, here through Zapier, and quote and job lookups run against the contractor's own API during the call, as set out in the webhooks and API actions reference. Nothing in this scenario relies on a native connector.

Example: a restaurant drain call at 10:40 pm
  • Caller
  • SI Employee
  • Your team
  • System
  1. 01Caller

    Kitchen calls at 10:40 pm

    Kitchen manager on the restaurant line: floor drain backing up by the dish station.

  2. 02SI Employee

    Matches the account

    Finds the site: priority 1, PO required, owned by the food-service supervisor.

  3. 03SI Employee

    Takes PO and access

    Checks the water can be shut off, then asks for the PO or approver and who meets the tech.

  4. 04SI Employee

    Transfers to the supervisor

    Live transfer to the food-service supervisor, then the backup on the approved path.

  5. 05Your team

    Supervisor sends the tech

    Confirms the job and sends the on-call tech with the access notes.

  6. 06System

    Job opened, summary saved

    A webhook opens the job; summary, recording and transcript land in the account.

Example: fictional contractor and rules. A real setup follows the rules the owner approves.

The routing rules fit on one page. In this example they read like this:

  • Priority 1 (water on the floor, sewage in a food or public area, no water to a building): live transfer to the book's supervisor, then the backup. If neither answers, the job is marked urgent and a Zapier step on the webhook texts the summary to both and the owner.
  • Priority 2 (one restroom down, a slow kitchen drain, a leak stopped at the valve): the summary reaches the supervisor the same way; they choose tonight or the morning.
  • Priority 3 and routine requests: booked into an open agreement slot, or left as a request for the office to confirm.
  • Tenants in managed buildings: checked against the management company's emergency rules first.
  • New callers on the main number: job taken down; urgent ones go to the on-call tech.

Facilities calls carry one extra rule. When a job means shutting off water in a medical office building, the facilities supervisor hears about it before the technician arrives. CDC lists large, complex plumbing systems among the places Legionella can grow, and slow or no water movement and temperatures of 77 to 113 F among the conditions that help it[5]. In this example both buildings have a water management contact, and that person gets the call.

PO numbers, site access and the paper trail

The PO question comes after the emergency is understood, never before it: nobody with water on the floor wants to be asked for paperwork. In this example the order is fixed: what is happening, is anyone at risk, can the water be shut off, who will meet the tech, and only then the PO.

Example script: 'Your supervisor is next. Before I put you through, do you have a purchase order number for tonight? If not, who approves after-hours work for this site, and what's the best number for them?'

If the caller has no PO, the job still goes ahead under the agreement's emergency terms. The summary marks it PO pending, with the approver's name and number, so billing starts the morning with a short list instead of a hunt. Calls are recorded and transcribed, and the greeting says so: federal law allows recording when one party consents[6], but some states, Washington among them, require every party's consent and accept a recorded announcement as consent[7].

Site access follows the same pattern: who will meet the technician, which entrance, whether a security desk needs the tech's name, and where the shutoff is if the caller knows. The answers land in the job record, not in a voicemail.

Following up on open quotes

In this example the contractor has about 60 open repair quotes at any time, most of them with facility and property managers. The modelled follow-up is plain: the billing clerk texts from the office number on day 3 and day 10, naming the site and the repair. Texts go first because eight in ten Americans say they don't generally answer their cellphone when an unknown number calls[1]. More in building relationships with facility managers.

When the manager calls back, the call no longer waits for the estimator. The SI Employee looks the quote up through the contractor's API, answers what is written on it, takes the PO if one exists and books the work. Changes to scope or price go to the estimator with the call summary. The method is in following up on unsold plumbing estimates.

What the numbers would look like

Calls that ring past three rings while both CSRs are busy roll to the new line: one call in four in this example, and four in five of those are routine (PO lookups, access details, quote callbacks, job status). So the new line would finish 20% of weekday calls, each one a voicemail a CSR would otherwise return. The hourly cost is BLS total compensation for private-industry office and administrative support workers: $36.73 per hour worked in June 2026[8].

ExampleModelled weekday office time at Eastgate Commercial Plumbing
Example: worked figures
InputExample
Weekday calls to the office85
Minutes per routine call4
Calls completed without a CSR (%)20%
Office staff cost per hour, with benefits$36.73
Calls a month1,845
Staff hours on these calls123
Hours handed off25
Monthly value of that staff time$903

How it is worked out: Calls a day ร— 21.7 working days ร— minutes per call รท 60 ร— share handled = hours; hours ร— hourly cost.

Assumptions

  • Hourly cost of $36.73: BLS total compensation per hour worked for private-industry office and administrative support workers, June 2026 ($25.22 of it wages).[8]
  • Eighty-five weekday calls, four minutes a call and 20% finished without a CSR (one call in four rolling over, four in five of those routine) are invented for this example.

Example only: modelled, not measured. Change the inputs to match your own call log.

In this example that comes to roughly 25 hours of CSR time a month, about $900 at the BLS rate. Nobody would be let go. What changes is a shorter callback list and a CSR who stays on the dispatch board, where commercial response windows are kept or missed.

The bigger effect would be in billing and renewals, and it is harder to count. Example: if 11 night invoices a month went out without a PO and each waited two extra weeks, capturing the approver on the call would bring that cash forward. Missed response windows show up at renewal.

The first 30 days in this example

Example: a modelled first month
  1. Days 1-3

    Export the account list; each supervisor checks owner, priority and contact tree for their book.

  2. Day 5

    Test calls for every book, including a caller with no PO and a tenant in a managed building.

  3. Day 8

    After-hours calls move to the new line; daytime overflow follows after three rings.

  4. Day 15

    Supervisors listen to a sample of recordings and fix routing misses.

  5. Day 30

    Compare night routing misses, PO-pending invoices and quote replies with the month before.

Example timeline; a real rollout follows the contractor's own schedule.

Two things would get close attention in the first month: night transfers that reached the wrong supervisor, which usually means an account sits in the wrong book, and calls where someone asked for a person and waited. Supervisors can listen live, whisper guidance or take the call over; an unsure supervisor takes over.

The answering service stays under contract for the first two weeks as a fallback, so not every rule has to be right before the first night.

Lessons from the scenario

  • Fix the account list before the greeting: most routing misses here trace back to an account in the wrong book or a stale contact tree.
  • Ask for the PO once the emergency is clear, and never hold a tech back for it.
  • Capture who meets the tech and which door, every time. Codes stay in the field app.
  • Route by book and priority, not by who holds the on-call phone.
  • Give open quotes a fixed rhythm, texts before calls.

For the detail behind each step, see serving commercial accounts after hours, managing property manager work orders, grease traps and FOG rules for restaurants and when to wake the on-call tech.

Frequently asked questions

Is Eastgate Commercial Plumbing a real company?

No. It is a fictional contractor used to show the method. Every figure is either modelled from the sources listed or invented for the example and labelled that way.

Why does each book of accounts get its own number?

Because each line transfers to one person, then that person's backup. Separate numbers let a restaurant's 10:40 pm call ring the food-service supervisor instead of whoever has the on-call phone, and each line only holds its own accounts.

What happens if a caller has no PO number at night?

In this example the job still goes ahead under the agreement's emergency terms. The approver's name and number are captured and the job is flagged PO pending for the billing clerk in the morning.

Would the phone line keep alarm or lockbox codes?

Not in this example. Codes stay in the field-service app, where technicians already see them. The call captures who will meet the technician and which entrance to use.

Can a supervisor step into a call?

Yes. Supervisors added as team members can listen to a live call, whisper guidance, or take the call over at any point.

Does it connect to field-service software?

Through webhooks (for example via Zapier) or the contractor's own API. In this example new jobs are created by webhook, and quote and job lookups run against the contractor's API during the call. Creating jobs directly in field-service software is planned, not live.

References

  1. Pew Research Center (2020). Most Americans don't answer cellphone calls from unknown numbers (opens in a new tab) โ†‘

  2. U.S. Bureau of Labor Statistics (2026). Occupational Outlook Handbook: Plumbers, Pipefitters, and Steamfitters (opens in a new tab) โ†‘

  3. U.S. Bureau of Labor Statistics (2026). Occupational Outlook Handbook: Administrative Services and Facilities Managers (opens in a new tab) โ†‘

  4. U.S. Environmental Protection Agency (2012). Controlling Fats, Oils, and Grease Discharges from Food Service Establishments (EPA-833-F-12-003) (opens in a new tab) โ†‘

  5. Centers for Disease Control and Prevention (2026). Causes and How Legionella Spreads (opens in a new tab) โ†‘

  6. Legal Information Institute, Cornell Law School (U.S. Code) (2026). 18 U.S. Code ยง 2511 - Interception and disclosure of wire, oral, or electronic communications prohibited (opens in a new tab) โ†‘

  7. Washington State Legislature (2026). RCW 9.73.030: Intercepting, recording, or divulging private communication; consent required; exceptions (opens in a new tab) โ†‘

  8. U.S. Bureau of Labor Statistics (2026). Employer Costs for Employee Compensation, Table 4: Private industry workers by occupational and industry group (June 2026) (opens in a new tab) โ†‘

Book a demo

See Ava handle your calls.

Book a short demo. Weโ€™ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo