A small business can automate useful work while keeping important decisions with its staff. For a Zanus AI CRM evaluation, separate actions that follow fixed rules from changes needing someone’s approval. The demonstration should show both the proposed change and the authority required to carry it out.

Classify the actions before enabling them

Writing a call note, proposing a task and changing a customer’s commercial terms have different consequences. List the actions your workflow might take and ask the business owner which can run automatically. Specify who may approve exceptions and what context they need.

Do not use a broad instruction such as “handle the customer” as an approval policy. Write explicit boundaries for discounts, refunds, record merges and changes to important customer details, even if those actions are outside the initial pilot.

Make approval a complete decision

Approval itemInformation to display
Proposed actionThe exact record and fields to change
ReasonThe source customer request and relevant context
ApproverA named role with suitable authority
ExpiryWhen changed circumstances require review again

Ask whether editing an approved proposal invalidates that approval. An approval for one change should not silently authorise a materially different one.

Test an approval that arrives too late

Create a proposal in a test account, then change the underlying record before approving it. For example, have staff resolve the customer request manually. Check whether the old proposal is still executable and whether the reviewer sees the updated context.

Also test a rejected request, an absent approver and two staff members responding at the same time. The system needs a clear final state and should not perform the action twice or leave staff uncertain about who decided.

Review completion after the click

An approved request is not necessarily a completed change. Inspect the destination record and the audit trail after execution. If the write fails, keep it linked to the original approval and route it for repair rather than treating approval as success.

Track proposals approved, rejected, expired and successfully executed, with manual repair time. Start with a narrow action set whose effects the business understands. Expand authority only when the approval and recovery paths remain clear under ordinary exceptions.

Questions and answers

Does approving a proposal prove the change was completed?

No. Verify the executed result in the destination record and keep failures visible with an assigned repair owner.

Mapping the Risk Spectrum Before You Configure Anything

Before a business enables any CRM automation that can alter customer records, it is worth constructing a simple internal map that places every candidate action on a spectrum from fully safe to fully restricted. This exercise is not a software configuration task; it is a conversation among the people who bear responsibility for customer relationships, financial exposure and data accuracy. The output of that conversation should be a written list that the team can reference throughout any evaluation or pilot.

Consider sorting actions into three working bands. The first band covers read-only or additive steps: logging that a call occurred, appending a note drafted for staff review, or creating a follow-up task that a person still has to confirm. These actions add information without removing or overwriting anything, so a missed step or duplicate entry is recoverable with little friction. The second band covers updates to existing records where a mistake is correctable but requires effort: changing a contact's preferred communication channel, updating a delivery address, or reassigning an account to a different staff member. These warrant a defined owner and a clear correction path. The third band covers changes with direct commercial or legal consequence: applying a discount, issuing a credit, merging two customer records, or modifying agreed contract terms. A single error in this band can affect revenue recognition, downstream reporting or a customer's contractual standing, and recovery may require co-ordination across several staff members.

The reason to draw these distinctions explicitly, rather than relying on intuition during setup, is that automation moves quickly and silently. When a human performs a risky action, the process of doing it creates friction that prompts a second thought. When a system performs it, the only equivalent friction is a well-designed approval requirement. Businesses that skip the classification step often discover their risk bands only after an exception occurs.

Designing the Approval Record as an Auditable Document

An approval is only meaningful if the person granting it has enough context to make an informed decision and if the record of that approval survives in a form others can inspect later. Treating an approval as a simple yes or no click understates what a sound approval process requires.

A useful approval record should carry at minimum the following elements: the precise action proposed and the exact fields or values it would affect; the source of the request, meaning which customer interaction or internal trigger generated the proposal; the identity of the individual making the request and the role of the approver being asked to authorise it; a timestamp of when the proposal was created; and a defined window after which changed circumstances should prompt a fresh review rather than allowing the original approval to be applied. Businesses should also decide in advance whether an approver may modify a proposal before authorising it, and if so, whether the modified version requires a separate approval chain.

