Customer status updates — Customers hear about progress before they think to call
Status updates send customers a short message when their job, order or case changes stage. The message comes from the system where the work is already tracked, so nobody has to remember to send it. It suits businesses where many calls are customers asking where things stand.
By Julia Ja, Owner
Repair status updates
Tue · brake noiseNot automated
A car waiting on a back-ordered part: the service writer calls that customer himself.
Why it matters
The problem it solves
Customers who can't see progress call to ask. Each call pulls a technician, service writer or paralegal away from the work to look up the job and read out its status.
When updates depend on memory, they go out on quiet days and stop on busy ones. Bad news is the hardest to send, so it often arrives last, after the customer has made plans around the old date.
Example · illustrative
An auto repair shop on a Tuesday
- At 9:40 am a customer drops off a car with a grinding noise from the front wheels.
- When the inspection is done, the service writer marks it in the shop system, and the customer gets a text linking to the estimate.
- She approves the brake job from her phone at lunch.
- 3:15 pm the job moves to readyAnd a pickup text goes out with the shop's hours.
- A second car is waiting on a back-ordered part, so the service writer calls that customer himself.
How it works
How customer status updates works
- Starts whenA job, order or case changes status in the system staff already use
- 1Step 1Notice the changeA status change in the job, order or case system starts the update.
- 2Step 2Fill in the messageThe business's approved wording for that stage is filled in with the customer's details.
- 3Step 3Send by text or emailThe message goes out on the channel the customer prefers, from the business's number or address.
- 4Step 4Route repliesReplies go back to staff in one inbox, with the job details attached.
- A person decidesDeliver bad newsDelays, extra costs or problems are messaged by a person, not the automation.
Before · by hand
- Customers call to ask whether their order is ready.
- Staff stop work to look it up and call back.
- Updates depend on someone remembering to send them.
- Bad news reaches the customer late, or not at all.
With customer status updates
- Customers get an update at each stage that matters to them.
- Fewer calls are only about status.
- Messages go out the same way every time.
- Staff handle the replies that need a person.
What we build
The parts of customer status updates
Your systems
- Twilio
- Tekmetric
- Shopmonkey
- Clio
- ServiceTitan
- Housecall Pro
What we build
1Status listener
A connection to the job, order or case system that sees each stage change, by webhook or a regular check.
2Stage map
A list of which stages send a message, which stay internal, and which channel each one uses.
3Stage messages
Approved wording for each stage, filled with the customer's name, the job and any link they need, such as an estimate or tracking page.
4Reply inbox
Customer replies land in a shared inbox or on the job record, so the person who owns the job sees them.
5Late-job flags
Jobs that sit in one stage too long are flagged to staff, so a person can call with the delay.
6Preferences and log
STOP replies, language and channel choices are saved, and every message sent is logged on the job.
Your team decides
- Staff deliver delays, extra costs and any other bad news themselves.
- The business approves the wording for each stage.
Industries it fits
What customer status updates looks like in each industry
Auto repair & tire shops
Texts go out when the vehicle is inspected, when the estimate is ready to approve and when it's ready for pickup. The estimate text links to the digital inspection, so the customer sees the photos before approving.
Everything for auto repair & tire shopsYour industry isn’t listed, or works differently? Describe it and get an answer in a minute.
Getting started
What you need first
We go through these with you in the audit, before anything is built.
Before we start
5 things to have ready- A system where job, order or case stages are already tracked, such as a shop system, case manager or shared spreadsheet.
- A clear list of your stages, and a decision on which ones customers should hear about.
- Approved wording for each stage, and a rule for which news a person must deliver.
- Customer phone numbers or emails, with permission to send updates.
- Someone who watches the reply inbox during business hours.
How a rollout runs
- 1Map the stagesWe list every stage a job passes through, and mark which ones customers care about and which are internal.
- 2Connect the job systemWe connect to where status is changed, and check that each change arrives with the right customer and job.
- 3Write the stage messagesWe write the wording for each stage with you, including links to estimates, tracking pages or portals.
- 4Test on sample jobsWe move test jobs through every stage and check that each message, reply and late-job flag lands in the right place.
- 5Launch and adjustAt first, staff get a copy of each update. Stages that confuse customers get new wording or are switched off.
What to measure
How to know it's working
Weekly report · customer status updates
IllustrationStatus calls per week
The main reason to build this. If 'where is my order' calls don't fall, the stages or wording need work.
Updates sent per stage
A stage with no messages often means staff skip it in the system.
Customer replies to updates
Replies show which messages raise questions, so the wording can answer them up front.
Jobs flagged as late
Shows where work stalls, and whether a person called before the customer had to ask.
Opt-outs
A rising count suggests too many messages, or the wrong stages.
We measure the baseline before building, so the change can be compared afterwards.
When it’s not a fit
- It only works if staff change the status as the work moves. If stages are updated at the end of the day, updates arrive late.
- Too many stages turn into noise. Customers usually want a few messages, not one for every internal step.
- It doesn't replace a call for bad news. Delays, extra costs and problems still need a person.
- Check first whether your job system can share status changes. Some older systems only export files, which limits when updates can go out.
Tool or custom build
Do you need a custom build?
Option A · a ready-made tool
An off-the-shelf tool may be enough
Many job and shop systems include customer updates, such as Tekmetric and Shopmonkey for repair shops or on-my-way texts in Housecall Pro. They work well when the built-in stages match how you work.
Option B · built around your systems
When a custom build is worth it
A custom build makes sense when updates come from more than one system or follow your own stages. It can also route replies to the person who owns the job.
Not sure which fits?
What it typically costs
Typical ranges as of October 2026. Not a quote.
Ready-made tool, set up by us
An existing platform on your own account, configured for your business.
- Setup, one timepaid to Lorryn
- $750–$1,500
- Tool subscriptionpaid to the provider
- $15–$75 / month
Fits when your process matches what the platform already does.
Custom build
Built around how you work, with no platform subscription. You own it.
- Build, one timebasic version to full version
- $2,000–$5,000
- Running costshosting and usage, on your accounts
- ~$10–$40 / month
Fits when your systems, rules or exceptions don't match a ready tool.
Optional Automation Care: $125 · $250 · $375 / month
1, 2 or 3 hours of support a month, with monitoring and alerts included. Without it, you run it yourself after handover.
Typically works with Twilio, Tekmetric, Shopmonkey, Clio.
Booking into or writing to your field-service, practice or shop software adds up to $500 to the ready-made tool (often a built-in feature) and $500–$1,500 to a custom build.
Your price depends on volume, the systems involved and how many exceptions need a person. Our team confirms a fixed price before any work starts.
Proof and who stays in charge
Who does what
The automation does the routine steps. A person makes the call.
- 1Notice the changeAutomated
- 2Fill in the messageAutomated
- 3Send by text or emailAutomated
- 4Route repliesAutomated
- 5Deliver bad newsA person
Consent and privacy
Texts go only to customers who gave their number for updates or opted in, and say they're automated. Customers can reply STOP at any time.
FAQ
Questions about customer status updates
Usually. It reads status changes from systems like Tekmetric, Clio, ServiceTitan or Shopify, or from a spreadsheet if that's what you use.
Yes. Replies land in a shared inbox or on the job record so a person can answer.
Yes. You pick the stages and approve the wording, so customers aren't flooded with texts.
We recommend that a person sends delay news. The system can flag late jobs so nobody forgets to call.
Either or both. Customers can choose, and the business sets a default for each stage.
Yes. Each customer can have a preferred language, and the wording for each stage is approved in every language you use.
The update follows what the system says. A short pause before sending lets staff undo a wrong click, and a person sends any correction.
Yes. They can reply STOP or ask staff, and the choice is saved on their record.
Related use cases
Often built together
- Inventory & operationsProduction tracking boardA live board of every order's stage, with a view for each role and updates from the floor.
- Customer communicationReview requestsAsks customers for a review after a finished job or visit, and flags new reviews for a reply.
- Customer communicationInbox triageSorts incoming emails by type and urgency, links them to the customer, and routes them to the right person.
Want customer status updates for your business?
Pick the step that suits you. Every path starts with how the work runs today, and we'll say honestly whether it's worth automating.
- Right now · any hour
Ask Lorryn AI
Describe your process and get a first answer in a minute: what to automate, what it connects to, and a rough estimate.
- Free · 15 or 30 minutes
Talk to our team
Bring one process to a video call. Leave knowing whether it’s worth automating and how.
- Free · 6 of 15 spots left
Get a free written plan
Free for businesses with 3 or more employees, while spots last (normally $250).
Claim a free audit9 of 15 claimed