121 CRM feature · Team inbox

Replace invisible private threads with clear ownership and context.

Bring supported channels into a shared view where conversations can be assigned, answered and followed through. 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

Team inbox in a working customer journey

Illustrative example

Message arrives
Thread assigned
Context checked
Action recorded

Message arrives
A fictional tenant reports a non-urgent repair.
Thread assigned
The duty coordinator accepts ownership.
Context checked
The contact and recent conversation history are visible.
Human decision
Action recorded
A contractor call task is set before the thread is resolved.

Illustrative workflow — names, organisations and activity are fictional.

Fictional product demonstration

See team inbox 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

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 02

Email conversations

Sends and receives supported email messages against the customer conversation and contact record.

How it works: Handles an eligible customer interaction through a configured inbox, number or connected channel.
Why use it: Keeps email context visible to authorised colleagues rather than one private mailbox.
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

SMS and MMS

Uses a configured phone provider and compliant number to send and receive supported text and media messages.

How it works: Handles an eligible customer interaction through a configured inbox, number or connected channel.
Why use it: Supports quick customer updates while preserving the thread in the CRM.
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

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 05

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.

Use it with purpose

What good team inbox looks like

A fictional property manager routes maintenance enquiries to the duty team while keeping the tenant, property context and response history visible. The useful outcome is a record that another person can understand and continue, not simply another automated event.

Centralise supported channels

Bring configured messages into one operational queue rather than expecting staff to monitor several personal inboxes.

Assign the conversation

Give each active thread an owner or team and make reassignment deliberate.

Resolve with a next step

Close only when the question is answered or another owned action exists.

Configuration decisions

Decide the operating rules before switching team inbox 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.

Define queues and coverage

Agree which channels enter the inbox, staffed hours and absence cover.

Set service categories

Use a small set of useful labels for routing and review.

Human review point

Protect access

Give people only the conversation visibility needed for their role.

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 property manager routes maintenance enquiries to the duty team while keeping the tenant, property context and response history visible. The example shows the role of the CRM while keeping the consequential decision with a person.

Message arrives

A fictional tenant reports a non-urgent repair.

Thread assigned

The duty coordinator accepts ownership.

Human judgement

Context checked

The contact and recent conversation history are visible.

Action recorded

A contractor call task is set before the thread is resolved.

Boundaries and checks

Plan for the limits of team inbox

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

Data and context

Not every external channel or historical message may synchronise.

Account and provider setup

A shared inbox still needs staffing, triage and escalation rules.

Keep a person accountable

Human responsibility

Sensitive information may require a restricted or specialist process.

Questions about this page

Useful answers, without the sales fog.

1. Is team inbox 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 team inbox?

Start with three decisions: define queues and coverage, set service categories, protect access. Then test ordinary, missing-data and exception cases with fictional records.

3. What is a practical way to measure whether team inbox is helping?

Measure whether the intended customer work becomes visible and owned. For this page, review centralise supported channels, assign the conversation, resolve with a next step rather than treating clicks, sends or record counts as proof of business value.

4. Can team inbox be fully automated?

No. Sensitive information may require a restricted or specialist process. Automation can coordinate repeatable steps, while people remain responsible for judgement, exceptions, consent and correcting the record.

Read all CRM questions

Continue the journey

Conversations Permissions and roles Human handover Call tracking

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