A homeowner asks for a cleaning quote on Instagram. Another sends an email. You answer one, ask the other for the property size, then leave for a job. By the afternoon, you have to search through conversations to remember who needs a reply.
This is an illustrative situation, not a client case. It gives us a useful starting point: one place to see each request and its next action, while keeping the original conversation where it belongs.
Give each request a place
Start with a shared list your team can actually maintain. One row represents one request, even if that customer sends several messages. Give it a short reference so two people don't create separate records for the same job.
Record the date received, the service requested, the contact channel, the current status and the person responsible. Add a next action and the date it is due. A contact reference or link to the original conversation is usually more useful than copying the entire message history.
For example, a fictional request for a move-out clean might say: “Waiting for details; owner: Alex; next action: confirm property size; due: Tuesday.” After those details arrive, Alex updates the same record. Sending a quote changes its status, but it doesn't complete the job.
Make the next action visible
Keep the status choices short enough that everyone knows what they mean. “New,” “Waiting for details,” “Quote sent,” “Booked” and “Closed” could work for a first version. Agree on what counts as booked before using that label. A quote sent to a customer is not an accepted booking.
A spreadsheet can support this first step. Google Sheets provides dropdown lists, which let you use the same status choices across rows. Its filters and filter views can help you review a subset of requests. These features organize what people enter; they don't automatically read your inbox or know when a customer has replied.
Review open requests at a time that fits your working day. Look for overdue actions and rows with no assigned owner. If someone is away, assign the next action to a person who can take it. A colored cell won't do that on its own.
Keep a person in charge of replies
Begin with internal reminders rather than automatic customer messages. Before following up, check the original conversation. The customer may have answered, declined, changed the scope or asked you to stop contacting them.
Keep prices, scheduling commitments and unusual requests under human review. If a reminder would be useful, first decide who receives it, when it should stop and how a completed action is recorded. Those rules matter before connecting any new tools.
Limit the list to information needed to coordinate the work. Don't put door codes, payment details or private documents into a general request tracker. Decide who can view or edit the information and remove access when a person no longer needs it.
Try the process before buying software
Walk through a few fictional requests first: one missing details, one awaiting a decision and one already booked. Check that another team member can tell what happens next without asking you to explain each row.
Then try a small batch of real requests using your approved business tools. Note where people have to copy information, which fields they skip and whether the list stays current. Compare the effort of maintaining it with the effort of finding the same answers in scattered conversations. This is a way to evaluate the process, not a promise of savings.
If you already use a booking system or customer management tool, check whether it supports the workflow before adding a second list. A separate tracker can create more work when it repeats information that already has a reliable home.
When a specific gap remains, you can scope a small change around it, such as bringing approved form submissions into the request list or preparing an internal reminder for review. See the request and quote tracking example for a possible first project. Bring your current process and tools to the conversation; the first step is understanding what needs to work better.