FieldEdge Integration: Wiring an HVAC, Plumbing or Electrical Website to the Dispatch Board

A 1980 idea meets a 2026 contact form

Follow one service request through a typical FieldEdge shop. It is 4:40 on a July afternoon and a condenser in a cul-de-sac has quit. The homeowner finds the company's site, fills in the form, and presses Send. The form emails an address the office shares. A customer service rep reads it when the phones allow, opens FieldEdge, searches for the customer, finds two with the same last name, picks one, and types the request into a new record. If the rep is fast and the afternoon is quiet, the homeowner hears back before supper. If not, the homeowner has already called the contractor who answered first.

The retyping costs minutes. The losses that never show up anywhere cost more. The Google click that brought the homeowner arrives nowhere, because email forms do not carry it. The lead source becomes whatever the rep picks from a list at 4:52 p.m. The homeowner who filled in the form and then phoned becomes two customers. When the owner later asks which ads paid for the new truck, the honest answer is a shrug with a spreadsheet attached.

FieldEdge is not the problem. Its home page says it is built for multi-truck operations and "Trusted by SMB and Mid-Market Service Leaders in HVAC, Plumbing, and Electrical," and it publishes an Open API with a lead endpoint made for exactly this handoff. The gap sits between the website and that API. This section is about closing it, written for owners and office managers at HVAC companies, plumbing companies and electrical contractors.

Every lead a dispatcher retypes arrives with exactly as much detail as the dispatcher had time to type.

Multi-truck shops, three plans and the website they need

FieldEdge sells three plans, as of November 2026: Select, Premier and Elite. None has a published price; each says "Request Pricing," and FieldEdge's FAQ says the figure varies with team size and add-ons. Select covers dispatching, booking and scheduling, basic agreements and quotes, customer management and flat rate pricing. Premier adds advanced dispatching, multi-option quotes and advanced service agreements. Elite adds outbound call recording, Proposal Pro, MarketingEdge with two-way texting and a consumer management portal.

Read those plan names and a customer profile appears: shops with several trucks, service agreements to renew and a dispatcher who lives on the board. That is a different reader from the owner-operator running two vans on Housecall Pro or Jobber, and a different budget from the larger operator on ServiceTitan. The website needs differ to match. A FieldEdge shop usually wants three things from its site: fewer retyped requests, a booking path that respects the dispatcher, and proof of which marketing filled the board.

FieldEdge's own tools, and the work that happens on your pages

A fair integration plan starts with what you already pay for. The table sets FieldEdge's own features, as its pages describe them in November 2026, beside what a website build adds. Where FieldEdge already does the job, we say keep it.

Two rows deserve a note. MarketingEdge's forms may suit a shop that only needs a landing page for a tune-up special; FieldEdge does not say how they embed on your own site, so ask before you buy around them. And if your office is happy taking every booking by phone, that is a legitimate choice. The online booking page covers the cases where it is not.

Credentials, a lead call and a signed callback

The mechanics decide what a website can honestly promise, so here they are in plain words, as of November 2026. FieldEdge's developer portal splits API users into members, meaning "Tenants that actively use FieldEdge to operate their business," and partners who build public apps for members. A member's internal app gets a client ID and secret in the FieldEdge Marketplace; a contractor without a Marketplace account requests access through FieldEdge's onboarding form. The website's server trades those credentials, plus the tenant ID from the FieldEdge web portal, for a token, and sends it with every call.

• A lead. Create Lead takes the customer, a service request with type, description and urgency, and the homeowner's preferred date, time and time zone. It returns a lead ID.
• A work order. Create Work Order needs four FieldEdge IDs: customer, business unit, lead source and task. A separate assignment call sets the technician and the time, and FieldEdge says it appears on the Dispatch Board at once.
• A callback. A registered webhook URL hears about work orders being scheduled or completed, invoices, customers and lead events. Each delivery carries an HMAC signature the server checks before believing it.
• A budget of calls. FieldEdge publishes 100 requests a minute and 1,000 an hour, both applying at once, so the integration queues its work instead of hammering the API.

The full map of endpoints, scopes and limits is on our FieldEdge API guide, with the questions to put to FieldEdge before a line of code is written.

Start with the sentence your office keeps repeating

This section is short by design: two deep pages and this front door. The table points each complaint to the page that answers it, including pages elsewhere on the site that cover the same job for other platforms.

Five trade builds that show the method

DataCram designs and codes contractor websites from San Antonio, Texas, on Next.js and our in-house content system, Athena CMS, and handles search, paid ads and local marketing for clients in every corner of the country. The four trade projects below are not FieldEdge integrations, and we make no claim that their owners run FieldEdge. They are here because each solves a problem every FieldEdge site faces: emergencies, pricing questions, page depth and scattered field data.

On a FieldEdge project the habits are the ones our API integrations work uses everywhere: the field map is agreed in writing before code, every lead is validated on the server, writes are idempotent so a retry never files a second customer, failed sends wait in a queue, and the office gets a log written in sentences. After launch, the Athena agent Argus watches the live site and flags a form that stops submitting before a homeowner notices. More builds are in our work.

Prices for a connection, a new site and the care after

Keep your current site and add FieldEdge to it: that work begins at $575, scaled to complexity, with a written number once we have reviewed the site for free. Joining two systems usually goes live the same day. If the site itself is the bottleneck, rebuilds are fixed-price by size, as our web design pricing lays out: $1,500 covers up to 10 pages, $2,250 covers 11 to 20, $3,750 covers 21 to 50, and $5,750 covers 51 to 70. We steer most trade shops to that last tier, because deeper sites rank better from the start. Each tier already contains design, copy, SEO, Athena CMS, forms, booking, a year of support and one custom API connection, and for a FieldEdge shop that connection is FieldEdge.

Website financing splits a build into 25% down and up to 12 months at 0%; on the $5,750 tier that means $1,437.50 at signing and twelve payments of $359.38. Ongoing care runs through hosting and maintenance, from $55 monthly. Whatever FieldEdge charges for your plan is between you and FieldEdge. For the trade side, see HVAC website design, plumbing website design and electrical website design; for the call side, the Google Ads guide for plumbers.

Looking costs nothing. We will design a free mockup of your home page, or put the site you have through a free audit. You can also call (210) 346-0848 and walk us through what happens after a homeowner presses Send. Very few owners have followed a request all the way into FieldEdge, and the trip tends to surprise them.