An online booking widget for field service requests
People decide they need a plumber at 10pm, not at 10am. Call it a service booking widget, a website appointment widget or online booking for field service — a request form on your Opsler website takes the enquiry while they’re still motivated and puts it in a queue for your office — waiting in the morning instead of gone to whoever answered the phone first.
The form on your Opsler site, and the queue it arrives in. A submitted booking lands as Pending — nothing reaches your calendar until you approve it.
Booking request versus confirmed appointment
This is a request flow, not a self-scheduling one, and that is deliberate. Nothing is committed to your board by a stranger filling in a form. A submission arrives as Pending, your office reviews it, and only then does it become Approved and get converted into a job — or gets cancelled if it isn’t a fit.
A live-availability booker only works if your calendar is a perfect reflection of who can actually do what, on the day, with the right parts on the van. For a shop of one to thirty people that is rarely true — the dispatcher holds most of that knowledge. A request queue captures the customer while they’re ready to buy and leaves the scheduling decision with the person who knows whether it can actually be done.
Where the booking form actually lives
Worth being direct about: there is no script you paste into an existing, separately-hosted WordPress, Wix or Squarespace site. The booking form is built into your free Opsler-hosted website — if you want this request flow, that site is where it lives.
What you can do is link to it from anywhere — a social media bio, a Google Business Profile, a QR code on a van, or a “Book now” button on another website pointing at your Opsler page. That is an ordinary hyperlink, not a special integration, and it is the honest version of what “embed it anywhere” can mean here.
Choose service, location and customer details
The form takes the customer’s name, phone and email, the service they want, their address, a preferred date and a preferred time, plus a description and any additional notes. That is the complete list — there is no photo-upload step on the booking form itself. If photo evidence matters to a job, it’s captured later, on the job record, once a technician is assigned.
Showing availability without exposing the internal diary
The customer states a preferred date and time; the form does not show them a live view of your technicians’ calendars, and nothing about their submission is checked against actual availability before it’s recorded. That is a limitation compared to a full self-scheduling product, and it is also what keeps your internal schedule private from anyone who fills in a public form.
Review, confirm or decline a request
Every submission lands in a Pending bookings queue with everything the customer told you. From there your office approves and converts it to a job on the dispatch board in one step, or cancels it if it isn’t going ahead. Nobody on your team is ever surprised by a job that appeared on the board without a human deciding to put it there.
Creating the customer and job without duplicates
A phone number Opsler already recognises is matched to the existing customer rather than creating a second record, and the request is routed to the team from that customer’s most recent job — so a returning customer reaches the crew who already know the property. A first-time enquiry goes to the whole office, since there is nothing yet to route on.
Confirmations, reminders and rescheduling
Your office is notified when a new request arrives, so a submission doesn’t sit unseen in the queue. What doesn’t exist yet is an automatic confirmation or reminder sent back to the customer the moment they submit — that conversation happens when your office calls or messages them to approve the request.
SMS is planned but not live on any Opsler plan today. Any confirmation or reminder you send the customer at this stage goes through your own phone or email, outside the booking record.
Accessibility, privacy, spam and security
Worth stating plainly rather than leaving you to discover it: the public booking endpoint has no CAPTCHA or rate-limiting in front of it today. In practice this rarely matters, because an unwanted or automated submission simply sits unapproved in your Pending queue rather than touching your schedule or your customer list — but if spam submissions become a real problem for your business, that is a genuine gap to know about rather than a feature to assume.
Online-booking product test checklist
Four things Opsler does, and four it deliberately doesn’t. Take the same eight questions to any field service booking software you’re evaluating.
| Capability | Opsler | Detail |
|---|---|---|
| A request form on your Opsler-hosted site | Yes | Built into the free branded website; not a script for a separate site |
| Requests land in a Pending queue, not straight on the board | Yes | Approve, decline or convert to a job — nothing is scheduled without you |
| Repeat customers matched, not duplicated | Yes | Matched by phone and routed to the team from their most recent job |
| The office is notified when a request arrives | Yes | An async notification fires on creation |
| A photo-upload field on the booking form | No | The booking record has no photo field at all |
| An embeddable widget for a separate WordPress, Wix or Squarespace site | No | No embed script or iframe exists — the form lives on your Opsler site only |
| Live calendar availability shown to the customer | No | The customer states a preferred date and time; nothing is calendar-verified |
| Spam protection (CAPTCHA or rate limiting) on the public form | No | None found in the code — an unwanted submission just sits unapproved in the queue |
Included on every plan, free Budding included — two seats, 50 jobs a month. Pro is $25 per seat per month, no seat minimum, with a 14-day trial that doesn’t ask for a card.
Online booking widget questions
In Opsler, it's a request form built into your free Opsler-hosted website: a customer fills in the service they want, their address, and a preferred date and time, and it lands in a Pending queue for your office to review. It is not a self-scheduling calendar and it is not a script you paste into a separate, already-existing website — the form lives on the site Opsler builds for you.
Requests, always. A submission arrives as Pending with everything the customer told you — service, address, preferred date and time, notes. Nothing touches your schedule until someone in your office approves it and converts it to a job, or calls the customer back first if the timing needs a conversation. That is deliberate: a live-availability booker only works if your calendar perfectly reflects who is actually free, which for most small teams the dispatcher — not the software — still knows best.
On the duplicate side, Opsler matches an incoming request by phone number against your existing customers rather than creating a second record, and routes it to the team that handled that customer's most recent job. On the double-booking side, the honest answer is that the queue is the safeguard, not the form — because nothing is scheduled until your office approves it, there's no way for two unrelated requests to land on the same slot automatically. The trade-off is that approval is a manual step, not an automatic one.
Ready to Run Your Business Without the Chaos?
Scheduling, dispatch, estimates, invoicing, customer portal, and a free branded website — start completely free, upgrade to Pro when you scale.
Free forever on the Budding plan. No credit card required.