BBomerang.ioAI agents and automation
All case studies
In productionAppointments and clinic sync

WhatsApp appointments on top of a scheduling system from 1998

Patients book appointments over WhatsApp and the booking is also recorded in the old Admissions system, without creating a second schedule.

How the data flows

  1. WhatsApp booking
  2. Web backend
  3. Agent on the PC
  4. Admissions VB6

2systems, one schedule

Client
Unimed
Industry
Medical center
Where
Argentina
Integrations
WhatsApp, Admissions VB6

The context

A medical center that gets patients over WhatsApp every day, but whose official schedule lives in Admissions: a Visual Basic 6 system on a Windows 7 PC. The staff had to keep working the way they always had.

The problem

The bot had to offer real appointments without replacing that system or creating a parallel schedule that would drift out of sync. Two schedules that don't talk to each other are worse than no bot.

What we built

  1. 01The bot talks on WhatsApp and books against a web backend.
  2. 02An agent installed on the clinic's PC syncs every change with Admissions in both directions.
  3. 03The backend adds deterministic locks to prevent duplicate appointments, wrong tests and booking loops.

What changed

  • Patients book over WhatsApp against real availability.
  • Staff keep using their usual system, with both schedules coordinated automatically.

Stack

Next.js 15React 19Neonn8nNode.jsVercel

Connects with

WhatsAppAdmissions VB6

Design something similar for your operation

No system is copied and pasted: what works here came from how this business runs. Tell us about yours and we will see what fits.

Tell us about your case

Other case studies