Back to all articlesMessaging permission

Offer Topic Choices Without Creating Preferences the Team Cannot Honour

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

A customer selects “Product updates” but declines “Offers.” Your team prepares a message announcing a new product with an introductory discount. Is it an update, an offer, or both? If different staff members give different answers, the preference menu has created a promise the operation cannot reliably keep.

Design topic preferences around purposes customers can distinguish and staff can consistently recognise. Define what each topic includes, what it excludes, and what happens when a message crosses a boundary. For genuinely mixed-purpose messages, a dependable default is to require permission for every included purpose, remove the unpermitted purpose, or keep the message on hold.

The goal is not the largest possible menu. It is the smallest useful set of choices that preserves meaningful customer control without asking the team to make distinctions it cannot sustain.

1. Decide which differences deserve separate choices

An all-or-nothing choice is less useful when customers have a clear reason to want one kind of optional message but not another. Someone may want practical guidance about a product they own while declining discounts. Combining both under “News and updates” forces that person either to accept unwanted messages or miss useful ones.

However, splitting every subject into its own checkbox does not necessarily improve control. A menu becomes unreliable when staff cannot explain the boundaries, messages routinely cross them, or the preference record cannot be checked accurately before sending.

Before creating a separate topic, ask:

  • Would a customer reasonably choose this independently? A distinction should reflect a meaningful difference in what they receive, not just your internal department structure.
  • Can staff identify it from the message itself? The classification should not depend on knowing who wrote it.
  • Can the team act differently when it is declined? If every message still goes to everyone, the choice is not operationally real.
  • Can you explain its exclusions? A topic that includes almost anything is not a useful permission boundary.

When these tests fail, simplify the proposed menu before offering it. If existing customers already made narrower choices, do not silently broaden those choices while simplifying the labels.

2. Write the permission boundary before the label

Start with a plain-language description of the purpose, then choose the label. Starting with an attractive label such as “Stay inspired” often leaves staff to invent its meaning later.

For each topic, write an internal boundary using this structure: “We may send messages whose purpose is X. This does not include Y. When X and Y appear together, apply rule Z.” Then write the shorter customer-facing explanation.

Classify the whole message: its opening, body, call to action, attachments and the purpose of its linked destination. A neutral opening does not make a discount message non-promotional. Equally, mentioning a product does not automatically make a practical instruction a new-product announcement.

Make the choices understandable where customers select them. Avoid a vague heading followed by unexplained checkboxes. For a web form, the W3C guidance on form labels explains that controls need labels identifying their purpose and that those labels should be programmatically associated with the controls. Clear wording and accessible implementation are separate responsibilities; both matter.

Also explain the channel covered by the choice. A WhatsApp topic selection should not be presented as permission for unrelated email or phone contact.

3. Use a filled topic-preference matrix

Fictional worked example: The following matrix is for a hypothetical business selling home coffee equipment. It is a recommended operating design, not an Alactic feature description or a customer result. All message examples below are hypothetical.

The business offers three optional WhatsApp topics. It keeps order-specific conversations outside this optional-topic menu and assesses their purpose and applicable permission separately. Buying something does not automatically select any optional topic.

Topic A: Offers and discounts

  • Customer-facing explanation: “Send me discounts, sale announcements and purchase incentives for coffee equipment and accessories on WhatsApp.”
  • Included purposes: Coupon codes, reduced-price announcements, bundles promoted through savings, and gifts offered as an incentive to purchase.
  • Excluded purposes: Standalone care instructions, factual launch announcements without an incentive, and updates about a specific existing order.
  • Overlap decision: A new-product launch with an introductory discount requires both Offers and discounts and New products. Removing the discount can make it a New products message if the remaining content has no purchase-incentive purpose.
  • Hypothetical allowed example: A discount on an existing accessory sent to someone who has selected Offers and discounts.
  • Must remain on hold: A discounted new-grinder announcement for a customer who selected Offers and discounts but declined New products.

Topic B: Care and how-to tips

  • Customer-facing explanation: “Send me practical guidance on using, cleaning and caring for coffee equipment on WhatsApp. This does not include discounts or product launches.”
  • Included purposes: Cleaning instructions, brewing guidance and routine equipment-care explanations without a sales purpose.
  • Excluded purposes: Discounted cleaning kits, recommendations framed to sell an upgrade, and announcements of newly released equipment.
  • Overlap decision: A cleaning guide ending with a discounted kit offer requires both Care and how-to tips and Offers and discounts. A genuinely standalone guide can be assessed only as Care and how-to tips.
  • Hypothetical allowed example: A cleaning checklist for an existing machine, with no promotional call to action, sent to someone who selected Care and how-to tips.
  • Must remain on hold: A cleaning-tip message linking to a page built primarily around a kit discount when the customer declined Offers and discounts.

Topic C: New products

  • Customer-facing explanation: “Send me announcements when new coffee equipment or accessories are introduced on WhatsApp. Discounts are a separate choice.”
  • Included purposes: Product-launch announcements and explanations of what a newly introduced item does.
  • Excluded purposes: Price promotions, routine care guidance, and availability changes for existing products. In this example, restock alerts are not offered as a topic.
  • Overlap decision: A launch announcement containing a practical brewing tutorial requires New products and Care and how-to tips if the tutorial is a substantive second purpose. A short specification explaining the new product is not, by itself, a separate how-to purpose.
  • Hypothetical allowed example: A factual announcement of a newly introduced grinder with a link to its specifications, sent to someone who selected New products.
  • Must remain on hold: A restock announcement assigned to New products merely because there is no better category.

