Resources / Integrations

Mapping plumbing inquiry fields into a job system

An integration can successfully send data while placing the location, problem or callback into fields staff do not use or cannot easily find.

01

The decision to make first

An integration can successfully send data while placing the location, problem or callback into fields staff do not use or cannot easily find. Agree a small field map with the people who read the receiving system before enabling any automated record creation.

02

What the handoff should contain

Map service address, callback, request category, summary, source and unconfirmed status; identify required destination fields and allowed values.

03

Suggested wording to approve

Example wording: “This connection should create a service request for staff review. It should not mark work as accepted or scheduled unless that separate workflow has been verified.”

04

Test the difficult case

Send a fictional request with a missing optional field, an unfamiliar category and an address correction, then inspect the actual destination record. Do not assume a named job-management product offers the required access or write permission merely because it appears in a software catalogue.

05

Worked example

Fictional example: The destination system requires a service category from a fixed list, but the caller’s wording is unfamiliar. The integration should use an approved review category or reject the mapping visibly. It should not invent a valid-looking technical category merely to make the API request succeed and leave dispatch with misleading information.

06

Review it in operation

Review fields staff manually rewrite and improve the mapping without adding unnecessary customer data to every integration payload.

Check before you launch

  • Agree a small field map with the people who read the receiving system before enabling any automated record creation.
  • Map service address, callback, request category, summary, source and unconfirmed status; identify required destination fields and allowed values.
  • Send a fictional request with a missing optional field, an unfamiliar category and an address correction, then inspect the actual destination record.
  • Review fields staff manually rewrite and improve the mapping without adding unnecessary customer data to every integration payload.

Missed plumbing call calculator ↗

Try Ava with your business’s public information ↗

Related guides

Your workflow, first

Let’s map your first week.

Bring the calls you want covered. We’ll agree the script, handoff and limits.

Start a pilot