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
Use a holdout group to estimate incremental campaign outcomes
Campaign attribution does not show what would have happened without the campaign. Use a randomised recipient holdout, fixed outcome window and intention-to-treat analysis to estimate the difference.
10 min readHandle late campaign replies without silently rewriting reports
Keep original campaign reports intact while making late replies and corrections visible. Use a three-clock policy and a filled reporting register to explain every revision.
10 min readAvoid double-crediting outcomes across overlapping campaigns
Use one outcome ledger and a transparent credit rule to reconcile overlapping campaign reports. A worked example compares first-touch, last-touch, and shared credit.
9 min readSet an attribution window that matches the campaign decision
Choose response and outcome windows from observed delays, campaign purpose, and the decision your report must support. Use a filled worksheet to compare cutoffs and see whether the conclusion changes.
9 min readReport campaign results when delivery status is incomplete
Managers need a result even when delivery records are unresolved. Use a fixed reporting cutoff, separate observed responses from delivery evidence, and publish conditional bounds instead of a falsely precise rate.
10 min readChoose the right delivery denominator for campaign reply rates
Selected, attempted, and confirmed-delivered recipients answer different campaign questions. Use this filled worksheet to match each denominator with the right responders.
8 min readCount unique campaign responders without inflating results
Separate unique responding endpoints from reply volume with a clear counting rule, a worked ledger and a reconciliation that exposes duplicates and uncertain attribution.
10 min readClose a Campaign With Unresolved Delivery Cases Honestly
A campaign can be operationally closed without pretending every delivery outcome is known. Use explicit evidence categories, a reconciliation cutoff, and a closure record that preserves unresolved cases and defines when to reopen.
10 min readHand Over an Unresolved Campaign Without Losing the Recovery State
An incident handover must preserve more than a status summary. Use this filled example to transfer confirmed totals, retry history, active holds, approval boundaries, and a clear next review point.
10 min readPrioritise Unfinished Campaigns After a Delivery Disruption
Do not resume every unfinished campaign at once. Use a recovery-priority board to separate expired messages, safe-to-resume work and campaigns whose previous attempts still need investigation.
9 min readRelease a Campaign in Batches to Limit Delivery Incident Exposure
Use evidence-based release checkpoints to keep an operational delivery problem from spreading across the whole campaign. Includes a fictional, filled checklist with unresolved cases, release approval, and a duplicate-triggered hold.
10 min readInvestigate Duplicate Campaign Messages Before Cancelling More Sends
A duplicate-message report is a reason to investigate, not proof that every campaign is affected. Reconstruct recipient evidence, campaign references and send attempts before choosing the smallest effective containment.
10 min readContain a Wrong-Content Campaign Before Sending a Correction
When a campaign contains the wrong content, pause further exposure first. Use a delivery-evidence worksheet to separate confirmed deliveries, failures, unsent recipients, and unknown outcomes before choosing who needs a correction.
10 min readDecide Whether a Delayed Campaign Message Is Still Worth Sending
A technically retryable message may no longer help its recipient. Use separate arrival and stop-release deadlines to choose whether to send, cancel, or request a replacement.
9 min readRestart a Paused Campaign Without Replaying Completed Work
Build an evidence-based restart packet that separates completed work, uncertain attempts, and a verified remainder—then approve a controlled release.
9 min readWhat to Verify After You Stop a Campaign
A stop request does not prove that every message was cancelled. Use a stop-verification record to separate unsent work, submitted attempts, later outcomes, and unresolved exposure.
10 min readDecide When a Campaign Queue Is Stalled Rather Than Merely Slow
A queued campaign needs more than a timer. Use successive observations, the age of the oldest pending work, processing evidence, and message relevance to decide whether to wait, investigate, or pause.
10 min readHandle Late Delivery Updates Without Reopening Finished Recovery Work
A late delivery update can change what you should do next without invalidating an earlier decision. Use a two-time timeline to correct open actions and preserve the record of completed work.
10 min readReconcile Campaign Totals When Dashboard Counts Do Not Add Up
Separate unique recipients from message attempts, account for retries and exclusions, and use a filled worksheet to explain every unresolved difference at a fixed cutoff.
10 min readStop Two Operators From Retrying the Same Campaign Failures
A failed-send list is not a work assignment. Use a shared recovery log, explicit ownership, and a final send gate to stop operators from unknowingly retrying the same recipients.
9 min readPrepare a Retry List Without Resending to Confirmed Deliveries
A failed-recipient export is only a starting point. Reconcile later delivery evidence, pending attempts and other recovery actions before authorising a fresh send.
9 min readSet a Retry Budget Before Recovery Becomes Repeated Sending
A retry limit only works if it survives shift changes, exports, and recovery runs. Use a campaign-specific worksheet to cap attempts, set a relevance deadline, assign exception authority, and close exhausted cases.
10 min readChoose Which Failed Campaign Messages Are Eligible for Retry
Use four evidence-based gates to separate correctable failures, temporary restrictions, uncertain outcomes, and messages that should not be sent again.
9 min readKeep Sending or Pause? Triage a Campaign With Partial Failures
Use recipient-level evidence to separate isolated failures from wider problems, contain affected work, and leave a clear decision record for the next operator.
9 min readTurn a guide into a working customer journey.
Explore the tools and services behind the operating process.