121 CRM feature · Round-robin booking

Give customers suitable availability while keeping workload and exceptions visible.

Share eligible appointments fairly across available team members using rules the business understands and reviews. 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

Round-robin booking in a working customer journey

Illustrative example

Call requested
Hosts checked
Owner assigned
Exception reviewed

Call requested
Theo chooses an introductory call.
Hosts checked
Only trained, available advisers are eligible.
Owner assigned
The configured rotation selects Asha.
Human decision
Exception reviewed
A specialist question is reassigned by a person.

Illustrative workflow — names, organisations and activity are fictional.

Fictional product demonstration

See round-robin booking 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

Make appointments easier to organise

OverviewContactsCalendarAppointmentsAutomation

Make appointments easier to organise

Coordinate availability, appointment status and the follow-up owner.

Mon

10:00

Discovery call

Rowan & Co

Tue

09:30

Site survey

Oakfield Homes

15:00

Drawing review

Marlow Works

Wed

Thu

11:30

Discovery call

Bramble Studio

Fri

13:00

Installation check

Field & Form

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

Round-robin calendars

Distributes eligible bookings across a configured group of users according to availability and assignment rules.

How it works: Applies configured availability, booking rules and connected-calendar settings to eligible appointments.
Why use it: Shares new appointments across a team without requiring a customer to choose a person.
Plan for: Sync, meeting-link and resource behaviour varies by calendar type and external provider.
Your team owns: Staff must handle exceptions, incorrect availability and bookings that need judgement.

Capability 02

Appointments

Stores scheduled customer interactions with time, attendee, owner, status and related contact context.

How it works: Applies configured availability, booking rules and connected-calendar settings to eligible appointments.
Why use it: Makes booked work visible alongside the customer conversation and follow-up.
Plan for: Sync, meeting-link and resource behaviour varies by calendar type and external provider.
Your team owns: Staff must handle exceptions, incorrect availability and bookings that need judgement.

Capability 03

External calendar sync

Connects supported external calendars for availability and event synchronisation, with behaviour varying by calendar type.

How it works: Applies configured availability, booking rules and connected-calendar settings to eligible appointments.
Why use it: Reduces double booking when the connection and conflict rules are correctly configured.
Plan for: Sync, meeting-link and resource behaviour varies by calendar type and external provider.
Your team owns: Staff must handle exceptions, incorrect availability and bookings that need judgement.

Capability 04

Appointment reminders

Uses configured notifications or workflows around booking, rescheduling, cancellation and attendance events.

How it works: Applies configured availability, booking rules and connected-calendar settings to eligible appointments.
Why use it: Keeps customers and staff informed without relying on a person to send each reminder manually.
Plan for: Sync, meeting-link and resource behaviour varies by calendar type and external provider.
Your team owns: Staff must handle exceptions, incorrect availability and bookings that need judgement.

Use it with purpose

What good round-robin booking looks like

A fictional advice team rotates introductory calls among trained advisers, excluding leave and specialist-only cases. The useful outcome is a record that another person can understand and continue, not simply another automated event.

Define eligible hosts

Include only people trained and available for the appointment type.

Choose distribution logic

Agree whether fairness, priority, availability or another rule drives assignment.

Review exceptions

Check manual reassignments, absences and specialist needs rather than assuming the rotation is always right.

Configuration decisions

Decide the operating rules before switching round-robin booking 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.

Set team availability

Confirm each host’s hours, connected diary, buffers and time zone.

Agree assignment rules

Document how ties, new starters, leave and unavailable hosts are treated.

Human review point

Test customer messages

Make sure confirmation identifies the right person and change route.

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 advice team rotates introductory calls among trained advisers, excluding leave and specialist-only cases. The example shows the role of the CRM while keeping the consequential decision with a person.

Call requested

Theo chooses an introductory call.

Hosts checked

Only trained, available advisers are eligible.

Human judgement

Owner assigned

The configured rotation selects Asha.

Exception reviewed

A specialist question is reassigned by a person.

Boundaries and checks

Plan for the limits of round-robin booking

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

Data and context

Round-robin rules do not assess skill or suitability unless explicitly configured.

Account and provider setup

External calendar data and host settings can affect apparent availability.

Keep a person accountable

Human responsibility

Reassignment may require a person when context changes.

Questions about this page

Useful answers, without the sales fog.

1. Is round-robin booking 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 round-robin booking?

Start with three decisions: set team availability, agree assignment rules, test customer messages. Then test ordinary, missing-data and exception cases with fictional records.

3. What is a practical way to measure whether round-robin booking is helping?

Measure whether the intended customer work becomes visible and owned. For this page, review define eligible hosts, choose distribution logic, review exceptions rather than treating clicks, sends or record counts as proof of business value.

4. Can round-robin booking be fully automated?

No. Reassignment may require a person when context changes. Automation can coordinate repeatable steps, while people remain responsible for judgement, exceptions, consent and correcting the record.

Read all CRM questions

Continue the journey

Calendar management Appointments Appointment no-show Team inbox

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