01What this guide helps you do
Distinguish configuration, testing and execution availability.
This guide focuses on one task within automations & workflows. Its completion test is specific: The team knows whether the rule is merely saved or actually running. 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 check whether a rule is live. Keep the scope limited to the relevant workflow. 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. 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
Write the intended behaviour as a trigger, condition and action before building it. Identify what should happen when the condition does not match and when a human is needed. Keep the first version narrow enough to test. Read the workspace's execution notice: some environments allow configuration and testing without live rule execution. A stored rule is not sufficient evidence that it will run for customers.
Rule state, workspace notice, live capability.
04Find the right workspace and feature
Start from Automations and Chatbot builder → Automation workflows. 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 workflow. 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 |
|---|---|---|
| Trigger | Event or phrase starting evaluation | Test matches and near misses |
| Condition | Scope of the intended task | Avoid unintended broad matches |
| Action | Reply, choice or handover | Check the actual next state |
| Execution state | Saved, tested or live capability | Read the workspace notice |
Apply these distinctions to the specific inputs for this guide: rule state, workspace notice, live capability. 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
Review all rules that could match the same message, not only the one being edited. Look for broad keywords, any-message triggers and repeated acknowledgements. Check the available action type and its destination. A button or list should describe a customer task clearly. A handover needs a real operational owner rather than only text promising that somebody will reply.
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 page's capability notice
Begin with the relevant inputs: rule state, workspace notice, live capability. 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: Inspect the saved rule state
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: Verify a controlled live event only when supported
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.
10A saved rule can exist without live execution
Read the notice on the automation page before interpreting a rule's saved badge or toggle. A workspace can allow rule configuration and testing while live execution is unavailable. That is a capability boundary, not proof that the customer's keyword was wrong.
Where live execution is supported, use a controlled event and available run history to verify the actual result. Where it is not, describe the rule as configured or tested and plan the supported workflow accordingly. Do not tell a client that a saved rule is responding to customers without evidence of execution.
| Check | Meaning for this task |
|---|---|
| Saved | Configuration exists |
| Tested | An example was evaluated |
| Live execution | The supported runtime actually handles events |
11Worked example
An administrator keeps a tested rule as configuration while live execution remains unavailable.
The useful lesson is the sequence of decisions, not a promised result for every business. In this scenario, begin with “Read the page's capability notice”, continue with “Inspect the saved rule state”, and finish with “Verify a controlled live event only when supported”. 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.
12Verify the result
Test a matching message, a near miss and a short multi-message conversation. Check both the response and the next state. Where execution history exists, compare the recorded run with the intended rule. A preview establishes only what happened in that test context. For live behaviour, verify the relevant capability and use an authorised controlled event before assuming the workflow is operational.
The team knows whether the rule is merely saved or actually running.
13Decide 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 workflow and the relevant status. | Calling the task complete without evidence. |
| The result conflicts with the intended choice. | Revisit: Inspect the saved rule state. | 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.
14The main mistake to avoid
The presence of a toggle does not override an execution-not-enabled notice.
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.
15Diagnose an unexpected result
Compare the expected result with the exact current state of the workflow. 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.
16Recover without duplicating work
If nothing happens, inspect trigger matching, saved state and execution availability before rewriting the response. If too much happens, review overlapping rules and repeated trigger conditions. Pause or narrow a problematic rule using the available controls, then retest. Keep a human route available while correcting the automation so customers are not trapped in a loop or a silent branch.
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.
17Use the workflow on web and mobile
Use short labels and concise responses that remain understandable on a phone. Check that buttons describe distinct choices and that list options lead to useful next steps. On the operator side, verify the complete rule after the keyboard closes. An hours schedule should be checked in its named time zone rather than inferred from the phone's current location or clock.
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.
18Keep a useful operational record
Retain only the information needed to explain the task: its purpose, the relevant workflow, 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 | Distinguish configuration, testing and execution availability. |
| Inputs reviewed | Rule state, workspace notice, live capability |
| Outcome to verify | The team knows whether the rule is merely saved or actually running. |
| Next owner | Workspace administrator |
19Protect 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 rule state, workspace notice, live capability. 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.
20Know the limits of this workflow
A saved rule, a tested rule and a published live workflow are separate states. Check the capability and execution status shown in your workspace.
Define a trigger, a narrow condition, an action and a safe handover. Test both the matching input and an input that should do nothing.
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.
21Review the process over time
Review fixed response text when products, locations, policies or hours change. Updating AI knowledge does not necessarily update a separate static automation reply. Give each important rule an owner and a small set of regression examples. Remove obsolete seasonal guidance and simplify overlapping rules. A smaller understandable workflow is easier to maintain than many rules whose combined behaviour nobody has checked.
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.
22Practical questions
What should I check before starting?
Prepare rule state, workspace notice, live capability. Then confirm the workspace and the relevant workflow. The first action is “Read the page's capability notice”. 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 knows whether the rule is merely saved or actually running. 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: The presence of a toggle does not override an execution-not-enabled notice. Keep the exact symptom, the relevant reference and the last completed action. Ask the workspace administrator or the appropriate support route to review the remaining issue, using a small reproducible example rather than a broad export of customer data.
23Completion 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 workflow were identified.
- The necessary inputs were reviewed: rule state, workspace notice, live capability.
- Read the page's capability notice.
- Inspect the saved rule state.
- Verify a controlled live event only when supported.
- The result was checked: The team knows whether the rule is merely saved or actually running.
- The task-specific risk was considered: The presence of a toggle does not override an execution-not-enabled notice.
- Any unresolved issue has an accountable next owner and a useful evidence reference.