Book meetings from your website chat with Cal.com

What happens in a chat

1. On your site

   Hazel offers your link

   When a visitor’s question mentions booking or a meeting, or Hazel has nothing to answer from, the reply ends with a Book a meeting button that opens your Cal.com link.

2. On your site

   The link carries a reference

   Hazelchat adds a random reference for that conversation to the link. Nothing about the visitor goes into it.

3. In Cal.com

   The visitor books on Cal.com

   Your Cal.com page, availability and confirmation emails stay as they are. Hazel never books, moves or cancels a meeting itself.

4. In Hazelchat

   Cal.com confirms it

   Cal.com sends a signed notice when a meeting is booked, cancelled or moved. Hazelchat matches the reference to the conversation.

Set it up

1. In Hazelchat

   Make booking the next step

   Open Behaviour → Actions, set Next step to Book a meeting and paste your Cal.com link as the Destination URL. Publish your agent.

2. In Hazelchat

   Connect Cal.com

   Under Confirm bookings on the same page, click Connect Cal.com. If your booking page runs on your own domain, enter it first. Copy the Subscriber URL and the Secret: Hazelchat shows the secret only once.

3. In Cal.com

   Add the webhook

   In Cal.com, open Settings, then Developer, then Webhooks, and choose New. Paste both, choose Booking created, Booking cancelled and Booking rescheduled, leave the payload template empty and save.

4. In Hazelchat

   Wait for the first notice

   The card says “Waiting for Cal.com” until a signed notice arrives (Cal.com’s ping test or the first booking), then “Connected” with the time of the last notice.

What you see

• Meetings booked from chat

  In Analytics, meetings whose booking arrived in the period, minus those cancelled since. Your own installation tests are left out.

• On each conversation

  In Conversations, a Booked a meeting or Booking cancelled badge, and a Bookings filter.

• Moved meetings

  A rescheduled booking stays one booking. It never counts twice.

• Clicks are not bookings

  A click on the button is never counted as a meeting. Only Cal.com’s signed notice is.

What Hazelchat keeps

A hash of Cal.com’s booking id, whether the meeting was booked, cancelled or moved, and the conversation it belongs to. Hazelchat keeps no name, email, answers to your booking questions, meeting time, location or meeting link.

The link gets utm_content=hz_ plus the reference, replacing any utm_content of your own, and utm_source=hazelchat and utm_medium=chat where your link has none. For Cal.com it also carries the reference as metadata[hazelchat_ref] and hazelchat_ref, which Cal.com passes back with the booking.

Calendly and other booking tools

Any HTTPS booking page can be your next step: Calendly, your own form or another tool. Hazel offers the link the same way. Hazelchat cannot confirm those bookings yet, so they do not appear in Meetings booked from chat. Calendly also sends booking notices only on its Standard plan and up.

Limits

• Only bookings made through the link in a chat count. A booking without the reference is not stored; the card tells you one arrived.
• If a booking you know came from a chat was not matched, add a hidden booking question with the identifier hazelchat_ref to the event type in Cal.com. Cal.com fills it from the link.
• Booking pages on your own domain must be entered in Hazelchat. Organisation pages on cal.com are recognised on their own.
• The figure is for your own use. Anyone holding the secret, including you, could send notices for your conversations.
• Disconnecting deletes the secret in Hazelchat and stops adding the reference. Delete the webhook in Cal.com too.

Questions