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 Chart Scales That Do Not Exaggerate Dashboard Changes
Use chart scales that make dashboard comparisons accurate: zero-based magnitude bars, clearly labelled trend close-ups, consistent panel ranges and visible gaps in time.
9 min readInterpret a Dashboard Change When the Team Mix Has Shifted
When an overall rate falls while team rates rise, check the mix of completed work. Use this worked report and reusable review record to explain the change accurately.
9 min readExplain Why a Weekly Total Cannot Always Be Built by Adding Daily Cards
Daily cards may count events, show a backlog at a moment, or count people who return on several days. Use this filled report-reading guide to choose a valid weekly interpretation before adding anything.
9 min readCompare Weekly Reports When Holidays or Closures Change the Context
A shorter operating week can complicate a reported decline. Use raw totals, calendar notes and matched weekdays to show what changed without claiming to know why.
9 min readRead Daily Spikes Without Mistaking Them for a Weekly Trend
A striking day deserves attention, not an instant trend label. Use an annotated daily series, comparable weekly totals and a decision checklist to separate a reporting event from a sustained change.
9 min readMake Saved Dashboard Filters Visible Before Readers Interpret Results
A correct dashboard total can still mislead when readers miss inherited filters. Use a visible scope strip and verify saved, shared, and exported populations before distribution.
10 min readInvestigate Conflicting Dashboard Totals Before Choosing One
When a dashboard, saved report, and export disagree, compare their reporting scope, date basis, filters, cutoff, and refresh state in order. Use a filled fictional worksheet to separate explainable differences from issues worth escalating.
9 min readAdd Freshness Labels That Show What a Dashboard Actually Knows
A refreshed page can still contain old data. Give readers separate timestamps for the page, source availability, and verified coverage—and tell them which conclusions must wait.
10 min readDecide Whether an Incomplete Dashboard Is Safe to Use
A dashboard can load successfully and still be unsuitable for a decision. Use this readiness checklist to identify what remains usable, what needs restrictions, and which conclusions must wait.
10 min readShow Zero, Missing, Delayed, and Not Applicable as Different States
A blank cell is not evidence of inactivity. Use a clear display contract to distinguish confirmed zero, missing values, delayed data, and measures that do not apply—with a worked dashboard legend and annotated report excerpt.
10 min readChoose Between Event-Date and Entry-Date Reports
A spike in records entered today may describe work completed earlier. Use a worked example and a reusable report card to choose the right date basis and make recording delays visible.
10 min readExplain Why a Report Changes After the Reporting Period Ends
A reporting period can end before all its records arrive. Use clear cutoffs, version labels, and a revision log to explain what changed without asking readers to disregard the earlier report.
10 min readPrevent Off-by-One-Day Errors in Report Date Filters
An end date can mean midnight at the start of a day or the end of that entire day. Use explicit boundaries, a named reporting time zone, and a filled boundary-test checklist to make adjacent exports reconcile.
9 min readChoose a Weekly Reporting Window That Readers Can Compare Reliably
Use completed calendar weeks for settled weekly comparisons, rolling windows for recent conditions, and matched week-to-date periods for progress checks. A filled decision table shows how to label each without inviting unequal comparisons.
9 min readSet Reporting Day Boundaries for Teams Working Across Time Zones
Stop conflicting daily totals by choosing one reporting time zone, separating it from local display time, and testing exactly where midnight events belong.
10 min readMake Today’s Partial Results Comparable With Previous Days
Compare unfinished days fairly using matching cutoffs, verified data completeness, and a filled worksheet—without inventing an end-of-day forecast.
10 min readChoose What Belongs in a Daily Dashboard and What Can Wait Until Weekly
Separate urgent exceptions from trends and unfinished outcomes. Use a filled decision table to assign each report component a reading frequency, maturity rule, and warning label.
10 min readUse Spoken Acknowledgements During Delays Without Hiding the Wait
Make live voice delays understandable with evidence-based acknowledgements, bounded repeats, and honest choices. Includes a filled delay-response brief.
9 min readFind Whether Slow Voice Calls Come From Waiting, Processing, or Playback
A long conversational gap is not one diagnosis. Use a segmented turn timeline and a filled diagnostic worksheet to locate waiting, response-preparation, audio-start, and interruption delays before changing prompts.
10 min readSet Voice Latency Targets Without Encouraging Premature Replies
Set different timing targets for acknowledgements, confirmations, complex answers, and human-help transitions—and make interruption, repair, and completion measures part of the decision.
10 min readMeasure Voice Response Latency With Clearly Defined Start and End Points
A voice assistant can acknowledge quickly and still answer slowly. Use separate timing measures, explicit event boundaries, and a filled hypothetical measurement sheet to explain the difference.
10 min readKeep the Conversation Owned During a Human Transfer
A transfer is not complete because someone answers. Use a filled transfer-state worksheet to define who owns the caller, what counts as acceptance, and how to recover when a handoff fails.
10 min readHandle Human Escalation When Nobody Can Take the Call
Use a clear fallback when a live transfer fails: explain the limitation, offer verified alternatives, and distinguish a saved request from a confirmed callback.
9 min readPrepare a Voice Handoff That Does Not Make the Caller Start Again
Give the receiving human the caller’s immediate need, what has already been tried, and what remains uncertain—with a filled handoff packet and an acknowledgement check.
10 min readTurn a guide into a working customer journey.
Explore the tools and services behind the operating process.