What is a booking widget?

A booking widget is a small form or button you add to your website so customers can request service. The goal is to capture name, email or phone, service details, and preferred timing without back-and-forth.

Do I need a separate scheduling tool?

Not necessarily. Many teams start with an inquiry form and confirm the time manually. If you want full appointment booking, you can still use a widget to capture details and then schedule the job inside Asteriq.

Where do the requests go?

With Asteriq, requests land in your Request Inbox so you can follow up, create a client, and turn it into a quote or job when ready.

How do I reduce spam submissions?

Use bot protection (like Turnstile), keep the form short, and avoid exposing direct email addresses in the form. Also consider requiring email or phone for follow-up.

Can I embed the widget or use a hosted link?

Yes. Most teams either embed the widget inline on a Contact page, or use a button that opens a modal or hosted request page.

How to add a booking widget to your website

Why add a widget

A widget improves conversion because it removes friction. Instead of “call us” or a generic email form, customers can request service in under a minute — and you get structured details you can act on.

Faster replies: requests land in one place, ready to assign.
Cleaner info: service type + notes + contact details are captured consistently.
Fewer missed leads: no buried emails, no “I forgot to reply.”

Two embed options

Most teams use one of these:

Option A: Inline widget (best for Contact / Get a Quote pages)

The widget appears directly on the page. It’s the cleanest experience and usually converts best.

Option B: Button → modal or hosted page (best for simple websites)

You keep your page clean and open the form only when the visitor clicks “Request a quote” or “Book a visit.”

Example embed snippet

Your app should show you the exact snippet inside Settings → Request Widget. This is a typical pattern:

<!-- Asteriq Request Widget (example) -->
<div
  id="asteriq-request-widget"
  data-widget-slug="YOUR_WIDGET_SLUG"
  data-mode="inline">
</div>

<script async src="https://app.asteriq.app/widget/v1.js"></script>

Replace YOUR_WIDGET_SLUG with the slug/public id you see in your widget settings.

What to ask for (keep it short)

The fastest way to lose leads is to ask for too much. Start with the basics:

Name
Email or phone (at least one required)
Service needed (dropdown is ideal)
Notes (optional)
Preferred date (optional — you can confirm later)

If you serve multiple services (handyman + cleaning + HVAC), add a service selector so the request is categorized immediately.

Setup steps

Create a Request Widget in your CRM settings (choose inline or modal).
Choose your services (the list shown to customers).
Decide what fields to collect (start minimal).
Copy the embed snippet and paste it into your website.
Test it on mobile and desktop, then submit one test request.

Best practices

Put it where intent is highest: Contact page, Services page, or a “Get a Quote” page.
Use one clear CTA: “Request a quote” or “Send a request” (avoid multiple buttons).
Confirm expectations: “We reply within 24 hours” reduces anxiety.
Protect against spam: bot protection + a simple honeypot field.
Follow up fast: the first 15–60 minutes matters more than any design tweak.

FAQ

Should I call it “booking” or “request”?

If you truly allow customers to pick a time slot automatically, call it booking. If you confirm the time later, call it a request — it sets the right expectation and reduces no-shows.

Can I add this to Wix / Squarespace / WordPress?

Yes in most cases. You typically paste the snippet into an “Embed” or “Custom Code” block. If your platform restricts scripts, use the hosted request link instead.

What happens after a request is submitted?

The request should land in your Request Inbox where you can assign it, create a client, and turn it into a quote or job.