121 CRM feature · Tasks and activities

Turn intentions into dated, reviewable actions.

Give customer work an owner, due date and visible context so follow-up does not live in memory. 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

Tasks and activities in a working customer journey

Illustrative example

Customer asks
Leila requests a call after 3pm.
Task created
Call Leila is due today and linked to the open opportunity.
Owner acts
Ben calls and records the outcome.
Human decision
Next step agreed
A document review is scheduled for Friday.

Illustrative workflow — names, organisations and activity are fictional.

Fictional product demonstration

Tasks and activities, shown as working software

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

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.

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

Tasks

Creates assigned, dated and optionally recurring actions against contacts or opportunities.

How it works: Tracks a potential deal, stage, owner or task using configured pipeline and record rules.
Why use it: Turns the next step into owned work instead of leaving it inside notes or inboxes.
Plan for: Pipeline position is only reliable when users and workflows update it consistently.
Your team owns: A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status.

Capability 02

Contacts

Stores a person or lead with contact details, activity, ownership and related records.

How it works: Stores or organises supported business data under configured fields, permissions and record rules.
Why use it: Gives a team one place to understand who a customer is and what has happened.
Plan for: The platform does not make imported, duplicated or incomplete data accurate without review.
Your team owns: A data owner must define the record model and resolve quality, ownership and access exceptions.

Capability 03

Opportunities

Represents a potential sale or deal linked to a contact, value, owner and pipeline position.

How it works: Tracks a potential deal, stage, owner or task using configured pipeline and record rules.
Why use it: Shows which customer conversations are active commercial work rather than general contacts.
Plan for: Pipeline position is only reliable when users and workflows update it consistently.
Your team owns: A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status.

Capability 04

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.

Use it with purpose

What good tasks and activities looks like

A fictional accountancy practice records a call-back against the contact and opportunity, rather than leaving a reminder in a private notebook. The useful outcome is a record that another person can understand and continue, not simply another automated event.

Create work in context

Add the task to the relevant customer or opportunity so another person can understand why it exists.

Make ownership explicit

Use one accountable owner and a realistic due date instead of a vague team reminder.

Close the loop

Complete, reschedule or explain the task so overdue lists stay meaningful.

Configuration decisions

Decide the operating rules before switching tasks and activities 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 task types

Use a short, useful set such as call, review and information request rather than dozens of labels.

Agree overdue handling

Decide when an overdue task is reassigned, escalated or deliberately rescheduled.

Human review point

Protect focus

Only create automated tasks when somebody is genuinely expected to act on them.

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 · Workflow sequence

Enquiry received

Capture source and customer

Acknowledgement

Set a clear response expectation

Human review

Check fit, consent and exceptions

Owner assigned

Name the person responsible

Follow-up due

Remind the owner, not the customer blindly

Illustrative exampleA conceptual workflow. Triggers, messages, delays and exceptions need configuration and testing.

Practical example

Follow one example from signal to next action

A fictional accountancy practice records a call-back against the contact and opportunity, rather than leaving a reminder in a private notebook. The example shows the role of the CRM while keeping the consequential decision with a person.

Customer asks

Leila requests a call after 3pm.

Task created

Call Leila is due today and linked to the open opportunity.

Human judgement

Owner acts

Ben calls and records the outcome.

Next step agreed

A document review is scheduled for Friday.

Boundaries and checks

Plan for the limits of tasks and activities

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

Data and context

Tasks do not complete work or judge its quality.

Account and provider setup

Too many automatic tasks can hide the important ones.

Keep a person accountable

Human responsibility

Private calendar items and CRM activities need an agreed boundary.

Questions about this page

Useful answers, without the sales fog.

1. Is tasks and activities 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 tasks and activities?

Start with three decisions: choose task types, agree overdue handling, protect focus. Then test ordinary, missing-data and exception cases with fictional records.

3. What is a practical way to measure whether tasks and activities is helping?

Measure whether the intended customer work becomes visible and owned. For this page, review create work in context, make ownership explicit, close the loop rather than treating clicks, sends or record counts as proof of business value.

4. Can tasks and activities be fully automated?

No. Private calendar items and CRM activities need an agreed boundary. Automation can coordinate repeatable steps, while people remain responsible for judgement, exceptions, consent and correcting the record.

Read all CRM questions

Continue the journey

Customer management Opportunity management Weekly CRM review Email marketing

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