Bot for booking with prepayment: how to check reservations, transfers and cancellations

What to check in the schedule

Describe the services, duration, breaks and rules for choosing a specialist. An hour slot and an hour and a half slot cannot be considered one entry. If a foreman works in two branches, his time must be reserved consistently; otherwise, each branch will show the same hour as free.

Check boundaries: last visit before closing, moving to another day, master's break and rescheduling. The client should see the time zone and a clear date. Changing the working day should not delete already confirmed entries without leaving a trace.

How to link a reservation and prepayment

The reservation has a period and condition. After its creation, the client receives payment associated with a specific order. Until the result is confirmed by the server, the entry should not be called paid. Returning to the page from the bank is not proof of payment.

A separate scenario: the money came after the reserve expired. Decide in advance whether the recording will be reinstated when time is available, a different slot will be offered, or a refund will be made. This business rule should be in the statement of work, and not appear after a client complaint.

Acceptance checklist

1. Two clients choose one last slot. Only one compatible reservation will be confirmed.
2. The client closes the payment: the reserve expires according to the agreed rule.
3. The payment notification comes again: the amount and entry are not doubled.
4. The client reschedules the visit: the old time is freed, the new one is actually available.
5. The administrator cancels the entry: the client receives the message and sees the current status.
6. After the return, finances and recording are agreed upon.
7. A reminder is not sent for a canceled or rescheduled old appointment.

Administrator's work

The administrator needs a record search, a change log, a manual transfer, and a clear reason for the failure. The master can see his workload, but access to the full client database is role dependent. Customer mailings and technical notices should have different rules and purposes.

If Telegram is unavailable, the notification may be delayed. Therefore, the record is stored in the main system, and the delivery of the message has a separate state. The message cannot be considered the only evidence of an existing reservation.

Demo and development

B demo recordings in a barbershop you can go through the client and owner interface using fictitious data. The demo does not prove the operation of real acquiring: payment integration is tested separately in a test environment.

For advice on bot development Prepare services, schedules, and cancellation policies. A general overview of the possibilities is in the article about client records; This material is dedicated specifically to testing the finished script.