Field work, dispatched like a delivery
Book the job with a customer, an address and an appointment window, send it out as a real route to the technician's phone, and close it with a photo and a signature.
14-day free trial, no credit card. Or book 30 minutes with us.
Same contacts, same calendar, same roles. Nothing to integrate.
How it fits togetherEvery job has a customer, a place and a window
- Customer, location, appointment window and assignee on every job
- Board view and schedule board
- Jobs show up in the shared calendar
Work orders
Each job gets a short number like FS-412 that people can say out loud and paste into an email.
Appointment windows
Move a job to another day and its window moves with it by the same amount.
In the calendar
Scheduled jobs appear in the platform calendar next to the rest of the team's work.
Shared contacts
The customer is a platform contact, and their record lists the field jobs done for them.
Planning defaults
Set how long a job usually takes, the average travel speed and a buffer between jobs.
Jobs go out through the route solver
- A preview of the order and arrival times first, nothing saved
- Jobs without a usable address are listed, not dropped silently
- The same solver and driver app your deliveries use
Optimize first
The preview shows the sequence, total distance and time, and any appointment windows it would miss.
A real route
Dispatching creates a fleet route for the technician's device, the same as a delivery round.
On the live map
Once dispatched, the technician's day shows on the fleet map alongside your vehicles.
Agents can book jobs
An agent can create a work order and assign it as a tool, for example from a customer call.
Flow steps
Flows have steps to create a job and to assign it, so a form or a webhook can start the work.
Proof from the field, on the work order
- Photo, signature and the name of who accepted it
- Distance from the job address worked out on the server
- An offline queue for places without signal
Photo and signature
The same proof a delivery stop takes: photo, signature, QR or barcode scans.
Where it was signed
The server compares the proof's position with the job address, so you can see it was signed on site.
Works offline
Updates queue on the phone and send when the signal comes back.
Feeds reporting
Work orders flow into reports alongside the rest of your operations data.
Service deskComing soon
Internal tasks, bugs and incidents on a list, a board and queues, linked to the customer conversations they came out of.
Guides and articles
Practical reading on route planning and electronic proof of delivery.
- Guide· 8 min
Route Optimization Best Practices
Learn how to plan smarter multi-stop routes with clean address data, time windows, capacity constraints, stop priorities, and dynamic re-optimization that adapts to real conditions.
- Guide· 6 min
Electronic Proof of Delivery (ePOD)
Learn how to implement electronic proof of delivery with Avyndo: capturing signatures and photos, working offline in the field, notifying customers automatically, and keeping a defensible audit trail.
- Article· 5 min
ePOD | Electronic Proof of Delivery in Practice
How to implement e-signatures, delivery photos, and automatic customer notifications.
Frequently asked questions
A job with a customer, a location, an appointment window and an assigned technician. It moves through statuses from scheduled to completed, and you can see it on a board, on a schedule board and in the shared calendar.
You optimize a technician's jobs and get a preview with the order, arrival times and any jobs that could not be placed, for example because they have no usable address. When you dispatch, it becomes a real fleet route on the technician's phone, planned by the same solver your deliveries use.
Yes. Jobs carry their window into the route plan, and the preview tells you if a window would be missed before you commit.
The driver app takes a photo, a signature, the name of the person who accepted the work, and QR or barcode scans, and it works offline with a queue. The proof is copied onto the work order, and the server works out how far from the job address it was captured.
Yes. Agents have tools to create and assign work orders, and flows have steps for creating and assigning a job, so a call, a form or a webhook can book a visit.
A service desk for internal tasks, bugs and incidents, linked to the customer conversations they came from, is coming soon. It is not available yet.
Plan one real day of jobs with us.
Try it free with your own jobs, or book thirty minutes and we will dispatch a day of your work together.