Build a Channel by Channel Marketing Consent Record

Small service businesses should record marketing permission separately for each channel and purpose. Recent guidance from the UK's Information Commissioner's Office and Advertising Standards Authority reinforces that consent must be clear, active, specific, and easy to withdraw.

A single field labeled "marketing consent" does not tell your team whether a person agreed to email, text messages, phone calls, or a particular type of offer. Your hosted CRM should preserve enough detail to show what the person accepted, when they accepted it, and what changed later.

Why a general consent field creates avoidable work

Service businesses often collect a name and email address through an inquiry form, estimate request, appointment process, or completed sale. That collection gives the business a contact record, but it does not automatically explain whether promotional messages are permitted.

The ICO states that consent must involve a clear affirmative action, and that organizations should not use pre-ticked boxes. It also notes that consent may be required for many marketing calls, messages, cookies, and similar activities.

The practical risk is not limited to an incorrect campaign. A vague field can leave staff unable to answer a basic customer question: what exactly did this person agree to receive?

Fix: replace the single permission field with an organized consent record. Keep service communications, operational notices, and marketing permissions distinct so staff can make the correct decision without guessing.

What current guidance means for CRM records

The ICO says consent should be specific, informed, freely given, and demonstrated through an affirmative action. It also says people must be able to withdraw consent, and that withdrawal should be as easy as giving it.

The ASA guidance adds that businesses relying on consent should tell people about their withdrawal right. It also describes conditions for certain existing-customer email or text messages, including similar services and a clear opportunity to refuse future messages.

These rules do not require every business to use the same form or CRM layout. They do require a record that matches the permission request and supports the decision made before a message is sent.

The fields to add or review

Use one record structure for every permission event. The exact field names can differ, but the meaning should stay consistent.

• Contact: identify the person or business record connected with the permission.
• Channel: record email, text message, phone, or another channel separately.
• Purpose: describe the type of marketing, such as service updates, offers, or educational information.
• Wording: preserve the notice or consent language shown when permission was requested.
• Action: record the affirmative action, such as selecting an unchecked box or confirming a preference.
• Date and source: record when and where the permission was collected.
• Status: show whether permission is active, withdrawn, expired under your policy, or under review.
• Withdrawal: record the date, channel, method, and scope of any opt-out.

Do not rely on a note such as "customer agreed" without supporting detail. A short note may help staff, but structured fields make filtering and campaign controls more reliable.

Separate channel permission from service contact

A customer may need an appointment reminder without wanting promotional messages. A prospect may request an estimate without agreeing to future offers. Your CRM should let staff complete necessary service communication without treating it as marketing permission.

Create separate statuses for operational contact and promotional contact. Then connect marketing workflows only to records with the required active permission for that channel and purpose.

Next step: review every automated message and label its purpose. If a message promotes additional work, a discount, or a related service, route it through the appropriate marketing permission check.

Make the collection screen match the CRM

The form, phone script, paper document, and CRM fields should describe the same choices. If the form asks about email offers but the CRM stores only a general marketing status, important detail disappears during handoff.

Use plain language and avoid combining unrelated permissions into one required choice. The ICO says consent cannot be required as the price of receiving a service.

Show separate choices when channels or purposes differ. For example, a person might choose email service offers while declining text messages. Store both selections instead of recording a single positive result.

Design the withdrawal process before sending campaigns

Every marketing workflow needs a reliable stop condition. A withdrawal should update the affected channel and prevent new messages, while leaving the history available for compliance and staff reference.

Do not delete the withdrawal record merely because the contact asks to stop. Deleting it can remove the evidence needed to prevent future messages and explain why a campaign was blocked.

1. Capture the withdrawal date, channel, and request source.
2. Change the permission status immediately.
3. Remove the contact from eligible campaign audiences.
4. Check connected sending tools for pending or copied lists.
5. Test that the next campaign excludes the contact.

Keep the process simple for staff. A clearly labeled preference action is safer than asking employees to interpret free-text notes during every campaign.

Review permission before using an old list

Past customers and older inquiries may still have useful commercial value, but age alone does not prove current permission. Before reactivating an old segment, confirm the original channel, purpose, wording, and withdrawal history.

The ICO advises organizations to keep personal data only as long as needed, while acknowledging that retention depends on the circumstances. Apply that principle to both contact details and permission history, using a documented retention decision rather than an indefinite default.

Next step: create an "unverified permission" status. Exclude those records from marketing until staff can confirm the lawful basis and the current channel preference.

Use a monthly permission check

A short recurring review can catch broken forms, stale exports, and workflow mistakes before they affect many contacts. Choose a sample of recent records from each collection source and compare the original request with the CRM entry.

• Confirm the selected channel matches the stored channel.
• Confirm the purpose is specific enough for staff to understand.
• Confirm the date and source are present.
• Confirm withdrawn contacts are excluded from active campaigns.
• Confirm staff can find the permission history without searching unrelated notes.

Record the review result and assign a correction when a field is missing. This turns consent management into a repeatable CRM practice instead of an emergency investigation after a complaint.

Give owners a report they can use

Owners do not need a complicated dashboard to manage permission quality. Three counts provide a useful starting point: active permission by channel, unverified records, and withdrawals recorded during the period.

Break those counts down by collection source, such as inquiry forms, completed jobs, referrals, or manual entry. A sudden change can point to a form problem, staff training gap, or import that did not preserve permission details.

Do not treat a larger permitted audience as the goal. The useful measure is a contact list that accurately reflects customer choices and lets staff send only what the record supports.

A practical standard for your CRM

Every marketing message should answer three questions before it goes out: which channel is being used, what purpose applies, and where is the permission record?

If the answer is unclear, pause that audience and correct the record or collection process. A channel-by-channel consent structure gives owners cleaner campaigns, clearer staff decisions, and a dependable history when a customer changes their mind.