AI in practice
The phone rings while you’re under a sink. Then what?
For a small business, the best measure of an AI assistant may be what happens after it hangs up.
When a customer calls Frankie’s Plumbing in San Diego and Frank Galvin has his hands full, an AI receptionist takes the message. Frank calls back between jobs. Five unremarkable words in that arrangement do an awful lot of work: Frank calls the customer back. Somebody owns the next move. Jobber’s filmed profile of Frankie’s Plumbing
Frank started the business with his wife, Monica, after twelve years as a plumber. Jobber, which sells the software they use, describes a business that once spread the work across paper, Google Calendar and separate payment tools. Today the technician can inspect a problem, take photos on a phone and send a price from the driveway. The customer can approve it there. Monica uses a QuickBooks connection in the office. That division of labor tells you more about a personal assistant for a small business than the voice on a demo call ever will. Read the owners’ account and see the field photos
One customer, three messages
Suppose a customer phones about a leak, texts a photo ten minutes later, then emails to say the tenant will let the plumber in. That’s one job. It can look like three leads to a busy office. A perfectly polite assistant could acknowledge every message and still leave the technician outside a locked building.
Here’s the job I’d give the assistant. Find the open request, attach the photo, keep the customer’s wording about access and prepare the callback with all three pieces in one place. If two open jobs share the phone number, ask which address the photo belongs to. Give the owner a short list of calls still owed when there’s a gap between jobs. Those are design choices for this example. Jobber’s own receptionist guide describes narrower, configurable actions including taking calls and texts, creating follow-up tasks and transferring certain calls to a person. Jobber’s receptionist guide
When an email can become an invoice
On October 27, 2026, Intuit published a walkthrough showing how a business can connect QuickBooks to Claude and create and send an invoice in a conversation. Its October release notes also describe emailing invoices, sending reminders and sharing payment links through supported assistants. Eligibility and rollout vary. This is a product capability. The Galvins’ case documents a different, specific use of QuickBooks in their office. Intuit’s walkthrough · October release notes
Try the following with sample records before giving an assistant access to your billing inbox. An approved job costs $480. The customer already paid a $150 deposit. A second email asks about adding a new fixture. The assistant should prepare a $330 balance, keep the fixture request separate, and let the owner compare the draft with the signed scope before sending it. If the deposit can’t be matched to that job, the draft should wait. If the customer disputes the charge, someone should see the dispute before the next payment reminder goes out.
That exercise reaches all the way into bookkeeping. A sent invoice, a customer’s promise to pay and money received are three different events. Have the assistant assemble the invoice, payment record and bank activity for the bookkeeper. A partial payment or a single deposit covering two jobs belongs on the review list. An owner can learn a great deal from watching what the assistant does with the one transaction that won’t fit.
For a first trial, I’d give it overflow calls for a week. Count how many callers got a callback when promised, how many had to explain the job twice and how many records needed fixing. Then decide whether it has earned the inbox. The number I’d put on Frank’s dashboard is the one he can do something about before his next job: who is still waiting for a call?