121 CRM feature · WhatsApp messaging

Let customers use a familiar channel without turning it into an unowned private thread.

Keep approved WhatsApp conversations visible to the team while respecting templates, consent and provider rules. 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

WhatsApp messaging in a working customer journey

Illustrative example

Message arrives
Thread identified
Team responds
Booking recorded

Message arrives
Owen asks whether Saturday surveys are available.
Thread identified
The message is linked to Owen’s contact record.
Team responds
Priya confirms the service area and offers two slots.
Human decision
Booking recorded
The agreed visit appears with the conversation context.

Illustrative workflow — names, organisations and activity are fictional.

Fictional product demonstration

See whatsApp messaging 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

Keep customer messages together

OverviewContactsInboxPipelineAutomation

Keep customer messages together

See the message, customer context and responsible owner in the same working view.

Search inbox

Bramble Studio

Jamie Clarke · Email

Contact confirmed

Could Thursday morning work for a short discovery call?

09:54

Yes — 11:30 is available. I can send the appointment details once the scope is confirmed.

10:02

Thursday morning would work well. Thank you.

10:24

Write a reply…

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

Connects an approved WhatsApp setup to supported inbox and automation experiences.

How it works: Handles an eligible customer interaction through a configured inbox, number or connected channel.
Why use it: Lets a business handle an opted-in messaging channel alongside other customer contact.
Plan for: Delivery, message types, geographic coverage, approval and charges vary by channel and provider.
Your team owns: A person must own sensitive conversations, failed delivery and any situation outside the approved script.

Capability 02

Conversations inbox

Brings supported connected message threads into a shared operational inbox.

How it works: Handles an eligible customer interaction through a configured inbox, number or connected channel.
Why use it: Helps a team see the customer history and coordinate replies from one working view.
Plan for: Delivery, message types, geographic coverage, approval and charges vary by channel and provider.
Your team owns: A person must own sensitive conversations, failed delivery and any situation outside the approved script.

Capability 03

Templates and snippets

Stores reusable message content for supported channels while allowing a user to review the final reply.

How it works: Handles an eligible customer interaction through a configured inbox, number or connected channel.
Why use it: Speeds up common responses without removing the need to check tone and context.
Plan for: Delivery, message types, geographic coverage, approval and charges vary by channel and provider.
Your team owns: A person must own sensitive conversations, failed delivery and any situation outside the approved script.

Capability 04

Messaging and calling compliance

Requires number verification, applicable registrations, consent, sender identity and opt-out handling for each channel and region.

How it works: Handles an eligible customer interaction through a configured inbox, number or connected channel.
Why use it: Makes channel setup a governed operational task rather than just a technical connection.
Plan for: Delivery, message types, geographic coverage, approval and charges vary by channel and provider.
Your team owns: A person must own sensitive conversations, failed delivery and any situation outside the approved script.

Use it with purpose

What good whatsapp messaging looks like

A fictional removals firm answers a WhatsApp availability question in the shared inbox and records the agreed survey appointment. The useful outcome is a record that another person can understand and continue, not simply another automated event.

Connect the approved channel

Use a properly configured business connection rather than a staff member’s personal account.

Keep context together

Associate the conversation with the customer record and current piece of work.

Hand off clearly

Assign the thread when a question needs pricing, judgement or another team.

Configuration decisions

Decide the operating rules before switching whatsapp messaging 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.

Confirm connection requirements

Check the number, business verification, templates and provider terms for the intended use.

Define response ownership

Agree who watches the channel and how absence or high volume is covered.

Human review point

Set content boundaries

Keep sensitive documents and complex decisions in an appropriate, approved process.

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 removals firm answers a WhatsApp availability question in the shared inbox and records the agreed survey appointment. The example shows the role of the CRM while keeping the consequential decision with a person.

Message arrives

Owen asks whether Saturday surveys are available.

Thread identified

The message is linked to Owen’s contact record.

Human judgement

Team responds

Priya confirms the service area and offers two slots.

Booking recorded

The agreed visit appears with the conversation context.

Boundaries and checks

Plan for the limits of whatsapp messaging

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

Data and context

Template and session rules can affect what may be sent and when.

Account and provider setup

Availability and messaging costs depend on the configured provider and account.

Keep a person accountable

Human responsibility

A familiar channel does not remove privacy, consent or record-keeping responsibilities.

Questions about this page

Useful answers, without the sales fog.

1. Is whatsapp messaging 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 whatsapp messaging?

Start with three decisions: confirm connection requirements, define response ownership, set content boundaries. Then test ordinary, missing-data and exception cases with fictional records.

3. What is a practical way to measure whether whatsapp messaging is helping?

Measure whether the intended customer work becomes visible and owned. For this page, review connect the approved channel, keep context together, hand off clearly rather than treating clicks, sends or record counts as proof of business value.

4. Can whatsapp messaging be fully automated?

No. A familiar channel does not remove privacy, consent or record-keeping responsibilities. Automation can coordinate repeatable steps, while people remain responsible for judgement, exceptions, consent and correcting the record.

Read all CRM questions

Continue the journey

Team inbox Customer management Multi-channel follow-up Web chat

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