A customer database in Excel is the most common CRM in small business, and it can do more than sit there: import it, and your phone line recognises the number a regular is calling from and answers from that customer's own row. No customer number to quote, no menu to sit through. If the number is not in the list, or two customers share it, nothing is read out and the caller is asked for something identifying instead. The recognition is a convenience, never the security.
Most small businesses have the same file: one row per customer, columns for the name, phone, address, what they bought or booked, notes. It survives because it is fast to edit and everyone understands it.
The trouble is that it only helps the person holding the mouse. A regular calls, and the person answering either recognises the voice or asks the same three questions again. Out of hours nobody answers at all, and the message that lands in voicemail begins with "you know me, I was in last month", which is true and completely useless without the file open.
With PhoneMyAgent you import the list (.xlsx, .csv or .json) and map the phone column. When someone rings, the agent checks that number against the list. Three outcomes, and the last two are the interesting ones:
Where your list has a second identifying column, the import can use it as a confirming question. The agent then finds the row, does not read it out, and asks the caller to confirm the name on the record first. It never says the name and waits to hear it back. Answer wrongly a few times and the lookup closes for that call and offers a message.
You upload the file on the Data page and the import asks which column callers identify themselves by, a customer number, a phone, sometimes a name, and what the agent should say back, in a sentence you approve. Columns you do not map are stored but never spoken, so payment history, credit notes or a frank remark about a customer stay yours.
Two things the product insists on, because a customer list is personal data:
More on the wider compliance picture, disclosure, recording and where data sits, is in GDPR and AI call answering in Europe. You can try the whole thing on 45 free minutes with no card.
| Voicemail | A phone book on the desk | Generic call centre | Your Excel list on the line | |
|---|---|---|---|---|
| Knows the caller | No | If someone looks | No | Yes, by their number or reference |
| Answers their own details | No | Yes, in office hours | No | Yes, exact match only |
| Available at 8pm | Message only | No | Sometimes | Yes |
| Sees only what you allow | Everything you record | Everything | Whatever you send | Only mapped columns |
| Cost | Cheap | Your time | Per call or seat | A monthly plan |
It answers from the caller's own row, books, takes messages and transfers on request. It will not read out a row it is not sure belongs to the caller, will not speak unmapped columns, will not search the list for anyone who asks, and does not give medical, legal or financial advice. Callers hear at the start that they are talking to an AI assistant. Rows are editable in the dashboard and export back to Excel whenever you want, and deleting the table deletes its rows.
If the list you actually live in is orders rather than customers, the order tracking walkthrough is the closer fit, and the general comparison of spreadsheet agents is in which kind of Excel AI agent you need.
Yes, when the list has a phone column and you map it. The agent matches the number the person is calling from against the list and answers from that row. If the number is on two rows, or withheld, or missing, it asks for a reference instead and reads nothing until one row matches exactly.
The list is stored for lookup, not mixed into the knowledge the agent quotes to anyone. On a call it sees one row, the one identified by the caller, and only the columns you mapped for speaking. You accept a data processing agreement before the import runs, and deleting the table deletes its rows.
No. There is no free search over the list. A caller reaches one row, found by the exact reference they give or by the number they are calling from, and ambiguous matches are refused rather than guessed at. That single rule is what makes a customer list safe to put behind a phone line.
Then caller ID is not proof of identity, so the agent stops using it for that table and asks for a reference. The import detects this at upload time and tells you, rather than letting it surface on a live call.
No. You keep working in Excel, upload a new version when it changes, and edit individual rows in the dashboard for small corrections. There is no live sync, so nothing changes what the agent says except an upload or an edit you made. Export gives you the whole table back with your own column headings.
They identify themselves the same way they do today, by quoting a customer number, an invoice number or an order reference, whichever column you mapped as the key. Caller recognition is a shortcut for the regulars, not a requirement for everyone.
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