01What this guide helps you do
Use the footer for concise context that belongs on every message.
This guide focuses on one task within templates & approval. Its completion test is specific: The footer adds useful context without obscuring the message. 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 write a useful template footer. Keep the scope limited to the relevant message template. 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 workspace administrator or campaign editor. 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
Choose the customer's actual communication purpose before drafting the template. Decide the language, message body, required variables and any supported header or buttons. Use the inline naming guidance: a readable display-style title is not necessarily an acceptable provider identifier. Prepare realistic fictional examples for variables so the full message can be reviewed without exposing customer data.
Sender context, recipient choice, available space.
04Find the right workspace and feature
Start from Campaigns → Template Studio. 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 message template. 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 |
|---|---|---|
| Name | Provider template identifier | Follow inline accepted format |
| Category | Message purpose | Match the actual content |
| Variables | Values inserted into the message | Provide complete examples and fallbacks |
| Status | Current provider decision | Recheck before campaign use |
Apply these distinctions to the specific inputs for this guide: sender context, recipient choice, available space. 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 the template's category, language and current provider status together. A local draft, a submitted template and an approved template are different states. Check that numbered placeholders form a coherent message when filled. Header and attachment capabilities depend on the selected template and available editor controls; the existence of an underlying provider format does not mean every format is exposed in Alactic.
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.
08Step 2: Keep it short
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: Read it with the body and buttons
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 adds a clear opt-out instruction to a promotional message.
The useful lesson is the sequence of decisions, not a promised result for every business. In this scenario, begin with “Choose the essential footer information”, continue with “Keep it short”, and finish with “Read it with the body and buttons”. 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 the complete message with representative values, including a contact whose optional data is missing. Check the header, body, footer and buttons as one customer experience. After submission, inspect the recorded provider status and use refresh when the screen appears stale. Approval confirms a provider state, not the truth of every business claim or permission to contact every person in a database.
The footer adds useful context without obscuring the message.
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 message template and the relevant status. | Calling the task complete without evidence. |
| The result conflicts with the intended choice. | Revisit: Keep it short. | 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 footer should not carry critical transaction details that vary by recipient.
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 message template. 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
Use the specific validation or rejection explanation to revise the draft. A naming error needs a name correction; a missing variable example needs a complete example; a provider rejection needs a relevant content review. Do not create repeated copies solely to avoid understanding a failure. If a previously approved template becomes unavailable, review campaigns that depend on it before attempting further sends.
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
Template lists and editors on mobile should be checked for the same name, language and status as the web view. Scroll through all personalisation fields and inspect the fully rendered preview after closing the keyboard. Status updates report the provider's current decision; reopening the application cannot force an approval or replace the provider's review process.
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 message template, 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 | Use the footer for concise context that belongs on every message. |
| Inputs reviewed | Sender context, recipient choice, available space |
| Outcome to verify | The footer adds useful context without obscuring the message. |
| Next owner | Workspace administrator or campaign editor |
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 sender context, recipient choice, available space. 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
Alactic can prepare and submit supported templates; Meta controls their classification, approval and later availability. Approval does not guarantee delivery to every person.
Build around one clear message purpose. Supply realistic fictional examples for personalisation, choose the appropriate category and inspect the recipient preview.
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
Use names that identify purpose and language without becoming ambiguous after several revisions. Keep obsolete templates out of new campaign plans and review frequently used content when prices, policies or offers change. Maintain a small set of test values for each common template. This makes future edits easier to evaluate than repeatedly checking only one familiar test recipient.
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 sender context, recipient choice, available space. Then confirm the workspace and the relevant message template. The first action is “Choose the essential footer information”. 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 footer adds useful context without obscuring the message. 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 footer should not carry critical transaction details that vary by recipient. Keep the exact symptom, the relevant reference and the last completed action. Ask the workspace administrator or campaign editor 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 message template were identified.
- The necessary inputs were reviewed: sender context, recipient choice, available space.
- Choose the essential footer information.
- Keep it short.
- Read it with the body and buttons.
- The result was checked: The footer adds useful context without obscuring the message.
- The task-specific risk was considered: A footer should not carry critical transaction details that vary by recipient.
- Any unresolved issue has an accountable next owner and a useful evidence reference.