Start with the leak, not the software
I draw the current path before recommending tools. If a website form reaches a shared inbox, the map must say who opens it, how quickly, and what proves that follow-up happened. “The team handles it” is not an owner.
Keep the first map to one page. Vendor names matter only when they change who receives the inquiry, where the next task lives, or whether source and outcome survive the handoff.
Map every entry point the same way
For each source, write one line from arrival to outcome. A useful employment-law example is: website form → intake queue → intake lead → consultation task → source and fit recorded. The same grammar should work for phone calls and referrals.
- Name the first receiver by role.
- Name the response expectation.
- Name the system that owns the next task.
- Require a source, status, and final outcome.
- Name the weekly exception reviewer.
Review exceptions, not every record
The operator should not spend Monday rebuilding the week from inboxes. The weekly review should show only missing owners, overdue next steps, unknown sources, unlabeled matter types, and records with no outcome.
That exception list is the smallest useful management system. It shows whether the map is being followed without turning intake into a reporting job.