Losing track of who needs a reply? Get email enquiries into one clear list

A customer relationship management system, or CRM, can hold that list. A shared spreadsheet may be enough to begin with. In our own operation, automated capture is backed by a separate check for enquiries that haven't reached it.

See who is waiting without opening every conversation

Keep the original message one click away. A short description should tell you enough to act without copying the whole conversation into another store.

The point is to avoid entering the same details twice and then searching for them later. A record full of optional fields doesn't help if it still leaves you wondering whether anyone replied.

Keep the screen easy to scan. “Needs a reply”, “Waiting for information” and “Ready to arrange” can be more useful than labels nobody has agreed how to use. Decide what moves a request from one state to another.

A prepared reply isn't a sent reply. Mark it as sent only when sending is confirmed, and keep proposed appointments separate from confirmed bookings.

Updates may come from outside the inbox too. A small phone app can capture a visit note and upload it to your local system, where it is matched to the existing job. The connection and matching rules need to fit your current records; an uncertain match should wait for someone to check.

Catch the enquiry that never made the list

An automation saying it ran doesn't tell you that every enquiry was captured. It could have looked in the wrong folder or skipped a message it couldn't understand.

Compare the incoming requests with the records created or updated, allowing for the normal processing delay. Flag anything without a matching result or a reason for being held. Keep the original message within reach so checking a mismatch doesn't become another search.

Unclear requests can wait for a person. Record why they stopped and who will deal with them. Guessing a complete description would leave you correcting the record later.

Don't create two jobs from one conversation

In this made-up example, someone asks for help, then sends a document in a second email. Those messages belong to the same enquiry. Two separate records could lead to duplicate replies or two people chasing the same work.

Use message and conversation references to help match updates. A returning customer may also be asking about a different job, so similar wording alone isn't enough to merge records.

Test an exact repeat, a follow-up and a separate request from the same person using made-up messages. Stop and restart the test too. Check that restarting does not create extra records.

During a trial, review the held messages alongside the enquiry list. Keep a missed item visible until it is dealt with. You need that list to plan the next call or visit, including the work the automation could not finish.