A customer has replied with the missing detail. The account manager assumes sales will respond. Sales assumes the service team is preparing a recommendation. The CRM status still reads “open.” Everyone can see the record; no one owns the next action.
A status is not an assignment
A follow-up rule needs an event, an owner, an action and a way to tell when it is complete. “New enquiry” may trigger review. “Waiting for customer” needs a follow-up date or a closing condition. “Quote sent” needs an owner for the next contact and a record of the result. Status labels alone do not create those responsibilities.
Look for queues that accept work without accepting accountability: shared inboxes, unassigned CRM views, forwarded messages and tasks created without due dates. Identify the point where a named person or role takes custody.
Build a safe recovery path
Decide what happens when an owner is away, a message bounces or a customer does not respond. A backup role and an aged-work view can be enough for a small team. A larger operation may need queue rules or workflow automation. In either case, document who reviews exceptions and how unresolved enquiries become visible.
A practical inspection
- Choose a recent enquiry that needed a follow-up.
- Identify the event that should have created the next action.
- Name the owner, due condition and completion evidence.
- Check how absence, bounce or no reply is handled.
- Review unassigned and overdue work with a named role.