Attain OS for field operations

Work order management that does not live in a dispatcher's memory.

Work orders, routes, assignments and service forms stop living in one person's memory and a phone that never stops ringing. They live in one workspace your field team opens in a phone browser and your office reads from a desk. Attain OS has no dedicated work-order module: you run work orders as Work Board tickets or Customer Care cases, and plan each day as a route.

14 days free · No card needed · Cancel anytime

Work Order Management for Field Teams: Tickets, Routes and Forms

Who this is for

What this looks like today

Installation and repair companies, utilities, maintenance contractors, inspection firms, delivery and logistics teams — anyone whose people spend the day away from a desk and whose customers judge them on whether someone showed up and did the job.

It is 9:40 and your dispatcher has two phones going. A customer wants an arrival time nobody can give. One technician is at an address that was already serviced last Tuesday, because that work order only ever existed in an email. Another is across the city from a call he could have taken on the way. The only evidence that yesterday's install was finished is a photo in somebody's personal camera roll, and the client refusing to pay will ask for it Friday. And eleven maintenance contracts come due this month, tracked in a paper agenda that lives in one desk drawer.

  • The dispatcher is the system, so nothing moves when the dispatcher is on another call
  • A technician arrives without the part, the access code or the notes from the last visit, so the trip is burned
  • The customer disputes a job and you have no record of what was done and when
  • Recurring maintenance visits are remembered only when the client calls to complain they were missed
  • Work across several sites in one day gets sequenced by whoever answers the phone first, not by the map

What changes

In Attain OS a work order is a ticket, and it travels complete. Put the customer, the address, the scope, the assignees, the priority and the due date on a Work Board ticket and link it to the customer record, where site access notes can sit in a custom field. The technician opens it in a phone browser and sees what the office wrote.

Planning the day stops being a phone call. Build each technician's day as a route: ordered stops with addresses, assignees, a due date and a customer link, shared with the team. You choose the order, because Attain OS does not optimize it, and it opens the whole route as Google Maps directions. Change the assignee on a ticket or a route and the person it moved to sees it on their own screen.

The job closes into a record. The technician marks the stop done, which saves the time and who did it, updates the ticket, and fills in a service form from its public link: checklist boxes, readings, notes. Shortly after, each submission can open a Customer Care case. Atty can then draft a job summary as a note, or the follow-up task for the next visit, for you to approve.

A day that is planned instead of narrated

Stops sit in the order you set, on a route your team opens on a phone, with directions one tap away. The office spends its morning on exceptions, not on reading the schedule out loud.

Fewer wasted trips

A ticket that carries the scope, the priority and the access notes is a trip you do not repeat, and a job that closes with a completed stop and a filled-in form is a question you can answer from a record. Attain OS does not calculate savings or send invoices; it keeps the facts in one place.

A record of who went and what was done

Each route stop saves when it was marked done and by whom. Service forms come back as saved submissions, and Customer Care cases keep internal notes, attachments, a resolution summary and a history of field changes. Nothing tracks a technician's location, so a completion time is when someone marked the stop, not a GPS check-in.

Add crews without adding coordinators

Most field companies hit a ceiling at the number of jobs one dispatcher can hold in their head. When assignments, routes and follow-ups are structure instead of memory, and Atty drafts the tasks and summaries for your approval, the same office can coordinate more technicians.

The apps that carry the work

Every one of these is built in and already connected to the others. Nothing here is an integration you have to buy or wire up.

Smart Tickets

Work orders as tickets and cases

Every request becomes a ticket with a customer link, a priority, assignees and a due date. Work Board tickets move through statuses you define, and Customer Care cases add internal notes, attachments and a resolution summary. With Smart Tickets, Atty drafts a ticket from pasted text, a file or a voice recording, and you review it before it is created.

  • A call or message turned into one assigned ticket, drafted by Atty for your approval
  • Priority and due date on every ticket so urgent work is easy to spot
  • A public form that opens a Customer Care case for each request
Smart Tickets
Routes

Routes with ordered stops

Build each technician's day as an ordered list of addresses, drag the stops into the order you want, share the route with the team and open the whole thing as Google Maps directions. Attain OS does not optimize the order or track vehicles: you decide the sequence and mark each stop done.

  • Daily routes per technician, crew or driver
  • Multi-site runs with drop-offs and pickups in the order you set
  • Each stop saves when it was marked done and by whom
Routes
Appointments

Booking pages for service windows

