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
Choose What Should Be Consistent Across Team Replies
Standardise the facts, disclosures and commitments that affect customer decisions—not every sentence. Use a filled response-consistency matrix to separate harmless wording differences from contradictory answers.
10 min readFind the Current Commitment in a Long Conversation
Reconstruct what your team currently owes a customer by tracing promises, accepted changes, unresolved requests, and completion evidence through a long shared-inbox thread.
10 min readDecide Which Internal Notes Belong in a Shared Conversation
Use a practical relevance test to separate confirmed constraints, unresolved assumptions, and unnecessary personal detail—and leave a handoff colleagues can act on.
10 min readWrite an Internal Conversation Summary That Supports the Next Reply
Turn a vague handoff note into a decision aid that separates customer requests, verified facts, open commitments, and the next action—with a filled fictional example.
10 min readCheck for New Customer Messages Before Sending a Draft
A good draft can become the wrong answer while a teammate is writing it. Use a final context check to spot changed dates, withdrawn requests, extra requirements, and repeated messages before deciding what to send.
10 min readRecover After Two Conflicting Replies Have Already Been Sent
Stop the next contradictory reply, verify the disputed facts, and give one person control of the clarification. Use a filled fictional recovery worksheet to separate availability, allocation, and customer commitment.
10 min readHandle Several Open Requests in One Customer Conversation
Keep several customer requests visible without fragmenting the conversation. Use a filled issue ledger, a clear threshold for separate tracking, and a closure check based on outcomes.
10 min readReopen a Conversation or Start a New One When a Customer Returns
Use the customer’s requested outcome—not the age of a thread—to decide whether to reopen unfinished work or track a separate request. Includes a filled triage table.
9 min readReview Old Unresolved Conversations Without Closing Them Blindly
Use a bounded review and an evidence-based worksheet to distinguish unfinished promises, unclear requests, corrections, and conversations ready for closure.
10 min readSeparate Waiting on the Customer From Waiting on Your Team
Use evidence-based waiting states to show whether unresolved conversations need action from the owner, an internal contributor, or the customer.
9 min readDefine What Resolved Means in a Shared Inbox
A reply is not a resolution. Use obligation-based closure criteria, a filled decision table, and clear exceptions for accepted transfers and customer non-response.
9 min readCover an Absent Inbox Owner Without Creating Duplicate Work
Use conversation evidence—not an absent status alone—to decide what needs cover. A filled checklist shows how to name one temporary responder, leave waiting work alone, and hand conversations back safely.
10 min readKeep One Accountable Owner When Several Teams Join a Conversation
When account, billing, and operations staff join a customer conversation, contribution can look like ownership. Use a filled responsibility table to keep one person accountable for consolidating input and sending the reply.
10 min readSet Rules for Claiming Conversations From a Shared Queue
Use oldest-eligible-first selection, visible claims, and documented exceptions to stop easy conversations being picked while difficult ones wait. Includes a filled fictional queue worksheet.
10 min readDecide When an Incoming Conversation Needs a Named Owner
Use unfinished work as the trigger for named ownership, keep quick answers lightweight, and make handoffs depend on explicit acceptance rather than inbox activity.
10 min readBudget the cost of learning before funding a larger messaging rollout
Set a bounded messaging pilot budget, verify the spending assumptions, and separate historical learning costs from the recurring economics needed to justify expansion.
9 min readDecide whether an extra message is worth its incremental cost
A journey’s average cost can hide an uneconomic extra step. Use a filled marginal-cost worksheet to estimate chargeable volume, compare plausible additional outcomes, and decide whether to fund, test, defer, or omit the message.
9 min readSet an affordable messaging cost per outcome from contribution assumptions
Build a messaging budget from contribution, not revenue. Use a filled hypothetical worksheet to separate observed sales from incremental outcomes and calculate how much messaging spend each scenario can support.
10 min readCompare messaging cost per outcome without hiding denominator problems
Cheaper delivery can conceal weaker business results. Use a filled comparison table to show verified outcomes, missing records, cost scope and the limits of each apparent winner.
9 min readAllocate a shared messaging bill to departments without arbitrary splits
Separate attributable charges from shared fees, choose evidence-backed allocation keys, and keep unresolved costs visible. A filled fictional worksheet shows how departmental chargebacks can reconcile to the full bill.
10 min readPlan a messaging budget when rates and payments use different currencies
Build a currency bridge that separates messaging usage, rate changes, exchange effects and documented fees—so an approved budget can be compared meaningfully with the amount paid.
10 min readClose a messaging cost month when usage records arrive late
Keep reviewed messaging costs stable without hiding late evidence. Define separate usage and billing boundaries, label estimates, and preserve a versioned adjustment trail.
10 min readExplain a messaging budget variance without blaming volume alone
Separate a messaging cost overrun into chargeable volume, market mix, category mix, rates, fees and residuals—with a filled hypothetical waterfall and a corrective action for each driver.
10 min readReconcile delivered-message records with billed messaging usage
Build an evidence-backed bridge from delivery records to billed units, calculate disputed value separately, and keep unit and monetary reconciliation statuses distinct.
10 min readTurn a guide into a working customer journey.
Explore the tools and services behind the operating process.