01What this guide helps you do
Make scale a sequence of reviewed operational decisions.
This guide focuses on one task within campaigns & broadcasts. Its completion test is specific: The team is prepared for both delivery exceptions and incoming replies. 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 prepare a large audience responsibly. Keep the scope limited to the relevant campaign draft. 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 owner. 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
Define one campaign objective and select the intended audience. Confirm that the template is available, relevant to the purpose and in the correct language. Prepare every variable value and fallback before review. If the campaign uses a header attachment, confirm that the chosen template supports it. Make the person responsible for replies available around the planned send time.
Audience quality, capacity, staffing, message purpose.
04Find the right workspace and feature
Start from Campaigns → Create campaign. 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 campaign draft. 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 |
|---|---|---|
| Audience | Matching and eligible contacts | Review both counts |
| Template | Approved message and language | Check current availability |
| Personalisation | Sources, fixed values and fallbacks | Preview varied records |
| Delivery choice | Confirmation or schedule | Verify time zone and final state |
Apply these distinctions to the specific inputs for this guide: audience quality, capacity, staffing, message purpose. 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
Read audience matching and eligibility separately. Then inspect each placeholder's mode: a contact field needs a source and fallback, while a fixed-value mode still needs text. Review the displayed time zone if scheduling. The campaign draft, saved campaign and confirmed send are separate stages; a successful save should not be interpreted as evidence that recipients have received the message.
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: Validate the audience and message
Begin with the relevant inputs: audience quality, capacity, staffing, message purpose. 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: Check visible allowances and readiness
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: Plan response handling before sending
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 business confirms reply ownership before contacting several thousand eligible customers.
The useful lesson is the sequence of decisions, not a promised result for every business. In this scenario, begin with “Validate the audience and message”, continue with “Check visible allowances and readiness”, and finish with “Plan response handling before sending”. 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
Preview more than one representative recipient, including a record with missing optional information. Read the complete message rather than each field in isolation. At final review, compare audience, template, variables, attachment and schedule with the original objective. After a real authorised send, use the campaign's recipient results to evaluate delivery instead of treating the confirmation button as a delivery guarantee.
The team is prepared for both delivery exceptions and incoming replies.
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 campaign draft and the relevant status. | Calling the task complete without evidence. |
| The result conflicts with the intended choice. | Revisit: Check visible allowances and readiness. | 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
A large imported list is not itself a ready-to-send audience.
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 campaign draft. 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
For a validation error, remain on the relevant step and correct the named field. For an uncertain save or send, reopen the existing campaign before repeating the operation. For partial delivery, classify recipient failures before planning a retry. A recovery audience should exclude people already reached and anyone no longer eligible. Broad resending can create duplicates without fixing the original cause.
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
On a phone, scroll through the whole message step before continuing; the keyboard can hide required values or fallbacks. Use the final review screen as a deliberate checkpoint after closing the keyboard. If connectivity changes after a confirmation, inspect the campaign's saved state on either device before pressing send again. The same campaign reference is more reliable than matching only its display name.
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 campaign draft, 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 | Make scale a sequence of reviewed operational decisions. |
| Inputs reviewed | Audience quality, capacity, staffing, message purpose |
| Outcome to verify | The team is prepared for both delivery exceptions and incoming replies. |
| Next owner | Campaign owner |
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 audience quality, capacity, staffing, message purpose. 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
Saving a campaign is not the same as successfully sending it. Recipient eligibility, template availability and provider delivery decisions remain separate checks.
Move through audience, message and review with one coherent business purpose. Confirm the recipient sample and schedule before authorising a real send.
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
Keep a short record of what the campaign was intended to achieve, its delivery outcome and the improvement needed next time. Review template availability and current permission before reusing an old audience. Compare results using consistent definitions. A useful campaign process improves relevance, data quality and reply handling; simply increasing message volume does not establish a better customer outcome.
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 audience quality, capacity, staffing, message purpose. Then confirm the workspace and the relevant campaign draft. The first action is “Validate the audience and message”. 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 is prepared for both delivery exceptions and incoming replies. 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: A large imported list is not itself a ready-to-send audience. Keep the exact symptom, the relevant reference and the last completed action. Ask the campaign owner 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 campaign draft were identified.
- The necessary inputs were reviewed: audience quality, capacity, staffing, message purpose.
- Validate the audience and message.
- Check visible allowances and readiness.
- Plan response handling before sending.
- The result was checked: The team is prepared for both delivery exceptions and incoming replies.
- The task-specific risk was considered: A large imported list is not itself a ready-to-send audience.
- Any unresolved issue has an accountable next owner and a useful evidence reference.