Automotive Operations
Customer portals and apps for UAE automotive service businesses
When every booking and status question goes through a phone call, staff time goes to the counter. We build customer apps and staff portals that connect to the workshop system you already run, in Arabic and English.
Delivered: customer apps and staff portal for EVS (Electric Vehicle Services).
- Service centres & EV networks
- Customer-experience leads
- Multi-branch operations teams
Where it breaks today
Where the customer journey stalls.
Common patterns in the sector, not a description of a specific organisation.
Booking needs a call or a visit
Customers phone or walk in to book, and the front desk re-keys vehicle and service details. Outside working hours nobody takes the booking.
Status questions fill the phone line
Customers call to ask where their car is, and advisers chase the workshop for an answer.
The record is locked inside the workshop system
Service history and the next service due exist, but customers can’t see them without asking.
A connected workflow
From a booking to a status update.
An illustrative starting point. We adapt the steps, roles and controls to your organisation.
Book
The customer picks a branch, a service and a free slot in the app, in Arabic or English.
Sync
The booking reaches the workshop system with the vehicle and service details filled in.
Work
Staff run the job in the system they already use; the portal reads its stages.
Update
The customer sees progress and history in the app, with notifications as the work moves.
What we’d build first · illustrative
Start with one workflow, end to end.
A possible first scope, not a delivered project. The real one is agreed with your team after discovery.
Customer app: booking and status
Branch, service and slot booking, vehicle records and job status for customers, on iOS and Android. This is the scope we delivered for EVS.
Staff web portal
Customers, vehicles, bookings and app content managed by your team in one place.
Integration with your workshop system
Bookings and job stages synchronised with the system you keep, subject to the interfaces it offers.
Job cards, approvals, parts and billing
Scoped separately as a later phase where your workflow needs them. Not part of the delivered EVS scope.
What we can scope next · not yet delivered
Repeated enquiries, answered from approved information.
Not part of the delivered EVS scope. This is AI-assisted enquiry handling we can scope next, for service businesses whose staff answer the same booking and status questions all day. It builds on a delivered portal; it is not a claim about results.
Intake
A customer asks by app, web or message, in Arabic or English, including outside working hours.
Look up
The assistant answers only from approved information: opening hours, services, booking availability and the customer’s own job status.
Book or prepare
It offers free slots or prepares the booking details for staff to confirm.
Hand off
Anything sensitive, unclear or outside the approved information goes to a named person, with the conversation attached.
Repeated status questions
“Where is my car?” answered from the workshop system’s job stages, for the signed-in customer only.
After-hours intake
Requests captured and queued with the details staff need in the morning.
Source-controlled replies
Answers drawn only from content your team approves and can update.
Human handoff
Identity-sensitive requests, complaints and pricing questions always reach a person.
A practical starting point
Tailored to your operation.
We don’t sell a packaged product for this sector. We have delivered customer apps and a staff portal for EVS (Electric Vehicle Services). For your operation, we build the workflow around how you work, then host and operate it on Azure, AWS or private servers managed by Vloud.
- Delivered for clients
Customer apps and staff portal for EVS (Electric Vehicle Services).
Here is the kind of work we have delivered.
See the delivered customer app and staff portal - Engineering capability
Mobile Application Development
iOS and Android applications for teams that work away from a desk, sharing one architecture with the web.
Explore - Hosted and operated
Hosted and operated for you
We can host on Azure, AWS or private servers managed by Vloud. Vloud is the hosting control panel we build and own, and ErrorLens, our monitoring product, helps us see issues in the systems we run. Hosting, support scope and operational ownership are agreed during scoping.
Explore - Illustrative engagement
A system for the workflow no SaaS supports
An illustrative engagement for an operations leader whose business-critical workflow runs on spreadsheets, email approvals, manual reporting and disconnected data.
See the example
What we ask a service business first
Do we have to replace our workshop software?
No. EVS kept its workshop system; the apps and staff portal synchronise with it. We first check what interfaces your system offers and which system owns each record.
How are booking conflicts and data sync handled?
First agree which system decides slot availability and owns vehicle, booking and job records. The scope should distinguish a pending request from a confirmed booking and define what staff do when synchronisation fails. Test competing slot requests and a lost confirmation response against your workshop interface before launch.
Can customers see only their own records?
Yes. Sign-in and access are designed so each customer sees their own vehicles, bookings and history, and staff see what their role allows.
What needs a separate phase?
Job-card approvals, parts and billing are separate pieces of work. We scope them on their own once the customer journey is live, rather than promising everything in the first release.
What evidence should we ask for before accepting the integration?
Ask to follow one test booking from the customer request to the workshop's accepted reference, then test a rejected request, an uncertain response and a retry. Include two customers requesting the same slot and an account trying to view another customer's vehicle. These are proposed acceptance checks for your project, not a claim that every workshop product supports the same interface.
Does the EVS project prove compatibility with our workshop software?
It proves the delivered EVS scope: Arabic-first customer apps, a staff portal and two-way synchronisation with the workshop system EVS retained. Your supplier, product version, available interfaces and permissions still need checking. It does not establish a ready-made connector for another system.
What should we prepare before discussing a customer portal?
Start with one customer task, such as booking a service or checking repair status. Name the workshop system you use, describe how branches share bookings, and tell us who can confirm its available interfaces. Note which system holds customer, vehicle, slot and job records, if you know. A short description is enough for the first call; keep customer details out of the initial enquiry.
More about this sector
Is this a ready-made garage software subscription?
No. We build a customer portal or app around your workflow and connect it to the system you keep. If a packaged workshop product already covers what you need, that may be the better route, and we'll say so.
Can the app be Arabic-first?
Yes. The EVS customer apps are Arabic-first with English alongside, including right-to-left layouts.
Can several branches share it?
Yes. If branches or partner stations share customers, slots or technicians, we design for that at the architecture stage.
Who handles releases and support after launch?
Your choice. We can host the system, handle store releases and fixes, or hand it to your team with documentation. The arrangement is agreed in the proposal.
Before you ask
Who owns the code?
You do, for the custom work we build for you. It is set out in the engagement agreement. Our own products stay ours.
Is our data ours?
Yes: your data belongs to you.
Will you sign an NDA?
If you need one, yes.
How do we start?
With a free 30-minute discovery call about the workflow, then a short discovery that turns it into an architecture and a phased plan.
How long will it take?
It depends on scope. We confirm scope, timeline and price in a written proposal after discovery.
Where is it hosted?
We can host in-region when data residency matters, or deploy to your own cloud account instead.
Explore further
Other industry perspectives.
- Product-backed: ArkanCS · ArkanERP · ArkanPM
Construction & Real Estate
Project controls, document workflows, inspections, payments, property operations and reporting. - Custom-built for your workflow · ArkanERP for project-driven businesses
Enterprise Operations
Internal systems, cross-department workflows, approvals, reporting and automation. - Custom-built for your workflow · Demonstrated in this sector
Government & Public Sector
Digital services, internal workflows, approvals, compliance and operational visibility. - Product-backed: LuminaEduSync
Education
Timetabling, teaching assignments, room bookings and the daily changes that disrupt the school day.
Start a conversation
What should your customers be able to do from the phone?.
Free 30-minute discovery call. Bring the workflow; we’ll tell you whether it’s a product fit, a custom build or neither.