One field-service platform for the office, the technician and the customer
A Fayetteville, NC pest control company runs its day from three connected interfaces: an office dashboard, a technician app and customer self-service. Forjwell is designing and building all three. Still in build.
01The challenge
In pest control the property is the account, not the person: homes change owners and tenants, and much of the work comes through property managers. The office needed one place to schedule and dispatch, technicians needed their day on a phone, and customers needed to see visits and approve extra work, all following the address rather than whoever lives there.
02Our approach
Drag to dispatch
A job pool beside a day, week and month calendar per technician. Dropping a card on a lane assigns and dispatches it; overlaps ripple down the lane and drops into the past are refused.
The technician's day
Today's route as a timeline, job detail with the office-set scope and access notes, check-in that unlocks near the property, and three Found something? flows for extra work and referrals.
Customers and tenants
Customers follow the technician on the way and approve found items with a swipe. Tenants of managed properties get a restricted view by design.
Built to be white-labelled
One typed data interface sits behind every screen, so the alpha runs on demo data today and the same product can later serve other recurring-service businesses.
03Inside the work
04Three interfaces, one property record
- Office dashboardToday, schedule, requests, documents
- Technician appRoute, job detail, check-in, inbox
- Customer appLive visit status and approvals
- Best slotOpen windows ranked by drive time
- Command paletteFind any property or job with ⌘K
- Property historyVisits and quotes follow the address
05The outcome
The office dashboard and the technician and customer app run end to end on demo data, with Android alpha builds for testing. Integrations such as maps, e-signature and payments are specified but not live yet. Eco Advantage is still in build, and this case study says so.
06Services used
