AIArcsen implements Salesforce Field Service for facilities managers and real estate developers in the Gulf and Egypt, from planned maintenance and emergency call-outs to snagging before handover. Technicians get the right job, the parts and the asset history on an offline mobile app, and completed work reaches billing in the ERP without retyping.
What we build
The right technician arrives with the parts and the history.
Work orders by territory and skill
We set up service territories, skills, operating hours and work types for planned preventive maintenance (PPM), inspections and emergencies, so each job goes to a qualified technician nearby. Maintenance plans raise PPM work orders on schedule from the asset record.
Scheduling and dispatch
Salesforce’s scheduling and optimization engine builds the day, and dispatchers adjust it on the dispatch console’s Gantt chart. For emergencies, the console finds the closest available qualified technician, and scheduling policies weigh travel, priority and service-level deadlines.
A mobile app that works offline
The Salesforce Field Service app for iOS and Android is built offline-first. Technicians in basements, plant rooms and remote sites still see their jobs and asset history, complete service reports with customer signatures, and sync when the signal returns.
Customers book their own visits
Appointment Assistant lets customers book, change and track an appointment, and bookings can also come from an app, a chatbot or the contact centre. Every booking becomes a service appointment the dispatcher can see and move.
Subcontractors on the same schedule
Contractor Plus licences give subcontractors a secure portal and the mobile app, so their jobs, times and proof of completion sit beside your own teams’ work, under the same service levels and the same reporting.
Parts, billing and briefs
Technicians record the parts they use from van stock, and completed work orders flow to billing in Oracle Fusion or your ERP. Agentforce can prepare a pre-work brief, so the technician arrives knowing the asset and its history.
Client work
From planned maintenance to handover day.
How we deliver
One territory first, then the whole operation.
Assess the operation
We map work types, territories, skills, contracts and the tools you run today. If you already run Salesforce, the free Salesforce Health Check scores the org in ten working days, and the report is yours to keep.
Design the schedule and the app
Scheduling policies, service-level rules and technician screens are designed with dispatchers and senior technicians, then tested against real jobs from your history before anything goes live.
Pilot, then roll out
One territory or service line goes live first. We tune the scheduling with your dispatchers, fix what technicians report, then add territories, subcontractors and customer self-booking in planned releases.
Run with managed services
Our managed services team supports dispatchers and technicians after go-live, keeps the app and integrations current through Salesforce’s three releases a year, and adjusts scheduling as the operation grows.
Questions we get
Asked by every buyer, answered straight.
Do we need Service Cloud to use Field Service?
Yes. Salesforce now sells the product as Field Service and Operations (it began as Field Service Lightning), and it requires at least one Service Cloud user licence. Dispatchers, technicians and contractors take their own licences, and an existing Service Cloud org needs at least one Dispatcher licence.
Does the mobile app work offline and in Arabic?
Offline, yes: the app is designed offline-first, and we define which records each technician carries before a shift. Arabic is among the app’s languages, but Salesforce’s right-to-left support for Field Service covers Hebrew only, in beta, so we test every technician screen in Arabic before go-live.
Can Field Service connect to Oracle Fusion, SAP or our CAFM system?
Yes. Through MuleSoft or APIs, customers, contracts, assets and price lists come from the ERP, and completed work returns for billing; at Ejadah, billing goes into Oracle Fusion. Where an existing asset or CAFM system stays, we agree which system owns each record before build.
How long does a rollout take?
It depends on the work types, the number of territories and the integrations. We usually start with one territory or service line, tune scheduling on live jobs, then add territories in releases. Technicians train on the app before go-live, and dispatchers have their console from the first day.
Check the foundations before the first van rolls out.
Start with a free Salesforce health check
Or talk to the team. See also: Real estate clients · Manufacturing clients.