Skip to content

Setup guide

Connect Scout to FieldEdge

Scout's team connects Scout to your FieldEdge account with you on a setup call. For FieldEdge shops, Scout takes a booking request for your office to confirm: your office turns it into a work order and sets the time.

Scout Help Center · Last updated

Before you start

  • Someone with admin access to your FieldEdge account, free for the setup call.
  • Each tech's mobile number, plus their FieldEdge employee ID. FieldEdge's tech records don't carry phone numbers, so Scout gets them from you.
  • Who in your office confirms booking requests.
  • Keep keys out of email and text. Scout's team enters them straight into your Scout's settings with you.

Steps

  1. Set up FieldEdge API access for Scout

    Scout connects through FieldEdge's API with three values for your account: a client ID, an API key and a target ID. FieldEdge decides what each connected app can read and write, so Scout's team checks what your access allows on the setup call.

  2. Enter the values in your Scout

    Scout's team types them into the CRM connection in your Scout's settings. Keys are saved only in your own Scout and aren't shown again once saved.

  3. Test the connection

    The test reads your live customer count from FieldEdge with exactly the values that were typed. A count back means they work.

  4. Save it and let Scout load your book

    After the connection is saved, Scout switches to it on its next restart, then loads your customers, work orders and invoices and keeps them up to date on its own.

  5. Add your techs

    Scout's team adds each tech with their mobile number and FieldEdge employee ID, so Scout can match them to FieldEdge and text them.

  6. Test calls, then go live

    Before go-live, Scout's team makes test calls with you, checks each call in Scout and checks that each booking request reaches your office. While you test, Scout's texts go only to a test phone, except when Scout is answering a customer who already texted in.

    Set up call forwarding

How a booking request works

  • When a caller wants a visit, Scout sends FieldEdge a booking request with the caller's details and the time they asked for. It arrives as a lead.
  • Scout marks how urgent the call is on the request, so emergencies stand out.
  • The time the caller asked for is a request, not a locked slot. Your office turns the request into a work order and sets the time.
  • Until then, Scout's own schedule shows the request. Once your office creates the work order, Scout shows the work order instead.

What Scout reads and writes in FieldEdge

Reads
  • Customers
  • Work orders and the schedule
  • Invoices
  • Your techs' names and IDs
Writes
  • Booking requests, which arrive as leads for your office to confirm
  • New customers your team asks Scout Chat to add, when your FieldEdge access allows it; otherwise Scout keeps them in Scout
Invoices
  • Scout texts reminders for open invoices
Doesn't do
  • Create, move or cancel work orders: your office does that in FieldEdge
  • Write notes or invoices in FieldEdge

What changes for your team

  • Your office confirms each booking request and turns it into a work order with a time.
  • Moving or canceling a visit stays with your office in FieldEdge.
  • Replies to Scout's texts land in Scout's inbox, where the office can read a conversation, take it over and hand it back.

Disconnect Scout from FieldEdge

Tell Scout's team, and we remove the saved connection from your Scout. Once Scout's API access to your FieldEdge account is turned off, Scout can't read or send anything there.

Requests your office already turned into work orders are ordinary FieldEdge work orders, so they stay put.

Troubleshooting and common questions

We can't find a booking request on the schedule.

A request is a lead, not a work order, until your office schedules it. Look for it with your new leads in FieldEdge.

Some of our FieldEdge data doesn't show up in Scout.

FieldEdge sets what each connected app can see. When your account's access leaves something out, Scout shows nothing for it rather than guessing. Ask Scout's team which parts your access covers.

A tech is missing or shows up twice.

On FieldEdge, Scout matches techs by employee ID only, because FieldEdge has no phone number to match on. Check that the ID Scout has for that tech is the one in FieldEdge.

Still stuck? Talk to us or email [email protected].

See what's sitting in your book.

We'll walk through how Scout gets jobs booked and invoices paid.