Field Service Ops Dispatch Platform
Community blueprint for operations teams: technician dispatch, SLA tracking, mobile checklists, and service reports.
Original user prompt
Build a field service operations platform for scheduling technicians, dispatching jobs, tracking SLA timers, and producing signed service reports.
Advanced outputs (CLAUDE.md, .cursorrules, Master Prompt)
Recommended Tech Stack
Recommended: - Next.js web console for dispatchers. - PWA/mobile web for technicians. - Postgres + Prisma for job lifecycle data. - Redis for live dispatch board updates. - Queue workers for SLA alerts and report exports. - Map provider API for routing ETA estimates. Why: - Clear state machine + async jobs are critical in ops tools. - PWA gives near-native workflow without full mobile app cost. Alternatives: - Native mobile app in V2 for heavy offline requirements. - Kafka if event volume outgrows queue-based approach.
🚀 Submit this blueprint to the Community Gallery
Your submissions are protected: anti-bot reCAPTCHA, daily anti-flood limits, data deleted after 14 days, zero account required. Only title + JSON are used for the gallery. Privacy policy: vibemeta.app/privacy
Why this prompt works
This blueprint targets high-intent operational searches with concrete dispatch architecture, SLA modeling, and offline behavior. It demonstrates that VibeMeta output is implementation-ready even for state-machine-heavy products.
How to use it in your project
- Start by implementing the state machine and transition tests.
- Keep offline idempotency requirements unchanged.
- Integrate map/ETA providers only after core dispatch flow is stable.
- Use MVP report generation before adding advanced optimization features.
Share this page or copy the full JSON to reuse the blueprint quickly.