When one customer should hear nothing promotional
Most marketing rules are written for groups: subscribers, customers, leads at a stage. They fail one person at a time. A customer waiting on a delivery that is badly late receives a cheerful offer. A customer disputing a damaged item is asked to review it. A relative who called to report a death sees a reminder arrive in the name of the person who died. Each message passed every check it was built with, and none of those checks knew that the relationship was, for the moment, in trouble.
Pieces of the answer already exist on the site. The post-purchase flows tutorial pauses its flow while a support ticket or a complaint is open, and the abandoned cart flows tutorial keeps shoppers out of its sends while a complaint is recent or an order has a support ticket open. The guide to supporting customers in vulnerable circumstances stops marketing and reminders through one route when a relative reports a death. The automation governance guide lists a legal hold among the global suppression flags every send checks. Each covers one flow or one situation. The general case, a pause for one person that every send respects, has to be built once, and the CRM fundamentals guide gives it its shape: when a ticket ought to stop promotion, the place for that fact is a field on the contact for workflows to read, rather than logic inside a workflow that looks at tickets.
| What goes wrong | Why the usual checks miss it | What a hold adds |
|---|---|---|
| The weekly offer reaches a customer with an open complaint | Consent and suppression pass; the complaint sits in a log the sending tool never reads | One field on the contact that every send reads |
| A review request arrives during a dispute about the same item | Only a flow built to read tickets knows about the dispute | The same rule in every flow and every campaign |
| Ads keep showing to a customer whose order is late | The customer list was uploaded before the issue began | Held customers left out of the next upload of any list that targets them |
| A reminder is addressed to someone who has died | The bereavement note stays with the support team | A hold set through the bereavement route, stopping promotion at once |
| Promotion resumes the day a complaint closes, or never | Pauses set by hand have no end and no owner | A release rule and an owner for every reason |
A hold does not resolve the issue. The complaint, the dispute and the recovery belong to the complaints procedure and the service recovery guide. The hold only makes sure marketing does not talk over them while they run. When the complaint is about the number of messages itself, the diagnosis for customers getting too many marketing messages sets the hold beside channel caps, a priority order and topic preferences.
Before you start
- The complaints log, from the complaints procedure tutorial: one log fed by every channel, with an open and a closed state. Complaint holds start and end from it.
- The automation inventory and the shared rails from the governance guide: every sending workflow, the global suppression check and the review rule for changing it. A hold is a change to a shared rail.
- The consent map from the tutorial on mapping consent across the stack, which lists the tools that read each permission and so every tool the hold must reach.
- The sync field table from the guide to syncing the CRM and the marketing platform, so the hold fields get one owning system and one direction like every other synced field.
- The people who hear first: the customer service lead, account managers or showroom staff, whoever handles billing disputes, and whoever owns data protection.
- A list of the messages the business sends as service, sorted by the purpose test in the guide to promotional and transactional email, because a later step keeps those running.
- Seed contactsAn inbox or test contact the business controls, added to a send or run through a workflow so the team sees exactly what real recipients would receive., one for each hold reason you expect, named so nobody mistakes them for customers.
The steps
List the situations that start a hold
With customer service and account management, list the situations in which a promotional message would do harm. An open complaint is the obvious one. A dispute about a delivery, a fault or a bill usually belongs too, even when nobody has called it a complaint. A bereavement reported by a relative belongs, handled through the route the vulnerable circumstances guide sets out. Other circumstances a support agent records with the customer's agreement, such as a serious illness or a crisis at home, can belong where the customer would rather not hear from marketing for a while. For each, write down where the business first learns of it and what marks its start and its end. Then write down what is out of scope. A problem that affects every customer at once calls for a business-wide pause, which the tutorial on leading marketing through a business crisis covers. A person who asks to stop marketing is an opt-out, handled in a later step. Debt collection, litigation and other legal processes are not covered here; whoever advises the business on them decides what applies.
Add a hold field with a reason and a start date
On the contact record in the CRMThe system that stores an organisation's contacts, companies, deals and interactions, and the processes built around it., add a small group of fields: whether a hold is active, the reason, chosen from a fixed list that matches the situations above, the date it started, who set it, who owns its release and the date it is next reviewed. Keep the reason a category and nothing more. The GDPR entry lists data minimisation among the regulation's principles, so the hold carries no more Personal DataAny information relating to an identified or identifiable living person, such as a name, email address, location data or an online identifier. than the send rules need. The detail of a complaint stays in the complaints log, and the detail of a bereavement or an illness stays in the support record, because the vulnerable circumstances guide keeps notes about a customer's situation out of marketing lists, segments and exports. That rule also decides what crosses to the marketing tools: the flag and its dates travel to the marketing platform, while the reason stays in the CRM, visible to the people who set and release holds. Where the same person exists on two records, the hold has to reach both; the diagnosis for unsubscribed contacts still receiving email shows how a second record brings back someone who should have been stopped. A hold is not a stage: the customer keeps the stage the tutorial on automating lifecycle stage changes sets by rule.
Decide who may set a hold and from which systems
Write a RACI matrix with a row for each reason and columns for setting, extending and releasing the hold, keeping to the framework's rule of one accountable role per row. A complaint hold is best set by the complaints log itself: logging a complaint against a known customer sets the field, so the hold does not depend on an agent remembering. A dispute hold can be set by the team that handles the dispute, a bereavement hold by the agent who takes the call as part of that one route, and a hold for other circumstances by the agent, with the customer's agreement. Marketing operations is accountable for the field, the rails and the report, never for whether a complaint is open. The CRM owns the hold and every other tool reads it; where complaints or support live in another system, the hold reaches the CRM field by one documented route rather than one improvised by each team. The sync guide's rule applies: a field two systems may write has no owner, so the marketing platform reads the hold and never writes it.
Check the hold at entry and before every send
Add the hold to the global suppression rail the governance guide describes, beside unsubscribed, bounced and do-not-contact, so every promotional workflow, campaign, newsletter and one-off send checks it. A change to a shared rail goes through the governance guide's second-person review, with a log entry. Check at entry and again before each send, because a hold is usually set while a sequence is already running; the diagnosis for customers receiving prospect messages traces what happens when a condition is read only once, at entry. Decide for each workflow what a hold does to a run in progress. A message tied to a moment, such as a review request after delivery or an offer that ends on a date, is skipped rather than sent late, while a long sequence can wait and resume from a sensible point after release. Record the choice in the workflow's inventory row. Before switching anything on, put a seed contact on hold under each reason and run it through every send in the inventory: nothing promotional should arrive, and every service message should.
Carry the hold to ad audiences, sales sequences and the marketing platform
If a separate marketing platform runs the sends, the hold crosses from the CRM in one direction, as the sync guide's field table sets out, and the check from the previous step runs there too. Text and messaging flows share the CRM record and the suppression rules with email, as the guide to SMS and WhatsApp automation says, so the hold gates them as well. Customer listsAn ad audience built from the advertiser's own sources: customer lists, site visitors or engagers. uploaded to ad platforms need care in both directions. A list refreshed by upload is only as current as its last upload, as the closed-won workflow tutorial notes, and the playbook for customer lists across ad platforms gives every list one refresh routine and one owner. Held customers come out of every list used to target them at the next upload at the latest. They stay in the lists that keep customers out of prospecting campaigns, or the hold would put them in front of acquisition ads. Sales and account management sequences, cross-sell calls and showroom follow-ups read the same field. Add a hold column to the consent map, so every tool that reads a permission also shows whether it reads the hold.
Keep the service messages the customer needs
A hold stops promotion, not service. The promotional and transactional email guide explains, from the UK regulator's direct marketing guidance, that what a message says and what it is for settle whether it counts as service or marketing, whatever the campaign is called. Delivery updates, repair and fitting appointments, receipts, account notices and the complaint correspondence are transactional messagesAn email triggered by a person's own action or account, such as a receipt, password reset or shipping notice, rather than a marketing send. the customer needs, and they keep running during a hold. The work is in the templates. A delivery update carrying an offer block or a "you may also like" panel is marketing for that purpose, so held customers receive the service version with the promotion taken out, the failure the unsubscribed diagnosis traces when marketing travels through the service stream. Review requests stop, as the post-purchase tutorial skips them for an open complaint, and so do referral invitations and similar asks. Bereavement needs more than a hold. The vulnerable circumstances guide stops reminders as well as marketing when a relative reports a death, so the bereavement reason also starts the support team's review of the reminders and notices the account would otherwise send, within the one route that guide describes.
Set a release rule and an owner for each reason
A hold that never ends becomes a silent opt-out nobody asked for, and a hold released from memory ends late or not at all. Give every reason a release event and an owner. A complaint hold releases when the log records the complaint closed, which the complaints procedure defines as the customer having received a complete answer with every agreed action finished, not the date of the last reply. A dispute hold releases when the team that owns the dispute records its outcome. A hold for other circumstances releases when the customer or the agent records that the arrangement is no longer needed, in line with the vulnerable circumstances guide's advice to keep such notes current. A bereavement hold has no release: the account is closed or transferred through the one route, and marketing does not resume to the person who died. Every hold also carries a review date, set by the business's own rule, so a hold whose release event never arrives comes back to its owner, who releases it, extends it with a reason or escalates it. On release, nothing held back is sent in a catch-up burst, sequences restart from a point that still makes sense, and the first promotional message says nothing about the issue. Promotional texts that resume keep the channel's own consent and quiet hours.
Treat an objection as a suppression, never a hold
A customer in a complaint may say "stop sending me this". That is no reason for a hold. The SOP for marketing opt-out requests treats a request to stop marketing, in whatever words and by whatever route, as an opt-out, and the GDPR entry states that an objection to direct marketing must always be honoured. An objection is recorded in the consent fields and becomes a permanent Suppression ListA list of addresses or contacts excluded from every send, such as unsubscribes, hard bounces and spam complaints. entry in every tool, texts and uploaded customer lists included, through the SOP's steps. A hold that expires would restore marketing the person has refused, so the two never share a field. Train the people who set holds to tell them apart: an agent's judgement that marketing would hurt right now is a hold; a customer's request to stop is an opt-out, passed to the SOP. Where the request is unclear, the SOP's advice is to ask rather than guess narrowly. Build the release workflow so it touches only the hold fields and checks the consent fields before anything resumes; the consent map shows how a withdrawal recorded by customer service reaches every other tool.
Report open holds and review them
Build one report of every open hold with its reason, start date, owner and review date, overdue reviews first. Add the checks that catch the failures this tutorial is built against: complaint holds whose complaint is already closed in the log, holds with no owner, held customers who received a promotional message, and held customers still in a targeting audience after the last upload. Send each owner their own overdue holds, and make the report part of the governance audit that marketing operations runs. Treat a promotional message reaching a held customer as an incident under the governance guide's routine, including the search for the same cause elsewhere. Leave the held seed contacts in place permanently and run them through every send again whenever the sync, the templates, the audiences or the complaints log changes. Read the counts against the business's own history; the site cites no outside standard for them.
Hold, suppression and pause side by side
Several controls stop messages reaching people. They differ in whom each covers, how long it lasts and who ends it.
| Control | Who it covers | Set by | Ends | What still reaches the person | Owned by |
|---|---|---|---|---|---|
| Marketing hold | One customer with an open issue | The complaints log and named support, account and finance staff | A release event for its reason, or its owner at review | Service messages; no promotion, review requests or targeting ads | This tutorial |
| Opt-out or objection | One person who asked to stop marketing | Whoever receives the request, recorded in the consent fields | Never by a workflow or a date | Service messages | Opt-out SOP |
| Flow exit or pause | People in one flow | That flow's own conditions | When the flow's condition clears | Everything outside that flow | Post-purchase and cart flow tutorials |
| Bereavement route | The account of a person who has died | The support agent who takes the call | The account is closed or transferred | What the route decides | Vulnerable circumstances guide |
| Customer gate | Customers, kept out of prospect sequences | The customer stage | When the person stops being a customer | Customer journeys and service | Governance guide; closed-won workflow |
| Business-wide pause | Everyone | The crisis decision owner inside marketing | A planned restart | Messages customers need, if the crisis owner agrees | Business crisis tutorial |
The hold and the opt-out are the pair to keep apart: one is the business's judgement about a moment, the other is the person's choice about the relationship. Once the hold exists, the flow pauses in the post-purchase and cart tutorials can read it instead of keeping ticket logic of their own.
A sofa maker pauses marketing during complaints (illustrative)
Plorvetink Sofas pauses marketing during complaints
Plorvetink Sofas, an invented maker of made-to-order sofas, sells online and through 3 showrooms. One quarter's complaints log shows 164 customers with a complaint or dispute open, most about late deliveries or damaged frames. 112 of them received the weekly offer email while the issue was open, 41 received a review request for the sofa they were disputing, and 27 entered the "complete your living room" sequence. A family that reported a death received a reminder addressed to the person who had died, and 19 of the quarter's complaints were about marketing received during an open complaint.
The team lists 5 reasons: complaint, delivery dispute, billing dispute, bereavement and other agreed circumstances, and adds a hold field with a reason and a start date. Logging a complaint sets the hold automatically, and 11 named people in customer service, the showrooms and finance may set the others. The hold joins the global suppression check at entry and before every send in 16 promotional workflows and the weekly campaign, and held customers drop out of the 2 retargeting lists at each weekly upload while staying in the prospecting exclusion list. Delivery, fitting and repair messages keep running, with the offer panel removed from the delivery update for anyone on hold. Complaint holds release when the complaint closes in the log, and any hold still open after 30 days goes back to its owner for review.
The first report of open holds lists 58, including 23 converted from "no marketing" tags that agents had added by hand over the previous year, after each tag was checked against the agent's note and those recording a customer's request to stop were passed to the opt-out procedure instead; 17 of the 23 belonged to complaints closed months earlier and are released that week, with the release workflow checking the consent fields first. In the next quarter no complaint is logged about marketing received during an open complaint, and the 5 seed contacts on hold receive every service message and nothing promotional.
The workflows section lists this tutorial next to the governance guide whose suppression rail it extends.
Common mistakes
- Pausing inside one flow only. The post-purchase flow stops and the weekly campaign carries on. Put the hold on the shared rail that every send checks.
- Using a hold for an opt-out. A hold expires and an objection must not. Send every request to stop marketing through the opt-out procedure.
- Recording the story in the hold. The marketing tools need a flag and dates, not the details of a complaint or a bereavement.
- Forgetting ad audiences. An uploaded customer list keeps targeting a held customer until the next upload removes them.
- Taking held customers out of exclusion lists. A customer missing from the exclusion is a target for prospecting ads.
- Stopping service messages too. The customer still needs the delivery update, without the promotion attached.
- No release rule. Holds set by hand outlive the issue and turn into silent opt-outs nobody chose.
