Walk-In Configuration

Service counter setup, token queue settings, walk-in reservation strategy, and queue depth notifications.

Walk-in settings control how patients without prior appointments are handled. Settings exist at multiple levels: service counters, centre-services, and doctor configs.

Multiple Levels

Walk-in configuration spans three levels: service counter queues, centre-service availability, and doctor-specific walk-in rules. All work together to manage walk-in patient flow.

Service Counter Walk-In Config

Service counters are physical reception points where walk-in patients are registered. Each counter has its own walk-in configuration:

{  "enabled": true,  "daily_limit": 50,  "notification_thresholds": [    10,    25,    40  ]}

Field	Type	What It Does
enabled	boolean	Whether this counter accepts walk-in registrations
daily_limit	number or null	Maximum walk-in patients per day at this counter (null = unlimited)
notification_thresholds	number[]	Patient count levels that trigger staff notifications (e.g., alert at 10, 25, 40 patients)

Walk-In Reserve (Slot Engine)

The slot engine can reserve a portion of appointment slots specifically for walk-in patients. This prevents online bookings from consuming all available slots:

{  "strategy": "PERCENTAGE",  "reserve_percentage": 20,  "reserve_count": 0,  "apply_to_online_only": true}

Field	Type	Default	What It Does
strategy	enum	NONE	Reserve strategy: NONE (no reserve), PERCENTAGE, or COUNT
reserve_percentage	number	0	Percentage of slots to reserve for walk-ins (used when strategy is PERCENTAGE)
reserve_count	number	0	Fixed number of slots to reserve (used when strategy is COUNT)
apply_to_online_only	boolean	true	If true, only online bookings are blocked from reserved slots; staff can still book them

How Reserve Works

When reserve strategy is PERCENTAGE with 20%, and a doctor has 10 slots, 2 slots will be hidden from online booking. Staff at the hospital can still book those slots if needed.

Centre-Service Walk-In Settings

Walk-in can be enabled per service at each centre:

{  "walk_in_enabled": true,  "walk_in_slot_strategy": "NEXT_AVAILABLE",  "walk_in_reserve_strategy": "PERCENTAGE",  "walk_in_reserve_percentage": 15,  "walk_in_reserve_count": 0}

Field	Type	Default	What It Does
walk_in_enabled	boolean	false	Whether walk-in patients are accepted for this service at this centre
walk_in_slot_strategy	string or null	null	How to assign slots to walk-ins: NEXT_AVAILABLE or QUEUE
walk_in_reserve_strategy	string or null	null	Whether to reserve slots: PERCENTAGE or COUNT
walk_in_reserve_percentage	number	0	Percentage of slots reserved for walk-ins
walk_in_reserve_count	number	0	Fixed count of slots reserved for walk-ins

Doctor Walk-In Config

Each doctor can independently control their walk-in availability:

{  "enabled": true,  "daily_limit": 20,  "serving_strategy": "FIFO",  "notification_thresholds": [    5,    10,    15  ]}

Field	Type	What It Does
enabled	boolean	Whether this doctor accepts walk-in patients
daily_limit	number or null	Maximum walk-in patients per day for this doctor
serving_strategy	enum	Queue processing order: FIFO (first-in-first-out) or PRIORITY
notification_thresholds	number[]	Alert the doctor when walk-in queue reaches these counts

How Walk-In Settings Interact

Walk-in availability is determined by checking all levels. All must be enabled for walk-ins to work:

Service Counter must have walk-in enabled and not at daily limit
Centre-Service must have walk_in_enabled = true for the requested service
Doctor Config must have walk-in enabled (if the service requires a doctor)
Slot Availability must have non-reserved slots available (or be within walk-in reserve)

What's Next

Service Configuration — Service-level walk-in settings
Doctor Configuration — Doctor-level walk-in preferences
Appointment Settings — Walk-in reservation in the slot engine config

walk-inconfigurationqueuecounters

Walk-In Configuration