Appointment scheduling software lets a customer pick a free slot with a person on your team, while the business controls which slots exist, who takes them and what happens next. For one person with one calendar a booking link is enough. For a team the rules decide: in RolChat a booking form's availability step lists seven settings and its meeting step three, and booking is included from the Standard plan.

Four buyer guides to online appointment scheduling software read for this guide mostly list features, and all four mention reminders and payments. The decisions behind such a checklist are how the settings combine on one team and what happens when a host drops out.

Why a team needs more than a calendar link

A booking page shows times that are really free, picks a host for the visit, records the booking where the team already works and has a plan for the day the host cannot come. A calendar link does only the first. One person can stop after that job. A team cannot, because each extra host is one more way for the schedule to disagree with itself.

Searches also call it customer, service or sales appointment scheduling software; all describe a page where an outsider books a member of staff. They differ in what sits behind it: a sales team wants the booking to become a lead, and a service team may want a ticket so that someone prepares for the visit. RolChat's booking form can create both.

A white meeting room table with red chairs and a whiteboard on the wall behind
A booking page puts a person and a time into a room like this without a round of e-mails.

The settings that decide whether a slot exists

RolChat's documentation on booking forms describes a form in four steps: fields, availability, meeting settings and appearance. The availability step holds seven settings, and each one is a decision the team makes before the page goes live. Every booking becomes a lead, which the guide to contact management software follows from there, and the booking page with its availability rules has a feature page of its own.

SettingWhat it controlsDocumented value
Host assignmentWho receives the bookingA specific agent, any free agent or round-robin
Working days and hoursWhen slots can existChosen on the form
Meeting lengthHow long each slot is15 to 120 minutes
BufferThe gap between two meetingsSet on the form
Maximum per dayHow many meetings one day can holdA cap set on the form
Booking horizonHow far ahead a visitor can book30 days by default
Minimum noticeHow soon before the start a slot closes24 hours by default

What a table cannot show is how the settings combine. Length and buffer set how many slots a block of hours can hold. By simple arithmetic, a 30-minute meeting followed by a 15-minute buffer uses 45 minutes of a host's time, so a four-hour block holds five meetings, not eight; the trial shows how many slots the page really offers. The daily maximum then caps the day even where the hours would allow more, which protects a host from a run of back-to-back calls. Minimum notice and horizon define the window a visitor sees. With the defaults of 24 hours and 30 days, the first bookable slot is a day away and the last is about a month out, so a team that cannot staff beyond two weeks should shorten the horizon.

Same-day bookings need a lower minimum notice, and the team accepts the interruptions.

Who gets the meeting

Which host mode is right depends on who knows best which person should take the meeting: the customer, the team or nobody in particular. A specific agent suits a named consultant or an account owner. Any free agent hands the booking to whoever is free, which suits a general consultation where the choice of person does not matter. Round-robin spreads meetings across the hosts in turn, so that no one collects them all, and fits a team that treats every booking as equal.

Tying a page to one agent is the most predictable setup, and that agent's absence leaves it with nobody to take the booking. Any free agent is the loosest rule. Round-robin is the mode for the question of whether a busy week lands on one person.

With several hosts, one test matters most: do their hours combine as expected? Give two hosts different working days and see which days the page offers. The documentation does not say. Check it in the trial, before the page is published anywhere.

Time zones, double booking and reminders

On time zones and clashes the documentation is explicit. Slots are shown in the visitor's time zone, and every zone has a name in the IANA time zone database, such as Europe/Berlin, so a booking from another country can be compared hour for hour. The meeting stores the zones of both parties, and each side is reminded in its own. And the server enforces availability: a taken slot, a slot outside working hours or one with the wrong length is refused, so two visitors can never book the same host at the same time.

The server, not the page, does the refusing. A page that only hides a slot after someone books can still show it to a second visitor who loaded the page a minute earlier; when the server enforces availability, the second request is refused.

