Skip to CRM content
121 CRM

121 CRM feature · Workflow goals

Prevent yesterday’s workflow from sending today’s wrong message.

Stop or redirect automation when its purpose has been achieved, circumstances change or a person takes over. The capability is described from official product evidence; its availability, configuration and any usage charges for a particular 121 account still need to be confirmed before reliance.

Subscribe to 121 CRMSeller, billing and cancellationExplore all CRM features

Fictional product demonstration

See workflow goals in the context of real customer work.

This coded interface uses realistic fictional data to explain the operating pattern; it is not a screenshot of a live customer account.

121

Northstar Joinery

Follow up consistently, with people in control

AR
OverviewContactsInboxPipelineAutomation

Follow up consistently, with people in control

Build the sequence, review each decision and test an exception before activation.

Draft v0.4

This example stays on this page and does not send messages or change CRM data.

Illustrative 121 interfaceAll people, organisations, dates and activity are fictional. Any figures are illustrative. Controls demonstrate interaction patterns, not enabled account features.

How it helps

See how the feature supports the work.

Each part has a clear job. It becomes useful when it fits the way customers already move through the business and your team knows when to step in.

Capability 01

Goals and exits

Moves or removes records when the configured outcome or stop condition has been met.

How it works
Runs an ordered sequence only after its configured trigger and conditions are met.
Why use it
Helps avoid continuing follow-up after the customer has already acted.
Plan for
Automation follows its configuration; it cannot repair poor data, unclear rules or an unavailable external service.
Your team owns
A process owner must approve, test, monitor and pause or correct faulty automation.
Capability 02

Waits and timing

Pauses a sequence until a duration, time, event or supported condition is reached.

How it works
Runs an ordered sequence only after its configured trigger and conditions are met.
Why use it
Keeps communication paced around the customer rather than firing every step at once.
Plan for
Automation follows its configuration; it cannot repair poor data, unclear rules or an unavailable external service.
Your team owns
A process owner must approve, test, monitor and pause or correct faulty automation.
Capability 03

Actions

Performs supported steps such as sending a message, updating a record, assigning work or calling a connected service.

How it works
Runs an ordered sequence only after its configured trigger and conditions are met.
Why use it
Coordinates routine execution across the customer journey.
Plan for
Automation follows its configuration; it cannot repair poor data, unclear rules or an unavailable external service.
Your team owns
A process owner must approve, test, monitor and pause or correct faulty automation.
Capability 04

Testing and execution logs

Supports test runs and operational evidence used to diagnose why a record did or did not follow a path.

How it works
Runs an ordered sequence only after its configured trigger and conditions are met.
Why use it
Gives a human a way to verify automation and investigate exceptions.
Plan for
Automation follows its configuration; it cannot repair poor data, unclear rules or an unavailable external service.
Your team owns
A process owner must approve, test, monitor and pause or correct faulty automation.

Use it with purpose

What good workflow goals looks like

A fictional appointment sequence stops reminders as soon as the booking is cancelled or the customer reschedules. The useful outcome is a record that another person can understand and continue, not simply another automated event.

Define success precisely

State the event or status that means the workflow has done its job.

Add stop conditions

Exit when consent changes, the record closes or a human exception is raised.

Review late events

Plan what happens when updates arrive after an action has already been queued.

Configuration decisions

Decide the operating rules before switching workflow goals on

A credible setup begins with ownership, eligibility and exception decisions. Those choices should be written in plain English and tested with realistic fictional data.

Choose observable goals

Use a reliable event such as confirmed booking rather than a vague assumption about interest.

Set cancellation behaviour

Decide whether pending waits and messages should end immediately.

Human review point

Test race conditions

Simulate goal completion just before and after scheduled actions.

From configuration to daily use

Keep the rule, the owner and the exception visible

The second view shows how the capability connects to work a person can review and continue.

121 CRM · Connected operations

Book discovery

October · illustrative availability

MTWTFSS1234567891011121314
11:3014:00

Appointment sequence

Booked

Calendar entry created

1 day before

Reminder scheduled

Exception

Owner reviews a reply

Journey summary

New

24

Illustrative

Owned

21

Illustrative

Due

4

Illustrative

Website
Referral
Direct
Illustrative exampleAll dates, counts and workflow states are fictional. Availability and behaviour depend on the agreed setup.

Practical example

Follow one example from signal to next action

A fictional appointment sequence stops reminders as soon as the booking is cancelled or the customer reschedules. The example shows the role of the CRM while keeping the consequential decision with a person.

Reminder active

A fictional booking has a message due tomorrow.

Customer reschedules

The appointment status and time change.

Human judgement

Goal detected

The old reminder sequence exits.

New path reviewed

The revised booking follows the appropriate confirmation process.

Boundaries and checks

Plan for the limits of workflow goals

Product capability is only one part of a dependable process. Data quality, provider configuration, consent, permissions and staff cover still matter.

Data and context

Goals depend on timely, accurate status updates.

Account and provider setup

Queued external actions may not always be retractable.

Keep a person accountable

Human responsibility

Several workflows acting on one record can create conflicting exits.

Questions about this page

Useful answers, without the sales fog.

1. Is workflow goals confirmed as included in every 121 CRM account?

No. The underlying capability is evidenced in official product documentation, but 121 plan entitlement, sub-account configuration, connected providers and usage charges have not been assumed. Confirm the intended setup before relying on it.

2. What should we decide before configuring workflow goals?

Start with three decisions: choose observable goals, set cancellation behaviour, test race conditions. Then test ordinary, missing-data and exception cases with fictional records.

3. What is a practical way to measure whether workflow goals is helping?

Measure whether the intended customer work becomes visible and owned. For this page, review define success precisely, add stop conditions, review late events rather than treating clicks, sends or record counts as proof of business value.

4. Can workflow goals be fully automated?

No. Several workflows acting on one record can create conflicting exits. Automation can coordinate repeatable steps, while people remain responsible for judgement, exceptions, consent and correcting the record.

Read all CRM questions

Continue the journey

Workflow branchesAutomationAppointment confirmationCustomer reactivation

Delegate the work. Keep the human.

Ready to organise the customer journey?

Subscribe through the approved secure checkout, or review pricing and responsibilities before you decide.

Subscribe to 121 CRMSeller, billing and cancellationCompare pricing

121 CRM

Your customers. Your conversations. Your business. Organised around clear ownership and human decisions.