What's new in waydot

Integrations

• Tickets from your client's system. Incidents from ServiceNow and Jira Service Management become waydot tickets every five minutes. An incident imported twice updates the ticket it already created instead of opening a duplicate, and a ticket a technician registered on site attaches to the client's incident when it arrives.
• Intake inbox and service accounts. Work arriving from other systems lands in an inbox for review, sent by dedicated service accounts rather than a person's login.
• Outbound webhooks. Subscribe to ticket, arrival and shift events. Every delivery is signed, retried with backoff when it fails, and can be replayed from the delivery log.

AI

• An assistant in the console. Triage of incoming work, ticket summaries and a dispatch assistant that answers questions about the operation within the permissions of whoever asks.
• Your keys or ours. Run AI features on your own provider keys, or on platform keys metered by use. Choose the provider and model for each task.
• Dictation in the field app. Technicians can speak notes and resolutions instead of typing them with one hand.

Workforce and finance

• Mileage and claims. Trips are built from the GPS trail between clock-in and clock-out and reimbursed at each technician's policy rate.
• Fleet. Vehicles, fuel logs and maintenance, with company-vehicle trips feeding fleet mileage.
• Legal breaks. Breaks under Mexican labor rules are tracked on the shift and subtracted from hours worked.
• Employment records. Employment, leave, documents and certifications on each person's file.

Field execution

• Automatic arrival is now reported on the ticket, with a confirmation for the technician.
• One flow for moving equipment. Transfers, handovers and registering equipment on a ticket share a single flow in the app.

Operations and security

• Scheduled visits with renewal plans for equipment reaching the end of its service life.
• Two-factor authentication with QR enrollment and single-use recovery codes, in the console and the field app.
• Plans and entitlements. Modules are enabled per plan, so each team sees the features it has.

Operations and dispatch

• Smart assignment ranks technicians by traffic-aware travel time, workload, shift and skills, assigns clear cases, and offers close calls to several technicians at once.
• Escalation chains wake the right people in order when a ticket stalls, and can take it back and dispatch it again.
• Ticket lifecycle with guarded transitions, multi-technician collaboration, follow-up visits and task lists that must be complete before a job can close.
• Knowledge base fed by resolved jobs, available offline to every technician.

Field execution

• Offline-first sync. Everything a technician needs works without signal and syncs in order, exactly once, when it returns.
• Background GPS with geofencing during shifts only, with location integrity checks against mocked positions and impossible travel.
• Geofenced attendance that replaces timesheets, with corrections that keep the original record.

Quality and safety

• Safety checklists (JSA) that hold a job until it is safe to start, plus hazard reports, incident reports, corrective actions and an SOS button.
• Evidence vault, post-job inspections, random field audits and a defect lifecycle.

Assets

• Inventory register and custody trail. Units move only through transfers, including technician-to-technician handovers by QR, against a four-level product catalog.

Intelligence

• SLA risk, dispatch recommendations and route optimization, plus hotspots, demand forecasts and contract health, with a model registry and tunable dispatch weights.

Platform

• Tamper-evident activity log, runtime role management, a rule-based notification engine, live updates across the console and the digital employee file.