The Alactic library
Practical guides for customer operations
From a better WhatsApp conversation to a clearer team handoff. Find a specific decision, a useful checklist or a workflow your business can put into practice.
1,030 articles
Decide When Two Message Purposes Need Separate Template Briefs
When a booking update also carries an unrelated offer, use recipient expectations, required facts, and requested actions to decide whether to keep one purpose or create separate template briefs.
10 min readAudit Whether Permission Records Support the Decisions Staff Make
Review whether staff can turn permission evidence into consistent messaging decisions, distinguish reviewer mistakes from observed actions, and verify corrections through the actual workflow.
9 min readCheck Whether Permission Still Applies When Someone Else Uses the Number
A reply from a familiar number does not prove the same person is still using it. Use a permission review to pause questionable messaging, clarify a new user’s choice, and preserve the earlier evidence.
10 min readKeep Channel Choices Separate When Customers Change How They Want Contact
A request to move a conversation is not agreement to future messages. Use a filled decision table to record channel-specific choices without erasing existing restrictions.
10 min readOffer Messaging Frequency Choices the Business Can Actually Respect
Turn vague promises of occasional messages into clear operating rules. Use a filled worksheet to define frequency choices, handle opt-outs, and resolve conflicting requests.
9 min readOffer Topic Choices Without Creating Preferences the Team Cannot Honour
Topic preferences work only when staff can apply the same boundaries. Use a filled preference matrix, explicit overlap rules and a hold process to make customer choices dependable.
10 min readVerify a New Messaging Choice After an Earlier Withdrawal
A new order or support question does not renew permission for optional messages. Use a scoped evidence review to recognise a fresh choice without erasing earlier restrictions.
10 min readMake a Withdrawal Effective Across the Places Staff Check Permission
A withdrawal is not operationally resolved while a working list still shows permission. Use an authoritative record, named copy owners, review evidence, and an explicit hold for anything that remains unresolved.
10 min readHandle a Withdrawal When Its Scope Is Unclear
When a customer says to stop messaging, restrict the plausible scope first. Separate what is clear from what remains uncertain, clarify only when useful, and record a decision that does not quietly preserve access.
10 min readRecognise Withdrawal Requests That Do Not Use a Standard Keyword
A customer should not need a special stop word to end unwanted messages. Use this interpretation table and review workflow to identify scope, act on clear requests and resolve genuine uncertainty.
9 min readDecide What to Do When Historical Permission No Longer Matches Expectations
Old permission is not a universal invitation. Use a filled review worksheet to compare the original purpose with today’s proposed message, then continue within scope, hold, or seek a fresh choice in an independently appropriate interaction.
10 min readReview a Historical Contact List Before Treating It as Messageable
A legacy contact list is not a permission record. Use a record-level review, targeted sampling and a filled decision workbook to separate supported permission, narrow permission, withdrawal and unknown status.
11 min readResolve Conflicting Messaging Permission Records
When one record says yes and another says stop, do not pick the convenient entry. Compare scope, chronology and evidence, preserve the contradiction, and hold uncertain sends until a reviewed decision is recorded.
10 min readRecord Verbal Messaging Permission Without Turning Notes Into Proof
A note saying “customer agreed” hides the most important details. Record the invitation, response, context and uncertainty separately, then decide whether a clearer written choice is needed.
9 min readVersion Permission Invitations Without Losing What People Originally Saw
Preserve the invitation behind every recorded choice. Use a version register to separate cosmetic edits from changed expectations, keep historical evidence intact, and decide when to ask again.
10 min readDistinguish Event Attendance From a Choice to Receive Messages
A badge scan, resource request, or business card is not interchangeable with a choice to receive ongoing messages. Use this event-permission review to separate specific requests from future messaging permission.
10 min readHandle Referred Phone Numbers Without Assuming Messaging Permission
A referral can explain why a number reached your team without proving its owner agreed to be messaged. Use a review sheet to choose a hold, a referrer-led invitation, or contact supported by independent evidence.
10 min readSeparate Permission for Enquiry Replies From Permission for Offers
A customer’s question is not an invitation to send ongoing promotions. Use a purpose-based decision map to separate enquiry replies, requested follow-ups and optional offers—and record each decision independently.
10 min readWrite a Messaging Invitation That Makes the Choice Understandable
Replace vague invitations with a clear choice: who will message, on which channel, about what, how often, and how to stop. Use a filled fictional brief and a comprehension review to find ambiguity before publication.
10 min readDecide Whether Existing Evidence Supports a Specific Message Purpose
A purchase, an enquiry and an affirmative messaging choice support different things. Use this worked example and filled decision record to assess evidence by purpose, separate uncertainty from opt-outs, and document what happens next.
10 min readChoose the Minimum Evidence to Keep in a Messaging Permission Record
A permission flag cannot explain what someone agreed to. Use a compact evidence record to connect the person’s choice to a channel, purpose and invitation—and identify the gaps that should stop a send.
10 min readVerify onboarding completion before handing the setup to operations
Use a documented acceptance check to verify asset identity, number association, reported status and business control before operations takes responsibility.
10 min readRun a go-or-no-go review before starting WhatsApp onboarding
Turn scattered preparation into a clear start decision. Use six readiness gates, evidence-backed findings, and a completed fictional scorecard to distinguish acceptable open work from a dependency that must stop onboarding.
10 min readPrepare an onboarding support packet that can be investigated
Stop repeating the basics in onboarding support exchanges. Build a concise report with the failing step, relevant asset identifiers, timed observations, redacted evidence and one answerable question.
10 min readTurn a guide into a working customer journey.
Explore the tools and services behind the operating process.