Live availability requests
Customers see open windows for their service type, and each request is held until the office confirms it.
SIZ Group builds a beekeeper booking website that lets each customer pick a real arrival window, with intake forms matched to every job type and confirmations that state exactly what happens next.
A swarm does not wait for a callback. Spring swarm calls arrive in bunches, often while the crew is already on a cutout across town, and the office has to decide in minutes which visit can move. A booking site that shows real openings lets the customer pick a window without a phone exchange. Online booking for bee removal works best when the calendar behind it is accurate.
Booking is different across the trade. A same-day capture needs a slot held for emergencies, hive inspection scheduling can be set well ahead of the season, and pollination contracts for orchards are booked early against bloom dates. One calendar rule for all of them causes double bookings.
Most offices take a call, write the address on a sticky note, check a shared calendar and text the customer back later. The slip happens between the note and the calendar, when the same crew is pencilled into two jobs or a swarm request never makes it onto the board.
Details disappear too. The office rarely learns whether the bees are in an open cluster, a tree or a wall until the crew arrives, so the wrong equipment goes on the truck. An intake form that asks those questions before the slot is confirmed fixes most of that. The availability request form should stay short, so the customer answers the urgent questions and nothing more.
The office manager will want to see the calendar working with real crews, not a demo. Test it with two crews, three job types and an open slot that someone books at the same moment another person does. The booking should block that slot for both of them and never offer it twice.
Appointment confirmation emails matter as much as bookings. Each customer should receive the arrival window, the crew lead's name, what to have ready and the number to call if plans change. Check each message on a phone before launch.
Customers see open windows for their service type, and each request is held until the office confirms it.
Swarm captures, cutouts and inspections each ask the questions the crew needs before it is dispatched.
Customers attach a photo of the cluster or entry point, which helps the office judge how urgent the call is.
The customer gets an email and, with consent, a text naming the window and the crew lead.
A reminder goes out the day before with a link to move the visit without calling the office.
The office sees each crew's day in one view, with same-day requests placed in the held emergency slots.
A homeowner finds a bee cluster under the deck on a Friday evening. They open the booking page, choose swarm capture, enter their street and attach a photo of the cluster. The form asks whether the bees are open air or in a structure, and whether the homeowner can keep pets clear of the deck.
The page shows the next open capture window for the nearest crew. The homeowner picks it, and a confirmation arrives with the crew lead's name and a note to keep the area clear. Next morning, a reminder message lets them move the visit with one link if the plan changes.
If the homeowner later finds a second cluster, the same booking flow starts again with the first visit already on record, so the office can see both jobs together.
Most beekeeping crews schedule work in field service software such as Jobber or Housecall Pro, or in a shared Google Calendar. The booking site should write into that same system, so the office never copies a request by hand.
Where the office keeps a spreadsheet, the form can add a row instead. Name the tools on the scoping call, because the handoff is where double entries and missed requests start.
Ask the office to list every place a booking lands today, including group texts and voicemails. Each source needs a clear home in the new system, or the old habits keep running alongside it.
Automated texts need the customer's consent under federal telephone rules, so the form records a clear opt-in and the reminder only sends to customers who gave it. Addresses, gate codes and photos belong in the office system, not in a URL or a public page.
Many states ask beekeepers to register colonies or apiaries, and any pesticide or miticide treatment must follow the product label. The site should only offer services the business is registered and insured to perform.
Yes. The page reads the same calendar your office uses, so a customer only sees windows a crew can take. Emergency slots can be held back for same-day swarm captures and released if no call comes in.
The request is saved with the photo and the address, and the office is alerted by email or text. Nothing is confirmed until a person has checked the request, so the customer is told when to expect a call. Swarm requests are never auto-confirmed, so the crew can still decline a job it cannot reach safely.
No. A customer can book with a name, phone number, address and a few job questions. Accounts are optional and only needed for repeat customers who want past visits in one place. Repeat customers can save their address and past job notes, which saves the crew asking the same questions each spring.
They are stored in the office system with access limited to staff and the assigned crew lead. They never appear in a web address or on a public page. Retention periods are agreed with you during the scoping call.
Book a free scoping call and we will walk through your crew calendar, job types and confirmation messages with you.