Reminders sit in the meeting settings: 24 hours and 1 hour before the meeting for the customer, and 15 minutes before for the agent. The documentation does not name the channel they travel on, so where the customer actually sees them is a question for the trial.

When the host becomes unavailable

People become unavailable, and a booking has promised their time. The documentation gives a form six ways to respond, chosen per form: cancel by hand, auto-cancel with an e-mail, flag for an Admin, reassign automatically to a free agent, offer a new slot, or the default hybrid, which reassigns if someone is free and otherwise offers a new slot. A plugin can report an agent as unavailable and so set the strategy running.

An empty meeting room with a long wooden table, grey chairs and a window at the far end
A booked slot is a promise, and the unavailable-host strategy decides what happens when nobody is sitting here.

Each strategy trades speed against control. Cancel by hand and flag for an Admin keep a person in the loop at the cost of minutes of attention, which suits consultations where each one matters. Auto-cancel with an e-mail is fast and honest, but the booking is lost. Reassigning automatically keeps the slot and changes the host, which works when hosts are interchangeable, the assumption behind any free agent and round-robin.

Pages built on one named agent sit oddly with automatic reassignment, because the customer came for that person, and offering a new slot is the gentler choice. That is a judgement, not a rule of the product. The hybrid is the default, and the useful habit is to choose the strategy at the same time as the host mode.

Where the booking lands: meeting, lead, ticket and rules

According to the documentation of web forms, a booking creates a meeting and a lead, and the meeting settings can also open a ticket on booking. The lead is a record in RolChat's CRM, so the person who booked is a record the team can open, not a name in a separate calendar tool. For a sales team that is the point: the booking arrives already attached to a lead.

Rules come next. The automation documentation lists booking created as an event, and a rule on it can check conditions and then act. The automation engine's actions include adding a tag, assigning an agent or a team, sending an e-mail, creating a ticket and calling a webhook. The marketing guide says the module has no rules engine of its own, so anything conditional about a booking is an automation rule, and Standard allows ten of them.

Booking forms live in the marketing module, which Owners, Admins and Managers use, while an Agent sees only the leads and meetings assigned to them. For a team that answers who sees what: the people who run the forms see the setup, and each Agent sees their own assignments.

Where visitors book: link, embed or chat widget

Visitors can reach a booking form by a link, inline on a page or as a popup, and an embedded form is a form like any other: the W3C's forms tutorial lists what a visitor on a keyboard or a screen reader needs from one, such as labels and clear error messages. Its place is a decision about the visitor's moment: next to the question that makes someone want to talk to a person, such as a pricing page or a contact page.

A hand marking a meeting with a blue marker on a large desk planner beside a keyboard
A meeting marked by hand on a desk planner.

Through the chat widget there is a second route. A trigger message is a small proactive popup that appears on chosen pages, and its call to action can be to book a meeting, which points at one of the booking forms. The pricing page does not say which plan carries trigger messages, so settle that before building on this route. The forms themselves are the lead and booking forms of the marketing module. The documentation does not describe an agent or an AI proposing slots inside a chat message, so the widget leads to the form and the form does the booking.

Booking in Standard: what it costs

According to the pricing page, booking is included from the Standard plan, and Lite does not include it. Standard costs $49 a month per company or $490 a year, which is two months free, and includes 10 agents and 5 sites; an extra agent is a $5 a month add-on. The plan price is per company, not per agent, so only agents beyond the limit cost extra, and the page lists meeting booking as a Standard feature instead of a separate scheduling subscription.

Enterprise is custom, with unlimited agents and sites, and the pricing page lists no booking difference between Standard and the plans above it, so none is claimed. There is no free plan: Lite and Standard start with a 30-day free trial, and after it the account continues on a paid plan.

What the booking form does not cover

Only a meeting booked with a host is described in the documentation. It does not describe payments or deposits at booking, recurring appointments, a waitlist, group or class booking, or the booking of rooms and equipment. Teams that need one of these should keep a dedicated tool for that part.

