An enquirer shares an email address in chat so a course centre can send a prospectus. That address is for the requested document. It does not by itself show permission for newsletters or promotions. The team needs separate service, CRM and marketing records.
Start with the purpose of the address
Record why the person supplied the address before moving it. Sending an evening course prospectus is a service purpose; adding monthly offers is marketing. Fulfil the request even if the person declines marketing. The customer verification guide helps when identity needs confirmation without secrets in chat.
Keep three records instead of one status
A single contact field cannot explain what the person asked for, what the team did, and whether future marketing is allowed. Use a small record for each job.

- 1Requested deliveryUse the address for the document or answer requested.
- 2CRM contactKeep identity and ownership in the approved contact system.
- 3Email subscriptionAdd marketing only after an approved choice and successful sync.
| Record | What it proves | Where it belongs | What closes it |
|---|---|---|---|
| Service request | The person asked for a named document or answer | Conversation and task record | Requested item sent or request closed |
| CRM contact | The email belongs to the contact record used by the team | Approved CRM or contact system | Corrected, merged or retained under policy |
| Email subscription | The person made a valid choice about future email marketing | Email platform and permission ledger | Withdrawn, suppressed or expired under policy |
A contact can exist in the CRM and leads workspace while the email-marketing state remains “not asked”, “declined”, “pending” or “subscribed”. None should be inferred from the address alone.
Ask for email marketing permission separately
Make the marketing request optional and specific. Name the business, email channel and messages, such as monthly course updates and open day invitations. Require a clear positive action.
The UK Information Commissioner’s Office says electronic mail consent should be freely given, specific, informed and unambiguous. It advises separate channel choices and records of who consented, when and how. Its limited soft opt in conditions should not be assumed from an ordinary enquiry. This UK example is not universal legal advice; local rules and the privacy owner determine the approved wording and basis.
Keep the WhatsApp opt-in guide beside this process. Permission for WhatsApp marketing does not automatically establish permission for email marketing, and the reverse is also true.
Record the choice and the sync outcome
For an affirmative choice, store the purpose, channel, prompt version, answer, source conversation and timestamp. Keep the subscriber state separate from the contact record.
Then record whether the email platform accepted the update. A configured CRM or webhook can fail, reject a malformed address or time out. Mark that result as pending or failed instead of silently treating the person as subscribed. A human owner should review the exception before any campaign uses the address.
The shared inbox can show the conversation and owner on supported, correctly configured channels. It does not approve wording or prove that an external email platform accepted the subscriber.
Make withdrawal operational
Withdrawal needs a usable route. When someone unsubscribes, record the channel, time and resulting suppression state. Keep enough suppression information to prevent a later import from adding the address back. Limit access and retention under the organisation’s privacy policy.
The ICO’s planning guidance recommends deciding the purpose, responsibility, lawful basis, accuracy and retention before direct marketing starts. That planning work belongs before a list upload, not after a complaint.
Test with a non-customer address: request a document, decline marketing, confirm delivery, then verify that the address is absent from the campaign audience. Repeat with a choice, sync failure and withdrawal. The campaigns workspace should receive only people who passed permission and suppression checks.
Use one owner for the handoff
Assign the handoff from chat to email: the conversation owner fulfils the request, marketing or privacy approves the prompt, and integration monitors updates. Review completed requests, prompts, positive choices and accepted subscriber updates separately. These counts describe the process, not sales causality.
Frequently asked questions
Can we email the prospectus the person requested?
Send the requested document to the address supplied for that purpose, subject to your organisation’s policy. Future promotional emails need their own approved basis and record.
Does creating a CRM contact make someone an email subscriber?
No. A CRM contact helps the team identify and serve the person. The email-marketing state needs a separate field, evidence and suppression path.
Should we use double confirmation?
That depends on the market, risk and email platform. A confirmation email can strengthen the record, but it does not replace a clear initial request or the organisation’s legal review.
Sources
Want help applying this guide?Ask the DripTell team
From reading to action
Want help applying this to your business?
Share your details. We will read the article you are on and start with a useful answer for your team.
DripTell Editorial
Practical guidance reviewed by the DripTell product and customer workflow team.
See how DripTell checks product claims, uses primary sources and handles corrections.
Editorial and source policy



