The simple idea
Choose five open customer conversations. Give each one a clear next action, an owner, a due date and a completion check.
Start with five open conversations
A customer follow-up can look active without moving forward. There may be a note in your customer records, an email marked unread or a task called ‘send proposal.’ None of those tells the whole team what should happen next.
Try a five-minute customer check. Choose five open conversations and make the next step clear for each one. The aim is a quick review, not a promise that every issue can be resolved in five minutes. If something needs investigation, assign that investigation rather than letting it disappear into another vague reminder.
Pick current conversations: a quote awaiting revision, a requested appointment, a question about scope, a proposal awaiting a decision or a customer waiting for an update. Start with the oldest unanswered item or the nearest commitment. You do not need to review the whole database at once.
Use five fields for each conversation
Open the customer records or shared spreadsheet your team already uses. Put these five fields beside each conversation so someone else can understand the next step without searching through messages.
- Customer need: What answer, decision or deliverable is the customer waiting for? Record the specific need rather than a broad label such as ‘sales lead.’
- Next action: What will move this conversation forward? Use a concrete verb: revise, send, confirm, review or call.
- Responsible person: Who owns that action? Name one person, even when other people will help.
- Due date: When should it happen? Use a date and, when useful, a time the owner can realistically meet.
- Completion check: What evidence will show that the action happened? A sent proposal, a recorded answer or a confirmed appointment is clearer than ‘handled.’
Keep the notes brief. Link to the relevant document or message where your team has appropriate access. Avoid copying sensitive customer information into a broadly shared sheet just to make the checklist complete.
Turn a reminder into a usable handoff
Here is a fictional example. A customer has asked for a revised proposal that separates the initial work from optional additions. The current task says ‘Send proposal.’ A colleague opening that task cannot tell which version is needed, who should prepare it or when the customer expects it.
Replace it with: ‘Alex sends the revised proposal by Friday at 2 p.m.’ The customer-need field says ‘Separate initial scope from optional additions.’ The completion check says ‘Record the sent version and send time in the customer record.’
If a manager must approve the revision first, make that dependency explicit: ‘Jordan reviews the revised scope by Thursday at 3 p.m.; Alex sends the approved version Friday.’ Alex still owns the customer-facing action and flags a missed approval before the deadline passes.
Sending the proposal completes this action. It does not mean the customer accepted it or the sale is complete. Record the next agreed step separately.
Separate customer waiting from team waiting
‘Waiting’ is not a useful status unless it names what is missing. ‘Waiting on our team: approval of revised scope’ needs an internal owner. ‘Waiting on the customer: preferred appointment date’ needs a clear record of what was requested and when.
Do not treat every customer delay as a reason to keep messaging. Respect the conversation, agreed timing and any request to stop contact. If your team owes an answer, resolve that responsibility before scheduling another customer reminder.
Keep the check small and repeatable
Use a brief daily check for work due soon, or a weekly review for less time-sensitive conversations. At the next check, look at the completion evidence before carrying a task forward. If it slipped, identify the blocker, agree a new action and update the customer when appropriate.
Start with your existing tools. Once the process is clear, workflow automation may help with routine reminders or handoffs, while a person remains responsible for exceptions. If your tools cannot support the process, explore custom software options before buying something new.
The useful result of this check is a record your team can act on: a need, an action, an owner, a deadline and a way to confirm completion. Which of your five conversations is still missing one of those?
If those next steps are still difficult to track, we can review your existing tools with you and identify one change that makes follow-ups easier to manage.