That limit settles a common confusion. Medical, dental, clinic and veterinary practices, salons, spas, tattoo studios, HVAC firms and banks often need more than a meeting with a host: patient or client records, deposits, service menus, job dispatch or regulatory duties. The documentation makes no industry or compliance claim for the booking form.

Consultation slots sold by a firm, such as an accountancy, are closer to what the form does: a customer, a host and a time, with a record afterwards. A calendar invite is the other thing buyers ask about: it normally travels as an iCalendar file, the format defined in RFC 5545, and the note below says what the documentation leaves open.

Confirm before you depend on it

The documentation does not describe a link where the customer cancels or reschedules, a video-call link added to the meeting, or a two-way link with an external calendar. The feature page mentions a team calendar and calendar invites; ask in the trial or on a demo what each one covers. Nothing was run live for this guide, which rests on the documentation.

Checks to run on a two-host form

Choose Standard at sign-up, since Lite does not include booking, then switch on the marketing module in Settings and build one booking form with two hosts. Most of the behaviour above can be checked in a short session on that form; the host drop-out test depends on a way to report an agent as unavailable.

Checks on one booking form
  • Set a 30-minute length, a 15-minute buffer and a daily maximum of three, then count the slots the page shows: they follow the settings, and no day offers more than three.
  • Open the page in two browsers and choose the same slot in both: the second booking is refused.
  • Book from a device set to another time zone: the visitor and the host each see the time in their own zone.
  • Make one host unavailable after a booking, if a plugin that reports agent availability is connected: the chosen strategy runs. If nothing can report it in your setup, ask on a demo how an unavailable host is detected.
  • Open the lead and the meeting as an Admin, then as an Agent: each role reaches what its permissions allow, and an Agent sees only assigned items.
  • Add a rule on the booking created event, such as adding a tag: it runs once per booking.

Run the checks before the link goes on a public page. Where the documentation was silent, as it is on the reminder channel, on how several hosts' hours combine and on how an unavailable host is detected, a demo is the place to ask.

The settings can also be walked through live: book a demo.

Frequently asked questions

Does a small team need round-robin booking?

Not at first. With one or two hosts, a page tied to a specific agent or the any free agent mode is enough. Round-robin starts to matter when bookings pile onto the same person. Every RolChat booking form offers all three modes, so the choice can change as the team grows.

Which plan includes appointment scheduling software, and is there a free one?

In RolChat, booking is included from the Standard plan at $49 a month per company, or $490 a year, with 10 agents and 5 sites. Lite does not include it. There is no free plan; Lite and Standard start with a 30-day free trial.

How do time zones work when a customer books?

The customer sees the slots in their own time zone. The meeting stores the zones of both sides, and each side is reminded in its own. The documentation says nothing more on the subject, so a test booking made from a device in another zone shows what the host sees.

How does the software stop two people booking the same slot?

The RolChat server enforces availability. It refuses a slot that is already taken, one outside working hours and one of the wrong length. The buffer, the daily maximum and the minimum notice then narrow which slots are offered in the first place.

What happens to a booking when the host cannot make it?

The unavailability strategy set on the form decides. The default is a hybrid: reassign the meeting to a free agent if there is one, otherwise offer the customer a new slot. Other strategies cancel by hand, cancel automatically with an e-mail or flag the booking for an Admin.

What does a booking create besides the meeting?

A booking creates a lead in the CRM next to the meeting, and the meeting settings can also open a ticket. The booking created event can start an automation rule, for example one that adds a tag or assigns a team.

Ruslan Nazarov
Ruslan Nazarov
Head of SEO at RolChat

Writes about customer support operations, live chat, AI-assisted service and the tooling behind great customer experience.

LinkedIn

Ready to let customers book your team?

Run booking pages, conversations and customer records in one RolChat workspace.