This last point deserves deliberate attention. Suppose a customer service representative raises a proposal to credit a customer's account for a specific amount following a delayed shipment. A supervisor reviews the proposal and judges that a smaller credit is more appropriate given additional context. If the supervisor edits the amount and approves in a single step, the resulting record may show an approval for a figure that no one originally proposed. Whether that matters depends on the business's internal governance expectations, but the question should be answered before the first live approval is processed, not after an auditor or a senior manager asks why a record shows a different figure than the original request.

A Fictional Worked Scenario: A Commercial Terms Request

The following is an illustrative scenario constructed to make the evaluation criteria concrete. It does not describe a real customer, a real business or confirmed software behaviour.

A customer contacts a small wholesale supplier asking whether their standard payment terms can be extended for a forthcoming large order. A customer-facing staff member receives the request and, following the supplier's process, initiates a proposal through the CRM automation to update the customer's payment terms field from the current setting to the requested extended period. The automation does not apply the change. Instead, it creates a pending approval record and routes it to the accounts manager, who holds the authority to modify commercial terms.

The accounts manager receives a notification and opens the approval record. They can see the customer's name and account identifier, the specific field to be changed and the proposed new value, the original customer message that prompted the request, the staff member who raised the proposal, and the date by which the customer expects a response. The accounts manager checks the customer's payment history in the CRM, which is visible alongside the proposal, and decides the extension is appropriate. They authorise the change.

At this point, a critical distinction applies. The authorisation is a decision, not yet a completed action. The execution step updates the payment terms field in the customer record. The accounts manager or an automated confirmation step should verify that the field now holds the correct value. If the write fails for any reason, the proposal record should remain linked to the failed execution attempt and route to a named repair owner rather than disappearing or appearing as approved when the record was never actually changed.

The customer service representative who raised the original request should receive a notification of the outcome, both so they can communicate it to the customer and so they understand the full cycle of a proposal they initiated. The customer, as the party whose terms are changing, may also warrant a confirmation communication, which is a separate step from the internal approval record.

Separating Customer Identity from Individual Requests

CRM records combine two distinct types of information that can be easy to conflate when designing automations: the identity record of a customer as an ongoing account, and the individual interaction or request that the customer made on a particular occasion. Approval processes should be designed with this distinction in mind.

Consider a business that receives a request to update a customer's billing address. The address update is a change to the identity record. The request itself is a discrete interaction. An approval to update the address should specify exactly which address field is being changed and to what value. It should not function as a general authorisation to modify other aspects of the customer's identity record. If a second request arrives shortly afterwards asking to update the same customer's primary contact name, that should generate a separate proposal, not fall within the scope of the address approval.

This matters because CRM records accumulate history and other records reference them. An address field on a customer record may feed into invoicing, logistics and correspondence. An automation that conflates a single customer interaction with permission to alter any part of the underlying identity record creates risk that is disproportionate to the action the customer actually requested. When evaluating any CRM automation tool, ask how granularly the approval can be scoped, and whether the system presents the specific field-level change rather than a general description such as "update customer details."

Testing Concurrent Approvals and Absent Approvers

Approval processes that work smoothly when a single approver is present and available reveal their gaps under ordinary operational conditions. Businesses should design, and then test, how the process behaves in at least the following situations before going live.

First, consider what happens when the designated approver is unavailable. A deputy arrangement requires more than a name; it requires that the deputy can access the same context the primary approver would have seen, and that the record shows clearly which individual ultimately authorised the change. If the business relies on a role rather than a named individual in the approval configuration, the audit trail should still resolve to a specific person at the point of decision.

Second, test concurrent responses. If two members of staff both have authority to approve a given class of proposal and both act on the same proposal within seconds of each other, the system should apply the action once and record one approval, not two. It should also prevent a scenario where the first response triggers execution and the second response finds nothing to act on but still records an apparent authorisation. Any evaluation of an approval-capable system should include a deliberate concurrent-response test with observable results.

