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 when a workflow timer starts and what can reset it
Stop routine edits from restarting workflow timers. Define the start event, meaningful resets, pause rules, and expiry checks with a filled fictional timeline your team can adapt.
10 min readSet timeouts that produce a clear next decision
Give every workflow wait a completion event, deadline, timeout destination, and accountable owner—and resolve competing events before releasing work.
9 min readOrder workflow actions by dependency rather than convenience
A workflow should advance when a prerequisite is confirmed, not merely when the previous action was attempted. Use a filled dependency worksheet to separate safe parallel work from steps that must wait.
10 min readSeparate workflow entry conditions from action-time checks
A record that qualifies when a workflow starts may not qualify after a delay. Use a filled eligibility matrix to decide what to check at entry, what to recheck before action, and how to handle changed or unknown states.
10 min readResolve overlapping conditions before choosing workflow branches
When several workflow conditions are true, decide whether one path wins or several may run. Use a filled decision table to define precedence, permitted combinations, exclusions, and recovery.
10 min readHandle unknown values without treating them as false
Missing evidence is not a negative answer. Use explicit true, false, and unknown states to route requests, resolve uncertainty, and prevent unsupported actions.
9 min readDecide whether a workflow runs once per person, request, or transaction
A completed workflow should not block a new request from the same person. Use a filled scope worksheet to define the unit of work, its identifier, and the actions that belong to each instance.
10 min readChoose the event that should start a workflow
Stop unrelated record edits from starting work. Compare creation events, meaningful state transitions, and scheduled checks, then define the evidence each start requires.
10 min readChoose Which Mobile Checklist Steps Need Evidence
Require evidence where a completion claim is ambiguous, another team relies on it, or rechecking is costly. Use this fictional worked worksheet to choose direct observation, a short note, or an approved photograph without burdening every step.
10 min readResume an Interrupted Mobile Checklist Without Losing Your Place
After a call or site move, the next unchecked box may not be the right place to restart. Use a resumption routine that separates saved entries, confirmed observations and conditions that need checking again.
10 min readUse Not Applicable and Blocked Without Hiding Incomplete Field Work
A blank checkbox cannot explain whether work is unnecessary, prevented, or simply unchecked. Use four clear states, evidence rules, and a completion gate that keeps unresolved work visible.
10 min readBuild Mobile Checklists That Can Be Used at the Point of Work
Turn a scrolling desktop checklist into a usable field tool: order steps around the work, define observable completion, ask for evidence selectively, and test whether workers can resume after interruptions.
11 min readSend a Field Exception That the Office Can Act On
Turn an on-site obstacle into a short decision request, with a filled example, separate supporting detail, and a practical way to review the result.
9 min readTransfer an Unfinished Field Job Between Mobile Workers
A job label does not tell a replacement worker what is actually on site. Use a state-based handoff to record progress, untouched work, missing materials, and what the next worker has personally confirmed.
10 min readHand a Field Visit Back to the Office from a Phone
A finished visit is not always finished work. Use a compact mobile handoff to separate what happened, what remains blocked, what was promised, and who must act next.
10 min readCheck Whether Downloaded Field Instructions Are Still Current
A downloaded brief can remain readable after the plan changes. Use departure, arrival and change-triggered checks to confirm the version in hand—and define when uncertainty means pausing the affected work.
10 min readKeep Working When a Mobile Upload Will Not Finish
A stalled upload should not trigger guesswork about whether a field task can continue. Use an evidence decision table, an approved fallback, and a visible pending record to separate physical progress from confirmed completion.
10 min readReconcile Field Notes After Working Without a Connection
A practical return-to-connectivity review: match temporary notes to visible shared entries, add only what is missing, preserve event order, and route conflicting updates for a decision.
10 min readDecide When a Field Worker Should Retry a Mobile Save
A timeout does not prove an update failed. Use component-level evidence, a practical decision table, and a filled handoff report to avoid unnecessary repeat submissions.
9 min readPrepare a Field Work Pack Before Connectivity Drops
A job assignment is not a usable work pack. Decide what workers must carry, test access without a connection, and set clear departure rules for missing instructions, contacts and constraints.
10 min readReduce Duplicate Alerts Across Mobile Channels
Give each field change one primary alert route, a clear acknowledgment rule, and a fallback that points to the same instruction—not a second task.
10 min readDistinguish a Seen Mobile Alert from an Accepted Field Change
A viewed alert is not an accepted instruction. Use a practical acknowledgement matrix to confirm changed entrances, arrival windows and cancelled visits—and decide what happens when a worker cannot comply or does not respond.
10 min readSet Notification Coverage for Field Shifts Without Alerting Everyone
Use a filled shift-coverage worksheet to name active recipients, track explicit acknowledgements, handle coverage gaps, and transfer responsibility without broadcasting every alert.
9 min readSeparate Mobile Alerts That Need Action from Updates That Can Wait
Prioritise field-team notifications by what delay would change, who needs to act, and whether a reliable review point comes before the deadline. Use a worked decision table to separate interruptions from updates.
10 min readTurn a guide into a working customer journey.
Explore the tools and services behind the operating process.