Skip to content
Field Console Pro
Open menuClose menu

CUSTOMERS & CRM

Know the customer.
Remember the context.

The contact. The property. The last visit. Bring the details around each customer together, so your next conversation starts a step ahead.

Get started See how it connects
ONE RELATIONSHIP. CONNECTED RECORDS.

A product-inspired illustration, using fictional data.

Field Console ProEverything connected to the customerILLUSTRATIVE · FICTIONAL DATA
Jordan Taylor

Sample customer · Customer workspace

Service locations

Home · Garden studio

Equipment

Heat pump · Service context

Service history

Completed visit · Saved summary

Related work

Jobs · Quotes · Invoices

One customer record, with the work and property details around it.

JORDAN TAYLOR / RELATED WORK

The next visit doesn’t
start from zero.

  1. PAST VISIT · HOMEHeat pump maintenance

    Completed service and the record of work stay connected to the customer.

  2. NEXT APPOINTMENT · GARDEN STUDIOEquipment service

    A different location. The same customer relationship.

Related quote Related invoice

Illustrative records—not a live application screen.

LESS SEARCHING. MORE CONTEXT.

A customer record
worth returning to.

Keep customer names, phone numbers and email addresses available to your authorized team. Find past and upcoming work without rebuilding the story from scattered records.

01

Keep the relationship current

Create and edit customer details as your business’s records change.

02

Find the work around it

Review related jobs, quotes and invoices in customer context.

SAMPLE SERVICE LOCATIONJordan Taylor / Home

Equipment belongs with the property.

Heat pump

Brand · Model · Serial number

Equipment notes & service history
Garden studio

Another service location for the same customer

Fictional example · Customer property equipment, not stock inventory

THE PERSON AND THE PROPERTY

One relationship.
More than one place.

A customer may call you to more than one property. Keep service locations under the customer and equipment records at the location where the work happens.

  • Keep each service location’s details together.
  • Record equipment brand, model, serial information and notes.
  • Use equipment and service context to prepare for the next visit.
Guide: customers, locations & equipment

THE RECORD BEYOND THE VISIT

Keep past work useful
for what comes next.

Customer service history brings previous jobs and their context into the next service conversation. Service Records keep the documentation of the work with the visit.

Explore the Service Record guide
THE WORK

Past visits. Related appointments.

Follow customer-linked jobs and service history. Open the record you need when planning the next appointment.

Jobs & scheduling
THE COMMERCIAL CONTEXT

A quote and invoice belong to a story.

Keep related quotes and invoices associated with the customer and the work. Each document retains its own status and workflow.

Invoicing & payments
THE CUSTOMER’S VIEW

Share the right information.

Authorized customers can return to their branded portal for eligible appointments, completed summaries and shared documents. Internal records stay private.

Customer experience

A PRACTICAL WAY IN. A WAY OUT.

Bring your records.
Keep them portable.

Start with the customer information you already have. Take supported operational records with you when you need them.

Read the import & export guide
CSV → CUSTOMERS

Start with customer import

Upload customer records from CSV, validate the rows and review errors before applying the import.

OPERATIONAL RECORDS → ZIP

Export useful business records

Export supported customer, job, quote, invoice, Service Record and payment data in a ZIP archive of CSV files.

Export coverage depends on record type. Document and photo files are not included, and the archive is not a complete accounting backup.

THE NEXT CONVERSATION STARTS HERE

Bring the customer
back into focus.

Make customers, locations and related work part of one connected workspace.

Get started Explore all features

Product access and plan activation have separate requirements. Team permissions and plan limits apply.