Short answers to the things people ask most often. Need something not here? Email hello@heldly.io.
Do the time options stay reserved while my invitee decides?
Yes. The moment you confirm send in Claude, Heldly places a tentative event on your Google Calendar for each option offered — and on every co-host's calendar if it's a multi-host meeting. Your colleagues see you as tentatively booked across all three slots. When the invitee picks, Heldly patches the chosen one to confirmed and deletes the rest synchronously, in a single request. If two invitees somehow click Confirm at the same instant, an atomic database check makes sure only one wins — no double-book.
What if multiple people from our side need to be in the meeting?
Heldly handles multi-host meetings on every plan — up to six hosts on one meeting (one primary, five co-hosts). You ask Claude in plain English: “find times that work for me, Sara, and Jonas next week.”Heldly intersects all three calendars, places the same tentative holds across all three, and the picker email goes to your invitee framed as you + N. Every co-host gets a copy of every receipt; when the invitee picks, the confirmed meeting lands on everyone's calendar at once, with Meet attached.
Can the invitee bring their colleagues too?
Yes — you can add up to five additional invitee addresses when you propose. Only the primary invitee gets the picker URL (one decision-maker, no race over who clicks first). When they pick, every additional address is added to the Google Calendar event and gets a copy of the receipt.
Does the invitee see my whole calendar?
No. They see the slots you offered and nothing else. Heldly's picker is “here are three times” — not a public availability page. Your other meetings, their titles, who's on them — none of that leaves Heldly.
What happens if my calendar changes after I send the picker?
The tentative holds Heldly places ARE on your calendar — real Google events that anyone using Find a Time inside your org sees as tentative blocks on you. If something tries to land on top, you see both and resolve it the way you'd resolve any double-book. Heldly never silently moves a hold; the calendar is the source of truth. If you want fresh times instead, ask Claude to reschedule the meeting and the old holds are replaced cleanly.
What if the invitee never picks?
Heldly sends them a nudge 3 hours before the picker expires (24 hours default; 72 hours for shareable links you paste into Slack or LinkedIn). If the window closes with no pick, every tentative on every host's calendar is deleted automatically and you get an email — nothing for you to clean up. If they visit an expired link later, the page tells them you've been notified and you can send fresh times by asking Claude.
Can the invitee reschedule or cancel themselves?
Yes. Every picker email and every confirmed calendar event has a one-click “need a different time?” link. The invitee fills in a short note, Heldly emails you, and you ask Claude for fresh times — no back-and-forth thread.
What do I do after the invitee picks?
Nothing. By the time the invitee's confirmation email lands, Heldly has already patched the tentative to confirmed (with Google Meet on the primary host's calendar), deleted the siblings on every host's calendar, and sent the receipts. You get a Heldly notification; the meeting is already where it should be.
Does it work with Outlook?
Google Calendar only today. Microsoft Graph is a real engineering lift; we'd rather ship the best possible Google experience first than a half-version of both. If you'd switch from Outlook for Heldly, email hello@heldly.io — it moves the roadmap.
What about pricing, and where does my data live?
Free forever at 5 meetings/calendar-month — no card to start. Unlimited removes the cap at €19 / $19 / 199 SEK per host/month depending on country. Business is €29 / $29 / 299 SEK per seat (1-seat minimum) and adds the domain claim, SSO, SCIM, audit log, and signable DPA. Multi-host scheduling is included on every plan. Your data lives in Supabase in Dublin (EU). We don't sell it, share it, or train on it. Google Calendar OAuth tokens are encrypted at rest and never returned to clients. Full details on the Privacy and Security pages.