Atmora Tech

Operations platform

Capacity, calendars
and the awkward reschedule

An availability engine that understands rooms, people, equipment and the rules binding them together, rather than a shared diary with a booking form on top. Designed for clinics, service networks, training providers and operations teams whose appointments need three things to be free at once.

  • Cloud
  • Private cloud
  • On-premise

Overview

Slots, resources and reschedules for organisations where an empty hour costs real money.

Most booking failures are modelling failures. A consultation needs a clinician with the right registration, a room with the right equipment, and a 10-minute cleaning buffer after it, and any tool that treats those as one calendar entry will double-book by Thursday. Booking Platform models resources separately, expresses a bookable service as a requirement set across them, and generates slots only where every requirement is satisfiable. Availability is computed from rules and cached with a short time to live, so a 90-day grid for 40 practitioners renders in well under a second.

Around that sit the parts that decide whether capacity is actually used: waitlists that refill a cancellation automatically, deposit and cancellation-fee policies, reminder sequences over SMS, email and WhatsApp, and a rescheduling flow that keeps the original booking reference. If your bookings amount to one person with one diary, this is far more machinery than the problem deserves, and a shared calendar with a form will serve you better for less.

Down from 14% to 6% after a three-stage reminder ladder with one-tap reschedule
No-show rate
Up 11 percentage points across 40 practitioners at Halden Group
Resource utilisation
71% of cancelled slots refilled from the waitlist within 2 hours
Cancellation refill
Down 38% in the first quarter after self-service rescheduling went live
Booking call volume

Modules

What ships in the box

  • Resource and capacity modelling
  • Availability and slot generation
  • Booking, rescheduling and cancellation
  • Deposits, fees and payments
  • Reminders, waitlists and no-show handling
  • Utilisation reporting and rosters

Integrates with

  • Google Calendar
  • Microsoft 365
  • Twilio
  • Stripe
  • Razorpay
  • ABDM
  • Zoom
  • Salesforce

Capabilities

What it does

  • Multi-resource requirements

    A service declares what it needs: a qualified practitioner, a room of a given type, named equipment and a buffer. Slots appear only where all of it is free, buffers included.

  • Rule-driven slot generation

    Availability comes from working patterns, exceptions, holidays and capacity caps rather than pre-created rows. Change a pattern and future dates recompute without touching bookings.

  • Waitlists with automatic refill

    Cancellations offer the freed slot to waitlisted customers in priority order with a short acceptance window, moving to the next candidate on expiry until the slot is taken.

  • Deposits and cancellation policies

    Policies set per service: deposit amount, free-cancellation window, late-cancellation and no-show fees. The customer sees the terms before confirming, and the charge cites them.

  • Reminder sequences

    Configurable ladders across SMS, email and WhatsApp with per-channel timing, quiet hours and a one-tap confirm or reschedule link carrying a signed token rather than a login.

  • Overbooking and buffer controls

    Deliberate overbooking is set per service with a cap and an absorption rule, so a clinic can run at 105% expecting no-shows without the grid silently double-booking a room.

  • Time zone and daylight-saving safety

    Bookings store an instant plus the originating zone, so an appointment made in March for October does not move by an hour, and cross-border sessions render for both parties.

  • Calendar synchronisation

    Two-way sync with Google Calendar and Microsoft 365 keeps practitioner busy time out of the bookable grid, with conflict rules deciding which side wins when a window is claimed twice.

FAQ

Questions we get asked

How large a grid can the availability engine handle?

A 90-day view across 40 practitioners and 25 rooms computes in under a second on a single application node, because slots are derived from rules and cached briefly rather than stored row by row. Beyond roughly 200 concurrent resources, we shard availability by site.

Can patients or customers reschedule without creating an account?

Yes. Reminder links carry a signed, single-purpose token with a short expiry that permits viewing, confirming, rescheduling or cancelling that one booking. Anything else, such as viewing history or documents, requires a login.

Does it replace our clinical or practice management system?

No. It handles capacity and appointments and hands the encounter to your clinical system through HL7 FHIR or a REST bridge. Clinical records, billing codes and prescriptions stay where your clinicians and auditors already expect to find them.

Start a project

Tell us what is
breaking.

We reply within one working day, and the first call is with an engineer who would actually work on it — not an account manager. If we are not the right studio for the problem, we will say so on that call.

Start a project