Skip to CRM content
121 CRM

Feature · Workflow automation

Move routine work forward without automating the judgement.

A CRM workflow can acknowledge, assign, remind and create tasks where configured. The useful design also names the stopping points, exceptions and people who remain responsible.

Subscribe to 121 CRMSeller, billing and cancellationRead the follow-up guide

Workflow builder

Put routine movement around a visible decision point.

The sequence makes triggers, actions, human review, ownership and reminders understandable before a workflow is enabled.

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

Workflow builder

Combines a start event with an ordered sequence of configurable actions.

How it works
Runs an ordered sequence only after its configured trigger and conditions are met.
Why use it
Turns a repeatable customer process into a visible, reviewable flow.
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

Triggers

Starts a workflow after configured contact, event, appointment, opportunity, course or other supported activity.

How it works
Runs an ordered sequence only after its configured trigger and conditions are met.
Why use it
Lets follow-up begin from a business event instead of waiting for someone to remember.
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

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 05

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 06

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.

Workflow anatomy

A trigger needs conditions, actions and an exit.

Visual builders, triggers, branches and wait steps are useful design ingredients, not proof that every action is enabled in a particular account.

Trigger and entry rules

Define the event, required data, duplicate behaviour and whether an existing customer may enter the workflow again.

Routine actions

Where supported, a workflow may record an acknowledgement, assign an owner, create a task or move a stage.

Wait, branch and exit

Set business-hour rules, stop conditions and a clear route when a reply, opt-out or exception changes the expected path.

Human oversight

Make the hand-off as deliberate as the automation.

A workflow should not keep running merely because its next step exists.

Human decision

Qualification

People decide fit, priority, capacity and any acceptance or risk question.

Sensitive or unusual replies

Ambiguous, upset, vulnerable or sensitive messages route to an appropriately responsible person.

Failure work

Rejected delivery, missing data and broken connections create visible work with an owner and next action.

Test record

Keep the version, owner and proof together.

A workflow should be accepted against representative cases and changed through a recorded control.

121 CRM · Control responsibilities
Control questionOwnerNext check
Who can export customer data?CustomerConfirm
Who changes workflow permissions?Agreed scopeRecord
What happens at account closure?SharedDefine
Which suppliers process data?SharedCheck
Illustrative exampleIllustrative governance pattern. It does not assert that a specific technical control or certification is in place.

Test before trust

Prove the sequence with ordinary and awkward cases.

A successful happy path does not establish that the workflow is ready for live customer communication.

Message and permission review

Approve content, identity, consent, opt-out and timing for every enabled communication channel.

Confirm cost

Usage and plan review

Some actions or connected services may carry separate execution or usage charges.

Change control

Record an owner, tested version, acceptance evidence and rollback decision for material workflow changes.

Questions about this page

Useful answers, without the sales fog.

1. Can 121 CRM follow up automatically?

Routine follow-up may be configured where the necessary trigger, channel, permissions and plan capability are available. Exact actions and charges are not assumed from the subscription checkout.

2. Will automated messages sound impersonal?

That depends on the message design, timing, context and escalation. Use automation for clear routine steps and keep relationship judgement with people.

3. How do we stop a workflow sending the wrong message?

Define entry and exit rules, opt-outs, reply handling, exception routes, test cases and a named owner who can pause the workflow.

Read all CRM questions

Continue the journey

Follow-up automation guideForms and lead captureCustomer conversations

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.