Back to all articlesMessaging permission

Decide Whether Existing Evidence Supports a Specific Message Purpose

Alactic Editorial10 min read

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

A customer asks whether an item is in stock. Another completes a purchase. A third selects a clearly described messaging option. Marking all three records as permission granted erases the differences that matter when deciding what to send next.

Start with the proposed message purpose, then ask what the retained evidence supports. An inbound stock question may support answering that question without supporting future offers. A purchase establishes a transaction, not agreement to every kind of message. An affirmative choice is useful only within its recorded scope and must be assessed alongside later instructions.

The output should be a purpose-specific assessment and a separate operational decision. Missing evidence may justify a hold while someone retrieves it. A clear applicable opt-out means do not send for that purpose—not hold the message while debating whether the earlier agreement was stronger.

1. Define the message before inspecting the contact

A broad purpose such as customer engagement makes almost any historic interaction look relevant. Describe the communication before reviewing the recipient record: who is sending it, through which channel, about what, and whether it is a single response or continuing communication.

For a hypothetical homewares retailer, four distinct purposes might be:

  • Stock answer: Reply on WhatsApp to the person's question about whether a blue lamp is available today.
  • Dispatch update: Send a WhatsApp dispatch update for an existing order.
  • Future stock alert: Send one WhatsApp message when that lamp returns to stock.
  • Monthly offers: Send recurring WhatsApp messages about homewares promotions.

The same person and product could appear in all four, but that does not make the purposes interchangeable. Answering today's question differs from starting a future conversation. A one-time alert differs from a recurring series.

Write the purpose narrowly enough that another reviewer can identify its limits. Do not decide that a person is generally contactable and then fit a message around that label.

2. Keep evidence outcomes separate from operational status

Use four evidence outcomes. These are recommended operating labels, not legal determinations or guarantees that a message can be sent.

  • E — Explicit agreement: A retrievable record shows an affirmative choice covering the proposed purpose, sender and channel. Preserve limits such as frequency or a single alert.
  • N — Narrow contextual support: The person initiated a specific request, and the proposed message stays within answering or completing it. This is not support for unrelated or continuing messages.
  • C — Conflicting evidence: A relevant refusal, opt-out or contradiction opposes the proposed purpose or its supporting evidence. Record whether this is a clear stop instruction or an unresolved contradiction.
  • U — Unsupported assumption: The available evidence does not establish support for the proposed purpose. A saved number, purchase or unexplained database flag cannot supply the missing scope.

Then record an operational status separately:

  • Proceed to remaining checks: Evidence supports the narrow purpose; platform checks and send authorisation still remain.
  • Hold for review: A defined evidence gap or genuine uncertainty needs investigation. Name an owner and a closing event.
  • Do not send for this purpose: The purpose lacks support without a pending evidence search, or an applicable stop instruction blocks it.

A clear opt-out is not an unresolved contradiction. Honour it immediately for its applicable scope; review may clarify that scope but must not delay the stop. Reserve uncertainty holds for genuinely unresolved evidence.

These two fields can change independently. An unsupported record can be on hold while its source is sought. Recovering that source may change the evidence outcome, but the hold itself never supplies permission.

3. Retrieve the record behind the label

A field marked opted in is a summary, not the complete evidence. Reviewers need the underlying record or a reliable route to retrieve it.

  • Origin: The conversation, form, checkout interaction or import.
  • Wording and action: What the person was shown and what they did, including the invitation preceding an affirmative response.
  • Scope: The business, channel, subject, frequency and any one-time limit.
  • Timing: When it happened and whether the original task remains open.
  • Recipient connection: How the record connects to the intended person and destination.
  • Later changes: Relevant opt-outs, corrections, withdrawals or contradictory messages.

A signature without the accompanying wording leaves a gap. A timestamp without an identifiable event may describe a purchase rather than a messaging choice. A number on an invoice establishes a contact detail, not permission to use it for every purpose.

Describe gaps literally. Record that the original invitation is unavailable rather than upgrading an imported note into explicit agreement. Preserve both the affirmative response and what it answered.

4. Worked example: compare four records by purpose

All people, records, wording and decisions below are hypothetical, not Alactic customer results. Cedar House is a fictional homewares retailer reviewing four contacts for WhatsApp messaging.

Filled evidence register

  • A — Maya, inbound stock question: Maya asks on WhatsApp whether the blue lamp is available today. The conversation is retained. She has not requested a future alert or recurring offers; no later contradictory message is recorded.
  • B — Owen, completed purchase: Owen buys a lamp online. The order includes his phone number, but the retained checkout record contains no WhatsApp messaging choice or request for WhatsApp updates.
  • C — Lina, signed choice followed by an opt-out: Lina actively selects and signs a retained choice naming Cedar House, WhatsApp and monthly homewares offers. It is linked to her number. Later, she asks Cedar House to stop promotional messages.
  • D — Dev, imported note: An imported note says Dev agreed to messages in an earlier conversation. It contains no original exchange, invitation, channel or date. A reviewer is searching for the source.

Purpose-by-purpose evidence assessment

Each cell below contains an evidence outcome only: E, N, C or U. Operational statuses follow separately.

Proposed WhatsApp purpose       Maya   Owen   Lina   Dev
Answer blue-lamp stock query    N      U      U      U
Send dispatch update            U      U      U      U
Send one future stock alert     U      U      U      U
Send monthly homewares offers   U      U      C      U

