Start with the promise, not the loudest notification.
A customer was promised an estimate yesterday. Someone else sent a second inquiry this morning. A third customer asked you to check back next month. All three may look unfinished, but they do not need the same response today.
Start a backlog review by checking the latest conversation, the promise already made and the next action due. Separate work that needs attention now from work waiting for a specific date or decision. Then choose a small, realistic set of actions for the people available.
This guide is for routine customer follow-up. It is a way to organize judgment, not an automatic ranking of customers. Your existing safety or urgent-service process takes priority when applicable.
Sort the work before contacting anyone.
Use one shared list of open requests. Check for replies or changes before adding a follow-up task; a stale list can send your team after work that is already resolved. Repeated messages may belong to one request, while two jobs from one person may need separate records.
On a small screen, swipe or scroll sideways to read the full table.
| Group | What puts it here? | Decision to make |
|---|---|---|
| Promise due or missed | A specific commitment is due, or has passed without completion evidence. | Confirm what remains, who can act and whether the customer needs an honest update. |
| Next action ready | The team has what it needs, and follow-up is appropriate now. | Choose the action and a responsible person with capacity. |
| Blocked | A missing detail, approval or internal decision prevents progress. | Name the blocker, the person who can resolve it and the next review date. |
| Waiting until agreed date | The customer or team has set a future point to revisit the request. | Keep the date visible. Do not chase early just to clear the list. |
Closed or withdrawn requests leave this active list only when the record supports that decision. A quiet customer is not automatically a lost customer. Keep contact preferences and stop requests visible before any outreach.
Choose work your team can actually finish.
Once you can see the groups, review due and missed promises first. Within comparable work, consider the promised time, the consequence of further delay and how long the next action has been waiting. An expensive potential job should not silently erase an earlier commitment.
Agree who has time for which actions today. A request assigned to somebody with no capacity still needs a decision. Use accepted backup coverage, a revised commitment or an explicit escalation to the person authorized to resolve the conflict.
Put a reasonable limit on actions actively being worked, based on the actual work and people available. Do not invent a universal quota of calls per day. A complicated estimate review and a simple receipt confirmation are different tasks.
Atlassian describes limiting work in progress as a way to reveal bottlenecks and focus attention on existing work. The review groups and worksheet here are JetSynapse’s suggested application to routine customer follow-up, not a tested productivity benchmark. Read Atlassian’s explanation of work-in-progress limits.
See the decision in a small example.
Fictional example: A repair business opens the day with four unresolved requests. The office team has a limited follow-up window before scheduled customer work.
On a small screen, swipe or scroll sideways to read the full table.
| Request | What the record says | A useful next action |
|---|---|---|
| A: estimate promised yesterday | The estimator has not confirmed it is ready. | Office owner checks with the estimator and arranges an accurate update. Do not mark the estimate sent. |
| B: second message this morning | The customer added a photo to an existing request. | Attach the new detail to that request and keep its owner; avoid creating competing callbacks. |
| C: asked for next-month contact | The requested date is recorded. | Retain the future review date and leave today’s contact queue. |
| D: requested estimate, missing scope | The team cannot prepare it without one detail. | Assign a bounded clarification step, subject to the customer’s contact preferences. |
The result is a decision for every request. It is not proof of a booking or sale. If the estimator is unavailable, request A remains visible as blocked even after the office has sent an update.
Use the backlog review worksheet.
Download the blank review worksheet (CSV). Open it in your preferred spreadsheet. No sign-up is needed. Keep any completed copy in your own approved workspace; use an internal reference rather than copying customer messages or sensitive details into it.
On a small screen, swipe or scroll sideways to read the full table.
| Field | What to record |
|---|---|
| Request reference and reviewed at | Which request this is, and when someone last checked the current record. |
| Last verified state | What is known to have happened, not what somebody intended to do. |
| Promise and due time | The actual commitment, including date and time zone when relevant. |
| Review group and blocker | Use the groups above. State the missing decision or detail if blocked. |
| Next action and owner | One specific action and the person who has accepted it. |
| Review time and completion evidence | When to check again, and what would show the action happened. |
For example, “follow up” is too vague. “Office team checks whether the revised estimate is ready before the agreed callback” tells the next person what to do. Completing that check does not automatically close the customer’s request.
Close the review without hiding unfinished work.
At the next review, check what changed: actions completed, promises missed, work still blocked and new requests added. If a request has an owner but never moves, look at capacity, missing authority or an unclear action before assuming another reminder will solve it.
Track the number of actionable requests waiting and the age of their due actions. Keep future scheduled work separate so a healthy waiting list does not look like an overdue backlog. If work arrives faster than the team can handle it, make that constraint visible to the person who can change staffing, scope or commitments.
Use the customer-path review for recurring patterns. Use this worksheet for today’s decisions. The goal is simple: nobody has to guess which request needs attention, who has it or what happens next.