Every repair counter gets the same call all day: is it ready yet. If you keep a repair tracking spreadsheet, the answer is already written down, one row per job, and an AI phone agent can read it out. The customer quotes their job or ticket number, the agent finds exactly that row and says where the repair stands, and anything that needs a decision from you, a quote to approve, a part that changed the price, still comes to you as a message or a transfer.
A repair business runs on two things at once: the work in front of you and the status of the work behind you. The spreadsheet handles the second part well. Job number, customer, device or vehicle, fault, status, promised date, sometimes a price.
The call is the interruption. Answering it means putting down a screwdriver, washing your hands, finding the row, reading it out. Not answering it means a voicemail you clear at seven in the evening and a customer who calls again tomorrow. Neither is the work you are paid for, and the question they are asking, what does row 118 say, is a lookup, not a judgment.
The one thing worth tidying before you import is the status column. A spreadsheet written for yourself tolerates shorthand: "w/p", a supplier name, a date with no context. A caller hearing that gets nothing.
Statuses that work on the phone are the ones a customer can act on:
You do not need to restructure the sheet. Mapping the column and approving the sentence the agent says is the whole configuration.
With PhoneMyAgent you upload the repair log (.xlsx, .csv or .json) on the Data page. The import asks which column callers quote, usually the job or ticket number, and what the agent should say back, in a sentence you approve: "Job 118, the screen replacement, is waiting for a part, expected Friday." Columns you do not map, your cost, the technician's notes, the margin, are stored but never spoken.
On a call it looks up exactly the number given. A near match is refused, because the near match is another customer's repair. If your sheet has a phone column, regulars are recognised from the number they are calling from. If nothing matches, the agent says so and takes a message rather than improvising a status. When a customer has several jobs open, it reads the five most recent and says there are more. You can try this on your own line with 45 free minutes and no card.
Money is the boundary worth being deliberate about. If the price is in the row and it is final, the agent can say it. If the job needs a quote approved, or the price changed because of what you found inside, that is not a lookup any more and it goes to you as a message or a transfer. Nobody wants an agent negotiating a repair bill from a stale cell.
| Voicemail | Call them back | Ticket portal | AI agent on your repair log | |
|---|---|---|---|---|
| Customer hears the status | Never on the call | When you get to it | If they registered | On the first ring |
| Works for walk-in trade | Yes | Yes | Rarely | Yes |
| Handles evenings and Saturdays | Message only | No | Yes | Yes |
| Your effort per call | Listening back | The full call | Setup and upkeep | None, email afterwards |
| Built from what you already keep | Yes | Yes | No | Yes, the spreadsheet |
It reads the status from the caller's own row, takes messages, books drop-offs when you allow booking, and transfers on request. It will not invent a completion date, will not approve or negotiate a price, will not guess between two possible jobs, and does not handle emergencies or give regulated advice. Callers hear at the start that they are speaking with an AI assistant, and every lookup appears on the call log next to the transcript, so you can see which job number was read out on which call.
There is no live sync. Import is an upload, export is a download. Most repair logs change several times a day, so the practical rhythm is either a re-upload when you close the day or editing individual rows in the dashboard as jobs move, which takes effect on the next call.
Shops with a counter as well as a bench may want the electronics shop walkthrough, which covers stock and price calls alongside repairs.
Yes, when the status is in your spreadsheet. The customer quotes their job or ticket number, the agent looks up exactly that row and reads back the status in the wording you approved. If the number does not match a row, it takes a message instead of guessing.
If your log has a phone column, the agent recognises the number they are calling from and can answer without a reference. Otherwise it asks, and if they cannot produce it, it takes a message with their number and what they asked so you can call back with the answer ready.
Only if the price is already in the row and you mapped that column. Anything that needs approval, a revised quote or a decision about whether to go ahead, is handed to you as a message or a transfer. The agent does not negotiate and does not make up a figure.
Either re-upload the sheet when it changes or edit rows in the dashboard as jobs move; both take effect on the next call. There is no live connection to your file, so the agent can only say what you uploaded or typed.
No. Lookups are exact, with no free search over the log, and ambiguous matches are refused. Where two rows could answer to one reference, the agent asks for a confirming detail only the right customer would know and reads nothing until one row wins.
Yes, and the job sheet is the same shape in both: a row per vehicle or device with a status and a promised date. Bike shops, appliance repair, shoe repair and phone repair counters all import the same way, because the call is the same call.
Never miss another call
An AI agent answers your business phone, knows your documents, and emails you what happened after every call. 45 free minutes to try, no card required.
Try PhoneMyAgent free