Where to start with automation when your business runs on a phone and Excel

Start with the work around the tools

The phone and Excel are rarely the real problem. The difficulty is what happens before and after each one.

A customer calls while you are driving or working on site. You remember to call back, but not until later. A job is agreed over the phone, then someone has to copy the details into a spreadsheet. A row is marked as “follow up”, but nobody is sure when or who should do it.

These gaps create repeated admin and make it harder to see which requests are waiting for a reply.

Before choosing a tool, follow one ordinary request from beginning to end. Write down:

• where the request arrives
• what information is collected
• where that information is recorded
• who decides the next step
• how the next action is remembered
• what happens when the request does not fit the usual pattern

Do not map every process at once. Choose one route that happens often and has a clear owner.

A phone and Excel workflow in practice

Imagine a small decorating business. Most new enquiries arrive by phone while the owner is on a job. Excel contains customer names, postcodes, job notes and follow-up dates, but the sheet is updated in batches.

A first automation might support the handoff like this:

1. The caller leaves agreed details through voicemail, a form or a receptionist process.

2. The details are turned into a short enquiry summary.

3. A new row is added to the relevant Excel table.

4. The owner receives a notification with the next action.

5. The owner reviews the request and decides whether to call, ask a question or close it.

The automation does not decide whether the job is suitable, produce a quote or promise an appointment. It moves information from the first contact to the person responsible for the decision.

That distinction matters. A useful first workflow supports a judgement; it does not hide the judgement inside a system.

What to automate first

The best starting point is usually a repeated handoff with a trigger and a clear next step.

New enquiries

If enquiries arrive by phone, email, WhatsApp or a website form, the business may have several versions of the same process. A simple workflow can bring the essential details into one place.

For a trades business, that may include the customer’s name, postcode, property type, broad description of the work and preferred contact method. For a cleaning company, it might include the property type, service and timing.

Collect only what the person handling the enquiry needs. A long questionnaire can make contact harder without improving the handoff.

Follow-up reminders

Many small businesses do not need a sophisticated customer relationship management system to improve follow-up. They may need a consistent reminder when a row reaches a certain status or date.

For example, when an Excel row changes from “new” to “quote sent”, the workflow could create a reminder for the agreed review date. If the status changes to “booked”, that reminder should stop or move to the next stage.

The rule needs to be visible and easy to correct. A person should be able to update the row without fighting the automation.

Repeated customer questions

Phone calls and messages often contain the same practical questions: service area, opening hours, information needed for a quote, or how to send photographs.

Approved answers can be prepared for these questions. A person can still handle anything unusual, sensitive or outside the business’s stated information. The point is to make routine replies more consistent, not to make the assistant answer every question.

Internal summaries

After a call, the useful output may be a short summary rather than a customer-facing message. The summary could show what the caller wants, what information is missing and who owns the next action.

This is often a sensible place to begin because the team can review the result before it affects a customer. It also reveals whether the business’s questions and categories are clear enough.

How Excel can fit into the first workflow

Excel is not automatically the wrong tool. If the sheet is understood by the people using it and the process is modest, it can be a practical starting point.

Make the table predictable before connecting anything to it. Use clear column headings, one row per customer request and a small set of agreed status values. Keep dates in date columns and avoid storing several unrelated pieces of information in one cell.

A basic enquiry table might contain:

• date received
• customer name and contact details
• location or postcode
• enquiry type
• status
• owner
• next action date
• notes

The useful test is whether another person could open the sheet and understand what needs attention without asking the owner for a translation.

If several people edit the file at the same time, or if different versions are being emailed around, the problem may be the way the spreadsheet is shared rather than the spreadsheet itself. That should be resolved before automation is added.

What should remain with a person?

Keep human approval for decisions involving judgement, sensitive information, complaints, money or a commitment to the customer.

A system can flag an enquiry as ready for review. The owner can decide whether the work is within the service area, whether the timing is realistic and whether a quote should be prepared. A workflow can remind someone to check an existing booking. It should not quietly change the booking without an approved process.

For healthcare, financial services and other sensitive work, routine administrative information may be suitable for assistance, while advice, assessment and decisions should remain with the appropriate person.

If the automation cannot understand a request, “send to a person” is a valid outcome. It is better than forcing every situation into the nearest category.

How to test a small automation safely

Before using a workflow with real customers, test it with ordinary examples, an incomplete message, an existing customer, a request outside the service area and a situation that needs a human decision.

Check whether:

• the right details reach the right place
• the status and next action are clear
• duplicate records are avoided where possible
• the person responsible receives the handoff
• an unusual request can leave the normal route
• a human can correct an error without technical help

For the first version, review every output. Note unclear wording, unnecessary questions and extra work before expanding the process.

Signs you are ready for a bigger system

You may eventually outgrow Excel when the business needs more detailed access controls, a fuller history of customer interactions, multiple people working on the same records or reporting across several workflows.

Review the process before buying a large platform. A bigger system will not make unclear ownership or inconsistent data disappear. The first workflow gives you evidence about what the business needs.

Starting with a phone and Excel can be sensible. Begin with one repeated handoff, make the next action visible and keep decisions with a person. Once that route is clear, decide whether another process is worth automating.

Amoskalets helps UK small businesses examine practical AI automation opportunities around the tools they already use. The starting point is a conversation about how enquiries, follow-ups and customer information are handled now. From there, the business can choose a focused first workflow and decide where human review belongs.

Find out more at amoskalets.com.