Alactic guides: CRM, WhatsApp and customer operations
Find a practical guide for the customer-operations decision in front of you. This library brings together 996 articles across 50 topics, from collecting an enquiry to reviewing campaigns, managing handoffs and designing reliable workflows.
Choose a topic below, then open an article. Each guide focuses on a specific operating problem with examples, checklists or decision criteria you can adapt to your business.
The guides are AI-assisted editorial resources. Worked business examples are fictional. Recommended processes describe operating practices; check your product, workspace and plan before relying on a particular software capability.
AI action safety
- Authorise Multi-Step AI Actions Without Granting a Blank Cheque
- Bind AI Write Approval to the Right Records
- Build an Approval Snapshot That Shows Exactly What the AI Will Change
- Cap the Number of Records an AI Action Can Change
- Check Whether a Read Tool Has Hidden Side Effects
- Choose Absolute and Relative Limits for AI Value Changes
- Choose Soft Removal or Permanent Deletion for AI-Requested Changes
- Decide What to Do When an Approved AI Action Only Partly Completes
- Decide Whether an AI Action Retry Still Has Valid Approval
- Decide Whether an AI Change Is Truly Reversible
- Decide Which AI Tools Can Run Read-Only and Which Need Write Approval
- Decide Which Changes Invalidate an AI Action Approval
- Define What Stop Means for an AI Action Already in Progress
- Keep an AI Preview Consistent with the Action That Executes
- Limit Which Fields an AI Assistant May Change
- Prevent Repeated Small AI Actions from Bypassing Overall Limits
- Recheck Permissions When an Approved AI Action Finally Runs
- Require a Final Review Before AI Takes an External Action
- Set Expiry Windows for Approved AI Actions
- Undo an AI Change Without Overwriting Someone Else’s Work
AI answer quality
- Answer Part of a Question Without Pretending to Answer All of It
- Build an AI Answer Scorecard That Separates Serious Errors From Style Issues
- Check AI Answers About Product Availability Without Inventing Features
- Check Whether AI Citations Actually Support the Answer
- Choose Realistic Questions for an AI Answer Evaluation Set
- Choose When an AI Assistant Should Ask a Clarifying Question
- Compare Two AI Answer Versions Without Rewarding Verbosity
- Correct a Wrong AI Answer Without Creating More Confusion
- Decide Whether an AI Answer Can Use an Estimate
- Decide Which Claims an AI Answer Must Support With Evidence
- Evaluate AI Answers When More Than One Response Is Acceptable
- Find Repeated Answer Defects Without Counting Every Mistake Equally
- Handle Requests to Confirm an Unverified Customer Assumption
- Keep AI Answers Within What the Evidence Actually Says
- Keep Conditions Attached When AI Summarises an Answer
- Label AI Recommendations Separately From Business Rules
- Remove Unsupported Promises From AI Customer Replies
- Resolve Disagreements Between AI Answer Reviewers
- Test Whether AI Answers Stay Accurate Under Pressure to Be Certain
- Write Useful AI Answers When Important Facts Are Unknown
AI knowledge preparation
- Assign an Accountable Owner to Each Category of AI Knowledge
- Build a Retrieval Test Set From Real Business Information Needs
- Decide What to Do With Knowledge That Has Missed Its Review Date
- Decide Whether a Knowledge Update Is Ready to Publish
- Decide Which Business Sources Are Ready for an AI Knowledge Collection
- Define What an Approved Source Is Actually Allowed to Answer
- Diagnose Whether a Retrieval Failure Comes From Missing or Hidden Knowledge
- Establish Source Precedence Before Conflicting Documents Reach Retrieval
- Identify Business Changes That Should Trigger Immediate Knowledge Review
- Keep Customer-Specific Exceptions Out of General AI Knowledge
- Prepare Tables So AI Retrieval Preserves Row and Column Meaning
- Quarantine Knowledge Conflicts That Cannot Yet Be Resolved
- Remove Duplicate Knowledge Sources Without Erasing Useful Differences
- Replace an Approved Knowledge Source Without Leaving Two Active Rules
- Score Retrieval Results for Supporting Evidence, Not Just Similar Wording
- Separate Current Rules From Historical Rules in AI Knowledge
- Separate Reference Facts From Embedded Instructions in Source Documents
- Set Knowledge Review Intervals According to the Cost of Being Wrong
- Test Whether Retrieval Distinguishes Similar Rules With Different Conditions
- Turn Long Documents Into Retrievable Knowledge Without Losing Conditions
API integration planning
- Agree what an API write actually means before connecting records
- Assess API changes that look compatible but alter business meaning
- Assign field-level authority when both systems can edit the same data
- Assign integration ownership across business, engineering, and vendors
- Build synthetic sandbox records that expose mapping mistakes
- Check whether a sandbox can support the integration decisions you need
- Choose a pagination approach that fits the way records will be read
- Create an API dependency register before changes arrive
- Decide whether sandbox gaps should block integration approval
- Define an API integration contract before either team starts building
- Define when a paginated API read is complete
- Map missing, blank, and null values without erasing useful data
- Map record relationships when the two systems structure data differently
- Map status and category fields without hiding unknown values
- Plan an API version transition with explicit approval and fallback limits
- Plan how a paginated read resumes after an interruption
- Preserve dates, times, and numeric meaning across API field mappings
- Set list-query rules so connected teams retrieve the same records
- Specify API rejection responses that business teams can act on
- Turn an integration contract into sandbox acceptance tests
Access and workspace governance
- Approve a one-off export without granting standing export access
- Approve temporary access without letting it become permanent
- Approve workspace invitations without letting membership spread unchecked
- Choose between one workspace and separate workspaces
- Decide who should be allowed to export workspace data
- Define access roles from real tasks instead of job titles
- Give cross-workspace managers only the access they need
- Grant contractors access with a clear end point
- Keep CRM and communications permissions aligned without making them identical
- Keep an access decision register that the next administrator can use
- Keep demonstration and training access away from live customer work
- Keep mobile access within the same workspace boundaries as desktop access
- Remove a leaver's access in the right order
- Replace shared staff logins without disrupting daily work
- Reset permissions when an employee changes teams
- Resolve access-denied requests without granting full administrator rights
- Run an access review that produces removal decisions
- Separate routine administration from high-impact workspace changes
- Set up emergency workspace access without creating a daily shortcut
- Stop duplicate user identities from undermining access removal
Agency customer operations
- Agree What Happens to Client Work Outside the Agency's Service Hours
- Assign Client Review Responsibilities by Decision Type
- Choose Workspace Boundaries for Clients With Multiple Brands
- Close an Agency Engagement With a Clear Transfer of Responsibilities
- Correct a Client Report After It Has Been Shared
- Decide When a Client Request Is a Scope Change
- Decide Whether an Agency Client Is Ready for Operational Onboarding
- Define What a Client Approval Covers Before Work Proceeds
- Define a Managed Service by Tasks, Decisions, and Exclusions
- Design an Agency Client Report Around Decisions the Client Must Make
- Handle Client Requests for Bespoke Reports Without Expanding Scope Silently
- Handle Late Client Reviews Without Treating Silence as Approval
- Keep Agency-Wide Standards Separate From Client-Specific Instructions
- Onboard a Client Moving From Another Agency Without Inheriting Assumptions
- Pause an Agency Service When Client Dependencies Remain Unresolved
- Resolve Conflicting Feedback From Multiple Client Stakeholders
- Separate Agency-Controlled Work From Client-Dependent Results in Reports
- Set Review Depth According to the Risk of Client Work
- Set Support Boundaries for an Agency-Managed Client Workspace
- Turn an Agency Kickoff Into a Signed-Off Operating Brief
Audience segmentation
- Build an exclusion hierarchy that overrides attractive audience signals
- Build needs-based audiences from evidence rather than broad labels
- Check product compatibility before including customers in an audience
- Choose the right recent-activity window for an audience
- Choose whether audience eligibility belongs to a person or an account
- Decide what to do when audience eligibility data is missing
- Decide when to freeze an audience and when to refresh it
- Give temporary audience exclusions clear release conditions
- Handle customers who have more than one valid need
- Investigate audience drift when the rules have not changed
- Keep active enquiries out of audiences that assume no current conversation
- Make customer-status audiences mutually understandable
- Reconcile audience counts before accepting a segment
- Resolve overlapping audiences without losing the reason someone qualifies
- Retire stale customer-need labels without erasing useful history
- Separate meaningful customer activity from weak engagement signals
- Test audience rules with boundary and conflict cases
- Translate service coverage into audience eligibility
- Turn an audience brief into explicit eligibility rules
- Use recent purchases to distinguish fulfilled needs from new needs
Automation design
- Choose the event that should start a workflow
- Choose when a workflow timer starts and what can reset it
- Choose when to split a large workflow into smaller workflows
- Choose which workflow decisions require human review
- Decide what happens to active workflows when rules change
- Decide when a completed record may enter the same workflow again
- Decide whether a workflow runs once per person, request, or transaction
- Define stop paths that cancel future work cleanly
- Design a safe default path for cases no workflow branch covers
- Design the next step when only part of a workflow completes
- Handle unknown values without treating them as false
- Keep manual overrides from being immediately undone by automation
- Order workflow actions by dependency rather than convenience
- Prevent competing workflows from making conflicting changes
- Resolve overlapping conditions before choosing workflow branches
- Resume a workflow after human review without using stale approval
- Separate workflow entry conditions from action-time checks
- Set timeouts that produce a clear next decision
- Write a workflow diagram in prose that two teams can interpret the same way
Automation testing
- Build Synthetic Records That Exercise Real Workflow Decisions
- Build a Regression Pack from Failures Without Retesting Everything
- Check That Repeated Events Do Not Repeat Business Actions
- Choose Synthetic Test Cases by Business Consequence
- Choose a Small Rollout Group That Can Reveal Meaningful Failures
- Compare Proposed Actions with Actual Outcomes Before Wider Rollout
- Decide Whether a Failed Automation Can Be Retried Safely
- Define Expected Results Before Running an Automation Test
- Distinguish Duplicate Events from Legitimate Repeat Requests in Tests
- Inject Failures at Action Boundaries to Find Partial Completion
- Rehearse Recovery When a Test Run Leaves the Wrong State
- Set Evidence-Based Gates for Expanding or Stopping a Rollout
- Test Both Sides of Every Numeric Threshold
- Test Event Sequences That Arrive in the Wrong Order
- Test Human Review Gates for Rejection, Delay, and Changed Inputs
- Test Missing, Blank, and Unknown Values as Different Cases
- Test Simultaneous Triggers Against the Same Record
- Test Time Boundaries Without Waiting Through the Whole Workflow
- Test a Changed Workflow Against Records Already in Progress
- Verify That Stop Conditions Still Work After a Run Starts
Business messaging foundations
- Agree on channel responsibilities before adding a messaging provider
- Budget staff capacity before opening a messaging channel
- Choose between the WhatsApp Business app and an API-based setup
- Choose which customer requests belong in messaging
- Decide when an app-based messaging setup has reached its limits
- Decide whether customers need a new messaging channel at all
- Decide whether messaging should replace or complement an existing channel
- Decide whether your business is ready to offer customer messaging
- Define evidence that a business messaging pilot is ready to expand
- Define what a messaging response does and does not commit the business to
- Explain who is answering on your business messaging channel
- Keep business messaging from becoming a personal staff obligation
- Make an asynchronous messaging service clear to customers
- Name one accountable owner for the business messaging channel
- Pause expansion when business messaging outgrows its operating model
- Resolve competing department goals for one messaging channel
- Set a messaging service promise your team can actually support
- Set boundaries for urgent requests on a messaging channel
- Start business messaging with a narrow service scope
- Tell customers where messaging ends and another channel begins
Business software decisions
- Ask Vendor Questions That Produce Evidence Instead of Reassurance
- Calculate Software Ownership Costs Beyond the Subscription
- Check Your Team's Readiness Before Committing to New Software
- Choose Between One Software Suite and Several Specialist Tools
- Choose Pilot Participants Who Can Expose a Bad Software Fit
- Compare Software Quotes When Vendors Price Different Things
- Decide Whether a Paid Add-On Is Worth Buying Now
- Decide Whether to Replace Software or Fix the Buying Assumptions
- Define What Implementation Help You Are Actually Buying
- Design a Software Pilot Around the Decision You Need to Make
- Evaluate Software Support Against the Interruptions Your Team Faces
- Make a Clear Buy, Extend, or Stop Decision After a Software Pilot
- Plan the Work of Switching Software Before Accepting a Long Commitment
- Resolve a Split Software Buying Decision with an Evidence Memo
- Run Vendor Demos Against Your Work Instead of Their Presentation
- Set Software Deal-Breakers Before Comparing Vendor Scores
- Stress-Test Software Costs Before Usage or Team Size Changes
- Test Whether You Can Leave a Software Vendor Before You Buy
- Turn Software Requests into Requirements You Can Actually Score
- Weight Software Requirements Without Letting Every Feature Become Essential
Business voice conversations
- Choose What a Business Call Summary Must Preserve
- Confirm Spoken Details Without Repeating the Whole Call
- Decide When a Call Summary Needs Human Review
- Decide Which Caller Interruptions Should Stop Assistant Speech
- Find Whether Slow Voice Calls Come From Waiting, Processing, or Playback
- Handle Human Escalation When Nobody Can Take the Call
- Handle a Second Speaker Without Assuming They Represent the Caller
- Keep Uncertainty and Corrections Visible in Call Summaries
- Keep the Conversation Owned During a Human Transfer
- Let Callers Pause to Find Information Without Ending the Conversation
- Measure Voice Response Latency With Clearly Defined Start and End Points
- Pace Spoken Answers So Callers Can Interrupt Usefully
- Prepare a Voice Handoff That Does Not Make the Caller Start Again
- Recover Cleanly When Both Sides Start Speaking
- Separate Caller Requests From Business Commitments in Call Summaries
- Set End-of-Turn Rules That Do Not Cut Callers Off
- Set Human Escalation Triggers for Live Voice Calls
- Set Voice Latency Targets Without Encouraging Premature Replies
- Turn Repeated Mishearing Into a Clear Call Recovery Decision
- Use Spoken Acknowledgements During Delays Without Hiding the Wait
CRM adoption
- Allow personal work aids without creating a second CRM
- Build role-based CRM training without creating a separate course for everyone
- Choose CRM dropdown options that staff can use without guessing
- Choose the daily work trigger that makes CRM updates easier to remember
- Choose the right support format for recurring CRM questions
- Create a safe CRM practice exercise that reflects real work
- Decide when CRM refresher training is worth taking staff away from work
- Decide when a new employee is ready to use the CRM independently
- Decide which CRM fields staff should have to complete
- Decide which spreadsheet work should move into the CRM
- Diagnose CRM non-use before prescribing more training
- Fix CRM field labels that different employees interpret differently
- Make leadership requests reinforce CRM use instead of bypassing it
- Reduce CRM field clutter without hiding information staff still need
- Replace retrospective CRM data entry with a minimum useful work note
- Retire a duplicate tracker without forcing staff back into it
- Sequence CRM onboarding around the work a new starter must do first
- Set a realistic boundary between immediate and end-of-day CRM updates
- Train experienced hires to unlearn CRM habits that do not fit your team
- Use CRM peer champions without making them permanent unofficial support staff
CRM measurement
- Account for Cancellations and Reversals in CRM Success Metrics
- Allocate Attribution Credit When Several Sources Contribute
- Choose First-Touch or Last-Touch Attribution for a Specific CRM Decision
- Choose Which Customer Outcome Your Conversion Metric Measures
- Choose a Cohort Entry Event Before Comparing Sales Results
- Choose the Right Denominator for Lead-to-Customer Conversion
- Compare Lead Cohorts Without Penalising Recent Arrivals
- Compare Small Lead Cohorts Without Overreading Percentage Changes
- Decide How Reopened Opportunities Affect Conversion History
- Decide When Historical CRM Metrics Need Restatement
- Decide Whether to Count People, Accounts or Opportunities
- Define a Qualified Lead Metric That Different Teams Can Calculate the Same Way
- Explain a Conversion-Rate Change With a Reproducible Metric Bridge
- Handle Unknown Lead Sources Without Inflating Channel Performance
- Keep Acquisition Source Separate From the Latest Enquiry Source
- Measure Sales Cycle Length Without Hiding Unfinished Opportunities
- Measure Stage Conversion Without Mixing Snapshots and Lead Journeys
- Reconcile CRM Won Opportunities With Booked Orders
- Separate Cohort Improvement From Changes in Lead Mix
- Set Attribution Windows Without Rewriting Historical Results Silently
CRM migration
- Build a CRM Field Map That Makes Transformation Decisions Explicit
- Choose Between a CRM Write Freeze and a Final Delta Import
- Choose One Cutover or Migration Waves Without Splitting Record Context
- Choose a CRM Validation Sample Without Overlooking High-Risk Records
- Close a CRM Migration With Evidence Rather Than an Informal Sign-Off
- Decide What to Migrate Before Mapping CRM Fields
- Define CRM Rollback Triggers Before Cutover Starts
- Design a CRM Test Import That Exposes Edge Cases
- Handle Historical Notes and Attachments That Cannot Be Imported Cleanly
- Keep Historical CRM Notes Understandable After Import
- Map Legacy Statuses Without Making Historical Records Look Current
- Preserve Record Relationships When CRM Identifiers Change
- Protect New CRM Changes When Rolling Back After Go-Live
- Reconcile CRM Amounts and Dates After Migration
- Reconcile CRM Record Counts Without Mistaking Differences for Data Loss
- Recover a Partially Failed CRM Import Without Duplicating Successful Rows
- Resolve Custom Fields That Look Equivalent but Mean Different Things
- Run a CRM Cutover Rehearsal That Produces a Go or No-Go Decision
- Set Rules for Blank, Unknown, and Default Values During CRM Migration
- Validate Imported CRM Records Beyond a Successful Import Message
Campaign briefs
- Check campaign claims against evidence before approving the brief
- Choose an offer that actually supports the campaign objective
- Choose one primary objective when a campaign has competing goals
- Choose which campaign brief deserves scarce preparation resources
- Collect stakeholder input without turning the campaign brief into a wishlist
- Decide which campaign changes require fresh approval
- Define when to hold, reduce, or cancel a campaign before launch
- Define who can approve a campaign and who only needs to advise
- Keep the campaign promise consistent across every asset brief
- Make conditional campaign approval precise enough to act on
- Map campaign dependencies before committing to a launch
- Match the campaign promise to fulfilment capacity
- Name campaigns so teams can find the right brief and version
- Reuse a previous campaign brief without carrying forward stale assumptions
- Separate campaign facts, assumptions, and unresolved decisions
- Set a campaign success threshold before asking for approval
- Turn an offer into a clear promise the business can fulfil
- Use evidence-based readiness gates instead of a green status label
- Write campaign scope boundaries that prevent late additions
Campaign delivery operations
- An Unknown Send Result Is Not a Failed Send
- Choose Which Failed Campaign Messages Are Eligible for Retry
- Close a Campaign With Unresolved Delivery Cases Honestly
- Contain a Wrong-Content Campaign Before Sending a Correction
- Decide When a Campaign Queue Is Stalled Rather Than Merely Slow
- Decide Whether a Delayed Campaign Message Is Still Worth Sending
- Hand Over an Unresolved Campaign Without Losing the Recovery State
- Handle Late Delivery Updates Without Reopening Finished Recovery Work
- Investigate Duplicate Campaign Messages Before Cancelling More Sends
- Keep Sending or Pause? Triage a Campaign With Partial Failures
- Prepare a Retry List Without Resending to Confirmed Deliveries
- Prioritise Unfinished Campaigns After a Delivery Disruption
- Queued Is Not Delivered: Decide What Each Campaign Status Allows You to Do
- Reconcile Campaign Totals When Dashboard Counts Do Not Add Up
- Release a Campaign in Batches to Limit Delivery Incident Exposure
- Restart a Paused Campaign Without Replaying Completed Work
- Set a Retry Budget Before Recovery Becomes Repeated Sending
- Stop Two Operators From Retrying the Same Campaign Failures
- What to Verify After You Stop a Campaign
Campaign measurement
- Avoid double-crediting outcomes across overlapping campaigns
- Choose between campaign variants when reply rate and outcome quality disagree
- Choose the right delivery denominator for campaign reply rates
- Choose the right randomisation unit for a campaign experiment
- Compare campaign cohorts only after equal outcome observation time
- Compare campaigns fairly when recipient mixes differ
- Count unique campaign responders without inflating results
- Decide whether a campaign test has enough evidence to act
- Find where campaign engagement stops becoming useful outcomes
- Handle late campaign replies without silently rewriting reports
- Include negative responses in campaign success decisions
- Keep campaign outcome coding consistent across reviewers
- Measure repeated campaign exposure without counting people repeatedly
- Measure reply quality instead of treating every response as success
- Report campaign results when delivery status is incomplete
- Set an attribution window that matches the campaign decision
- Set stopping rules before checking campaign test results
- Test one campaign change without confounding the result
- Use a holdout group to estimate incremental campaign outcomes
- Verify that an apparent campaign winner survives a confirmation test
Campaign scheduling
- Check Campaign Dates Against Events That Change Customer Availability
- Check Campaign Schedules Before Daylight Saving Changes
- Choose Between One Large Send and Staggered Campaign Waves
- Choose Between Sending Before a Closure and Waiting Until Reopening
- Choose Send Windows Across Customer Time Zones
- Choose a Campaign Date When Stock Arrival Is Uncertain
- Decide Whether to Send Near the End of a Staff Shift
- Move a Campaign Date Without Breaking the Rest of the Calendar
- Replan a Campaign When Staff Coverage Drops
- Resolve Two Campaigns Competing for the Same Send Window
- Review Recurring Campaign Dates Instead of Repeating Stale Schedules
- Schedule Campaigns When Customer Time Zones Are Unknown
- Schedule Separate Campaigns That Share One Reply Team
- Schedule a Campaign Against Available Appointment Slots
- Separate Promotions That Depend on the Same Inventory
- Set Quiet Hours for Campaigns That Cross Midnight
- Set a Final Inventory Check Before a Scheduled Promotion
- Set a Schedule Lock and Rules for Last-Minute Changes
- Size Campaign Waves to the Staff Available for Replies
- Space Campaigns That Share Customers Without Rebuilding Segments
Contact identity
- Ask for Identity Clarification Without Revealing Another Person's History
- Check That a Contact Merge Preserved the Right History
- Choose Which Contact Fields Survive a Merge
- Decide When Two Contact Records Are Likely to Be the Same Person
- Decide When a Contact Merge Needs a Second Reviewer
- Distinguish People With the Same Name Before Combining Their Records
- Handle Duplicate Contacts When Each Record Has Active Business History
- Handle a Role Address When the Person Behind It Changes
- Keep Separate People Separate When They Share a Business Number
- Keep a Person's History Intact When They Change Employers
- Keep an Evidence Trail for Contact Merges and Identity Corrections
- Link a Contact’s Alternate Numbers Without Creating Duplicate People
- Place Historical Notes When the Person Mentioned Is Unclear
- Repair Contact History After Two Different People Were Merged
- Represent One Person Who Works With Several Organisations
- Resolve Conflicting Contact Updates Without Treating the Latest Entry as Truth
- Review a Suspected Reassigned Phone Number Before Reusing Contact History
- Set a Review Order for a Backlog of Suspected Duplicate Contacts
- Stop Reopening Duplicate Contact Reviews Without New Evidence
- Update a Contact's Name Without Losing Their Identity Trail
Conversation design
- Accept a Customer Correction Without Reopening the Whole Conversation
- Ask Sensitive-Sounding Questions With a Clear Conversational Purpose
- Choose the One Question That Unblocks the Next Reply
- Clarify Vague Requests Without Asking Customers to Start Again
- Confirm Understanding Without Asking Customers to Repeat Themselves
- Decide When to Clarify and When to State an Assumption
- End an Exchange Clearly Without Adding an Unnecessary Question
- Give a Short Answer First and Add Detail Only When It Helps
- Handle Multiple Customer Requests Without Losing the Main Thread
- Handle Yes and No Replies When the Previous Message Was Unclear
- Repair Your Own Misunderstanding in a Short Reply
- Resolve Ambiguous References Such as “This One” and “The Other Option”
- Resolve Contradictory Customer Statements Without Sounding Accusatory
- Resume a Conversation Without Making the Customer Reread the Thread
- Shorten Customer Replies Without Removing the Useful Answer
- Split Compound Questions Without Turning the Chat Into an Interrogation
- Stop Repeating a Clarification That the Customer Cannot Answer
- Switch Direction Cleanly When the Customer Changes Their Goal
- Tell a Side Question Apart From a New Customer Goal
- Use Answer Choices Only When They Make the Question Easier
Customer feedback
- Allocate complaint review capacity between recurring issues and isolated failures
- Build a qualitative feedback codebook that different reviewers can use
- Choose between a feedback form and a short customer interview
- Choose feedback collection moments without hearing only from happy customers
- Close a complaint only when the closure reason is clear
- Code feedback that contains several issues without losing the connections
- Decide when repeated complaints should become one shared issue
- Diagnose missing feedback before treating silence as satisfaction
- Keep a complaint loop open when there is no resolution update
- Prioritise complaints by impact rather than volume or tone
- Reprioritise aging complaints without letting old cases disappear
- Resolve reviewer disagreements before publishing feedback themes
- Respond to feedback when the business will not make the requested change
- Set feedback request limits when several teams contact the same customer
- Triage a serious complaint when important facts are still missing
- Turn coded feedback into findings without overstating what customers said
- Update feedback codes without breaking comparisons with earlier findings
- Verify that a promised feedback action actually reached the customer
- Write a complaint acknowledgement that commits only to what the team can do
- Write feedback questions that distinguish an experience from a suggested solution
Customer onboarding
- Assign onboarding ownership without making everyone responsible
- Choose a first-value milestone customers can actually recognise
- Choose the minimum onboarding scope that still delivers value
- Close onboarding when first value is reached but optional work remains
- Decide what must be ready before customer onboarding starts
- Decide when an inactive onboarding should be paused
- Decide which onboarding work can run in parallel
- Diagnose delayed onboarding before choosing a recovery action
- Escalate onboarding blockers with a decision-ready brief
- Handle new onboarding requests without silently changing the plan
- Keep onboarding moving when the customer owner changes
- Plan onboarding when the customer has limited implementation time
- Reset an onboarding plan after a milestone is missed
- Resolve conflicting onboarding priorities inside the customer's team
- Restart paused onboarding without repeating completed work
- Run an onboarding kickoff that ends with decisions, not a presentation
- Set onboarding dates when customer dependencies are still uncertain
- Turn onboarding goals into milestones with clear acceptance criteria
- Validate first value before calling onboarding successful
- Write onboarding updates that reveal risks before dates slip
Data stewardship
- Build a Retention Schedule Around Real Business Events
- Carry an Approved Correction Through Known Customer Data Copies
- Check Record Dependencies Before Removing Old Customer Data
- Choose the Least Detailed Customer Data That Still Supports the Work
- Close Out a Customer Export After Its Purpose Is Finished
- Correct a Customer Fact Without Rewriting the Historical Record
- Decide What to Keep When Detailed Customer History Is No Longer Needed
- Decide When a Customer Export Needs a Second Reviewer
- Decide Which Customer Fields Are Worth Keeping
- Define the Smallest Customer Export That Answers the Business Request
- Give Temporary Customer Data Copies an Expiry and an Owner
- Inspect Free Text and Hidden Content Before Sharing a Customer Export
- Keep Customer Notes Useful Without Recording Unnecessary Personal Details
- Repair a Mistaken Customer Data Correction
- Resolve Conflicting Customer Values Without Guessing Which Is Correct
- Review Customer Attachments Before Keeping the Whole File
- Run Retention Reviews as a Manageable Recurring Work Queue
- Set Retention Rules for Customer Records With Unfinished Work
- Stop Collecting Customer Data That Nobody Uses
- Triage Customer Data Corrections Without Overwriting Uncertain Facts
Follow-up operations
- Ask a Quiet Prospect Whether to Continue or Pause
- Choose Which Overdue Follow-Ups to Handle First
- Clear an Old Follow-Up Backlog Without Contacting Everyone
- Close Follow-Up Tasks Only When the Intended Action Is Complete
- Decide Whether Switching Follow-Up Channels Is Appropriate
- Decide Whether a Follow-Up Has Enough New Value to Send
- Follow Up Around a Real Deadline Without Inventing Urgency
- Handle Follow-Up Promises That Depend on Someone Else
- Handle Silence After a Prospect Agreed to a Next Step
- Handle Silence After an Enquiry That Never Became a Conversation
- Pause Follow-Up Until a Specific Event Makes Contact Useful
- Recover From a Missed Follow-Up Without Making Another Weak Promise
- Replace Duplicate Follow-Up Tasks With One Coherent Next Action
- Resolve Vague Follow-Up Dates Before They Become Missed Promises
- Respect a Prospect's Request to Reconnect Later
- Restart Follow-Up When a Quiet Prospect Replies
- Separate Promises to Prospects From Internal Follow-Up Reminders
- Set Stopping Rules for Follow-Up Before Chasing Begins
- Set a Follow-Up Cadence From Prospect Evidence, Not a Fixed Sequence
- Turn a Verbal Follow-Up Promise Into a Clear Next Step
Forecasting discipline
- Account for Deals That Can Slip Together
- Allow Forecast Overrides Without Losing the Original Evidence
- Check Whether High-Confidence Forecasts Actually Close More Often
- Choose Forecast Ranges That Show Real Uncertainty
- Choose Forecast Weights When Historical Data Is Sparse
- Choose Which Forecast Uncertainty to Investigate First
- Decide When a Slipped Deal Still Belongs in the Current Forecast
- Decide Whether to Include Deals That Have Not Entered the Pipeline Yet
- Decide Which Pipeline Evidence Is Strong Enough to Enter the Forecast
- Explain a Forecast Change Without Hiding It in the New Total
- Forecast Deals Whose Final Value Is Still Uncertain
- Forecast Purchases That May Be Approved in Parts
- Freeze Forecast Snapshots Without Ignoring New Information
- Handle Missing Forecast Evidence Without Turning Unknown Into No
- Know When Old Conversion History No Longer Fits the Current Pipeline
- Remove Mutually Exclusive Outcomes From Your Forecast Total
- Replace Assumed Stage Weights With Probabilities You Can Defend
- Separate the Chance of Winning From the Chance of Closing This Period
- Set an Expiry Rule for Opportunity Probabilities
- Test How Much Your Forecast Depends on One Large Deal
Human and AI collaboration
- Agree Who Makes the Final Decision Across Two Teams
- Approve Part of an AI Recommendation Without Implying Full Consent
- Build an AI Escalation Packet a Manager Can Decide From
- Choose an Approval Delegate Before the Decision Owner Is Away
- Decide What Happens When an AI Approval Request Gets No Answer
- Decide When an AI Assistant Should Ask a Colleague or Escalate
- Decide When to Narrow an AI Assistant's Delegated Role
- Decide Which AI Recommendations Need Human Approval
- Handle One-Off Exceptions Without Expanding AI Authority
- Handle Urgent Requests That Exceed the AI Assistant's Authority
- Make AI Approval Requests Offer Real Choices
- Reduce Approval Overload Without Broadening AI Delegation
- Resolve Conflicting Instructions From Two Managers
- Resolve Disagreement Between an AI Recommendation and a Human Reviewer
- Separate Approval of Customer Wording From Approval of the Decision
- Separate Permission to Investigate From Permission to Commit
- Test Whether People and AI Interpret Delegation Rules the Same Way
- Treat Conditional Approval as an Unfinished Decision
- Turn Vague AI Delegation Instructions Into Clear Decision Boundaries
- Use Past Human Decisions Without Treating Them as Blanket Permission
Integration reliability
- Build an integration outage runbook with clear decision authority
- Choose a safe degraded mode when a dependency is unavailable
- Choose which integration failures deserve a retry
- Control intake when an integration cannot keep up
- Decide when a circuit breaker should stop calls to a failing dependency
- Decide when a dependency incident is resolved and restrictions can be removed
- Decide whether old queued work is still worth executing
- Detect silent integration stalls when no errors are being reported
- Diagnose queue growth before adding more workers
- Drain an integration backlog without causing a second outage
- Handle a timed-out write when you do not know whether it succeeded
- Isolate repeatedly failing queue items without hiding unfinished work
- Keep a manual outage workaround from creating conflicting updates
- Monitor integration reliability through completed business tasks
- Prevent one slow dependency from exhausting the whole integration
- Reserve integration capacity for urgent work during a backlog
- Set backoff and retry budgets that do not amplify an outage
- Set integration alerts that require a clear operational response
- Set integration timeouts around the business task, not a convenient default
- Trace one stuck business task across an integration
Lead assignment
- Approve manual routing exceptions without undermining fairness
- Assign leads when routing information is missing
- Choose one accountable owner when several people work a lead
- Choose the right fairness measure for lead distribution
- Choose what happens when every eligible lead owner is at capacity
- Choose when owners should pull leads instead of receiving assignments
- Cover planned leave without unnecessarily changing lead owners
- Decide when an existing relationship should override normal lead routing
- Decide when stale ownership justifies reassignment
- Define who belongs in a round-robin lead assignment pool
- Give new team members a controlled share of live leads
- Prevent repeated lead reassignment from disrupting continuity
- Reassign leads safely when an owner becomes unexpectedly unavailable
- Redistribute a departing employee’s leads without overloading the team
- Resolve conflicts between territory rules and specialist skills
- Separate required skills from preferred skills in lead routing
- Set lead ownership rules at shift boundaries
- Set workload caps that reflect actual lead effort
- Use acceptance windows without letting leads bounce between owners
- Weight lead allocation for part-time staff without creating catch-up debt
Lead capture
- Ask for missing enquiry details without making visitors start again
- Capture business phone extensions and alternate numbers clearly
- Choose a single-page or multi-step enquiry form
- Choose an accessible alternative to a form control that blocks enquiries
- Choose when phone verification is worth the extra capture step
- Choose which fields belong on the first enquiry form
- Confirm that an accepted enquiry reached the intended destination
- Decide what makes an incomplete enquiry worth accepting
- Decide when an enquiry form should use conditional questions
- Decide whether a phone number must be required on an enquiry form
- Design save-and-resume behaviour for unfinished enquiries
- Handle missing and conflicting source values at form submission
- Keep enquiry capture available while the main form is broken
- Make mobile enquiry forms usable without a perfect connection
- Preserve enquiry context when visitors move between pages
- Prevent repeat submissions when visitors are unsure a form worked
- Recover form errors without erasing the visitor's answers
- Separate lead source fields that answer different capture questions
- Validate international phone numbers without rejecting plausible enquiries
- Write enquiry form labels that prevent ambiguous answers
Lead qualification
- Ask about budget without confusing uncertainty with poor fit
- Build a short qualification question set without losing decision quality
- Choose qualification criteria that actually change a decision
- Decide what evidence is strong enough to qualify a lead
- Decide when old qualification answers need to be checked again
- Decide when you have enough qualification evidence to stop asking
- Distinguish hard qualification requirements from preferences
- Distinguish temporary qualification blockers from permanent mismatches
- Judge low-effort buying signals without overreading them
- Keep qualification scores from hiding decisive facts
- Qualify decision access without dismissing useful contacts
- Qualify interest in your offer rather than interest in any solution
- Record unknown qualification answers without turning them into a no
- Replace vague disqualification labels with defensible reasons
- Resolve conflicting qualification answers without guessing
- Resolve disagreements about whether a lead is qualified
- Separate fit from intent before deciding whether a lead is qualified
- Test whether a stated deadline reflects genuine buying intent
- Turn a vague enquiry into evidence of a real business need
- Write qualification notes that distinguish facts from assumptions
Loss analysis
- Ask for Loss Feedback Without Steering the Buyer Toward Your Explanation
- Build Loss Reasons That Separate Buyer Outcomes from Sales Explanations
- Choose a Primary Loss Reason When Several Factors Contributed
- Classify Losses to an Incumbent, Internal Build, or Manual Workaround
- Close Opportunities with Unresolved Outcomes Without Inventing a Loss Reason
- Correct a Loss Record When Later Evidence Changes the Story
- Decide Whether a Quiet Opportunity Is Lost or Dormant
- Decide Which Lost Opportunities Need a Deeper Review
- Define Evidence That Justifies Reopening a Lost Opportunity
- Distinguish a Price Loss from an Unclear Value or Scope Decision
- Handle Partial Losses When Only Part of the Buying Decision Ends
- Handle Renewed Interest When the Original Loss Barrier Still Exists
- Prevent Repeated Reopening from Erasing a Pattern of Unresolved Losses
- Reclassify Old Loss Reasons Without Erasing the Original Record
- Record Competitor Outcomes Without Turning Hearsay into Fact
- Record Internal Buying Barriers Without Blaming an Unnamed Stakeholder
- Reopen the Original Opportunity or Create a New Buying Decision
- Resolve Conflicting Accounts of Why an Opportunity Was Lost
- Separate Project Cancellation from a Decision to Keep the Status Quo
- Set Dormant Review Dates Around Buyer Events, Not Arbitrary Intervals
Manager routines
- Assign an owner to actions from cross-team review meetings
- Choose One Useful Focus for a Weekly Coaching Conversation
- Choose What Belongs in a Manager's Daily Exception Review
- Choose Who Needs to Attend a Team Meeting
- Decide Whether a Work Problem Needs Coaching or a Process Fix
- Decide Which Recurring Meetings to Keep, Merge, or Cancel
- Define Evidence of Completion Before Closing a Management Action
- Design a Decision Meeting That Ends With an Actual Decision
- Follow Up on Coaching Without Turning It Into Daily Policing
- Move Routine Status Updates Out of Meetings Without Losing Visibility
- Protect Planned Work While Leaving Room for Unplanned Requests
- Rebalance Team Workload Without Rewarding Hidden Overwork
- Remove the Manager as a Bottleneck for Routine Decisions
- Review Overdue Actions Without Repeating the Same Status Question
- Run a Weekly Capacity Review Before Committing to More Work
- Set Action Deadlines That Reflect Dependencies and Available Capacity
- Set Intervention Thresholds Without Taking Over Every Problem
- Triage an Exception Queue That Cannot Be Cleared Today
- Turn Repeated Daily Exceptions Into a Separate Management Decision
- Use Work Evidence in Coaching Without Reviewing Everything
Messaging cost planning
- Allocate a shared messaging bill to departments without arbitrary splits
- Budget a multi-message journey without charging every step to every recipient
- Budget for messaging when the recipient market mix is uncertain
- Budget the cost of learning before funding a larger messaging rollout
- Choose low, base, and high messaging budgets from explicit assumptions
- Close a messaging cost month when usage records arrive late
- Compare messaging cost per outcome without hiding denominator problems
- Decide how much messaging budget to hold in reserve
- Decide whether an extra message is worth its incremental cost
- Explain a messaging budget variance without blaming volume alone
- Find which messaging cost assumption is worth investigating first
- Handle uncertain message categories before approving a budget
- Keep a messaging rate sheet that can explain an old estimate
- Plan a messaging budget when rates and payments use different currencies
- Reconcile delivered-message records with billed messaging usage
- Separate message charges from the rest of the communications bill
- Set a monthly messaging spending envelope across competing requests
- Set an affordable messaging cost per outcome from contribution assumptions
- Set reforecast triggers before messaging spend drifts
- Turn a messaging plan into a delivered-message cost estimate
Messaging permission
- Audit Whether Permission Records Support the Decisions Staff Make
- Check Whether Permission Still Applies When Someone Else Uses the Number
- Choose the Minimum Evidence to Keep in a Messaging Permission Record
- Decide What to Do When Historical Permission No Longer Matches Expectations
- Decide Whether Existing Evidence Supports a Specific Message Purpose
- Distinguish Event Attendance From a Choice to Receive Messages
- Handle Referred Phone Numbers Without Assuming Messaging Permission
- Handle a Withdrawal When Its Scope Is Unclear
- Keep Channel Choices Separate When Customers Change How They Want Contact
- Make a Withdrawal Effective Across the Places Staff Check Permission
- Offer Messaging Frequency Choices the Business Can Actually Respect
- Offer Topic Choices Without Creating Preferences the Team Cannot Honour
- Recognise Withdrawal Requests That Do Not Use a Standard Keyword
- Record Verbal Messaging Permission Without Turning Notes Into Proof
- Resolve Conflicting Messaging Permission Records
- Review a Historical Contact List Before Treating It as Messageable
- Separate Permission for Enquiry Replies From Permission for Offers
- Verify a New Messaging Choice After an Earlier Withdrawal
- Version Permission Invitations Without Losing What People Originally Saw
- Write a Messaging Invitation That Makes the Choice Understandable
Mobile team operations
- Build Mobile Checklists That Can Be Used at the Point of Work
- Check Whether Downloaded Field Instructions Are Still Current
- Choose What a Field Worker Must See on the First Mobile Screen
- Choose Which Mobile Checklist Steps Need Evidence
- Decide When a Field Worker Should Retry a Mobile Save
- Decide Which Reviews Are Safe to Complete on a Phone
- Distinguish a Seen Mobile Alert from an Accepted Field Change
- Hand a Field Visit Back to the Office from a Phone
- Keep Mobile Record Updates Short Without Losing Meaning
- Keep Working When a Mobile Upload Will Not Finish
- Prepare a Field Work Pack Before Connectivity Drops
- Reconcile Field Notes After Working Without a Connection
- Reduce Duplicate Alerts Across Mobile Channels
- Resume an Interrupted Mobile Checklist Without Losing Your Place
- Review Documents on Mobile Without Missing the Important Detail
- Send a Field Exception That the Office Can Act On
- Separate Mobile Alerts That Need Action from Updates That Can Wait
- Set Notification Coverage for Field Shifts Without Alerting Everyone
- Transfer an Unfinished Field Job Between Mobile Workers
- Use Not Applicable and Blocked Without Hiding Incomplete Field Work
Multilingual conversations
- Ask for language preference without slowing the conversation
- Build a bilingual terminology list around customer misunderstandings
- Change conversation language without losing unresolved details
- Check customer understanding without asking only 'Is that clear?'
- Choose Hindi script or Romanised Hindi from customer evidence
- Choose language formats when customer participants need different things
- Correct a mistranslation without creating a second conflicting explanation
- Decide which business terms to translate and which to explain
- Hand off a mixed-language conversation without flattening its meaning
- Handle code-switching without changing language after every message
- Handle unfamiliar regional wording without guessing the customer's meaning
- Keep names and reference codes intact across languages
- Keep translated message versions aligned when the source changes
- Make dates, amounts, and units unambiguous in multilingual messages
- Preserve courtesy without changing the meaning of a translated message
- Resolve ambiguous Hinglish replies before treating them as agreement
- Respond when no available colleague speaks the customer's language
- Review translations without approving text you cannot verify
- Set translation review depth according to the consequence of an error
- Write Hinglish instructions that customers can act on
Quotes and proposals
- Agree on a Proposal Review Plan Before Sending the Quote
- Choose Between a Fixed Quote, a Range, and Paid Scoping
- Decide When Requirements Are Complete Enough to Quote
- Decide Which Quote Changes Need Fresh Internal Approval
- Distinguish a Scope Clarification From a Chargeable Change
- Follow Up on a Proposal That Has Gone Quiet
- Give Quote Approvers the Evidence Needed for a Decision
- Handle an Expired Quote Without Silently Reusing Old Terms
- Keep One Current Quote When Buyers Have Several Versions
- Offer Proposal Options Without Creating Version Confusion
- Price a Scope Change Without Hiding Its Timing Impact
- Reduce Proposal Scope to Meet a Budget Without Losing the Core Outcome
- Resolve Open Proposal Questions Without Another Full Rewrite
- Respond When a Buyer Says a Competing Quote Is Cheaper
- Separate Buyer Interest From Approval of a Specific Proposal
- Set Quote Approval Rules Around Exceptions, Not Every Document
- Show What Changed Between Proposal Versions
- Stop Informal Additions From Becoming Unpriced Proposal Commitments
- Turn Conflicting Buyer Requests Into One Quotable Brief
- Write Quote Assumptions Buyers Can Actually Confirm
Renewals and retention
- Assign One Recovery Owner When Several Teams Contributed to the Failure
- Choose Between Renewing the Current Service and Offering a Smaller Scope
- Choose a Service Recovery Remedy That Addresses the Actual Failure
- Close a Cancelled Account Without Leaving Service Loose Ends
- Decide Whether Another Recovery Attempt Is Credible After Repeat Failures
- Decide Whether an Account Is Ready for a Renewal Conversation
- Decide Whether to Offer a Retention Alternative After a Cancellation Request
- Distinguish a Cancellation Request From a Request to Fix a Problem
- Handle a Renewal Decision That Is Still Unconfirmed Near the End Date
- Interpret Conflicting Account Health Signals Before Escalating
- Keep Missing Account Health Data Separate From Genuine Customer Risk
- Keep Recovery Commitments Visible After the Customer Renews
- Prioritise At-Risk Accounts When Recovery Capacity Is Limited
- Process Cancellation Requests Without Repeated Retention Pressure
- Resolve Unfinished Service Promises Before Presenting a Renewal
- Set Account Health Triggers That Lead to Specific Retention Actions
- Set Renewal Review Dates Around the Customer's Decision Process
- Use Renewal Feedback to Change the Account Plan, Not Just Record a Score
- Verify That Service Recovery Worked Before Closing the Case
- Verify Who Can Make the Renewal Decision Before Asking for Commitment
Reports and dashboards
- Add Freshness Labels That Show What a Dashboard Actually Knows
- Choose Between Event-Date and Entry-Date Reports
- Choose Chart Scales That Do Not Exaggerate Dashboard Changes
- Choose What Belongs in a Daily Dashboard and What Can Wait Until Weekly
- Choose a Weekly Reporting Window That Readers Can Compare Reliably
- Compare Weekly Reports When Holidays or Closures Change the Context
- Correct a Dashboard Summary After It Has Been Shared
- Decide Whether an Incomplete Dashboard Is Safe to Use
- Explain Why a Report Changes After the Reporting Period Ends
- Explain Why a Weekly Total Cannot Always Be Built by Adding Daily Cards
- Interpret a Dashboard Change When the Team Mix Has Shifted
- Investigate Conflicting Dashboard Totals Before Choosing One
- Make Saved Dashboard Filters Visible Before Readers Interpret Results
- Make Today’s Partial Results Comparable With Previous Days
- Prevent Off-by-One-Day Errors in Report Date Filters
- Read Daily Spikes Without Mistaking Them for a Weekly Trend
- Set Reporting Day Boundaries for Teams Working Across Time Zones
- Show Zero, Missing, Delayed, and Not Applicable as Different States
- Turn a Weekly Report Into a Short, Evidence-Linked Action Summary
- Write a Dashboard Summary That Separates Facts From Explanations
Sales handoffs
- Carry Customer Stakeholder Context Into Delivery Without Making Assumptions
- Choose Between a Single Handoff and a Phased Transfer
- Choose What Sensitive Sales Context Delivery Actually Needs
- Close the Sales Handoff Without Erasing Remaining Sales Obligations
- Decide When a Sales Handoff Needs a Live Meeting
- Decide When a Sold Deal Is Ready for Delivery Handoff
- Divide Responsibilities When Several Delivery Teams Receive One Sale
- Handle New Customer Requests That Arrive During the Handoff Window
- Introduce Delivery to the Customer Without Creating Two Competing Contacts
- Make Delivery Acceptance Explicit Instead of Assuming Ownership Has Moved
- Make Sales Handoff Claims Traceable Without Forwarding the Entire History
- Resolve Conflicting Sales Records Before Delivery Relies on Them
- Return an Incomplete Handoff Without Creating an Ownership Deadlock
- Separate Customer Expectations From Confirmed Delivery Commitments
- Set Boundaries for Temporary Sales Cover and the Return Handoff
- Transfer Dependencies That Sales Cannot Resolve Before Delivery Starts
- Transfer Unresolved Sales Commitments Without Losing Accountability
- Transfer an Account When the Sales Owner Leaves Unexpectedly
- Transfer an Active Account Between Salespeople Without Restarting Discovery
- Write a Handoff Summary That Helps Delivery Make Its First Decisions
Sales pipeline design
- Choose between one pipeline and separate buying-motion pipelines
- Choose the right pipeline correction for a stalled deal
- Clean an unreliable pipeline without replacing bad data with guesses
- Correct stage history when administrative edits look like buyer progress
- Decide when parallel purchase paths should be separate opportunities
- Decide whether a proposed pipeline stage deserves to exist
- Define sales stages around buyer progress instead of seller activity
- Define stalled deals using stage context rather than one universal timeout
- Define the exact event that makes an opportunity closed won
- Handle missing evidence without pretending a deal has passed its stage gate
- Move a deal backward when buyer progress has genuinely reversed
- Move open opportunities to revised stage definitions without guessing
- Prevent duplicate opportunities from representing the same purchase
- Represent a genuine buyer pause without leaving a deal falsely active
- Represent conditional buyer commitments without overstating progress
- Require only the pipeline fields needed for the current stage
- Separate buyer inactivity from seller inactivity in stalled opportunities
- Set rules for opportunities that skip sales stages
- Track parallel buyer approvals without turning them into a false sequence
- Write stage exit criteria that two sellers can apply the same way
Service enquiries
- Ask for missing service requirements in the right order
- Check appointment prerequisites without asking customers to do technical work
- Check that a service appointment has enough time for the known work
- Choose between a named appointment time and an arrival window
- Confirm site access before sending a service team
- Decide when repeated rescheduling needs a fresh booking review
- Decide whether an enquiry needs a booking, a clarification or a site visit
- Decide whether to proceed when site conditions differ from the booking
- Give an assessment site visit a clear purpose and stopping point
- Handle a business-initiated appointment change with usable alternatives
- Handle service requests that sit at the edge of your coverage
- Reassess a service request when the customer reports a change
- Reschedule a service appointment without losing the agreed scope
- Resolve a missed visit before choosing another appointment
- Resolve conflicting requirements before confirming the visit
- Separate service requests that need action now from those that can wait
- Set a readiness gate before confirming a service appointment
- Split a service enquiry with several problems into bookable work
- Turn a completed site assessment into a ready next appointment
- Use customer photos and documents without treating them as proof of diagnosis
Shared inbox operations
- Check for New Customer Messages Before Sending a Draft
- Choose What Should Be Consistent Across Team Replies
- Cover an Absent Inbox Owner Without Creating Duplicate Work
- Decide When a Saved Reply Needs Editing or Should Not Be Used
- Decide When an Incoming Conversation Needs a Named Owner
- Decide Which Internal Notes Belong in a Shared Conversation
- Define What Resolved Means in a Shared Inbox
- Find the Current Commitment in a Long Conversation
- Hand Over Open Inbox Conversations at a Shift Change
- Handle Several Open Requests in One Customer Conversation
- Keep One Accountable Owner When Several Teams Join a Conversation
- Recover After Two Conflicting Replies Have Already Been Sent
- Reopen a Conversation or Start a New One When a Customer Returns
- Resolve Conflicting Answers Within the Inbox Team
- Review Old Unresolved Conversations Without Closing Them Blindly
- Review Reply Quality Without Rewarding Fast but Incomplete Answers
- Separate Waiting on the Customer From Waiting on Your Team
- Set Rules for Claiming Conversations From a Shared Queue
- Write an Internal Conversation Summary That Supports the Next Reply
Template lifecycle
- Choose Between Revising a Rejected Template and Requesting Review
- Choose a Fallback When a Template Is Still Pending at the Business Deadline
- Contain the Operational Impact of a Paused Template
- Create a Version Register That Distinguishes Approval From Release
- Decide When a Repeatedly Paused Template Should Be Retired
- Decide When a Template Change Needs a Separate Version
- Decide Whether Work Can Resume After a Template Pause
- Decide Whether a Pending Template Still Needs to Go Live
- Diagnose a Rejection Before Rewriting the Template
- Handle Partial Approval Across Template Language Versions
- Investigate a Paused Template Without Guessing the Cause
- Map Dependencies Before Replacing an Approved Template
- Prioritise a Backlog of Pending, Rejected, and Paused Templates
- Resolve Conflicting Template Status Records Before Staff Use Them
- Retire Old Templates Without Losing the Decision History
- Rewrite Rejected Wording Without Changing the Message’s Real Purpose
- Run a Controlled Cutover Between Template Versions
- Set Rollback Criteria Before Releasing a Replacement Template
- Set an Escalation Rule for Templates Stuck in Review
- Stop Repeated Resubmissions That Do Not Resolve the Rejection
Template media
- Build Sample Media That Represents the Asset You Intend to Use
- Check Template Images for Cropping Before They Go Into Use
- Check What a Product Image Implies Before Using It
- Choose Between a Document Attachment and Message Text
- Choose Between a Real Photograph, Illustration, and Mockup
- Choose a Template Image That Helps the Recipient Decide
- Create Safe Sample Assets Without Using Customer Information
- Decide When a Localized Message Needs a Separate Media Asset
- Fix Contrast and Color Dependence in Template Creatives
- Inspect Document Attachments for Hidden and Unintended Content
- Keep Essential Information Available Without Reading the Image
- Make Text Inside Template Images Readable on Small Screens
- Name and Version Media Files So Staff Pick the Right Asset
- Optimize Media File Size Without Losing Useful Detail
- Prepare Document Attachments for Reading on a Phone
- Record Where Template Media Came From and How It May Be Used
- Replace an Outdated Asset Without Missing Its Other Uses
- Run a Final Media Release Review With Clear Stop Conditions
- Set Expiry and Review Dates for Time-Sensitive Media
- Test Template Creatives With Difficult Content, Not Just Ideal Examples
Template planning
- Assemble a Template Review Packet With Clear Readiness Gates
- Build Variable Examples That Expose Weak Template Wording
- Choose Between Reusing an Existing Template and Writing a New Brief
- Choose Which Language Variants a Template Brief Actually Needs
- Choose Which Template Details Stay Fixed and Which Become Variables
- Decide How Much Detail Belongs in a Template Message
- Decide When Optional Content Requires a Separate Template Brief
- Decide When Two Message Purposes Need Separate Template Briefs
- Define Every Template Variable So Different Teams Use It the Same Way
- Handle Grammar and Text Expansion in Template Language Variants
- Keep Sensitive Details Out of Template Copy and Review Examples
- Make Dates, Times, Amounts, and References Unambiguous in Templates
- Plan Template Wording for Missing or Unconfirmed Information
- Remove Time-Sensitive Assumptions From Reusable Template Wording
- Resolve Conflicting Reviewer Requests Without Losing the Message Purpose
- Review Translated Templates for Meaning, Not Just Fluent Wording
- Set Terminology and Tone Rules Before Drafting Language Variants
- Verify Operational Claims Before a Template Enters Review
- Write a Template Action Request That Leaves No Next-Step Ambiguity
- Write a Template Content Brief That a Writer Can Use Without Guessing
Voice-note operations
- Catch Negations and Self-Corrections in Voice Notes
- Check Handling Preferences Before Transcribing or Sharing a Voice Note
- Choose Between Replaying Noisy Audio and Asking for a New Message
- Choose Text or Voice When Replying to a Business Voice Note
- Choose a Full Transcript or an Action Summary for a Voice Note
- Confirm Relative Dates in Voice Notes Before Acting
- Correct a Reviewed Transcript When the Sender Disputes It
- Decide What to Share From a Voice Note With Another Team Member
- Decide Which Parts of a Voice-Note Transcript Need Human Review
- Handle Numbers, Units and Amounts That Sound Alike in Voice Notes
- Handle Voice Notes With Multiple Speakers Without Guessing Who Said What
- Handle a Request Not to Keep or Transcribe a Voice Note
- Handle a Truncated Voice Note Without Completing the Sender's Thought
- Make a Voice-Note Request Usable When Someone Cannot Listen
- Mark Unclear Transcript Passages Without Turning Guesses Into Facts
- Respond When a Customer Sends Sensitive Details in a Voice Note
- Review a Voice Note Split Across Several Audio Messages
- Separate Requests, Background and Tentative Ideas in Long Voice Notes
- Verify Names in Voice Notes Without Guessing the Spelling
- Write a Confirmation Reply That Makes Voice-Note Errors Easy to Correct
Webhook processing
- Build a Review Queue for Webhook Events That Cannot Progress
- Choose When to Acknowledge a Webhook Receipt
- Choose Whether to Process Webhook Payloads or Read Current Source State
- Choose a Webhook Event Identity That Survives Redelivery
- Choose the Smallest Safe Ordering Boundary for Webhook Events
- Classify Webhook Failures Before Retrying Them
- Close Webhook Gaps After a Receiver Outage
- Decide How Long to Keep Webhook Deduplication Records
- Decide Whether to Apply, Ignore, or Hold a Late Webhook Event
- Handle Concurrent Deliveries of the Same Webhook Event
- Handle Webhook Events That Arrive Before Their Required Context
- Investigate Duplicate Webhook Spikes Without Counting Them as New Work
- Monitor Webhook Freshness Separately From Receipt Success
- Prevent Repeated Side Effects After a Webhook Worker Crashes
- Reconcile Missing Webhook Changes Against Source Records
- Record Webhook Processing States Without Hiding Unfinished Work
- Replay Webhook Events Without Repeating Completed Actions
- Separate Source Redelivery From Internal Webhook Retries
- Set the Right Boundary for Webhook Deduplication Keys
- Trace a Webhook From Receipt to Applied Business Change
WhatsApp onboarding
- Assess an existing WhatsApp setup before changing providers
- Build a WhatsApp asset inventory before starting onboarding
- Check whether a business number can receive onboarding verification
- Choose a WhatsApp display name that matches your business identity
- Choose a display name when one company operates several brands
- Choose between a new number and an existing business number
- Choose the right business portfolio for WhatsApp onboarding
- Confirm business control of a phone number before registering it
- Decide whether to reuse an existing WhatsApp business account
- Decide whether to wait, retry, or escalate a stalled onboarding step
- Diagnose onboarding blocked by missing access
- Investigate a phone number reported as already registered
- Investigate a rejected WhatsApp display name before resubmitting
- Plan the onboarding cutover for a number already serving customers
- Prepare an onboarding support packet that can be investigated
- Reconcile business identity details before verification review
- Resolve employee-owned numbers before WhatsApp onboarding
- Run a go-or-no-go review before starting WhatsApp onboarding
- Set asset custody expectations when an agency handles WhatsApp setup
- Verify onboarding completion before handing the setup to operations
Choose a useful starting point
Start with the decision causing the most rework, missed follow-ups or unclear ownership. Use one guide to define a small change, agree who owns it and review the result before extending it across your team.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications