A day of calls, texts and web forms for a mobile repair shop, every reply drafted

A day of texts, voicemails, web forms and after-hours calls sorted, estimates and schedule holds drafted for your okay. For mobile repair shops in NE Arkansas.

Demonstration using synthetic data

Every record, name, address, and log entry on this page is invented for the demonstration. No client, client system, or production record is involved, and no business result is claimed.

Author
Tanner Rusher
Published
Written for
Trades and service businesses
Example · fictional dataAbout 45 seconds, with music, one made-up after-hours call and one made-up voicemail played aloud.

Who this is for

Mobile repair outfits in Northeast Arkansas: RV and camper service, small engine, appliance repair, and any two- or three-person shop where the techs are out on jobs all day and the messages pile up on one phone. If the owner answers texts at red lights and builds estimates after supper, this is that job.

The problem, in your words

Customers reach you every way there is: a text, a voicemail, the form on your website, a call after hours. Each one wants a price, a time, or an answer to the same question you answered yesterday. You are under an RV for most of the day, so they wait, and some of them call the next shop on the list instead.

What happens, step by step

  1. Texts, voicemails, web forms and after-hours calls all land in one list.
  2. Each message is sorted by what it needs, and voicemails are transcribed.
  3. The details are pulled into a ticket: who, where, which unit, and what is wrong.
  4. Replies are drafted: estimates from your own rate sheet, answers from your own list of common questions, polite declines for work you do not take, follow-ups and payment reminders.
  5. Proposed holds go on the techs’ schedule.
  6. After hours, calls are answered and taken down without quoting a price or booking anything.
  7. You review the day’s drafts in one place and approve, edit or skip each one.

What you approve

Every message. Nothing goes to a customer until you approve it, and details the run was unsure of, such as a surname heard two ways, are marked for you to check before you send.

What the example run showed

The video is a real run on fictional data: one made-up Monday for Twin Lakes Mobile RV Service, a made-up two-tech shop, with 10 texts, 9 voicemails, 6 web forms and 3 after-hours calls. All 28 items were sorted right, 106 of 110 details were read right, 98.4% of the voicemail words were transcribed right, and all 13 estimates were for the right job. 39 replies were drafted and none was sent. Ten details were marked for a check, and one misheard surname got past those marks, which is why a person reads every message. Reviewing the whole day was estimated at about 18 minutes.

Setting it up in your shop

This is business automation that works with the phone number, website form and calendar you already have. It starts with a 20-minute call about how customers reach you and what you send back. If it fits, a Workflow Review maps the job, and an Automation Pilot builds it around your rate sheet. I’m in Jonesboro and can come to the shop.

Whether the workflow, the systems, or the approval rules look different in your organization, the next step is the same conversation.