A connected set of tools for a car rental agency in Tangier: the website presents vehicles and collects requests, while the application and CRM support ongoing management of the business.
Internal project
The workflow in four steps
Reservation
Choose dates and submit a request to the rental agency.
Contract
Prepare the rental file after the agency confirms the request.
Operations
Track the vehicle, schedule and rental extensions.
Return
Close the rental and retain its history.
Understand the implementation
Behind each booking, an entire rental operation
The public website is the entrance to this project. BX Cars connects online bookings, daily agency operations and an Android application. The same information needs to remain useful from the first date selection to the return of the vehicle.
01
One vehicle, several connected workflows
A customer may be choosing a vehicle while the agency extends an existing rental. Availability therefore accounts for both reservations and active contracts. The public calendar and operational schedule use the same underlying records.
The agency must confirm the request. The contract then follows the rental through preparation, approval, extension, closure or cancellation. The customer record retains information that can be reused for a subsequent rental.
Explore the interface
Demonstration based on the project code. Interactions stay on this page and all data is fictional.
Amounts in the BX Cars demo are fictional and shown in euros for the Belgian portfolio. They are not the agency’s rates.
The interface shown is in French.
Try it in this preview
Open “Try an approval” in the preview.
Approve one of the fictional requests.
Return to the overview, then reset the demo to try again.
What to look for The pending count goes down and the confirmed count goes up. Approval is simulated: no email is sent and no real reservation is created.
Loading the demonstration…
How the solution works
02
From a photograph to a usable record
A contract photograph submitted through Telegram can become a draft through text recognition. The agency checks the extracted information before approving it. Automatic recognition prepares the work; the review remains a distinct step.
The record then joins the contract, customer and scheduling workflows. This continuity matters: checked information becomes useful further along the process instead of being entered again in separate tools.
03
An application built for daily operations
The dashboard brings together pending requests, vehicles out on rental and returns to monitor. Fleet management also covers expenses, vehicle documents and maintenance. Mileage readings help prepare maintenance schedules.
Android notifications concern relevant business changes. Routine GPS readings do not generate a constant stream of alerts. The application supports work on the move with adapted access to operational screens and records.
04
Recognising a customer beyond the booking
The CRM keeps previous rental history and driving ratings in the customer record. When someone returns, the agency can pick up the relevant context instead of starting from scratch.
That continuity helps assess trust before another rental. The history and rating inform the agency’s decision; they do not guarantee how a future rental will go.
Technical choices and their purpose
A shared foundation for business rules
Laravel and MySQL connect vehicles, reservations, contracts and customers. Availability rules are central: an extension must remain consistent with the dates offered elsewhere.
Integrations with specific responsibilities
Telegram and n8n help prepare records; Wialon supplies fleet data; Firebase delivers Android notifications. PDF documents support rental administration. Each integration belongs to a defined workflow.
A platform for the whole agency
The public website, management workspace and Android application share the information needed to run the business. Bookings, contracts and fleet follow-up form one connected journey.
Website and bookings
Vehicle presentation, availability by date and price estimates. The journey is available in French, English, Dutch and Arabic, with requests confirmed by the agency.
Daily operations
A dashboard and schedule bring together requests, active rentals, departures, returns and delays. Access is organised around each team member’s role.
CRM, contracts and customer records
Preparing, approving, extending and closing contracts, with checks for date conflicts. Documents, previous rentals and driving ratings are brought together in the CRM. When a customer returns, the agency can review their history to assess trust and make an informed decision about the next rental.
Android application
The team can use management tools in the field and receive notifications when important changes occur. The interface is adapted for phones.
Fleet and telemetry
GPS tracking, mileage and alerts support vehicle management. Maintenance schedules and expenses can be viewed by vehicle.
Contract automation
A photo submitted through Telegram is analysed using text recognition to prepare a draft. The team checks the information before approval; summaries support follow-up.
A connected journey with human approval
01
A booking or contract photo provides the initial information.
02
The team checks the record, dates and vehicle before approval.
03
Scheduling, contracts and fleet follow-up support the rental through to its return.
Visit the public website
The link opens the project website. Private workspaces require authorised access.
