Modules / Beta

Let people book without splitting planning apart.

Create booking pages that connect to your Planning Hub, calendar and customer context.

Use Nylas Scheduler as the engine while SideIQ owns the public page, embed and portal experience.

Offer 1:1, collective, group and round-robin appointments without a separate booking tool.

Every booking can become a SideIQ appointment connected to CRM, planning and follow-up.

SideIQ Applicatie Screenshot

What you get

01

Booking that belongs to operational planning.

Scheduler & booking lets visitors, prospects and customers choose a time without your team rebuilding the appointment afterwards. SideIQ owns the surface and context; Nylas powers availability.

02

Booking pages

public SideIQ-owned pages with their own slug and metadata

03

Website embeds

iframe code for external websites without the full landing layout

04

Portal booking

appointment types can also be available inside the customer portal

05

Meeting types

1:1, collective, group and round-robin configurations

06

Calendar availability

Nylas Scheduler uses connected calendars and availability rules

07

Language and styling

booking UI with language, color and branding from configuration

08

Planning Hub connection

booked moments connect to appointments, routes and team planning

MODULE · SCHEDULER & BOOKING

Scheduler & booking koppelt afspraakpagina’s aan agenda, CRM, klantportaal en planning. Boekingen landen direct in het werkproces.

SideIQ Applicatie Screenshot

Why this is different

01

What separate booking tools do

An external booking tool creates a calendar event and leaves your team to make CRM, planning, follow-up and execution line up afterwards. The booking exists, but the workday is still fragmented.

02

How SideIQ handles it

SideIQ uses Nylas for the scheduler engine, while keeping the booking surfaces under its own control: public pages, embeds, portal booking and the connection to Planning Hub and CRM.

03

Why it matters

A booked appointment is not just a calendar block. It starts a customer moment with prep, location, follow-up and sometimes route planning. That is why booking belongs in the same flow.

Why this is necessary

A booking is the start of work

Without connected booking, your team still has to figure out what needs to be done after every appointment. The calendar is filled, but customer context, intake questions, preparation, planning and follow-up are often spread over separate tools.

That's exactly where external appointment tools fall short. They solve the problem of choosing a time slot, but don't always understand what that time slot means for CRM, planning, route, customer portal or execution. Once booking lives outside SideIQ, the system loses context about why someone booked and what action is needed next.

SideIQ therefore makes scheduler and booking part of the Business Operating System. Appointment pages, calendar sync, customer relations, intake questions, scheduling and follow-up remain connected within the same workflow. The more agreements are made via SideIQ, the better the SideIQ brain understands what needs to be prepared, whose turn it is and what next step logically follows. This way, a booking does not become a separate agenda block, but the starting point of well-prepared work.

Examples

Request a demo

visitors choose a fitting time slot themselves

Intake calls

round-robin distribution across available team members

Service appointments

appointment types with duration, host and location context

Customer portal

existing customers schedule follow-ups in the same environment

Website embed

booking directly on your external website without a separate toolchain