Skip to content
Guide

Bookings when the power cuts: what stays and what does not

By Fayez AlshamiPublished: 3 min read
TL;DR

A calendar on a server outside the shop survives when the router dies. What you lose is the clerk's reply and the front-desk screen. The customer's confirmation has to leave before the cut, not sit on a laptop that never charged.

A clinic in Maadi goes dark for two hours after noon. The clerk kept appointments in Excel on the desktop, and the desktop's UPS lasts about ten minutes. The customer calls. There is no screen, and there is no last copy. The paper book that was "for emergencies" has not been written in for a month, because Excel was easier.

Power cuts in Syria are not a footnote. They are a design constraint. A system that lives only on a machine inside the shop dies with the machine.

Where the appointment is stored

On a server outside the shop, with the database backup the host already runs. The slot locks in that table, not in a file on the desktop. When the power returns, the screen reads the same rows. A booking confirmed at 1 p.m. does not wait for the clerk to boot the PC before it "saves."

If the router is down, WhatsApp on the clerk's phone may still work on mobile data. That is not enough when the phone is the only place that holds the sentence "you're booked." The confirmation is a message that leaves at that moment: branch, name, time. If the front desk screen is gone, the customer still has the text. After the lights return, the clerk opens the system and sees the same hour.

The notebook versus messages alone is a booking system versus WhatsApp appointments. Messages with no shared table contradict each other when two people answer from two phones in the dark. The Arabic clinic flow, including the lock on the chair, is WhatsApp clinic booking.

What the server does not promise

If the customer's mobile network is weak and the confirmation never arrives, they do not know they are booked. Do not fix that with a second "just in case" slot on paper. Ask them to reopen the chat when they have signal. There is one row. A paper duplicate is the double booking you were trying to leave.

A cafe kitchen has the same limit. The ticket on the server remains. A thermal printer with no power does not print. Someone reads the ticket from a phone on mobile data, or you wait for the lights. No program cooks without power in the room.

A barber with two branches keeps each branch's table on the server as well. A cut in Jaramana does not erase Sahnaia. It only stops the people answering from the dark shop. That layout is barber booking across branches.

A cheap habit before any software

At the end of the day, export tomorrow's appointments to a message the clerk sends herself. That is a fallback if the host is unreachable for an hour, not a replacement for the table. The paper copy is thrown out when the lights return, so the notebook does not start booking on top of the system.

I host these tables off the shop's network because power in Damascus is not part of the customer's contract. What I am on the hook for is that the row remains. What I am not on the hook for is a dark shop receiving people as if electricity were a detail.

Frequently asked questions

If a customer books while my shop is dark, is the slot saved?

If the bot and the table are on the server and the customer's network is up, yes, even while your shop is off. You see it when the screen comes back.

Is the old front-desk phone enough?

It is enough to reply, if it has data. It is not enough to be the database. The page that reads the table from the server is the screen. The phone is just glass.

Do I need a generator for booking to work?

A generator brings the lights back so you can receive the person at the door. The booking itself does not wait for the generator if the row lives outside the shop.

Guides & comparisons

Need this built or connected for your business?

See services