AccuLynx Online Booking: The Homeowner Picks the Hour, and the Job Carries It

Sunday night, a ceiling stain and an office that opens Monday

Roof problems keep homeowner hours. They get noticed after dinner, in the rain, on weekends, by people who would rather tap a time than leave a voicemail and wait for a callback that arrives during their own meeting. Phone tag has no winner, only a loser who finds out later: the roofer whose inspection went to the company that let her choose a slot. We have written about why the first business to answer tends to win the job. Booking is the version of answering that keeps working while the office sleeps.

AccuLynx runs the office side of scheduling well. Its plan page lists a shared appointment calendar in both Pro and Elite, its Fall 2025 update says the calendar "fully integrates with Outlook and Apple Calendar in real time," and staff can set an initial appointment straight from the in-app lead form. What we did not find, as of October 2026, is a page where a homeowner books for herself. The Customer Portal lets homeowners "see upcoming appointments" and does not describe booking or rescheduling them. So the booking page belongs to your website, and the AccuLynx integration hub maps everything else a site can connect.

What a booking page may touch on an AccuLynx calendar

Everything a booking page does in AccuLynx runs through its public API. That needs the AppConnections add-on switched on in your account and a key created by a Location or Company Administrator in Account Settings. You create the key; we never ask for a login. Accounts with several locations connect each one separately, so a two-office roofer has two keys and, usually, two inspection calendars. Here is the exact reach, as of October 2026.

Read that table twice and the design writes itself. The site may look at anything on the calendar, and it may write exactly one thing: the first appointment on a job it just created. That happens to be precisely what an inspection booking needs. The wider resource list is on our AccuLynx API guide, and AccuLynx's own initial appointment reference is public.

Live, nearly live and merely requested: a label for every moment

Owners ask whether the booking is real time. Parts of it are, and a good page is built so nobody has to guess which parts. Here is the sequence on a site we build, with an honest label on each step.

1. 1.Live: reading the calendar. When the homeowner reaches the time step, the server reads the inspection calendar you chose and removes every window already taken. It reads again the moment she presses confirm, because the first read may be minutes old.
2. 2.Live: creating the lead. The server finds or creates her contact, looks up the IDs for lead source, job category, work type and trade type, and creates the job. It lands in the Lead milestone, unassigned.
3. 3.Live: setting the time. The server writes her window as the job's initial appointment. Calendar reads list initial appointments as their own event type, and during setup we confirm which calendar shows the ones the site writes, so the next visitor is not offered the same hour.
4. 4.Not live: the gap between looking and confirming. If someone in the office books that window inside AccuLynx while she types her address, the second read catches most collisions. Nothing can hold a slot, so the page never claims one is held.
5. 5.Not automatic: the inspector. AccuLynx creates the lead unassigned. The office assigns a rep, or the site does it through Update Company Representative if you want a rule such as one rep per county.

When the office moves the time inside AccuLynx, the site can hear about it. AccuLynx's webhooks include Job Appointments Initial Created and Job Appointments Initial Updated, so a reschedule can trigger a fresh notice to the homeowner. AccuLynx's webhook guidelines set a 10-second timeout, warn that duplicate events happen, and disable a subscription whose listener errors too often. So our listener answers at once, ignores repeats and does the real work afterward.

Storm week, when the calendar runs out before the phone stops

After hail, every roofer in the county meets the same arithmetic: more homeowners than inspectors. A booking page that keeps offering Tuesday at 10 to the fortieth caller is not helping anyone. The glow of a full calendar fades the first time three inspectors are booked into one cul-de-sac at the same hour and a fourth is booked across town.

The capacity rules live on the website, because AccuLynx's API exposes appointments, not your staffing logic. We put them in plain settings the office can change without us: how long a window is, how many inspections each calendar takes per day, how much drive time sits between them, how far ahead the page looks, and which ZIP codes it serves. In a surge, the office flips the site to request mode, shortens the horizon and moves the phone number above the calendar. The storm and insurance leads guide covers the rest of that week, from triage questions to duplicate canvass leads.

Texts, emails and the inspector's phone after she taps confirm

A booking is only as good as the message that follows it. Homeowners book, then wonder whether it worked. Inspectors get booked, then forget to look. Each side needs a confirmation, and the real question is which system sends it.

Try the demo booking page, then see a Phoenix quote tool

The booking page on our roofing demo shows the homeowner's side: six short steps, about a minute, a confirmation text at the end. It is a demonstration site we built, not client work, and it is not wired to anyone's AccuLynx account. It does answer the first question owners ask, which is what the homeowner actually goes through. The demo's roof inspection page shows where a booking button earns its place.

For a real roofer, American Roofing & Waterproofing in Phoenix, we built the site around a custom instant-quote tool that turns visitors into booked inspections, plus a multi-step estimate form and a free 21-point inspection offer. We do not claim that company runs AccuLynx; the point is that booking flows are work we ship, and the project is in our work. Roofers weighing other systems can read our ServiceTitan integration section, and the design side is on our roofing website design page.

From the first call to a working booking page, with prices

1. 1

   Agree the slot rules

   Which calendar, how long a window, how many per day, which ZIP codes and what the confirmation says. Written down and approved before any code.

2. 2

   Turn on API access

   You enable AppConnections and your administrator creates a key for each location. The key goes into the site's server settings, never the browser.

3. 3

   Map the lead

   Lead source, job category, work type and trade type for a booked inspection, chosen from the values already set up in your account. The lead forms page has the full field map.

4. 4

   Build, then test in the live account

   With no sandbox, test bookings run in your location under a test lead source, and each one is closed out by a named person.

5. 5

   Launch and keep a log

   Every booking is logged on the site with its AccuLynx job ID. A failed write is queued and retried, and a person hears about it.

On price: inspection booking is included in every new site package from $1,500, fixed, on our web design pricing page, and we recommend the 51 to 70 page package at $5,750. With 0% website financing, 25% goes down and the rest spreads over up to twelve months; for a $5,750 build that means $1,437.50 at the start and twelve payments of $359.38. Adding booking to the site you already have is quoted after a free review, from $575 depending on complexity, and our API integrations page puts a typical two-system connection at one to three weeks.

Start with the free mockup, a free site audit of what you run today, or the AccuLynx website checklist if a launch is already close. Or call (210) 346-0848 and tell us how your inspection calendar works now.