121 CRM feature · Workflow branches

Let the workflow adapt without becoming an unreadable maze.

Create understandable routes for meaningful differences, with a safe fallback for records that do not fit. 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 CRM Seller, billing and cancellationExplore all CRM features

Customer Thread

Workflow branches in a working customer journey

Illustrative example

Response arrives
Outcome read
Branch chosen
Fallback reviewed

Response arrives
A fictional customer answers the estimate email.
Outcome read
The recorded status is accepted, declined or unanswered.
Branch chosen
Each known outcome receives a suitable next step.
Human decision
Fallback reviewed
Unexpected data creates a task for a person.

Illustrative workflow — names, organisations and activity are fictional.

Fictional product demonstration

See workflow branches 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

Fictional

Follow up consistently, with people in control

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

Conditions and branches

Routes a record through different configured steps when relevant data or events differ.

How it works: Runs an ordered sequence only after its configured trigger and conditions are met.
Why use it: Lets one process handle common variations without pretending every customer is the same.
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

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 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 branches looks like

A fictional quote workflow separates accepted, declined and unanswered outcomes, while unexpected statuses go to a review queue. The useful outcome is a record that another person can understand and continue, not simply another automated event.

Branch on a real decision

Split only where the next action genuinely differs.

Keep paths named clearly

Use labels a service owner can understand without opening every technical condition.

Include an else path

Treat unmatched data as an exception rather than silently dropping the record.

Configuration decisions

Decide the operating rules before switching workflow branches 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.

Limit branch depth

Prefer a few clear paths or smaller connected workflows over deeply nested logic.

Check mutual exclusivity

Test whether a record can match several branches and which one should win.

Human review point

Assign branch ownership

Name who reviews each path and who maintains the logic.

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

Illustrative

Owned

Illustrative

Due

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 quote workflow separates accepted, declined and unanswered outcomes, while unexpected statuses go to a review queue. The example shows the role of the CRM while keeping the consequential decision with a person.

Response arrives

A fictional customer answers the estimate email.

Outcome read

The recorded status is accepted, declined or unanswered.

Human judgement

Branch chosen

Each known outcome receives a suitable next step.

Fallback reviewed

Unexpected data creates a task for a person.

Boundaries and checks

Plan for the limits of workflow branches

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

Data and context

Branching cannot repair ambiguous fields or contradictory statuses.

Account and provider setup

Complexity increases testing and change risk.

Keep a person accountable

Human responsibility

Goals, waits and concurrent updates may cause records to leave a path unexpectedly.

Questions about this page

Useful answers, without the sales fog.

1. Is workflow branches 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 branches?

Start with three decisions: limit branch depth, check mutual exclusivity, assign branch ownership. Then test ordinary, missing-data and exception cases with fictional records.

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

Measure whether the intended customer work becomes visible and owned. For this page, review branch on a real decision, keep paths named clearly, include an else path rather than treating clicks, sends or record counts as proof of business value.

4. Can workflow branches be fully automated?

No. Goals, waits and concurrent updates may cause records to leave a path unexpectedly. 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 conditions Workflow goals Workflow exception handling

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 CRM Seller, billing and cancellationCompare pricing