Online Booking for FieldEdge Shops: Requested Windows, Confirmed Slots and the Line Between Them

A Book Now button that quietly sends an email

Most contractor sites have a button that says Book Now. Press it on a typical FieldEdge shop's site and you get a form, a thank-you message and, somewhere in the building, an email nobody reads until morning. The homeowner believes she has an appointment. The dispatcher has never heard of her. At 7:30 a.m. the rep calls to "confirm," which is the polite word for starting over, and the homeowner, who booked a competitor at 9:52 the night before, does not pick up.

FieldEdge itself is built for the office side of this. Every plan lists booking and scheduling plus "Call Booking," and the scheduling page promises you can "Take and schedule calls anywhere and anytime." As of November 2026 we found no homeowner-facing booking widget on FieldEdge's own pages; Podium's marketplace page says its FieldEdge connection sends confirmation texts when a customer schedules, which is a messaging layer rather than a booking page. So the booking experience on your website is yours to design, and the Open API gives it two honest shapes.

If your shop is already on ServiceTitan, Housecall Pro or Jobber, those platforms ship booking tools of their own and their pages read differently from this one. FieldEdge shops start from a cleaner slate, which is mostly good news.

Asked for, or held: two booking designs on the Open API

The first design sends a request. FieldEdge's Create Lead operation takes the customer, a service request with type, description and urgency, and an appointment block with preferredDate, preferredTime, timezone and availabilityNotes. Those are preferences, and the page says so: the homeowner picks a window, the office confirms it. FieldEdge's webhook list includes lead.offered, lead.accepted and lead.rejected, which suggests leads pass through an accept step, though the documentation does not describe the screen your office sees. We test that with your team before launch.

The second design holds a real slot. The server finds or creates the customer, creates a work order with the four IDs FieldEdge requires (customer, business unit, lead source and task), then assigns a technician with a scheduleDateTime and estCompleteDateTime. FieldEdge says the assignment takes effect immediately and shows on the Dispatch Board. Powerful, and also a promise: the reference lists no availability or capacity endpoint, so the website can only offer slots from a capacity table your office controls.

Six questions the page asks before it shows a single time

A booking page for HVAC, plumbing or electrical work is half calendar and half triage. The questions below decide which design applies, which technician skill is needed and how long to hold. Each answer lands in a specific place in FieldEdge, so nobody has to read a paragraph to find out the homeowner has no heat.

The service agreement question earns its place. FieldEdge's customer search can filter on whether a customer has a service agreement, so a returning plan member who enters a known phone number can be greeted as one, offered maintenance windows first, and spared the sales pitch. Agreements matter to these trades; our HVAC website marketing ideas explain why they deserve their own pages.

No heat at 2 a.m. is a phone call, not a calendar

The fastest way to lose an emergency job is to show the homeowner a calendar. A burst supply line or a dead furnace in January wants a person, so the booking page detects the emergency answer and swaps the calendar for the after-hours number, large, with a short line on what happens next. If the homeowner still submits, the lead goes in flagged urgent and the on-call phone hears about it.

We built exactly this pattern for Bleuwave Plumbing, where an emergency flag moves an active leak ahead of the queue and a homeowner who cannot name the problem can ask the form for help. That project is not a FieldEdge integration, and we do not claim the client uses FieldEdge; it is proof of the triage logic, which travels well. For HVAC, the same idea pairs with instant pricing, as on Bleuwave HVAC.

An open slot on a website is a promise made in the dispatcher's name, so the dispatcher should get to decide how many there are.

After the tap: confirmations, callbacks and the hourly budget

The confirmation should arrive within seconds and match the design. A request gets "we have your request for Tuesday morning and will confirm by 9," never "you're booked." A held slot gets the date, the window and a way to change it. Texts go through your own messaging provider with consent captured on the form; FieldEdge's customer record has a marketingSmsOptIn flag, which is about marketing, so transactional consent is collected separately. This is not legal advice; the ServiceTitan texting page covers 10DLC and opt-out rules that apply whatever software you run.

When the office confirms, FieldEdge can tell the website. Its webhook events include work-order.scheduled, job.scheduled and lead.accepted. They are notification-only, so the server fetches the record before acting, and it checks the X-FieldEdge-Signature header first. One more constraint shapes everything: FieldEdge's published limits are 100 requests a minute and 1,000 an hour, both applying at once. A held-slot booking spends several calls, so we queue writes, cache the lead source and business unit lists, and keep a busy Saturday from eating the hour.

Building it, in the order we work

1. 1

   Agree the design per service

   We sit with the dispatcher and decide which services may be held as slots and which stay requests. Emergencies always stay calls.

2. 2

   Confirm API access with FieldEdge

   Your company sets up its Marketplace app, or requests access through FieldEdge's onboarding form. The credentials go straight into the server's settings.

3. 3

   Map every answer to a field

   Each question gets a destination: service type, urgency, description, customer, or a note. Lead sources and business units are chosen from your own FieldEdge lists.

4. 4

   Build the capacity table, if slots are held

   The office sets how many tune-ups per zone per morning. The site never offers more, and an admin screen lets the dispatcher close a day in one click.

5. 5

   Test with labeled records

   Test bookings carry an obvious name and go in at agreed times, so no technician drives to a fictional furnace.

6. 6

   Launch, then watch

   The Athena agent Argus checks that the booking form still submits, and the log shows every request, its FieldEdge reply and any retry.

Price, a demo to click through, and a free first look

A booking step costs nothing extra on a new build: it ships with all four of our fixed-price site tiers, which run $1,500 (10 pages or fewer) to $5,750 (51 to 70 pages, the tier we recommend), per web design pricing. Retrofitting booking and the FieldEdge connection onto your existing site begins at $575 and depends on how many services and rules are involved; we write the quote after reviewing the site, free. New builds can be paid 25% up front and the rest over 12 months at 0% through website financing.

To feel a booking flow before talking to anyone, click through the booking page on our demonstration roofing site, a demo we built, not client work. The FieldEdge integration hub maps the rest of the connection, the FieldEdge API guide has the endpoint detail, and HVAC website design, plumbing website design and electrical website design cover the site around the button. Or start with a free site audit.