FIELD SERVICE OPERATIONS

One platform. Every tenant under its own URL path.

Dispatch tickets, run customer portals, and equip technicians — isolated per company with path-based tenancy /o/{slug}/….

Start as org admin Already have access?Routes & developer setup →

Built for real field operations

Dispatchers lose visibility when tickets, customer updates, and technician notes live in separate channels. Service Ticket SaaS centralizes the lifecycle — from intake through assignment and completion — with path-based tenancy so every organization keeps its own URL space and data boundary.

Tenancy

One slug per org — /o/{slug}/a|c|t/…

Roles

Admin, customer, technician, platform operator

Security posture

JWT + HttpOnly cookies; APIs scoped by tenant

Extensibility

Workflow hints, attachments, offline-ready technician shell

How to get started

Pick the path that matches your role — each uses the same secure signup and login APIs.

Admin

Organization Admin

Create your company, pick a URL slug, and open your admin console. Manage tickets, invite staff, and build your customer directory.

Create organization

Portal

Team & Customers

Use the link your service provider sent you to join. Once registered, simply use the unified login to access your role-specific dashboard.

Lifecycle of a ticket

The journey of a ticket from reporting to resolution with Reviewer oversight.

1. Intake

New

Customer or Admin creates the ticket outlining the reported issue. It awaits dispatcher assignment.

2. Execution

Assigned → In Progress

A Technician is dispatched to the field. They log materials, add photo evidence, and manage the repair.

3. QA & Review

Review

The Technician submits the work for review. The Reviewer role evaluates the evidence in their Review Queue.

4. Governance

Audit

Sensitive changes like email updates or password resets require a Governance Request, creating an immutable audit trail.

5. Resolution

Resolved

The Reviewer approves the ticket, finalizing the timeline and permanently closing the loop with the Customer.

How it works

Get your team up and running in minutes. Our multi-tenant architecture ensures complete data isolation.

Admin

Organization Admin

Create your company, pick a URL slug, and open your admin console. Manage tickets, invite staff, and build your customer directory.

Create organization →

Portal

Team & Customers

Use the link your service provider sent you to join. Once registered, simply use the unified login to access your role-specific dashboard.

Unified URL Reference

Every organization and portal lives under its own path.

Admin Console

/o/[slug]/a/dashboard

Complete oversight. Tickets, customers, technicians, and settings.

Technician App

/o/[slug]/t/jobs

Native-feel PWA. Map views, job checklists, and status updates.

Customer Portal

/o/[slug]/c/my-tickets

Self-service transparency. Request help, track history, and view files.

URL cheat sheet

Admin app · /o/your-slug/a/dashboard
Admin ticket detail · /o/your-slug/a/tickets/…
Sign in (all roles) · /o/your-slug/login
Customer portal · /o/your-slug/c/my-tickets
Technician jobs · /o/your-slug/t/my-jobs
Technician jobs · /o/your-slug/t/my-jobs
Role settings · /o/your-slug/a/settings · /c/settings · /t/settings

Authenticated product screens live only under /o/{slug}/…. Bookmark your org paths after sign-in; older flat URLs such as /dashboard are not served.

How it works lists every public route, demo seed accounts, and local dev commands.

Platform operators — sign in via /platform/login (also in the site menu), then use the shared console for /platform (overview, tenants, operators) and /platform/legal. Use only on secure networks.