01What this guide helps you do
Recognise when content or recipient feedback needs review.
This guide focuses on one task within delivery & message quality. Its completion test is specific: The team does not treat every quality restriction as a technical outage. Use that result to decide whether the task is finished. Opening a page, entering a value or seeing a brief notification can be part of the process without establishing the complete result.
02When to use this workflow
Use this workflow when your immediate goal is to separate quality concerns from software errors. Keep the scope limited to the relevant delivery investigation. If you are solving a different problem, use the related guides at the end rather than applying every action here to unrelated records.
The usual operational owner is the campaign operator or support lead. If another person owns the relevant business facts or permissions, involve that person before changing the shared record. Individual access and business authority are not always the same thing.
03Prepare the information you need
Start with the exact message or campaign reference and its most recent outcome. Preserve the original attempt so you can distinguish it from a retry. Collect the visible provider explanation, the affected recipient context and a comparable successful result where available. Avoid assuming that a frequently used test number represents the delivery behaviour of every future recipient.
Provider feedback, complaint pattern, campaign content.
04Find the right workspace and feature
Start from Campaigns → Campaign details and Inbox. Treat this as a feature locator: the arrangement of menus can differ between the web interface and the native application. Confirm the workspace name and the relevant record before proceeding, especially if you manage more than one business or use both India and UK accounts.
The target of this task is a delivery investigation. Keep its identity visible while you work. A similarly named record or a previously open browser tab can otherwise make a correct action affect the wrong context.
05Understand the information on screen
| Information | What it means | Practical check |
|---|---|---|
| Reference | Specific original attempt | Keep it with the investigation |
| State | Latest delivery evidence | Distinguish pending and final |
| Reason | Provider or validation explanation | Choose recovery from the cause |
| Scope | Recipient or campaign-wide issue | Avoid unnecessary broad changes |
Apply these distinctions to the specific inputs for this guide: provider feedback, complaint pattern, campaign content. You do not need to collect every possible field in the workspace. Use the information needed to make this decision and to verify its result.
06Inspect the current state first
Separate submission, delivery, reading and customer response. These events answer different questions and may arrive at different times. Read whether the current result is pending or final before taking action. A provider engagement restriction is not the same as a malformed number or a temporary service interruption. The appropriate next step depends on the stated reason, not just the red failed label.
If the intended result is already present, check whether any further action is necessary. This is particularly useful after an interrupted session or when another teammate may have completed part of the work.
07Step 1: Read the provider's explanation
Begin with the relevant inputs: provider feedback, complaint pattern, campaign content. Resolve any ambiguity that would change which record or business decision the task concerns. Keep a short note of the original state if you will need to compare it later. This creates a clear starting point for the next action instead of relying on memory after several screens have changed.
08Step 2: Review relevance and targeting
Use the result of the first action as the context for this one. Check the exact label, selected value or evidence involved rather than assuming that a default matches the intended task. If you identify an inconsistency, resolve it before proceeding. Keep the change narrow enough that its effect can be understood without comparing many unrelated edits.
09Step 3: Adjust future outreach before widening volume
Finish by checking the observable result, not only whether the interface accepted an interaction. If the result is still pending or cannot be verified, preserve that distinction in your notes. A clearly recorded unresolved state is more useful than announcing completion and discovering the missing part during a live customer task. Use the verification guidance below for the relevant feature.
10Worked example
A campaign with poor recipient relevance is reviewed before the next broadcast.
The useful lesson is the sequence of decisions, not a promised result for every business. In this scenario, begin with “Read the provider's explanation”, continue with “Review relevance and targeting”, and finish with “Adjust future outreach before widening volume”. Compare the result with the completion test before applying the same process to a wider set of records.
Use invented names and references when practising this example. Keep the structure realistic, but do not copy a live customer conversation or payment record into training material simply to make the demonstration look authentic.
11Verify the result
Compare the individual recipient result with the campaign summary after refreshing the same scope. Do not add overlapping funnel stages as though they were separate people. If a correction was made, test the specific corrected issue with an appropriate controlled recipient. Keep the outcome of that test separate from the original report so failures are not hidden by a later successful attempt.
The team does not treat every quality restriction as a technical outage.
12Decide what to do next
| What you observe | Appropriate next step | What to avoid |
|---|---|---|
| The expected result is visibly present. | Keep the result and continue with the intended business task. | Repeating a completed action without a reason. |
| The result is still pending or uncertain. | Review the current delivery investigation and the relevant status. | Calling the task complete without evidence. |
| The result conflicts with the intended choice. | Revisit: Review relevance and targeting. | Changing unrelated records to hide the symptom. |
Use the observed state to choose a branch. A recovery action should address the actual cause and preserve any work that is already correct. If several people are involved, make the next owner explicit so a pending state does not become an unattended task.
13The main mistake to avoid
Fixing a user-interface error cannot change a provider quality decision.
This mistake can make the task appear finished while leaving the business outcome unresolved. Return to the inputs and the named steps when the result is unclear. Keep a useful distinction between what you observed and what you expected. If a weaker signal is all that is available, describe the remaining uncertainty and identify how it can be checked.
14Diagnose an unexpected result
Compare the expected result with the exact current state of the delivery investigation. Record which of the three actions was last completed and what happened next. Keep the exact validation message or visible status where one exists. This separates an input problem from a saved-state problem and helps another person reproduce the same example.
Check the workspace, selected record and current view. Change one relevant factor at a time. If you change several unrelated settings together, a later success may not explain which change actually resolved the issue.
15Recover without duplicating work
Retry only when the failure reason supports retry and the recipient remains eligible. Check the saved message before repeating an uncertain send. For a provider-controlled restriction, use the indicated guidance or a suitable authorised alternative contact route rather than attempting repeated identical outreach. For a formatting issue, correct the verified record without guessing digits or changing unrelated contacts.
If the result depends on a provider or another authorised person, record that dependency and use the appropriate route. Do not simulate success by manually changing an unrelated display value or by removing evidence of the original outcome.
16Use the workflow on web and mobile
Mobile reports may show a compact summary before individual recipient details. Open the affected campaign or message to inspect the full reason. Match the report period and workspace when comparing it with desktop. A push notification is not the authoritative delivery report, and a missing notification does not establish that the underlying message or status event is absent.
When comparing devices, match the same account, record and relevant filters. A desktop screenshot and a mobile screen from different contexts are not evidence of inconsistent data. If a layout problem prevents completing the task, report the screen name, device context and the affected control with private details removed.
17Keep a useful operational record
Retain only the information needed to explain the task: its purpose, the relevant delivery investigation, the action taken and the observed result. If the operation produced a safe reference, keep it with the time and workspace context. This makes a later handover or support query more precise than a screenshot with no explanation.
| Record | Useful content |
|---|---|
| Purpose | Recognise when content or recipient feedback needs review. |
| Inputs reviewed | Provider feedback, complaint pattern, campaign content |
| Outcome to verify | The team does not treat every quality restriction as a technical outage. |
| Next owner | Campaign operator or support lead |
18Protect private information
Use the minimum customer or business information needed for the task. Restrict access to authorised colleagues, and redact unrelated names, numbers and message content when sharing a screenshot. An evidence reference is often more suitable than copying the underlying private document into a general field or support message.
For this workflow, the useful input categories are provider feedback, complaint pattern, campaign content. They should help you make and verify the decision; they are not a reason to publish a customer database, credentials or internal operating notes. The fictional example in this guide can be used for training without exposing live records.
19Know the limits of this workflow
Accepted, sent, delivered and read are not interchangeable. Alactic cannot override a provider's recipient-level delivery restriction.
Start with the individual outcome and the reported reason. Classify the failure before retrying so a transient issue is not confused with a policy or recipient decision.
Read the linked source material for decisions controlled by a provider or by the applicable commercial terms. A practical guide explains how to approach the task; it does not add a new contractual guarantee or establish that every business use is legally suitable. Use the responsible business owner for unresolved exceptions.
20Review the process over time
Group recurring failures by cause and assign corrective work accordingly. Data errors, content relevance, provider restrictions and reporting delays need different responses. Retain honest provisional and final results. A pilot gives evidence about the tested configuration and recipients; it should not be advertised as proof that every contact in a future larger campaign will receive the message.
Update related instructions when the underlying business fact or product behaviour changes. Keep a representative example from this workflow so a future revision can be compared with an explicit expectation rather than judged from memory.
21Practical questions
What should I check before starting?
Prepare provider feedback, complaint pattern, campaign content. Then confirm the workspace and the relevant delivery investigation. The first action is “Read the provider's explanation”. Starting there keeps later decisions grounded in the correct record and avoids trying to solve a different problem with this workflow.
How do I know the task is complete?
Use this observable test: The team does not treat every quality restriction as a technical outage. If a state is pending, describe it as pending. If a save or provider operation is uncertain, inspect the current record before repeating it. The result matters more than whether a button was pressed.
What if the result still does not match?
Review this risk first: Fixing a user-interface error cannot change a provider quality decision. Keep the exact symptom, the relevant reference and the last completed action. Ask the campaign operator or support lead or the appropriate support route to review the remaining issue, using a small reproducible example rather than a broad export of customer data.
22Completion checklist
Use this checklist as a final review of the task, not as a substitute for the steps above. If an item remains unresolved, identify the next action and its owner. Do not mark a provider-dependent or unverified result complete merely because the rest of the checklist is finished.
- The intended workspace and delivery investigation were identified.
- The necessary inputs were reviewed: provider feedback, complaint pattern, campaign content.
- Read the provider's explanation.
- Review relevance and targeting.
- Adjust future outreach before widening volume.
- The result was checked: The team does not treat every quality restriction as a technical outage.
- The task-specific risk was considered: Fixing a user-interface error cannot change a provider quality decision.
- Any unresolved issue has an accountable next owner and a useful evidence reference.