Talk to it.
Watch it work.

OkPilot works by letting you type plain language instructions instead of clicking through menus. You describe what you need, the assistant builds a plan, and you approve it. Setup takes 48 hours, and no training is required for dispatchers or field staff.

An operations coordinator sends a request, a route is planned, a technician completes work, and proof returns to the operation.

You run it by talking

This is what using OkPilot actually looks like. You type what you need. It figures out how to do it.

Every instruction follows the same pattern: you say what you need, OkPilot shows the plan, and you give the go-ahead.

  • Dispatch and route work
  • See risks before customers do
  • Approve changes with context

No report builder, no filter maze. Just an operating conversation.

OkPilot operating assistantLive operation
Re-route the two delayed HVAC visits and let the customers know.
I found a faster sequence for both visits. No other appointments move.
2 routes updated2 customers notified18 min saved
Suggested planReady to approve

Raj takes the 3:30 PM visit. Maria keeps the 4 PM window. Both customers receive an updated ETA.

Ask OkPilot anything about today’s operation↵

Describe your operation. It builds itself.

No configuration screens. No IT project. Tell OkPilot how your operation works in plain words, and it creates the stages, proof requirements, customer notifications, and terminology to match. Change it any time the same way.

"We deliver prescriptions from two pharmacy locations. Drivers need to capture a signature. Customers get a tracking link." That is the setup. The system builds itself around what you said.

48 hours from description to live. Not weeks. Not months.

Step 1

Describe your operation

"We run same-day deliveries for three restaurant brands across the city..."

Step 2

Stages appear

Assigned → En route → On site → Proof captured → Complete

Step 3

Proof requirements attach

Photo at the door, signature on handoff, barcode scan on pickup

Step 4

People and roles slot in

Driver Supervisor Admin

Step 5

Your terminology applied

Your words, not generic labels. "Drops" not "tasks." "Riders" not "resources."

Under the hood

Six objects that reshape to anything

Every field operation is a combination of these building blocks. That is why OkPilot does not need a separate product per industry.

Job

The thing that needs doing

Site

The place it happens

Person

The one who does it

Proof

The evidence it happened

Stage

Where the job stands

Account

Who it belongs to

It catches problems before you do

OkPilot watches everything in motion and surfaces issues before they become problems. It does not just track. It thinks ahead.

Delivery
Heads up

Order #1042 is 14 minutes behind schedule. Carlos just finished two blocks away. Reassign to Carlos?

Approve Dismiss

You tap approve. The customer gets an updated ETA. No phone call needed.

Service
Heads up

Jake's HVAC job at 140 Oak St has been on-site for 2h 45m, 45 minutes over the estimate. His next appointment at 3:30 PM is at risk. Push the 3:30 to 4:15 and notify the customer?

Approve Dismiss

The downstream customer gets a heads-up before they start wondering. You did not have to notice the overrun yourself.

Inspection
Heads up

Priya completed the inspection at 22 Elm St but the roof photo is missing. She is still 4 minutes away. Remind her to capture it before she leaves the area?

Send reminder Skip

Catching a missing photo while the inspector is still nearby saves a second trip.

It shows the plan. You give the nod.

Nothing happens without your approval. OkPilot never reassigns a team member, messages a customer, or changes a route until you say go. It explains what it is about to do, shows the impact, and waits. You stay in control at every step.

We ran the operation before we built the software.

2,000,000+ tasks dispatched through our own operations since 2018. Every feature in OkPilot exists because we needed it ourselves.

Common questions

No. Operators type what they need in plain language. Field staff see their next job, tap for directions, and snap proof at every stop. Most teams are comfortable within their first shift.

Nothing happens without your approval. OkPilot always shows you the plan before acting. You review what it is about to do, and if it does not look right, you adjust it or dismiss it.

Yes. You can drag jobs, reassign people, override routes, and edit stages any time. OkPilot works alongside you, not instead of you.

48 hours from description to live. You describe your operation in plain language and OkPilot builds the stages, proof requirements, and terminology around it. No migration project, no IT involvement, no consultant sitting in your office for six weeks.

See it running your operation

Book a demo. We will configure OkPilot to your business and show you your day running itself.

Live in 48 hours

Per team member pricing

Book a demo
Get 30 days free trial