Let people pick a time inside your form — in your design, in their time zone, without a single request to Calendly from their browser.
Step 3 of 4
When suits you?
Intro call · 30 min
Times shown in your time zone · Europe/Berlin
Sending someone from your form to a Calendly page is where enquiries go to die. QueryCue puts the booking inside the form: one more step, in your typography and your colours, showing the real free slots from your calendar.
Add a booking step to the flow, pick which of your Calendly event types it books, and that’s the setup. The visitor sees days and times — nothing that looks like someone else’s product. And because they’ve already told you their name and email earlier in the form, QueryCue doesn’t ask twice: it recognises those fields and passes them straight to Calendly.
The booking itself happens when the form is submitted, not when a time is clicked. Nothing is reserved while someone is still filling in step 4 — and if the slot can’t be booked, the form doesn’t submit. You never end up with a lead who thinks they have an appointment they don’t.
Paste a Calendly personal access token in the settings and hit „test connection”. It’s stored encrypted and never sent back to a browser.
Choose the event type from a dropdown of your real Calendly events. The builder also lists the questions Calendly requires for that event, so you can add matching fields to the form instead of finding out the hard way.
Free slots are fetched by your server, rendered as native form elements, and grouped by day in the visitor’s own time zone. Long ranges are stitched together automatically — Calendly’s seven-day query limit doesn’t leak into the UI.
On submit, QueryCue books the invitee: name, email, phone if needed, guests, the location — and the answers to Calendly’s required questions, mapped from the fields the visitor already filled in. Calendly then does what it does best: calendar invite, reminders, workflows.
In native mode the visitor’s browser loads nothing from Calendly — no widget script, no iFrame, no cookies from a US scheduling service. Every call to Calendly is made server-side. Prefer the classic widget? Then it only loads after the visitor agrees to it.
Days and slots are ordinary form elements in your design system. No visual seam between „your website” and „someone’s booking tool” — which is exactly where people bounce.
Answers and appointment arrive together. The booked time lands in the submission as a readable date, so it shows up in your notification email and in the webhook payload like any other answer.
Anything that can create real calendar entries from the open web needs guarding. The booking route takes a nonce, is rate-limited per visitor (bookings and slot lookups separately), and only accepts event types that genuinely belong to the connected account — nobody can point it at someone else’s calendar. The time zone a browser sends is checked against a whitelist rather than trusted.
And if you’d rather use Calendly’s own widget after all, nothing loads behind the visitor’s back: they see a short notice — who receives the data, that their IP address goes to Calendly in the US — and the widget appears only after they click to load it. Their choice is remembered for the visit, not stored in a cookie.
Calendly’s own strictness is handled too: required invitee questions are answered from the fields the visitor filled in, matched by label and — where needed — by type, with phone numbers normalised to international format. The question text is passed through byte for byte, because Calendly matches it exactly; a stray trailing space in a question name is enough to make it reject the booking as empty. QueryCue got that wrong once, in production. It doesn’t anymore.
It travels with everything else the form collected:
Real Calendly availability, inside your form, without sending anyone away. Comes with Pro.