"Is it ready yet?" is the call every repair counter takes all day. The answer is on the repair ticket: the device came in on Monday, it went out to the service partner on Tuesday, the part is due Thursday. An AI phone agent can hold that ticket list, match the caller to their own job by the ticket number on their receipt, and answer in twenty seconds, including the hardest version of the call, the one where the device is not with you at all and there is nothing to collect yet.
A repair is the one purchase where the customer has given you their thing and got nothing back. A phone, a laptop, a watch, a bike, a coffee machine. They are living without it, and the estimate they were given ("about a week") starts feeling like a maximum on day three rather than an average.
So they ring. Not because they expect it to be ready, but because silence and a missing device feel the same as being forgotten. The counter is busy, the bench is busier, and whoever picks up has to put down a screwdriver, find the ticket, and explain the same thing they explained yesterday.
The information was never the bottleneck. The bottleneck is that only a person standing at the computer can turn a ticket into a sentence.
The tricky calls are the ones where you have already passed the device on: a warranty job that went to the manufacturer's service partner, a board that went to a specialist, a part on back order from a supplier. You genuinely do not know when it is coming back, and the caller genuinely wants a date.
The right answer here is not a date. It is: where the device is, when it left you, and when you next expect news. That is honest, it is checkable, and it is all recorded on your ticket already.
An automated line can say it as well as a person can, provided the sheet holds it. If your list has a column for "sent to service partner on", map it. If it does not, add one before importing; it converts your worst call type into your most reassuring one.
With PhoneMyAgent you upload the repair list (.xlsx, .csv or .json) on the Data page, choose the column the customer quotes, usually the ticket or job number printed on their receipt, and approve the sentence the agent may say, for example: "Repair 8812 for Mrs Novak is with the service partner since 22 July, and we expect an update by the end of next week." Columns you leave unmapped, your cost, the technician's notes, the customer's password hint, are stored but never spoken.
Then point a number at it, one from us or your existing line forwarded, and call it yourself. The 45 free minutes with no card are enough to import a real list and hear how it handles a ticket that exists and one that does not.
Matching is exact and never approximate. A ticket number finds one repair or none, a customer with two devices in hears the five most recent, and someone who has lost the receipt is either recognised from the number they are ringing from or offered a message. What the agent does on an order status call works through each case.
Every call arrives afterwards as an email with the transcript and a summary, so you can see what was asked without having taken it.
Repair references get quoted badly over the phone. People read a serial number instead of a ticket number, or read the ticket number off the wrong line of the receipt. Two things help: keep the reference short and print it in one obvious place, and decide in advance whether a serial or IMEI is also a valid way in, because if it is, it needs to be a mapped column too.
Where a reference could match two rows, for example a customer with a second repair on the same device, the agent asks for a confirming detail rather than picking one. It never reads out a row it is not certain about.
| Voicemail | The bench answers it | A status board on your site | AI agent on your ticket list | |
|---|---|---|---|---|
| Answers during a busy counter hour | Message only | Interrupts the work | Yes | Yes |
| Handles "it is with the service partner" | No | Yes | Rarely | Yes, from your sheet |
| Tells the caller when to expect news | No | Yes | No | Yes, if the sheet holds it |
| Cost per call | Listening back | Bench time | Development work | Included in the plan |
| Setup | None | None | Weeks | Minutes, from the list you keep |
It reads the status and dates your row contains, takes messages, books drop-off or collection appointments when you allow it, and transfers to you on request. It will not quote a repair price that is not agreed, approve extra work, promise a date the sheet does not hold, or speak columns you left unmapped. It does not handle emergencies or give regulated advice, and callers hear at the start that they are speaking to an AI assistant.
Keep money and liability with a person. A caller asking "how much will it be" for an unquoted job, or asking whether their data survived, should become a message with their number, not an answer from a line.
There is no live sync with Excel or Google Sheets: you upload a new version when the list changes, or edit one row in the dashboard when a device moves, which applies to the next call. Billing is a monthly plan with an allowance of minutes, never per minute.
The full walkthrough of building the sheet itself is in repair tracking spreadsheets that answer the phone, and the shop-counter version of this problem is in an AI receptionist for an electronics shop.
Yes. You import your repair ticket list, choose the reference customers quote from their receipt, and approve the sentence the agent reads back. On a call it looks up that exact ticket and gives the status, the location of the device, and the next expected step, or takes a message if it cannot identify the caller.
Exactly that, if your sheet records it: when the device left you, where it went, and when you next expect news. This is the call type most worth automating well, because it is the one that otherwise gets repeated every two days by the same worried customer.
No, unless the price is already agreed and stored in a mapped column. An unquoted repair is a conversation with a person, so the agent takes a message with the caller's number instead of estimating. The same applies to approving extra work found during the repair.
If your list includes a phone column, the agent can recognise the number they are calling from and answer without a reference. If it cannot identify them, it says so and takes a message with their name, number and what they described, so you can call back with the answer ready.
It is built to refuse rather than risk it. Lookups are exact, with no free search over the list and no partial matches. Where one reference could fit two rows, it asks for a confirming detail only the right customer would know and reads nothing until a single row wins.
As current as your last upload or edit. There is no live connection to Excel or Google Sheets, so a status reaches a caller only after you have uploaded the sheet or changed the row in the dashboard. For most repair counters a daily upload, plus edits when something moves, is enough.
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