Operational decisions for those assessments

  • Maya: Proceed to remaining checks for the direct stock answer. Do not send the other three purposes on this evidence.
  • Owen: Do not send any of the four purposes on the retained evidence. His purchase does not establish a WhatsApp channel choice.
  • Lina: Do not send monthly offers: her clear promotional opt-out blocks that purpose. The other three purposes are unsupported by this record, so do not send them on this evidence either.
  • Dev: Hold all four proposed purposes while the assigned reviewer seeks the source. Every evidence outcome is currently U, not a permission outcome disguised as a hold.

Maya's question supports a direct answer, not an automatic stock-alert subscription. Owen's order explains why a dispatch update might be useful, but usefulness does not fill the missing channel evidence. A separate relevant conversation or retained choice could change his assessment; this example does not mean dispatch updates are never appropriate.

For Dev, recovering the original conversation could change one or more U outcomes. A retained request for one stock alert, for example, would support that purpose within its stated scope, not monthly offers. If the source cannot be found, close the review with U unchanged and a do-not-send status rather than leaving an indefinite hold.

Lina's before-and-after comparison

The hypothetical timeline makes the explicit-agreement outcome visible without treating it as current permission:

Assessment point             Purpose          Evidence   Status
Before later opt-out         Monthly offers   E          Remaining checks
After promotional opt-out    Monthly offers   C          Do not send

Before the opt-out, Lina's retained affirmative choice supports monthly offers within its wording. After it, the clear stop instruction determines the operational decision. The historical E assessment explains the record; it is not available permission now. Neither version establishes support for a stock answer, dispatch update or future stock alert.

5. Use a filled decision record, not a blanket badge

A reusable record should connect the purpose, source, assessment and action. Keep it concise and reference retained material rather than scattering copies across systems.

The following filled artifact continues the hypothetical Dev example. Its fields can be reused for other reviews.

Recipient and destination: Dev; WhatsApp number in contact record
Proposed purpose: One future blue-lamp stock alert
Evidence reference: Imported contact note D
Available scope: Unspecified agreement to messages
Missing evidence: Original invitation, response, channel and date
Later instructions checked: None found in the reviewed records
Evidence outcome: U — available evidence does not support this purpose
Operational status: Hold for review; no send authorised
Review owner: Messaging operations lead
Next action: Search retained conversations for the source
Review closing event: Source recovered or search documented as unsuccessful
If recovered: Reassess purpose, recipient connection and later instructions
If unavailable: Keep U; change status to do not send for this purpose

The note does not claim the underlying agreement never existed. It states what the available evidence supports now and what would justify reassessment. That distinction prevents an incomplete record from becoming either presumed permission or an unsupported historical accusation.

Record only the boundary actually supported. For Maya, that would be a direct answer to her blue-lamp question. Reusing her assessment for monthly offers would require a new review, not a copied status.

6. Apply platform checks after the evidence assessment

Supported evidence does not make a message ready to send. For the WhatsApp Business Platform, approved templates are used to initiate conversations and outside the 24-hour customer-service window. That window opens or resets with a user message. Check the current WhatsApp Business Messaging Policy for precise requirements.

Keep these decisions distinct:

  1. Does recipient evidence support this particular purpose?
  2. Does the proposed message meet current platform requirements?
  3. Has an authorised person or process approved the actual send?
  4. What happened after submission, including any recorded delivery outcome?

An inbound question does not keep the service window open indefinitely. Template approval neither supplies missing permission nor guarantees delivery. Campaign preparation, template review and actual delivery are separate states.

If automation assists the assessment, provide a clear human escalation path for missing or contradictory evidence. This workflow is an operating recommendation, not a claim that a particular Alactic control exists. Check your workspace and current plan before relying on product support, and do not assume capabilities are identical across CRM, Communications, ACID or Android.

7. Repair weak records without widening the purpose

Evidence repair often means retrieving existing material, not sending another message. Do not assume that an incomplete record supports an outbound request for permission.

  • Missing wording: Recover the version shown when the choice was made. Today's form does not establish what someone saw earlier.
  • Unclear affirmative response: Retrieve the preceding invitation. A positive reply alone may not identify the accepted purpose.
  • Clear applicable opt-out: Stop messages for that purpose. Investigate scope only where necessary; do not suspend the stop while investigating.
  • Genuinely unresolved contradiction: Hold the affected purpose and assign a reviewer. Document the contradiction rather than selecting the convenient record.
  • Completed contextual task: Do not keep using a resolved enquiry to support new conversations.
  • Unrecoverable import: Close the review as unsupported. Keeping a contact and having evidence to message that contact are different decisions.

A later user-initiated interaction may offer an opportunity to clarify preferences with specific wording. That future possibility does not support a send now.

8. Test whether reviewers reach the same decisions

As a hypothetical starting exercise, give two reviewers the same proposed purpose and evidence for 20 records before authorising sends. Ask each to record both an evidence outcome and an operational status independently.

Compare three observable results: how many records have retrievable purpose-specific evidence, how often reviewers disagree, and how many holds close with either recovered evidence or a documented unsupported outcome. Also check whether clear opt-outs were blocked immediately rather than placed into uncertainty review. These are process measures, not compliance or delivery claims.

Use disagreements to improve instructions. If purchases are repeatedly treated as channel permission, add Owen's distinction to the review guide. If affirmative replies cause confusion, require the preceding invitation. If holds never close, make the owner and closing event mandatory.

Start with one upcoming messaging task. For each recipient, leave a supported boundary, a defined investigation, or a clear do-not-send decision—not a blanket permission badge.

Messaging permissionWhatsAppOperational workflowsEvidence review

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