Third, test rejection followed by a similar but distinct request. If an approver rejects a proposal, and shortly afterwards a staff member raises a new proposal for a similar but not identical change, the two records should be independent. The rejection of the first should not automatically influence the outcome of the second, nor should the second be treated as an attempt to circumvent the first rejection without a clear escalation mechanism. The practical question for an evaluating business is whether the system surfaces the history of related proposals to the approver of the second request, so they can make an informed decision rather than reviewing the new proposal in isolation.

Acceptance Criteria a Business Team Can Observe

Acceptance testing for an approval workflow does not require technical expertise, but it does require a prepared set of observable conditions that the team agrees on before the test begins. The following criteria are offered as a starting framework for a business evaluation exercise, not as a claim about any specific system's behaviour.

For each test scenario, the team should be able to observe and confirm: that the proposal record contains the exact field name and proposed value before any approval is given; that the approver's identity, role and decision timestamp appear in the audit trail after approval; that the customer record reflects the change after execution and that the audit trail links the change to the specific approval record; that a proposal which expires or becomes stale due to a change in underlying circumstances does not execute when eventually actioned; and that a failed execution remains visible, linked and assigned rather than dropping out of view.

These are observable states rather than claimed features. A team conducting an evaluation can check each one by inspecting records directly after each test step. If a particular state is not observable, that is information the business needs before deciding whether to extend automation authority in that area. The inability to observe the audit trail after an approval, for instance, should prompt a conversation with the vendor about how that traceability is provided, not an assumption that it exists.

Handover Arrangements When Staff or Roles Change

Approval workflows are configured against roles, named individuals or both, and organisations change over time. A practical evaluation should include a question about what happens to pending proposals when the designated approver leaves the business, moves to a different role, or is on extended leave during a period when time-sensitive proposals accumulate.

In well-constructed processes, the handover arrangement is documented before the person departs rather than discovered in their absence. This means the business should be able to answer: who holds authority to re-route pending proposals if the configured approver becomes unavailable; how proposals are surfaced to a successor rather than remaining invisible in an inactive account; and whether the audit trail correctly attributes the substitute approval to the person who actually made the decision, rather than inheriting the departed approver's identity.

These questions are administrative and process-design questions, not solely software questions. Even a system that handles re-routing correctly depends on the business maintaining accurate role assignments and reviewing them when personnel change. The evaluation of a CRM automation tool should include a review of how the business itself will maintain the configuration, not only how the software behaves when it is correctly maintained.

Narrowing the Initial Pilot to Preserve Clarity

A common failure mode when introducing approval-gated automations is to begin with an action set that is broad enough to cover many real scenarios but too wide for the team to track exceptions clearly during the early period. When staff encounter an unusual case and are uncertain whether the automation handled it correctly, they need to be able to investigate quickly. That investigation becomes harder when many different action types are in flight simultaneously.

A more reliable approach is to begin with a single action type that the business understands thoroughly, run it long enough to encounter at least one exception in each of the main exception categories, and build the team's confidence in the recovery process before expanding the scope. The exception categories worth planning for include a proposal that arrives after the situation it was meant to address has already been resolved manually, a proposal that is approved but fails to execute, and a proposal where the approver has a legitimate reason to want more information before deciding. Knowing how the team handles each of these in a low-stakes context prepares them for the same situations when higher-risk action types are added later.

Businesses that can describe in plain language what their approval records contain, who is responsible for each stage of the process, and what the repair path looks like when something goes wrong are in a much stronger position to extend automation authority thoughtfully. The goal is not to automate as much as possible as quickly as possible, but to build a process the team trusts well enough to act on confidently, question appropriately when something looks wrong, and hand over to a colleague without losing continuity.

Sources and next steps

This independent Sysevo guide proposes evaluation steps, not hands-on Zanus AI results. Check the official Zanus AI Front Office overview and ask the vendor to demonstrate your exact workflow and confirm its current availability.

For related context, read Zanus AI CRM integration and lead handoff. To compare providers using the same requirements, explore Sysevo CRM or book a Sysevo demo. Sysevo publishes this guide and sells its own business software.

Related workflow guides

For current Sysevo subscriptions and usage options, compare plans and pricing.