This matrix intentionally leaves some messages without a home. That is useful: it exposes a permission gap instead of hiding one inside a catch-all topic. An internal “Other” bucket may help route review work, but it should not become a customer permission category that quietly authorises everything.

4. Choose an overlap rule the team can repeat

For this hypothetical matrix, the rule is: every substantive purpose needs its corresponding topic permission. Do not classify by the most prominent sentence or the sender’s preferred label.

A substantive purpose gives the customer a distinct reason to act, learn or purchase. Ordinary supporting detail does not always create another topic. Product specifications can support a launch announcement; an extended care lesson serves an additional purpose. Write down these boundary decisions so reviewers do not repeatedly debate the same pattern.

Use this sequence for mixed messages:

  1. Identify each purpose in the complete message and its destination.
  2. Map each purpose to the matrix.
  3. Check whether the recipient has selected every required topic and whether a later opt-out changes that permission.
  4. If permission is missing, remove the unsupported purpose, limit the message to recipients whose choices cover it, or hold it.
  5. If no topic fits, escalate the classification rather than choosing the closest label.

Removing a purpose means removing it from the actual customer experience, not merely changing the internal category. Renaming a discount as a “helpful update” does not resolve the mismatch.

Splitting a mixed message into separate messages can clarify purposes, but each resulting message still needs its own permission check. Splitting is not permission to send more.

5. Make uncertainty a visible hold state

A hold should answer a concrete question. “Needs review” without a reason tends to become a queue nobody can clear.

Record the proposed message, the disputed purpose, the relevant preference evidence, the reviewer responsible and the condition for release. Useful hold reasons include:

  • Boundary unclear: Reviewers disagree about whether a tutorial is supporting detail or a second purpose.
  • Preference evidence missing: A record contains a selected topic but not enough context to establish which wording the customer saw.
  • Conflicting choices: A later request to stop messages conflicts with an older selection.
  • No matching topic: The message concerns restocks, but the offered menu never covered restock alerts.
  • Destination changed: A previously informational linked page now opens with a promotion.

Resolve each hold through evidence, a content change, a clarified boundary or a decision not to send. Do not release it merely because the planned send date has arrived. Where customer clarification is appropriate, do not assume permission to send an optional outbound message just to request broader permission.

Give staff a route to a named human reviewer. If automation assists classification, ambiguous cases should reach that reviewer rather than silently inheriting a topic.

6. Keep topic choice separate from channel eligibility

A selected topic answers one question: does this message purpose fit what this customer chose? It does not settle every requirement for sending through a particular channel.

For WhatsApp, recipient permission matters and opt-outs must be honoured. Approved templates are used to initiate Platform conversations and outside the customer-service window, which opens or resets with a user message and lasts 24 hours. Check the current WhatsApp Business Messaging Policy for precise requirements.

A topic called Offers and discounts is your customer-facing permission label, not a determination of a platform message category. Likewise, template approval does not establish that a recipient selected the relevant topic, and it does not guarantee delivery.

Keep campaign preparation, template review and actual delivery as separate states. Add the topic-permission check without treating it as a substitute for the others. A message can be fully prepared yet remain on hold because the customer’s choices do not cover its purpose.

7. Repair the design when real work exposes a weak boundary

If staff repeatedly disagree, first inspect the matrix rather than assuming they need more reminders. A topic may contain incompatible purposes, or its exclusions may be too abstract to apply.

For a hypothetical recovery exercise, take a set of recently drafted messages and have two staff members classify them independently using only the written definitions. Record disagreements before discussing them. If both interpretations fit the wording, revise the boundary and add the disputed message as an example.

If an incorrect send has already occurred, pause further affected sends, identify the mismatch and correct the record or decision rule that caused it. Honour any resulting stop request. Changing a label after the event does not retroactively expand the customer’s choice.

When merging topics, do not assume that a customer who selected one old topic selected the other. Preserve the narrower permission until there is adequate evidence for the broader one. When splitting a topic, retain the wording and context of the original choice so staff can assess what it actually covered; do not manufacture precision the customer never supplied.

8. Test the matrix before publishing the menu

Run a small, explicitly hypothetical acceptance test: choose twelve representative message drafts, including straightforward messages, mixed-purpose messages and messages that should remain on hold. Have two reviewers independently record the required topics, the reason and the release decision.

Measure three things:

  • Decision agreement: How many drafts received the same topic and hold decisions?
  • Unresolved coverage: How many drafts have a purpose that no offered topic covers?
  • Permission traceability: For each proposed send, can staff identify the customer choice and wording supporting it?

Use disagreements to revise specific matrix entries, then repeat the affected cases. Do not invent an acceptable error rate for sending outside a customer’s choices; the test is a way to uncover ambiguity before it reaches customers.

Your next action is to fill one matrix entry for every topic you intend to offer, then test it against an awkward message rather than an easy one. If the team cannot explain why that message is allowed, excluded or on hold, the preference is not ready to promise.

Messaging permissionTopic preferencesCustomer operationsWhatsApp

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications