Skip to content
Live13+ production solutions40+ clients deployeddirect + partner
GLARUS Solution

Online Appointment System

Zeour's online appointment system lets customers book service visits against available branch and service capacity. Booking channels, reminders and self-service changes support the pre-visit journey, while appointment-to-ticket conversion connects scheduled arrivals with the GLARUS branch queue.

One platform · 13 solutions · 6+ countries direct + via partners
GLARUS online appointment hero strip — mobile booking, WhatsApp flow, conversion to live ticket, and admin policy UI
Overview

Service-Based Booking and Branch Capacity

Set working hours, slot durations and capacity rules centrally, then let customers choose an available visit time. Staff can follow bookings, changes and no-shows alongside the live service operation.

Appointment booking calendar on a laptop with confirmation on a phone
GLARUS online appointment lifecycle overview — configure → book → confirm → auto-convert → serve / analyze
Appointment lifecycle: configure → book → confirm → auto-convert → audit.

Connecting Bookings to Arrival

The queue management system handles service order after appointments convert to live tickets. Customers who want to wait remotely without reserving a future slot can use virtual queuing.

A self-service kiosk can support on-site booking and arrival confirmation. For practices needing clinical records as well as scheduling, review the MediCare clinic management system.

Deep Dive

Scheduling Rules, Reminder Channels and Booking APIs

Zeour GLARUS appointments is the customer-facing scheduling layer of the broader GLARUS branch operations platform. The booking flows live in MobileWCSA (Laravel + Vue, customer-facing) — mobile app, web portal, WhatsApp, Telegram, ChatBot, SMS. The rules — which services accept appointments, slot duration, branch hours, capacity, lead time, cancellation policy — live in MSA / GLITT (the central control plane). At the right moment, appointments auto-convert into live branch tickets in EMS (the operator cockpit at each branch). The result: customers self-book, get reminded, walk in, and are called by name — without ever queueing.

Zeour GLARUS MobileWCSA Appointments — the customer-facing online appointment platform built on top of the GLARUS branch operations stack. 24/7 self-service booking via mobile app, web portal, WhatsApp, Telegram, ChatBot, or SMS. 15-minute slot granularity with central rule configuration in MSA / GLITT. Automatic conversion of appointments into live branch tickets ~10 minutes before slot time — visitors arrive and are called by name. Email / SMS / WhatsApp / Telegram reminders, multi-branch scheduling, identity verification (passport / national ID / OTP), and a full audit trail. GDPR / HIPAA / PDPL aligned, cloud or on-premise. Works for a solo practice with one calendar just as well as for a multi-branch, multi-department network.

Key Functionalities

Deep dive diagram of GLARUS appointment modules — booking layer, MSA policy engine, conversion worker, notification stack

Omnichannel Booking Flow

Mobile app, web portal, WhatsApp Business, Telegram, ChatBot, SMS, and on-site kiosk — all booking against the same slot grid, same customer profile, same audit trail. Customer's channel preference is stored on their record for follow-up reminders.

Centrally Managed Slot Rules

Admins configure appointment policy once in MSA / GLITT: which services accept appointments, slot duration, branch hours, capacity per slot, lead time for conversion, cancellation policy, identity verification requirements, and reminder cadence.

Real-Time Slot Availability

Redis + Laravel Echo broadcasting ensures slot state is consistent across every channel. Two customers can't book the same slot for the same counter; capacity is enforced live; high-traffic appointment days (visa centers, vaccination drives) scale without conflict.

Identity Verification at Booking

Configurable per service — email OTP, SMS OTP, national ID, passport number, customer code, SAML / OIDC for SSO. Required for regulated industries (banking, government, embassies). Booking rejected on mismatch without leaking existence.

Multi-Channel Notifications

Confirmation + ICS calendar invite + pre-visit reminders via Email, SMS, WhatsApp Business, Telegram, and mobile push. Configurable cadence (24h / 4h / 30 min) per service. Resilient outbox pattern with retry — no notification ever lost.

Auto-Convert to Live Ticket

Each appointment carries a `convert_to_ticket_time` (typically ~10 minutes before slot, configurable). Scheduled worker converts the appointment into a live EMS branch ticket at that moment. Early-arrival kiosk flow also converts on-demand. No-show auto-expires after the window.

Reschedule + Cancel Self-Service

Configurable cancellation policy per service. Self-service from mobile / web / WhatsApp; assisted reschedule by reception. Every action audited. No-show counts tracked per customer for future risk gating.

Per-Customer Profile + History

One customer record holds phone, email, language preference, channel preference, priority flag (VIP / disabled / pregnant), and the full booking + conversion history across every branch. Reception can pull the history during arrival or rescheduling.

Multi-Branch + Multi-Country Scoping

One MobileWCSA installation serves any number of branches across any number of countries. Each branch has its own working hours, services, and capacity. Each country has its own locale defaults; per-region data residency for cloud deployments.

Webhook Events for External Systems

Every booking, reschedule, cancellation, conversion, and no-show fires a webhook to your CRM / HIS / ERP / SMS provider / BI tool. Full OpenAPI specification for partner integrations.

Analytics + Audit

Dashboards: bookings per channel, slot utilization, no-show rate, top services, daily / weekly / monthly trends. Full audit log per appointment for compliance and incident review.

Audit-ready records and operational dashboards.

  • Bookings per channel, slot utilization, no-show rate, top services
  • Daily / weekly / monthly trend lines + per-branch and per-country breakdowns
  • Full audit log per appointment (booking, reschedule, cancellation, conversion)
  • Configurable data retention + right-to-be-forgotten workflow

Resilient Worker Pipeline

Scheduled jobs for slot generation, conversion-on-time, expired-appointment cleanup, reminder dispatch, and analytics rollup. Branch-local execution where appropriate so a WAN outage never blocks branch operations.

Software Components

Customer-Facing Booking

MobileWCSA — Web + Mobile Booking

Laravel + Vue customer-facing app that powers booking on web and mobile. 24/7 self-service slot selection, identity verification, confirmation, ICS calendar invite, and reschedule / cancel flows.

WhatsApp Business + Telegram + ChatBot

Conversational booking flows over WhatsApp Business Cloud API, Telegram, and a configurable website / Messenger ChatBot. Same slot grid, same confirmation experience.

SMS Booking

Low-bandwidth path for feature-phone users. Book a slot via SMS commands; receive confirmation and reminders via SMS.

On-Site Kiosk Booking

CSA self-service kiosks include an appointment-booking flow for walk-up bookings on the day-of or for future visits.

Central Control Plane (MSA / GLITT)

Appointment Policy Engine

Slot duration, branch hours, capacity per slot, lead time for conversion, cancellation policy, identity verification requirements, reminder cadence — all centrally managed and propagated to every branch.

Customer & Branch Configuration

Customer records (phone, email, language, channel preference, priority flags), branch hierarchy, service catalog, multi-language content packs.

MSA Frontend

Modern dashboard for the control plane — appointment configuration, branch management, customer search, analytics, audit log viewing.

Branch Execution (EMS)

EMS Counter Cockpit

Branch-side operator UI where appointments convert into live tickets at the right moment. Operators call, repeat, transfer, or no-show; appointment metadata follows (code, customer name, identity verification status).

Branch-Local Database

Each branch holds its own copy of today's appointments + tickets. Resilient to WAN outages — local execution continues even if MSA is unreachable; reconciles when connectivity returns.

Auto-Conversion Worker

Branch-side scheduled job that promotes appointments into live tickets at `convert_to_ticket_time`. Idempotent and retry-safe.

Real-Time + Notifications

Redis + Laravel Echo Broadcasting

Sub-second slot-state propagation across every channel. Prevents double-bookings; powers live appointment-status updates on mobile clients.

Multi-Channel Notification Outbox

Email (SMTP / Microsoft Graph), SMS (Twilio / MessageBird / Vonage / Infobip), WhatsApp Business Cloud API, Telegram, mobile push. Resilient outbox with retry, lease locking, and deduplication.

ICS Calendar Invites

METHOD:REQUEST ICS files attached to confirmation emails. Outlook / Google / Apple Calendar compatible. Timezone-aware (Europe / London default, configurable).

Webhook Dispatcher

Booking / conversion / cancellation / no-show events fire signed webhooks to external CRM / HIS / ERP / BI systems with retry on transient failure.

Operations & Security

Scheduled Worker Jobs

Slot generation, conversion-on-time, expired-appointment cleanup, reminder dispatch, analytics rollup. Bearer-token-gated endpoints for cron drivers.

REST API + Bearer Auth

Full booking / management API. Customer-scoped Bearer tokens (with `temporary_password` flow for first-time onboarding). OpenAPI specification for partner integrations.

Audit Log

Every booking, reschedule, cancellation, conversion, and access event logged with actor / timestamp / structured metadata. Compliance-ready.

Rate Limiting + Lockout

Sensitive endpoints (login, booking, cancellation) rate-limited per customer + IP. Account lockout on repeated failures. Auto-expiry of unused appointment codes.

Hardware Components

Customer-Facing Hardware

GLARUS Self-Service Kiosks (KIOSAPP066 / AUTO666)

On-site appointment-booking kiosk with thermal printer, capacitive touch, multi-language UI. Walks customers through service / day / slot selection without reception involvement.

QR Stands & Posters

Wall-mounted QR codes that open the WhatsApp / Telegram / web booking flow on the customer's phone — no app download required.

Branch Operations

EMS06 Hardware Keypad

Multi-function counter keypad with 8-digit LCD for calling appointments and walk-in tickets from the operator counter.

SSD06 LED Counter Display

8-digit dot-matrix LED panel showing the appointment / ticket being served at each counter.

CounterDSA LCD Display

10", 13.3", 15" Full-HD per-counter screen with appointment / customer details on call.

Waiting Area + Signage

GRAVIA Digital Signage Controller (GRAVIA06)

Drives lobby TVs showing upcoming appointments + currently-called numbers. Updates in real time as appointments convert.

CONT06 Industrial Branch Server

On-premise branch controller that runs the full GLARUS stack locally — including branch-side EMS + appointment conversion worker.

Appointment Architecture — GLARUS MobileWCSA + MSA + EMS Pipeline

GLARUS appointments is a three-tier system that splits responsibilities cleanly: customer-facing booking lives in MobileWCSA, central policy lives in MSA / GLITT, branch execution lives in EMS. The integration moment — appointment auto-converting to a live branch ticket — is what makes this an operations system instead of a calendar tool. Cloud SaaS or on-premise; same architecture, same operator experience, sovereign data where required.

GLARUS appointment three-tier architecture image — customer channels, MSA central plane, EMS branch execution
01Architecture Tier

Tier 1 — Customer Channels

Where customers actually book — mobile, web, WhatsApp, kiosk

  • MobileWCSA web portal (Laravel + Vue) — responsive booking flow with slot picker, identity verification, confirmation
  • Native mobile apps (iOS + Android) — same flow, push notifications, offline-tolerant
  • WhatsApp Business Cloud API + Telegram + ChatBot — conversational booking on the channels customers already use
  • SMS booking — feature-phone path for low-bandwidth markets
  • CSA on-site kiosks — walk-in bookings + appointment-holder confirm-on-arrival
02Architecture Tier

Tier 2 — Central Plane (MSA / GLITT)

Policy, customer records, slot rules, analytics

  • Appointment policy engine — slot duration, branch hours, capacity, lead time, cancellation rules, identity requirements
  • Customer record store — phone, email, language preference, channel preference, priority flags, full booking history
  • Multi-language content packs — confirmations, reminders, error messages per locale
  • Webhook dispatcher — signed events to CRM / HIS / ERP / BI / SMS providers
  • MSA Frontend — modern operator dashboard for the control plane
03Architecture Tier

Tier 3 — Branch Execution (EMS)

Where appointments become live tickets and operators serve customers

  • Branch-local EMS operator cockpit — calls appointment-converted tickets alongside walk-in and virtual queue tickets
  • Auto-conversion worker — promotes appointment → live ticket at `convert_to_ticket_time`
  • Branch-local database — resilient to WAN outages; reconciles on connectivity recovery
  • Counter displays (LED / LCD) + GRAVIA queue boards showing converted appointments + walk-ins
  • Customer feedback capture at end of service

Real-Time + Notification Pipeline

Real-time
  • Redis + Laravel Echo broadcast slot state across every customer channel — two customers can't book the same slot for the same counter
  • Confirmation + ICS calendar invite delivered on booking via the customer's preferred channels (Email / SMS / WhatsApp / Telegram / push)
  • Pre-visit reminders fire at configurable intervals (24h / 4h / 30 min) through a resilient outbox with retry
  • Auto-conversion worker promotes appointment to live ticket at `convert_to_ticket_time` — typically 10 min before slot
  • Webhook dispatcher fires signed events for every state change — retry-safe with exponential backoff
  • No-show window expiry runs as a scheduled job — appointments past the window are auto-marked NO_SHOW

Online Appointment System vs Calendar Tools vs Phone Booking vs Standalone Schedulers — What You Need

Most "appointment" tools are calendars. They show a time on a screen. An enterprise appointment system like GLARUS MobileWCSA is the only category that closes the loop — appointment converts to live branch ticket, audit trail is regulator-ready, integration is native, and identity verification is built in.

Comparison of GLARUS appointment system vs phone booking vs generic calendar vs standalone vendor scheduler
How an enterprise appointment system compares to phone, calendar tools, and vendor schedulers.

GLARUS Online Appointment System

Best for: Real organizations with branches, services, capacity rules, identity requirements, and a need to integrate with branch operations.

Comparison
  • Omnichannel booking (mobile / web / WhatsApp / Telegram / ChatBot / SMS / kiosk)
  • Centrally managed slot rules + per-service / per-branch / per-counter capacity
  • Automatic conversion of appointments into live EMS branch tickets
  • Multi-channel notifications + ICS calendar invites + identity verification
  • Multi-branch / multi-country / multi-language with full audit trail
  • Full GLARUS platform integration (queue, kiosk, signage, wayfinding, visitor, feedback)
  • Cloud or on-premise · GDPR / HIPAA / PDPL / ISO 27001 aligned

Phone-Based Reception Booking

Best for: Nothing in 2026. It is what you are getting rid of.

Comparison
  • Customer calls reception during business hours
  • Reception types the booking into a spreadsheet or Outlook calendar
  • Double-bookings when two callers reach two phones at the same time
  • No reminders, no audit trail, no analytics
  • No-show rates of 20–35% with no path to improve

Generic Calendar Tool (Calendly / Acuity / etc.)

Best for: Solo consultants and small offices with a single calendar to share.

Comparison
  • Time-slot picker on a web page, syncs to Google / Outlook calendar
  • Basic email reminders, no WhatsApp / Telegram / SMS in most plans
  • No identity verification, no multi-branch capacity rules
  • No integration with a queue management system — appointment doesn't become a live ticket
  • Audit trail is "the calendar"; compliance posture is "trust us"

Standalone Queue-Vendor Scheduler

Best for: Customers who already have that vendor's queue system and want a matched scheduler.

Comparison
  • Vendor-specific scheduling that integrates with their queue product
  • Limited channels — usually web + email, sometimes SMS
  • Vendor-specific data model that doesn't federate across multi-country deployments cleanly
  • Licensing tied to the vendor's entire stack
  • Limited webhook / API extensibility

Online Appointment System — Deployment Checklist

A practical 5-phase rollout playbook for going live with GLARUS MobileWCSA Appointments — from a single-branch pilot to a multi-country estate. Use it as a project plan with your Zeour partner.

Deployment checklist graphic for GLARUS online appointment system — discovery, central config, channel setup, pilot, scale
  1. 01

    1) Discovery & Policy Design

    Checklist
    Inventory branches, services, working hours, current appointment volume, current no-show rates
    Decide slot duration per service (5 / 10 / 15 / 30 / 60 min) and per-slot capacity
    Define identity verification policy per service (none / email OTP / SMS OTP / national ID / passport / SSO)
    Set cancellation and reschedule rules per service (free up to 24h / limited within 24h / locked at conversion lead time)
    Choose channels for launch: which mix of mobile / web / WhatsApp / Telegram / ChatBot / SMS / kiosk
    Decide deployment model — managed cloud (with regional data residency) or on-premise
  2. 02

    2) Central Configuration (MSA / GLITT)

    Checklist
    Provision MSA + branch databases; configure branches, services, working hours, capacity
    Set up appointment policy: slot grids, conversion lead time, cancellation policy, identity verification
    Configure reminder cadence per service (24h / 4h / 30 min) and channel preferences
    Provision notification providers — SMTP / Microsoft Graph for email, Twilio / MessageBird / Infobip for SMS, WhatsApp Business Cloud API account, Telegram bot token
    Configure ICS template + timezone (default Europe / London, override per branch)
    Set up RBAC for admins (per-country / per-branch / per-service scoping)
  3. 03

    3) Channel Setup

    Checklist
    Publish mobile apps (iOS App Store + Google Play) with branding
    Deploy web booking flow at https://book.your-domain.com (or path on existing site)
    Onboard WhatsApp Business account, get template messages approved, configure conversational flow
    Configure Telegram bot + ChatBot conversational flows
    Set up SMS booking shortcode if used
    Configure CSA kiosks for on-site appointment booking + confirm-on-arrival
  4. 04

    4) Pilot Branch Go-Live

    Checklist
    Pick a pilot branch with moderate appointment volume and engaged reception staff
    Train reception team on the admin UI, assisted reschedule flow, and customer support escalations
    Run a friends-and-family booking cohort for 1 week to validate the end-to-end flow
    Monitor: booking success rate, conversion-on-time rate, no-show rate, reminder delivery rate
    Tune slot capacity and reminder cadence based on real data
    Scale to the full pilot branch — measure outcomes for 2 to 4 weeks before further rollout
  5. 05

    5) Multi-Branch / Multi-Country Scale

    Checklist
    Roll out to additional branches in waves using the same configuration templates with local overrides
    Add languages as the deployment expands — locale-aware confirmations + reminders + ICS invites
    Federate analytics dashboards across branches / countries for executive reporting
    Plan custom integrations — CRM (Salesforce / Dynamics / HubSpot), HIS (Epic / Cerner), ERP (SAP / Oracle), identity (SAML / OIDC), BI (Power BI / Tableau / Looker)
    Optimize: tune slot rules based on no-show patterns; consider deposit / pre-payment for high-risk slots
    Annual policy review — adjust slot capacity, reminder cadence, cancellation rules based on accumulated data

Online Appointment System Gallery

Visual highlights of GLARUS MobileWCSA Appointments — the customer-facing scheduling layer of the GLARUS branch operations platform.

GLARUS MobileWCSA appointment booking flow with branch / service / day / slot picker and identity verification step
Booking flow: branch → service → day → slot → identity verify → confirm.
GLARUS appointment booking over WhatsApp Business — conversational flow with slot picker and confirmation card
WhatsApp Business booking — conversational slot picker with ICS invite attached.
GLARUS appointment auto-converting into a live EMS branch ticket 10 minutes before slot time
Auto-conversion: appointment → live branch ticket ~10 min before slot.
GLARUS MSA admin UI for appointment policy configuration — slot duration, capacity, lead time, reminders, identity verification
Central policy in MSA — slot rules, capacity, conversion lead time.
GLARUS appointment architecture diagram with customer channels, MSA central plane, and EMS branch execution
Three-tier architecture: channels → MSA → branch execution.
Problem vs Solution

Why Phone-and-Paper Booking Fails

Phone-and-paper booking drives no-shows, double-bookings, and front-desk overload — here is why an online appointment system is essential.

Why phone-based reception booking and generic calendar tools fail versus an enterprise appointment system
Why phone bookings, calendars, and standalone schedulers fall short — and how GLARUS fixes it.
The Problem01

Phone-Reception Bottleneck

Receptionists spend 30–50% of their day on "I'd like to book an appointment for…" calls. Customers wait on hold. Slots get double-booked because two callers were on different phones. The reception desk becomes a switchboard instead of a concierge.

The Zeour Approach

Self-Service Across Every Channel

Customers book on the channel they already use — mobile, web, WhatsApp, Telegram, ChatBot, SMS, or kiosk. Reception load for routine bookings drops 70–90%. Receptionists go back to concierge work.

The Problem02

Calendars Don't Talk to the Queue

Generic scheduling tools (Calendly, Acuity, custom forms) sit completely separate from the branch operations stack. The appointment shows up in a Google Calendar; nothing tells the queue cockpit. The customer arrives, finds no ticket, and goes back to reception — defeating the point of the appointment.

The Zeour Approach

Appointments Auto-Convert to Live Tickets

`convert_to_ticket_time` (typically 10 minutes before slot) triggers a worker that promotes the appointment into a live EMS ticket. The customer arrives, sees their name on the queue board, and is called. No double-checking. No "we're still trying to find your appointment."

The Problem03

No-Show Rates Above 20%

Email confirmation gets buried; SMS is unreliable; the customer just forgets. Industry studies show 20–35% no-show rates for healthcare, banking, and government appointments. That's burned capacity that could have served a walk-in instead.

The Zeour Approach

Multi-Channel Reminders + ICS Invites

Confirmation + ICS calendar invite immediately on booking. Reminders at 24h, 4h, and 30 min via Email + SMS + WhatsApp + Telegram. No-show rate drops 30–50% within the first month, every time.

The Problem04

No Identity Verification

Anyone can book any slot under any name. Banks, embassies, government service centers, and visa offices need to know that the person booking is the person who shows up. Generic scheduling tools have no built-in identity step.

The Zeour Approach

Verify Identity Before the Visit

Configurable per service: national ID, passport, SMS OTP, customer code, or external SAML / OIDC SSO. Regulated industries get the verification they need without scaring off the rest.

The Problem05

Single-Branch Tools at Multi-Branch Companies

A bank with 50 branches running 50 separate appointment calendars is 50 separate problems. Customers can't see availability across branches; staff in one branch can't see a customer's history at another; reports don't roll up.

The Zeour Approach

One Platform, Every Branch, Every Country

One MobileWCSA installation serves any number of branches across any number of countries. Centralized policy in MSA, branch-local execution, customers can hold one profile and book anywhere.

The Problem06

No Audit Trail, No Compliance Posture

A regulator asks "when did this visa applicant first book, and how many times did they reschedule?" Most scheduling tools have a calendar view, not an audit log. GDPR / HIPAA / PDPL compliance becomes a manual reconciliation exercise.

The Zeour Approach

Full Audit Trail + Compliance Posture

Every booking, reschedule, cancellation, conversion, and access event logged with actor + timestamp + structured metadata. Configurable retention. Right-to-be-forgotten workflow. GDPR / HIPAA / PDPL aligned by design.

Features

Appointments Features

Key features of GLARUS online appointment system — omnichannel booking, slot engine, auto-conversion, notifications, identity verification, API
Feature highlights that move you from phone-and-spreadsheet to enterprise appointment booking.

Omnichannel Booking — Mobile App, Web, WhatsApp, Telegram, ChatBot, SMS, Kiosk

15-Minute Slot Granularity (Configurable in MSA: 5 / 10 / 15 / 30 / 60 min)

Centrally Managed Slot Rules + Branch Working Hours (MSA / GLITT)

Per-Service, Per-Branch, Per-Counter Capacity Caps

Automatic Conversion of Appointments into Live Branch Tickets

Configurable Pre-Conversion Lead Time (default ~10 minutes before slot)

Multi-Channel Notifications: Email · SMS · WhatsApp · Telegram · Push

Pre-Visit Reminder Cadence (configurable: 24h, 4h, 30min, etc.)

Identity Verification (Passport / National ID / OTP / Appointment Code)

Per-Customer Appointment History + Priority Flags (VIP / Disabled / Pregnant)

Multi-Branch + Multi-Country Customer Profile (one identity, every branch)

Self-Service Reschedule + Cancel (with configurable cancellation policy)

No-Show Detection + Auto-Expiry of Unconverted Appointments

Calendar Invites (ICS METHOD:REQUEST) — Outlook / Google / Apple

Real-Time Slot Availability (Redis + Laravel Echo broadcasting)

REST API for External Bookings (Bearer-token authenticated)

Webhook Events for Booking / Cancellation / Conversion / No-Show

Multi-Language UI with Full RTL (Multiligual baseline; extensible to any locale per engagement)

Branding + Theming (Custom Logo, Colors, White-Label Available)

Analytics Dashboard: Bookings, Conversions, No-Show Rate, Slot Utilization

Cron-Driven Expired Appointment Cleanup

GDPR / HIPAA / PDPL / ISO 27001 Aligned (Cloud or On-Premise)

Resilient Email Outbox with Retry (no notification ever lost)

Audit Log of Every Booking, Reschedule, Cancellation, and Conversion

Core Components

Appointments Components

Scheduling Rules, Reminder Channels and Booking APIs.

GLARUS appointment core components diagram — booking layer, slot engine, conversion worker, notification stack, identity, multi-branch, API, audit
Core building blocks of a complete enterprise appointment platform.

Omnichannel Booking Layer

Every channel a customer might use, with consistent slot availability and confirmation experience.

  • Mobile app (iOS + Android), responsive web portal
  • WhatsApp Business Cloud API, Telegram, ChatBot conversational flows
  • SMS booking for feature-phone / low-bandwidth markets
  • On-site CSA kiosk booking for walk-ins and future visits

Slot Engine + Capacity Enforcement

15-minute slot granularity (configurable 5 / 10 / 15 / 30 / 60 min) with real-time capacity enforcement via Redis.

  • Per-service slot duration and capacity rules
  • Branch working hours + holiday calendars in MSA / GLITT
  • Redis-backed Laravel Echo broadcasting for live slot state
  • Server-side validation rejects double-booking even on race-conditions

Auto-Conversion to Live Ticket

The integration that makes GLARUS appointments different from a calendar tool.

  • `convert_to_ticket_time` calculated per appointment (default ~10 min before slot)
  • Branch-side worker promotes appointment → live EMS ticket at the right moment
  • Kiosk recognition for early-arrival on-demand conversion
  • No-show auto-expiry after configurable window

Multi-Channel Notification Stack

Confirmation, reminders, and ICS calendar invites delivered through every channel.

  • Email (SMTP / Microsoft Graph), SMS (Twilio / MessageBird / Vonage / Infobip)
  • WhatsApp Business Cloud API, Telegram, mobile push notifications
  • Resilient outbox with retry + lease locking + deduplication
  • ICS METHOD:REQUEST invites (Outlook / Google / Apple)

Identity Verification Stack

Configurable per service — match the verification to the risk profile.

  • Email OTP, SMS OTP, national ID, passport number, customer code
  • SAML / OIDC for single-sign-on with corporate / government IdPs
  • Rate-limited booking endpoints with timing-safe compare
  • Audit-logged verification attempts with structured metadata

Multi-Branch / Multi-Country Scoping

One installation serves any number of branches across any number of countries.

  • Centralized policy in MSA, branch-local execution in EMS
  • Per-country locale defaults + per-region data residency
  • Cross-branch customer profile (one identity, every branch)
  • Per-branch role scoping for operators

REST API + Webhooks

Bearer-token-authenticated API for external bookings; signed webhooks for downstream systems.

  • POST /api/book_appointment / cancel_appointment / convert_appointment_to_ticket
  • Slot lookup, customer management, appointment history endpoints
  • Booking / conversion / cancellation / no-show webhooks (signed, retry-safe)
  • OpenAPI specification + Postman collection + partner SDK
Benefits

Slot Utilisation and Appointment Attendance

Benefits infographic for GLARUS online appointment system — lower phone load, lower no-shows, faster arrivals, higher slot utilization
Measurable outcomes: less phone load, fewer no-shows, faster service, higher slot utilization.
01

Cut "phone reception" load for appointments by 70–90% via 24/7 self-service

02

Reduce no-show rates by 30–50% with timely multi-channel reminders

03

Shorten branch wait time on arrival to under 2 minutes per appointment

04

Eliminate double-booking with central slot rules and per-counter capacity caps

05

Improve customer satisfaction (CSAT / NPS) at banks, hospitals, and embassies by 20–40 points

06

Free reception staff to handle complex cases instead of routine scheduling

07

Standardize the booking experience across single-branch, multi-branch, and multi-country estates

08

Generate audit-ready records for compliance (GDPR, HIPAA, PDPL, regulatory inspections)

09

Convert appointment → live ticket automatically so the queue cockpit always reflects reality

10

Future-proof with omnichannel APIs, identity verification, and full GLARUS platform integration

Process

From Available Time Slot to Served Appointment

Booking, confirmation, reminders and arrival conversion bring a scheduled visit into the branch workflow.

How GLARUS online appointment system works — five-step timeline from policy configuration through audit
  1. Configure Rules in MSA / GLITT

    Admins define the appointment policy centrally: which services accept appointments, slot duration (5 / 10 / 15 / 30 / 60 min), branch working hours, per-slot capacity, lead time for conversion, cancellation rules, and required identity verification. Rules cascade to every customer-facing channel.

  2. Customer Books (Anywhere)

    Customer opens the mobile app, web portal, WhatsApp Business chat, Telegram bot, ChatBot, or SMS flow. They pick a branch, a service, a day, and an open 15-minute slot. Capacity is enforced live (Redis-backed) so two customers never book the same slot for the same counter.

  3. Confirm + Reminders

    The system returns an appointment code (e.g. AB1234) and convert_to_ticket_time. A confirmation goes out via the customer's preferred channels (Email + SMS + WhatsApp + Telegram). An ICS calendar invite is attached. Pre-visit reminders fire at configurable intervals (24h, 4h, 30 min).

  4. Convert the Appointment on Arrival

    About 10 minutes before the slot (configurable), the appointment converts automatically into a live branch ticket on the EMS counter cockpit. If the customer arrives early, the kiosk recognizes them and lets them confirm-on-arrival to trigger conversion immediately.

  5. Serve, Audit, Analyze

    Operator calls the ticket from EMS — appointment metadata follows (appointment code, customer name, identity verification status). The full booking + conversion lifecycle lands in the audit log. Analytics roll up: booking volume per channel, no-show rate, slot utilization, top services, daily / weekly / monthly trends.

Industries

Appointments Use Cases by Industry

Explore the service environments relevant to appointments.

Industries served by GLARUS online appointment system — banks, hospitals, government, embassies, telecom, insurance, universities, more
Industries where appointments need to convert to live operations.
Banking & Financial Services
Healthcare (Hospitals & Clinics)
Government Service Centers
Embassies & Visa Centers
Insurance Branches
Telecom Service Centers
Universities (Student Services)
Pharmacies
Tax & Vehicle Licensing Offices
Public Service Halls
Notary & Legal Offices
Driving Test Centers
Diplomatic Missions
Specialty Clinics & Dental
Veterinary Clinics
Real Estate Viewings
Beauty & Wellness
Personal Training & Coaching
Salons & Barbershops
Religious & Heritage Sites
FAQ

Online Appointment System FAQs

Get answers to the most common questions about our appointments.

What is an online appointment system?

An online appointment system lets customers self-book a specific time slot for a specific service at a specific branch, instead of phoning, queueing in person, or relying on staff to schedule. A modern enterprise appointment system like Zeour GLARUS MobileWCSA does it across every channel a customer might use — mobile app, web portal, WhatsApp, Telegram, ChatBot, SMS, kiosk — with central rule configuration, automatic capacity enforcement, multi-channel reminders, identity verification, ICS calendar invites, and (the critical piece) automatic conversion of the appointment into a live branch ticket near the slot time, so the queue cockpit always reflects reality.

Does the appointment system fit a solo practice or single location?

Yes — a single location with one or two service calendars is a standard deployment shape, covered by the Starter tier at 1–3 sites. You get the same 24/7 booking, reminders, and no-show controls as enterprise deployments; pricing and setup are simply sized to one site. Because appointments, virtual queueing, and walk-in queueing share the GLARUS platform, a small practice can start with booking alone and switch on the rest later without changing systems.

How does the GLARUS appointment system work?

Five steps. (1) Admins configure the appointment policy centrally in MSA / GLITT — services that accept appointments, slot duration (5 / 10 / 15 / 30 / 60 min), branch hours, capacity, lead time, cancellation rules, required identity verification. (2) Customer books via their preferred channel (mobile / web / WhatsApp / Telegram / ChatBot / SMS / kiosk) — they pick branch + service + day + slot. (3) System returns an appointment code (e.g. AB1234) plus convert_to_ticket_time; sends confirmation + ICS invite + reminders. (4) About 10 minutes before the slot, the appointment auto-converts into a live branch ticket on the EMS counter cockpit. (5) Operator calls the ticket; full booking + conversion lifecycle is in the audit log; analytics roll up everything.

How does the appointment-to-ticket conversion work?

This is the difference between a real appointment system and a generic calendar tool. Every appointment in GLARUS carries a `convert_to_ticket_time` — typically 10 minutes before the slot (configurable per service). At that moment, a scheduler / worker job converts the appointment into a live branch ticket in EMS. The customer arrives, the ticket is already in the queue, and the operator calls them by name. If the customer arrives early, the kiosk recognizes their appointment code and can convert it on the spot. If they don't show up, the no-show window expires and the ticket is auto-marked NO_SHOW.

What channels can customers book through?

All of them. Native mobile app (iOS + Android), responsive web portal, WhatsApp Business Cloud API, Telegram, website ChatBot, SMS, and on-site kiosk (CSA). The booking flow is consistent across channels — same slot availability, same identity verification, same confirmation experience. Customers can mix channels too: book on WhatsApp, get the reminder via SMS, scan a QR at the branch to confirm-on-arrival. All bookings land in the same central database with the same appointment code.

What slot durations are supported?

Per-service: 5, 10, 15, 30, 45, 60 minutes, or any custom duration in 5-minute increments. The slot grid is generated from branch working hours and per-slot capacity. The example in our trainer documentation uses 15-minute slots (e.g. 10:30-10:45) which is the most common configuration. Capacity-per-slot is also configurable — for example, 4 counters serving a service can accept 4 appointments per 15-minute slot.

How does identity verification work at booking?

Configurable per service. Options include: nothing (open booking with email + phone), email OTP, SMS OTP, national ID, passport number, customer code from a pre-issued list, or a SAML / OIDC redirect to an external identity provider for SSO. For regulated industries (banking, government, embassies) the typical configuration is national ID or passport number plus SMS OTP. The booking flow rejects mismatched / missing identity data with a clear message and never leaks whether a particular ID exists in the system.

Can customers reschedule or cancel?

Yes, subject to the cancellation policy you configure per service. Typical setups: free reschedule up to 24h before; reschedule within 24h limited to one move; cancellation after the conversion lead time is rejected (because the appointment is already a live ticket). Self-service from the mobile app and web portal; assisted reschedule by reception staff via the admin UI. Every reschedule and cancellation lands in the audit log with actor, timestamp, and previous-state metadata.

How do reminders work?

Configurable cadence per service. Common configurations: confirmation immediately on booking, reminder 24 hours before, reminder 4 hours before, reminder 30 minutes before. Delivery channels: Email, SMS, WhatsApp Business, Telegram, push notification (mobile app). The customer's channel preference is stored on their customer record. Reminders go out through a resilient email / SMS / WhatsApp outbox with retry — a temporary provider outage never loses a reminder. Sent reminders are visible in the customer's history for support escalations.

Does it integrate with the rest of the GLARUS platform?

Yes — and that's why customers pick it over a standalone scheduling tool. Appointments flow through MSA / GLITT centrally and convert into live tickets in branch-level EMS at the right moment. Walk-in tickets (CSA self-service kiosks), virtual queue tickets (MobileWCSA), and appointment-converted tickets all live in the same EMS queue with one set of priority rules. Reception sees one queue. Counter operators see one queue. Reports are unified across channels. The customer experience feels seamless because it is.

How does multi-branch / multi-country deployment work?

A single MobileWCSA installation serves any number of branches across any number of countries from one central control plane (MSA / GLITT). Each branch has its own working hours, services, and capacity rules. Each country can have its own language / locale defaults and per-region data residency for cloud deployments. Customers can hold one profile and book across branches; staff in one branch can see customer history from any branch (subject to role-based access controls).

Is GLARUS appointments GDPR / HIPAA / PDPL compliant?

Yes. Personal data is encrypted in transit (TLS) and at rest. The full audit trail logs every booking, reschedule, cancellation, conversion, and access event. Configurable data-retention windows + right-to-be-forgotten workflow let you honor subject-access requests in minutes. Role-based access, rate limiting on every sensitive endpoint, and 2FA on admin accounts close the technical surface. For regulated environments (government, healthcare, defence), on-premise deployment keeps every byte of personal data inside the customer's data centre.

How does it handle no-shows?

Three layers. (1) Multi-channel reminders cut no-show rate by 30–50% just by reaching customers reliably. (2) Each service has a configurable no-show window after the slot — appointments not converted within the window are auto-marked NO_SHOW. (3) Per-customer no-show count is tracked; configurable rules can require deposits / pre-payment / extra verification for repeat no-shows. Analytics surface no-show patterns by service, branch, and slot — so you can tune slot capacity and reminder cadence based on real data.

How is real-time slot availability handled?

Redis + Laravel Echo broadcast slot-state changes in real time across every customer-facing channel. When customer A books slot 10:30 at branch1 / service 8, customer B opening the same booking flow 100ms later sees the slot as unavailable. This is critical at peak times — embassy visa days, end-of-month banking, vaccination drives — where dozens of customers race for limited slots. The Redis-backed enforcement also means a single MobileWCSA deployment scales to thousands of concurrent bookings without conflict.

Is there an API for external bookings?

Yes. A secure, token-authenticated REST API covers the full appointment lifecycle — creating and cancelling bookings, converting an appointment into a live branch ticket, available-slot lookup, and customer-record management. Webhooks fire on every state change — booking, conversion, cancellation, no-show — so your CRM / HIS / ERP / SMS provider can react in real time. The full API specification is shared with integration partners as part of a development engagement.

How long does deployment take?

A single-branch pilot with the standard channels (mobile + web + WhatsApp + SMS) typically goes live in 3 to 4 weeks: 1 week of discovery (services, slot rules, branch hours, capacity, identity policy, cancellation policy), 1 week of configuration in MSA, 1 week of branding + channel setup (WhatsApp Business onboarding, SMS gateway, ICS), 1 week of UAT + reception training. Multi-branch rollouts use the same configuration templates and add 1 to 2 weeks per wave. Our partner network sizes each engagement up front; on-premise deployments take longer due to infrastructure provisioning.

Cloud or on-premise?

Both. Most commercial customers (banks, retail, hospitality) pick managed cloud for speed of pilot and zero-ops overhead. Regulated environments — government ministries, defence sites, hospitals running on-site EHRs, embassies, central banks — go on-premise so all personal data stays inside their perimeter. The application is identical in both modes; the only structural difference is the deployment topology.

How does pricing work?

Configured per deployment — branches × services × channels × integrations × hardware. Cloud customers typically subscribe per branch per month with channel-based pricing (WhatsApp Business has its own per-conversation cost; SMS varies by provider). On-premise deployments are perpetual licence plus annual maintenance (typically 18–22% of licence). Pilots start small and expand. Most customers see ROI within 6 to 12 months from reduced no-show rates, lower phone-reception load, higher slot utilization, and improved customer retention. Contact your local Zeour partner for a tailored quote — or use the ROI calculator on the /pricing page.

Can I white-label it?

Yes. White-label and OEM arrangements are available through the Zeour partner network. Custom branding (logo, primary color, typography, custom domain), per-language content, and custom email / SMS templates are standard. For resellers and integrators we offer multi-tenant deployments where each end-customer has its own isolated database and branding within a single GLARUS instance.
Get Started Today

Ready to Transform Your Operations with Appointments?

Discuss your workflows, deployment requirements and integration scope with the Zeour team.

Glossary

Definitions for the operational terms that appear across this page. Tap any chip to read the long-form entry plus its cross-links.