Customer
Book and track service
System evidence overview
Home-services marketplace architecture. Strong Solution pattern proof for home-service-app.
No invented clients, ROI, revenue, uptime, certifications, or fake metrics.
Layers
Workflow
Shield
Users
Cpu
Layout Dashboard
Book and track service
Accept and fulfill jobs
SLA and quality control
Illustrative system lifecycle
Step 1 / 5
Book
Customer booking experience.
Product modules
A cashless, location-aware service ecosystem coordinating customers, verified technicians, operations teams, payments, SLA enforcement, and quality-controlled aftercare.
Explore how the operations console coordinates address geocoding, proximity availability, cashless checkouts, and dispute holding loops.
Simulator Ready
Click "Confirm & Find Tech" in Customer App to trigger dispatch telemetry
Riyadh's home-services market faced deep friction around technician scheduling, service delays, and trust in cash-only transactions.
Manual Matching: Operations dispatchers had no automated proximity checks, leading to severe scheduling delays.
SLA Negligence: Lack of arrival guarantees or live tracking caused high no-show rates.
Cash Friction: Bypassed pricing structures and direct cash disputes compromised platform integrity.
KYC Verification Gaps: Operations lacked systematic checks for vendor licenses, certifications, and background checks.
Pricing Inconsistencies: Arbitrary pricing calculations for materials and service charges eroded customer trust.
Quality Disputes: No clear rework windows or holding patterns to protect customers from low-quality repairs.
A unified operations engine coordinating customer interfaces, vendor applications, and an administrative console. Built-in geofenced matching priorities, cashless checkouts, 3-day dispute holding loops, and modular AMC capability build accountability into every visit.
The platform coordinates service requests, proximity validations, diagnostic compliance, and cashless quality hold release under strict SLA guardrails.
Customer browses bilingual Arabic/English catalog, marks geocoded address coordinates in Riyadh, and initiates cashless authorization.
Matching engine sweeps Olaya/Al-Malaz grids, checks capacity rules (min 3 vendors active), and dispatches work order parameters.
Technician completes geofenced check-in, fills standard diagnostic forms, requests approval for materials, and marks job done.
A 30 SAR platform fee is processed. Fund payout enters a 3-day dispute buffer window, followed by a 45-day quality hold release loop.
Integrated services running customer experiences, technician dispatch apps, and administrative controls.
Bilingual service search, address geocoding, and slot selection.
Onboarding KYC wizards, job queues, route mapping, and diagnostics checklist.
Riyadh zone mapping, availability checks, priority matching, and escalation rules.
Structured sub-service categories and localized Arabic content schemas.
Unified cashless checkouts, platform fees, ledgers, and 45-day holds.
3-day dispute windows, revisit branches, and vendor ratings impact rules.
Basic/Standard/Premium visibility rights, AMC schedules, and emergency dispatch.
Live monitoring maps, verification queues, and extra-cost approvals.
API gateways, PostgreSQL/Redis schemas, token verification, and encryption.
Detailed screens, telemetry flows, and engineering specifications across all core modules.
Service categories, geocoded address selection, scheduled checkouts, and tracking.
KYC profiles, radial availability, job details, diagnostics check sheets, and payouts.
Zonal routing grid, match sequence priorities, SLA tracking, and manual overrides.
Sub-service catalog structures, vendor skills, and localized Arabic schemas.
Checkout gateway, commission tables, ledgers, holding queues, and reconciliation.
Dispute intakes, evidence collection, free revisits, penalties, and rating impact.
Vendor membership packages, recurring AMC calendars, and corporate contracts.
Operational dashboards, maps, exception monitoring, and settlement lists.
NestJS APIs, PostgreSQL/Redis configurations, and JWT token authentication.
Share operational roles, checkpoints, and integration constraints. We map architecture boundaries without inventing fixed timelines from a form submission.