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

Campaign briefs

Write campaign scope boundaries that prevent late additions

Use a filled scope worksheet and a practical decision rule to assess late requests without losing the campaign’s audience, primary action, or message clarity.

9 min read
Campaign briefs

Keep the campaign promise consistent across every asset brief

Build one canonical promise record, compare four asset briefs against it, and resolve contradictory offers without making every team use identical wording.

10 min read
Campaign briefs

Decide which campaign changes require fresh approval

Keep minor edits moving without letting material changes inherit stale approval. Use a change-control table to decide when to log an edit, seek targeted sign-off, or reopen the brief.

10 min read
Campaign briefs

Make conditional campaign approval precise enough to act on

“Approved subject to changes” is not a launch instruction. Use a bounded approval record to define permitted preparation, evidence for closing conditions, and the person who must authorise release.

10 min read
Campaign briefs

Use evidence-based readiness gates instead of a green status label

Replace vague campaign status updates with observable readiness gates, explicit evidence and a versioned decision. Use the filled checklist to distinguish ready, blocked and accepted exceptions.

9 min read
Campaign briefs

Map campaign dependencies before committing to a launch

Turn a busy campaign task list into a dependency map that shows what blocks authorisation, who owns each missing input, and what evidence will clear it.

9 min read
Campaign briefs

Define who can approve a campaign and who only needs to advise

Stop treating every campaign comment as a veto. Assign authority by issue, give advisers a clear response window, and define how unresolved objections reach a decision.

10 min read
Campaign briefs

Name campaigns so teams can find the right brief and version

Separate campaign identity, document revisions, and approval evidence so colleagues can find the right brief—even after a rename or a new recurring edition.

9 min read
Campaign briefs

Check campaign claims against evidence before approving the brief

Use a claim-evidence register to separate supported facts from estimates and promises, assign accountable reviewers, and decide which wording can proceed.

9 min read
Campaign briefs

Turn an offer into a clear promise the business can fulfil

Use a filled offer-definition sheet to align marketing, sales and fulfilment on the benefit, customer actions, boundaries and recovery decisions before production.

10 min read
Campaign briefs

Choose an offer that actually supports the campaign objective

A familiar discount can generate activity without advancing the campaign. Use a filled offer-selection matrix to compare customer action, delivery burden, and likely misunderstandings before choosing.

10 min read
Campaign briefs

Set a campaign success threshold before asking for approval

Turn a reasonable campaign objective into a bounded approval decision, with a justified outcome floor, explicit staffing commitments and clear revision rules.

10 min read
Campaign briefs

Choose one primary objective when a campaign has competing goals

Use a shared decision table to choose the audience action that matters most, protect essential guardrails, and explain which stakeholder requests belong elsewhere.

9 min read
Template lifecycle

Prioritise a Backlog of Pending, Rejected, and Paused Templates

A rejected template is not automatically more urgent than a pending one. Use business dependencies, usable alternatives and evidence readiness to decide what to investigate, protect or deliberately defer.

10 min read
Template lifecycle

Resolve Conflicting Template Status Records Before Staff Use Them

When a spreadsheet, staff note, and workspace disagree, reconcile the exact template—not just its name. Use timestamped evidence, correct the operational records, and hold unresolved cases from use.

10 min read
Template lifecycle

Handle Partial Approval Across Template Language Versions

One approved language does not make a WhatsApp template family ready. Use a language-version readiness matrix to release eligible versions, hold others, and manage alternatives without silently changing a customer’s language.

10 min read
Template lifecycle

Retire Old Templates Without Losing the Decision History

Remove obsolete WhatsApp templates from everyday use without erasing why they existed. Use a retirement checklist and a compact archive record to preserve ownership, replacement decisions, and unresolved dependencies.

10 min read
Template lifecycle

Set Rollback Criteria Before Releasing a Replacement Template

A previous template is not automatically a safe fallback. Define stop-use triggers, verify the old version against current operations, and authorise a clear choice: revert, hold use, or switch to a checked alternative.

10 min read
Template lifecycle

Run a Controlled Cutover Between Template Versions

Make a new WhatsApp template operationally authoritative with a clear release decision, reconciled pending work, individual acknowledgements, and verification evidence.

9 min read
Template lifecycle

Map Dependencies Before Replacing an Approved Template

A replacement template can be ready while procedures, saved choices and authorised workflows still point to the old one. Build a bounded dependency map, assign owners and resolve each known use before authorising the switch.

10 min read
Template lifecycle

Decide When a Template Change Needs a Separate Version

Keep wording history without creating version clutter. Use a practical classification method to separate harmless corrections from changes to commitments, variables, offers, and downstream workflows.

10 min read
Template lifecycle

Create a Version Register That Distinguishes Approval From Release

An approved template is not automatically the version staff should use. Build a manual register that separates reported status from internal release decisions and points each message purpose to one authoritative version.

10 min read
Template lifecycle

Decide When a Repeatedly Paused Template Should Be Retired

Repeated restoration is not a lifecycle strategy. Use a filled hypothetical scorecard to weigh business value, unresolved uncertainty, staff effort, and alternatives before retaining, redesigning, or retiring a WhatsApp template.

10 min read
Template lifecycle

Decide Whether Work Can Resume After a Template Pause

A template becoming available again is not permission to restart. Use a documented gate to check suitability, unresolved findings, ownership and fallback readiness.

10 min read

Turn a guide into a working customer journey.

Explore the tools and services behind the operating process.

Explore Communications