Services and availability
Define service durations, prices, staff availability and any shared resource requirements. Agree how changes affect existing appointments.
TAILORED BUSINESS SYSTEMS · EGYPT
Appointments organised around your team and services.
An appointment is more than a time in a calendar. It may depend on a particular employee, a service duration, a room, a deposit or a cancellation rule. Rukivo builds booking systems around those details for service businesses in Egypt.
We start with how a booking is requested, confirmed, changed and completed. That makes it possible to agree sensible availability checks and a clear client record before choosing extra calendar or messaging connections.
WHAT WE CAN SCOPE
The details that make the system useful.
Client and appointment records
Keep booking history, client details and relevant notes together. Limit access to the information each role needs.
Deposits and booking status
Track agreed deposits, outstanding amounts and cancellation or rescheduling stages. Actual payment processing is a separate integration to scope.
Calendar connections and reminders
Discuss supported calendar APIs and notification providers. Define who receives reminders, when they are sent and the approval or consent requirements.
AN EXAMPLE TO DISCUSS
Follow a complete workflow.
This illustrates a possible scope. Your rules, connections and acceptance checks are agreed separately. Demo companies and records are fictional.
- Choose a service, member of staff and available time.
- Confirm the appointment and record an agreed deposit.
- Reschedule or complete it while keeping the original booking history.
Questions that shape your quote.
- Which services, staff, rooms and availability rules must be coordinated?
- What are your deposit, cancellation and no-show rules?
- Will clients request bookings themselves, or will your team enter them?
BUILT TO SCOPE
A clear scope before a clear price.
Focused basic systems are EGP 10,000–18,000 to build. Connected systems with agreed integrations are EGP 18,000–40,000. Multiple systems and multiple integrations receive a custom quote. Every system also has a monthly running subscription of EGP 2,000–5,000 for the agreed domain, database, hosting and infrastructure. Optional SKU/barcode labels are EGP 3,000–5,000 once; one additional API connection is EGP 5,000–10,000 once; AI assistance is an additional EGP 3,000–10,000 per month. Final pricing, inclusions and usage limits depend on your needs and written scope.
Compare packages and add-onsBefore we build together.
Can it prevent overlapping appointments?
We can build availability checks around the agreed staff, duration and resource rules. The demo includes staff overlap checks; your production rules are reviewed separately.
Will it automatically send WhatsApp messages?
Messaging needs a suitable provider and an explicitly agreed integration. Provider charges and supported actions are confirmed before launch; the demo sends no messages.
Can customers book through a portal?
A client-facing booking flow can be included in the project scope. Account access, booking approval and which details clients can see must be agreed.
Start with the work you want to improve.
Tell us what happens today and what a better process should look like.
Complete your project brief