Share a booking page with real availability so customers pick a service window without an account, cancel or reschedule from an emailed link, and get email reminders. A booking blocks your calendar and adds the customer to your records. The booking page does not book recurring series.

  • Customer-facing booking for service windows
  • Assignment among team members by the customer's pick or by round-robin
  • Email reminders before the visit
Appointments
Tasks

Recurring maintenance tasks

Set a task to repeat every few days, weeks or months, with assignees, a due date and a customer link. The due date lands on the shared calendar with a reminder. There is no contract or warranty record, so keep contract terms in the customer's custom fields.

  • Quarterly and monthly maintenance as recurring tasks
  • Due dates that appear on the shared calendar
  • Assignees notified in the app, by push or by email, per their settings
Tasks
Forms

Service forms and checklists on a phone

Build a form with checkboxes, numbers, dates, dropdowns, ratings and text fields, and open its public link on a phone with no login. Each submission lands in a table and can open a Customer Care case shortly after, because processing runs on a schedule. Forms have no signature, photo or file-upload field.

  • Service and inspection checklists completed on site
  • Meter readings and results captured in number and text fields
  • Incident reports that open a case for each submission
Forms
Work Board

A board for the day's work orders

One drag-and-drop board shows the day's work. Define your own statuses, such as unassigned, assigned, on site, done and waiting on parts, and give each ticket a priority from P0 to P5 and one or more assignees. Anyone in the office can see where work stands without asking.

  • An unassigned column worked down every morning
  • Waiting-on-parts and waiting-on-access statuses that stop jobs disappearing
  • Priority levels so urgent jobs stand out
Work Board
Customer Management

Customer records and follow-up

A customer record holds name, phone, address, preferred contact method and language, plus free-form custom fields you can use for site access notes, equipment or contract terms. Tickets, tasks, routes and cases can link back to the customer.

  • Access notes and site details in custom fields
  • Preferred contact method and language on each record
  • Customers added automatically when they book through your booking page
Customer Management
The Feed

One activity feed for the project

The project feed lists what changed across the workspace in one chronological view, so the office reads one record instead of scrolling a group chat for the one message that mattered. Team members can comment on feed entries.

  • One place to see what changed today
  • Comments on feed entries, so the office and the field read the same note
The Feed
WhatsApp + Atty

Atty on WhatsApp for your team

Atty works over WhatsApp for the people in your organization, so a technician or driver can ask for today's route or send a voice note in the chat they already use, and Atty prepares the change for approval. WhatsApp and voice are enabled per organization on request. Atty does not reply to your customers on WhatsApp.

  • Ask Atty for today's route or open tickets without opening the app
  • Describe a finished job by voice note and let Atty draft the update for approval
  • Approve or reject the change in the same chat
WhatsApp + Atty
Working guide

A field app for work orders has to show each technician the job, the address, the scope and the access notes before the trip, and let the office see what was completed without a phone call. It also needs a day plan the technician can follow in order, and a form for the findings at each visit. Check those working parts first, then decide separately whether you need dispatch, route optimization or invoicing.

In practice

A day of tickets, stops and visit records

  1. Early morning · the day plan

    Before the first call, the dispatcher reviews the unassigned tickets and builds each technician's day as ordered stops. Every stop carries the address, the scope and the access notes. The technician opens the same order on a phone, so the day does not start with a call asking where to go next.

    Routes
  2. Mid-morning · an urgent call

    A customer reports a leak that cannot wait. The office opens a ticket with the customer link, a priority and a due date, then assigns it to the technician who can reach the site soonest. The customer's earlier tickets sit on the same record, so the technician sees the history before leaving.

    Work Board
  3. Midday · the site visit

    On site, the technician completes the service form: checkboxes for the checks, number fields for readings and a text field for parts used. The form arrives as a saved submission. It has no signature or photo field, so the technician writes specific notes in the fields that exist.

    Forms
  4. Afternoon · a part is missing

    The job cannot finish until a part arrives. The ticket moves to a waiting-on-parts status the team defined, so the office can see blocked work without asking anyone. The next visit becomes a task with an owner and a due date, not a reminder kept in someone's head.

  5. Late afternoon · recurring maintenance

    Quarterly maintenance for a set of contracts comes due this month. Recurring tasks repeat on the schedule you set, with assignees and a customer link, and their due dates appear on the shared calendar. Contract terms stay in the customer's custom fields, because the workspace has no contract record.

    Tasks
  6. Friday · a disputed visit

    A client disputes a completed job. The office opens the route stop to see who marked it done and when, reads the saved service form and checks the case history for field changes. The record shows what the team entered. It is not a signed or photographed proof of service.

    Customer Care
