Manage inbox hygiene
Keep the conversations view usable as volume grows.
Purpose
When to Use This SOP
- The conversations view feels cluttered
- Replies are being missed
- Team members are unsure who owns each conversation
- Internal notes and external replies are being confused
- Leads are replying but pipeline stages are not being updated
- Missed calls or inbound SMS messages need follow-up
- The business needs a simple daily inbox routine
Before You Start
- Do not treat the inbox as a replacement for pipelines, tasks, or workflows. The conversations view shows communication. It should support the operating process, not become the entire process.
You should know:
- Who reviews inbound messages
- Which users are assigned to contacts or opportunities
- What counts as urgent
- When a conversation should create a task
- When a reply should move a pipeline stage
- When a human handoff is required
- How internal notes are used
Step-by-Step Procedure
- 1Define who owns inbox review
Assign responsibility for reviewing conversations.
This may be:
- One admin
- One sales user
- One support user
- A rotating team member
- The assigned contact owner
- The opportunity owner
Do not leave inbox ownership vague.
If everyone is responsible, no one is responsible.
- 2Separate internal notes from external replies
Make sure the team understands the difference between:
- A message sent to the contact
- An internal note for the team
- A task
- A pipeline update
Internal notes should be used for team context, not for replying to contacts.
Before sending anything, confirm whether it is visible to the contact or only visible internally.
- 3Create a read and unread discipline
Unread conversations should mean something.
Create a simple rule:
- Leave unread only when action is still needed
- Mark reviewed when no action is needed
- Assign the conversation if a specific person must respond
- Create a task if follow-up should happen later
- Move the opportunity if the reply changes the sales status
Do not use unread as a permanent storage system.
- 4Review inbound replies first
Prioritize replies from real contacts before reviewing system messages or old threads.
Look for:
- New replies
- Appointment questions
- Pricing questions
- Cancellation or reschedule requests
- Support issues
- Objections
- “Stop” or unsubscribe messages
- Wrong-number replies
- Urgent service issues
Replies often indicate that a workflow should stop or a human should take over.
- 5Check missed calls and voicemail-related messages
Missed calls should have a clear follow-up path.
For each missed call, confirm:
- Was a missed-call text-back sent, if configured?
- Did the contact reply?
- Should the team call back?
- Should a task be created?
- Should the opportunity move stages?
- Should the contact be marked as needing review?
Do not assume missed-call automation replaces human follow-up.
- 6Assign conversations when ownership is clear
If a message needs a specific person, assign it.
Assignment is useful when:
- A sales rep owns the opportunity
- A support person owns the issue
- A calendar owner needs to respond
- A manager needs to review the conversation
- A team member had the previous interaction
Avoid leaving important conversations unassigned.
- 7Create tasks for delayed follow-up
If follow-up is needed later, create a task instead of relying on memory.
Tasks may be needed for:
- Call back tomorrow
- Follow up after appointment
- Review document
- Send proposal
- Check payment status
- Confirm onboarding details
A task should include the action, owner, and due date.
- 8Move pipeline stages when the conversation changes status
Some replies should change the opportunity stage.
Examples:
- Contact books an appointment
- Contact asks for proposal
- Contact says they are not interested
- Contact becomes a client
- Contact requests follow-up later
- Contact no-shows and then replies
- Contact says the timing is wrong
The inbox should not be disconnected from the pipeline.
- 9Respect opt-out and do-not-contact signals
If a contact says stop, unsubscribe, wrong number, or do not contact, treat that seriously.
Confirm:
- The correct opt-out or do-not-contact status is applied
- Marketing workflows stop where appropriate
- The team does not keep manually messaging
- Notes are added if context is needed
- The contact is handled according to platform and business rules
This is a planning baseline, not legal advice. Consent and communication rules vary by location, industry, message type, and platform requirements.
- 10Create a daily inbox cleanup routine
Set a simple daily routine.
Suggested routine:
- Review new inbound replies
- Review missed calls
- Review unread conversations
- Assign messages that need owners
- Create tasks for delayed follow-up
- Move pipeline stages where needed
- Add internal notes for context
- Confirm urgent messages are handled
- Clear messages that no longer need action
A clean inbox makes the team faster and prevents leads from slipping through cracks.
Checks Before You Finish
- ✓Inbox owner or review process is defined
- ✓Team understands internal notes vs external replies
- ✓Unread status has a clear meaning
- ✓Inbound replies are reviewed first
- ✓Missed calls have a follow-up process
- ✓Conversation assignments are used where needed
- ✓Tasks are created for delayed follow-up
- ✓Pipeline stages are updated when replies change status
- ✓Opt-out and do-not-contact signals are respected
- ✓A daily cleanup routine is defined
Common Mistakes
- Treating the inbox as a task manager
- Leaving every conversation unread
- Forgetting to assign conversations
- Confusing internal notes with outbound replies
- Letting replies sit while workflows keep sending
- Not stopping follow-up after someone replies
- Ignoring missed calls because text-back exists
- Failing to move pipeline stages after important replies
- Manually messaging contacts who opted out
- Letting old conversations clutter daily review