One operational workspace from verification to payout.
Verify how service shops and individual technicians register credentials, manage radial zone availability, accept dispatch tickets, submit extra-cost requests, and clear quality-hold ledgers.
Interactive Technician Workspace
Toggle verification profiles, simulate incoming jobs, submit extra-cost approval checksheets, and view earnings settlement logs.
Technician Operations Terminal
Iqama document verification checklist completed. Verification audits checked manually by admin staff.
Technician SLA & Compliance Board
Telemetry updates, credentials validations, Iqama identity audits, and 45-day payout locks.
Direct off-platform cash requests from customers are strictly monitored. All invoices must compile base diagnosis and controlled material-cost approvals. Quality hold locks settlement for 45 days.
Operational Onboarding & KYC Checklists
Technicians and service shops undergo validation checks prior to joining the active Riyadh matching dispatch grid. Administrative consoles handle Iqama records, certifications, and licenses. Under compliance guidelines, no realistic identity documents are displayed.
Category Capabilities & coverage
Verified technicians are mapped to specific capability profiles. This determines their eligibility within search filters (e.g. AC Maintenance, Plumbing Repairs). Subscription priorities determine queue order, and no fixed subscription pricing ranges are exposed.
Dispatch Ticket Acceptance Gates
When a customer requests a service in Riyadh, the dispatch engine calculates proximity parameters and pushes a ticket to eligible technicians. Technicians have a fixed, deterministic accept/reject window. Countdown visuals are static to prevent server-side rendering inconsistencies.
Route Telemetry & Issue Diagnosis
Once accepted, the technician updates dispatch logs through standard workflow checkpoints (Accepted → Route Started → Arrived). On-site, technicians complete diagnostic forms outlining defects before starting any repairs.
Coordinates matching rules prevent technicians from marking arrival if located outside geofence bounds.
Technicians can select predefined delay reasons to keep operations teams informed of exceptions.
Enforces diagnostic checklists prior to submitting billing updates or starting work logs.
Controlled Extra-Cost Approval
If materials or replacement tools are required, technicians submit extra-cost requests via the mobile app. The request requires photos of receipts and formal confirmation from both the customer and admin team. Direct off-platform payment collection is strictly forbidden.
Completion Verification & Evidence Audits
To close a ticket, technicians are required to upload before-and-after photos of the work area. Once verified by customer signature, a final diagnostic checksheet confirms completion, releasing the base visitation record to the finance ledger.
Earning Ledgers & Payout holds
Settlement & Payout Quality Controls
Earnings are processed cashless (minus the standard 30 SAR platform cut). Fund payout is subject to a 3-day customer complaint window and a 45-day payout quality hold. This ensure funds remain available in quality hold for rework warrants if quality failures are reported.
Have a complex workflow that needs a custom platform?
We can map your operations, design the software architecture, and build the dashboards, apps, and automation layers needed to run it.