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
Ask for Identity Clarification Without Revealing Another Person's History
When several CRM records could fit a caller, ask for context they can supply independently—not details pulled from someone else’s history. Use this filled clarification brief to resolve matches or leave them safely unresolved.
10 min readResolve Conflicting Contact Updates Without Treating the Latest Entry as Truth
Use a field-by-field conflict ledger to distinguish reported plans, established changes and corrections—without overwriting uncertainty or inventing a current employer.
9 min readPlace Historical Notes When the Person Mentioned Is Unclear
Use dated evidence to distinguish a confirmed person, an established organisation, and unresolved attribution—without turning an old CRM filing choice into proof.
9 min readHandle a Role Address When the Person Behind It Changes
Keep a shared business address separate from the people who use it. Use this filled transition map to preserve useful history without assigning a predecessor’s decisions or preferences to a replacement.
9 min readLink a Contact’s Alternate Numbers Without Creating Duplicate People
Use an evidence-based worksheet to distinguish additional phone numbers from replacements, preserve valid contact points, and keep uncertain matches out of confirmed records.
9 min readDistinguish People With the Same Name Before Combining Their Records
Use an evidence-based worksheet to distinguish namesakes, keep unresolved records separate, and create display labels that help staff select the right contact.
10 min readRepresent One Person Who Works With Several Organisations
Keep a person's identity separate from their business affiliations. Use a filled relationship decision table to choose role labels, handle workspace limits, and record which organisation each interaction concerns.
10 min readKeep a Person's History Intact When They Change Employers
A job move should change a person's affiliation, not erase their history. Use a filled worksheet to record the new relationship, retain the former one, and keep past activity in its original business context.
10 min readUpdate a Contact's Name Without Losing Their Identity Trail
Keep the current name visible without creating a second person. Use a filled decision worksheet to separate name changes from uncertain matches, retain only useful history, and repair mistakes safely.
9 min readRepair Contact History After Two Different People Were Merged
An incorrect contact merge does not make every interaction unreliable. Use an evidence-led worksheet to separate attributable history, contain uncertain notes, and test the repaired records before staff resume work.
10 min readHandle Duplicate Contacts When Each Record Has Active Business History
One person can have several active enquiries without needing several contact records. Use a filled relationship map to plan identity consolidation, preserve separate histories, and verify every link afterward.
10 min readDecide When a Contact Merge Needs a Second Reviewer
Use identity evidence, linked history, recovery limits, and the consequences of error to decide who may approve a contact merge—and when nobody should proceed.
9 min readSet a Review Order for a Backlog of Suspected Duplicate Contacts
Review suspected duplicates by the customer interactions they could disrupt, the identity evidence still missing, and the history a mistaken merge could mix—not simply by the age of the flag.
10 min readChoose Which Contact Fields Survive a Merge
Resolve conflicting contact fields using attributable evidence, explicit preferences, and field-level dates—not whichever record was updated last. Includes a filled survivorship worksheet.
9 min readReview a Suspected Reassigned Phone Number Before Reusing Contact History
When someone at a familiar number denies knowing your contact, pause identity assumptions. Use this review checklist to protect earlier conversations and separate the new respondent’s record without rewriting the past.
10 min readKeep Separate People Separate When They Share a Business Number
A shared business number identifies an endpoint, not necessarily a person. Use this filled worksheet to separate receptionists and buyers, record speaker evidence, and keep unresolved interactions out of individual histories.
10 min readDecide When Two Contact Records Are Likely to Be the Same Person
Use connecting evidence, shared-channel checks, and a clear contradiction rule to assess suspected CRM duplicates without turning matching fields into proof of identity.
10 min readKeep enquiry capture available while the main form is broken
A broken form needs more than an alternative email address. Use a checked fallback channel, clear visitor wording and a shared capture record, then reconcile every enquiry before closing the interruption.
10 min readConfirm that an accepted enquiry reached the intended destination
A success message is not proof that an enquiry reached your CRM or inbox. Use a synthetic test and a filled reconciliation checklist to connect acceptance evidence to a destination record—and investigate gaps safely.
9 min readPrevent repeat submissions when visitors are unsure a form worked
A disabled submit button is only the first safeguard. Define clear submission states, preserve the identity of an attempt, and make retries safe when the server receives a form but the visitor never sees the response.
10 min readRecover form errors without erasing the visitor's answers
Specify error messages, preserved answers and recovery actions together so visitors can correct an enquiry without rebuilding it.
10 min readAsk for missing enquiry details without making visitors start again
A missing detail should not mean a new form. Use a focused message brief to preserve what the visitor already submitted, clarify the one unresolved point, and recognise when capture is complete.
10 min readDesign save-and-resume behaviour for unfinished enquiries
Define what saving protects, how visitors return, when access expires and what turns a draft into a submitted enquiry—with a filled worksheet and release checks.
9 min readDecide what makes an incomplete enquiry worth accepting
Separate missing essentials from missing detail so your form accepts clear enquiries, clarifies ambiguous requests and offers honest alternatives when a reply is not possible.
10 min readTurn a guide into a working customer journey.
Explore the tools and services behind the operating process.