1. Find the right customer.
Start with a contact already in the CRM. Send a reply from a test phone and see whether the system places it in the correct record. A newly created duplicate contact is a workflow problem even if the message arrived.
2. Give one person the next action.
Ask how an agent accepts responsibility and how a colleague knows someone is answering. Avoid relying on a verbal agreement that disappears at the end of a shift.
3. Preserve the reason for the conversation.
The replacement agent should see the relevant history, the customer’s request, and any promises already made. Check attachments and notes rather than assuming plain-text history tells the whole story.
4. Stop automation from talking over a person.
Reply during a scheduled follow-up sequence. Verify what stops, what remains queued, and how a teammate restarts an appropriate workflow. Record the behavior in the team’s operating notes.
5. Know where to go when delivery is uncertain.
A sent request is not proof of delivery. Ask what states the interface exposes, how failures are explained, and which person owns follow-up. Repeat the exercise on the alternate channel your customers use.