Honor a clear stop-contact request across channels

Instruction: State the immediate actions and write the message to the other record owner.

Context:

A prospect replies to your business email: “Stop contacting me. No emails or calls.” The CRM shows an active email sequence, a call task tomorrow, and a possible duplicate record owned by another rep. The duplicate has not been confirmed as the same person.

Under this fictional company’s policy, stop-contact requests must be recorded and honored across channels. Use the approved suppression and identity-review processes; do not merge uncertain identities. An external confirmation message is not required.

Updated

Example Answer

I would stop both known routes of contact now: unenroll the confirmed record from the email sequence and cancel tomorrow’s call. I would record the prospect’s exact request, its source and time, apply the approved suppression controls, and verify that pending outreach actually stopped.

My internal message would say: “This prospect requested no emails or calls. Their confirmed record is suppressed, and my pending outreach is canceled. Your record may be the same person. Please pause its outreach while we verify identity through the approved process, then confirm the outcome. Please do not contact the prospect to resolve the duplicate.”

I would flag the possible duplicate to operations and preserve the activity history and request. If it is the same person, the suppression must carry through both records and connected tools. If it is a different person, operations can resolve the pause against the correct identity and preferences. I would check completion with the other owner and escalate any tool that still has pending contact. No additional external message is needed here.

What the interviewer is assessing

  • Essential: Stops email and calling, records the request, and checks that suppression took effect.
  • Stronger: Prevents contact from the possible duplicate while preserving identity uncertainty and following through on resolution.
  • Red flags: Removes only one channel, deletes the evidence, or merges records before identity is confirmed.

Follow-up

Interviewer: The other rep says the possible duplicate is their lead and wants to finish their sequence.

Response: I would ask them to keep outreach paused until identity is resolved and route the disagreement to the responsible operations owner. Ownership does not override a confirmed preference. If the records match, the same suppression applies; if they do not, operations should restore only the appropriate record’s permitted workflow.

Related Questions