Workflow map

Which part of the job each app carries

JobAppWhat it does here
Work orders as ticketsWork BoardEach work order is a ticket with a customer link, a priority, a due date and one or more assignees. Define the statuses your dispatch uses, such as unassigned, on site and waiting on parts. Moving a card is the update the office reads.
Customer problemsCustomer CareComplaints and warranty questions become Customer Care cases with internal notes, attachments and a resolution summary. A person sets priorities and assignees, and every field change stays in the case history.
Daily routesRoutesBuild each technician's day as ordered stops, share it with the team and open it as Google Maps directions. You choose the sequence, and each stop records when it was marked done and by whom. The route does not estimate arrival times.
Service visit formsFormsBuild the checklist, readings and notes as a form and open its link on a phone with no login. Each submission saves to a table, and a case can open when the scheduled processing runs. Forms have no signature or photo field.
Customer historyCustomer ManagementA customer record holds the address, contact details, preferred contact method and custom fields for site access notes. Tickets, tasks, routes and cases link back to it. The record has no sales pipeline.
Booked service windowsAppointmentsCustomers pick an open service window on a booking page without an account and get email reminders. The booking blocks your calendar and adds the customer to your records. Recurring series cannot be booked this way.
Start here

Forms for the calls that start a visit

Maintenance request form

Capture what is broken, exactly where it is and when the problem started, so the visit is planned for the right fix.

Warranty claim form

Collect the product, proof of purchase and fault details a reviewer can check before anyone books a warranty visit.

Vehicle checkout form

Log mileage, fuel and damage at checkout and return, so the next technician knows the van's condition.

Shipping request form

Give whoever books a courier the pickup point, package count and weight, so the pickup is not missed.

Mistakes to avoid

Three habits that waste the trip

Sending a technician without the access note

A technician who arrives without a gate code or a parking rule loses the trip and the customer's patience. Put access instructions in the customer's custom field, then copy the one that matters onto the stop so it appears on the route. Check the stop before the crew leaves the yard.

Promising arrival times from the route

A route lists stops in the order you set. It does not estimate arrival times or track vehicles, so a time promised from the route alone is a guess. Put the time window in the calendar or on the booking page, and keep the route for sequence and directions.

Treating a saved form as proof

A saved service form and a completed route stop record what your team entered. They are not a signature or a timestamped photo, because forms have no signature or photo field and nothing tracks location. Write specific notes, and check with your own advisers what evidence a dispute needs.

Working checklist

Routine for a technician's day

Before the first stop

  • Check each stop's address and access note.
  • Confirm which tickets need a part or a special tool.
  • Agree who takes calls about rescheduled stops.

At the end of each visit

  • Mark the stop done and submit the service form.
  • Move the ticket to its next status, or to waiting on parts.
  • Write the next step as a task with a due date.
What this agreement means

Choose the parts you run from a phone

  • Use tickets for work orders, routes for the day's order and forms for what was found on site.
  • Keep dispatch, route optimization, invoicing and vehicle tracking in the tools that already do them.
  • Decide what a finished visit must record before you build the form that captures it.

This is a working pattern for a field team, not a dispatch system or proof of service. Confirm what your contracts and customers require before you rely on the record.

Frequently asked questions

Is a field service app the same as field service management software?

Not in most cases. Field service management software usually adds dispatch optimization, scheduling across skills, invoicing and parts tracking. A workspace for tickets, daily routes and service forms covers the field work around those features, so check which of those jobs you need before you compare products.

Can technicians use it without installing anything?

Yes, for the browser parts. Routes, tickets and service forms open in a phone browser, so there is nothing to install. Where your organization has WhatsApp enabled, a technician can also send Atty a voice note or a photo for a drafted update, and a person approves it before anything changes.

Does the route track technicians or find the fastest order?

No. You choose the stop order, the route opens as Google Maps directions, and nothing tracks a vehicle or a technician's location. There is no automatic dispatching and no live tracking either.

What does a completed visit prove?

It records that someone marked a stop done, with that person and the time, and that a form was submitted with its answers. It is not a signature, a stamped photo or a GPS check-in. Keep notes specific, and ask your own advisers what proof a customer or insurer can require.

Who Attain OS Is For — One Operating System for the Team You Actually Run

Attain OS BETA