CALL-E

RingBack

An open slot. Filled by phone. When an appointment opens up, RingBack calls the waiting list in order. The first person to accept gets the slot, and the result updates the local appointment book.

Built by Ludo321 with CALL-E. Honorable Mention · CALL-E Hackathon.

Watch the demo Explore the local demo

A local Python application. Simulation is the default. The submitted video uses simulation and a local calendar.

Concept illustration of a service studio, a yellow telephone and an appointment block beside an empty diary slot.

One slot. One acceptance.

The app keeps the appointment state connected to the calling sequence, including cancellations, rescheduling and outcomes that need a person.

  1. Choose the opening

    Select the appointment slot and eligible waiting-list contacts. Review the proposed campaign and its calling conditions.

  2. Offer it in order

    Ask one person at a time. A clear acceptance stops calls to the remaining contacts for that opening.

  3. Update the diary

    Check the result and slot availability before saving. Ambiguous results or multiple possible old bookings need human continuation.

A replacement booking in the diary.

Illustrative waitlist and booking. The author’s video demonstrates the flow in simulation.

First contact
Declines the offered time. Continue.
Second contact
Accepts the opening. Check that it is still available.
Local booking
Save the confirmed replacement and stop the sequence.
Remaining contacts
Not called for that opening.

The app uses its own local diary, with CSV and ICS imports. It does not provide two-way Google Calendar or Outlook synchronization.

Try an opening in simulation.

Load the demo data, choose an appointment opening and follow the waiting list through to an updated local diary.

Open the author’s local setup

Start in simulation.

The author’s quick start runs a local web interface with Python 3.12 and its standard library. Demo data, CSV and ICS imports let you inspect the appointment flow before configuring real calls.

  • Test the stop rule. A confirmed acceptance should leave later contacts uncalled for that slot.
  • Check before saving. Recheck slot availability and resolve which earlier booking should be released.
  • Recover uncertain results. Keep an available call ID and read its result before deciding on another attempt.
  • Make follow-up deliberate. The app queues follow-ups for a person to trigger.

If a real call request times out before returning a call ID, reconcile that attempt before retrying.

The author’s application is in a repository with an MIT license. The linked setup instructions apply to that source version.

Follow one opening.

Watch the simulated sequence, then inspect it in the local app.

Watch the demo Open local setup

RingBack is contributed by Ludo321. CALL-E maintains this case guide. The studio illustration and written waitlist example are conceptual; they are not product screenshots, call records or evidence of revenue.