Skip to CRM content
121 CRM

121 CRM feature · Web chat

Help a visitor move from a quick question to a clear next step.

Turn useful website chats into visible conversations, contact records and owned follow-up. 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 web chat 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

Keep customer messages together

AR
OverviewContactsInboxPipelineAutomation

Keep customer messages together

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

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

Live chat

Provides a website chat channel that can create or continue a contact conversation.

How it works
Handles an eligible customer interaction through a configured inbox, number or connected channel.
Why use it
Turns a visitor question into a visible enquiry that the team can own and follow up.
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

Chat widget

Adds supported live-chat or connected-channel entry points to a website.

How it works
Publishes or collects information through a configured visitor-facing page, form or content experience.
Why use it
Lets a visitor ask a question without hunting for a separate contact route.
Plan for
Generated or templated content is not automatically accurate, accessible, compliant or ready to publish.
Your team owns
A person must review content, test the journey and explicitly publish or change live assets.
Capability 03

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 04

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 05

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.

Use it with purpose

What good web chat looks like

A fictional dental practice receives a non-clinical pricing question through web chat, answers it and offers an enquiry call without collecting clinical details. The useful outcome is a record that another person can understand and continue, not simply another automated event.

Set expectations immediately

Tell visitors when the chat is monitored and what information should not be shared.

Capture enough context

Ask only for details needed to answer or continue the conversation.

Continue without repetition

Keep the transcript with the contact so the next person can see what was already discussed.

Configuration decisions

Decide the operating rules before switching web chat 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 staffed hours

Decide what the widget says during staffed and unstaffed periods.

Define safe questions

Keep clinical, legal, payment and other sensitive decisions outside a general chat flow.

Human review point

Plan abandoned chats

Agree whether and how a partially identified visitor may be followed up.

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 dental practice receives a non-clinical pricing question through web chat, answers it and offers an enquiry call without collecting clinical details. The example shows the role of the CRM while keeping the consequential decision with a person.

Visitor asks

Nadia asks whether new-patient appointments are available.

Context captured

The chat records her preferred contact method.

Human judgement

Human answers

Reception explains the non-clinical booking options.

Next step owned

A call task is assigned for the requested time.

Boundaries and checks

Plan for the limits of web chat

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

Data and context

A widget does not guarantee an immediate human response.

Account and provider setup

Anonymous visitors may leave before enough information is captured.

Keep a person accountable

Human responsibility

Sensitive information should not be invited into a general-purpose chat.

Questions about this page

Useful answers, without the sales fog.

1. Is web chat 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 web chat?

Start with three decisions: choose staffed hours, define safe questions, plan abandoned chats. Then test ordinary, missing-data and exception cases with fictional records.

3. What is a practical way to measure whether web chat is helping?

Measure whether the intended customer work becomes visible and owned. For this page, review set expectations immediately, capture enough context, continue without repetition rather than treating clicks, sends or record counts as proof of business value.

4. Can web chat be fully automated?

No. Sensitive information should not be invited into a general-purpose chat. Automation can coordinate repeatable steps, while people remain responsible for judgement, exceptions, consent and correcting the record.

Read all CRM questions

Continue the journey

Forms and lead captureTeam inboxWeb-chat handlingMissed-call text back

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.