Call people who book a demo

​

When to use it

• People book meetings with your team in Calendly, Chili Piper, HubSpot Meetings or a similar scheduling tool.
• Someone on your team, often an SDR, confirms and qualifies bookings before the meeting.

​

What you need

• A list the rep dials, its _id, and an API key. See Before you start.
• A phone number question on the booking page, preferably required.
• Zapier or Make, or your scheduling tool’s own webhooks with a small piece of code.

​

Set it up

​

What to send

curl https://client-api.salesfinity.co/v1/contact-lists/YOUR_LIST_ID \
  --request POST \
  --header 'x-api-key: YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
    "first_name": "Alex",
    "last_name": "Moreno",
    "email": "[email protected]",
    "company": "Quarryline",
    "phone_numbers": [{ "type": "mobile", "number": "+15125550163" }],
    "notes": "Booked: Demo, Thu 30 Oct, 10:00 AM ET, with Sam. Call to confirm and qualify.",
    "tag": "Booked a call"
  }'

1. Trigger: Calendly → Invitee Created or Rescheduled, Chili Piper →
   Meeting Created, or your scheduling tool's trigger for a new booking.
2. Filter by Zapier: only the event types that should get a call.
3. Formatter → Date / Time → Format: the start time, in the rep's
   time zone.
4. Formatter → Numbers → Format Phone Number, to E.164.
5. Action: Webhooks by Zapier → Custom Request
   Method:  POST
   URL:     https://client-api.salesfinity.co/v1/contact-lists/YOUR_LIST_ID
   Headers: x-api-key     YOUR_API_KEY
            Content-Type  application/json
   Data:    the JSON from the cURL tab, with the booking's fields
            mapped into it, and "tag": "Booked a call".

1. Trigger: Calendly → Watch events, or your scheduling tool's module
   for new bookings.
2. Filter: only new bookings (not cancellations), and only the event
   types that should get a call.
3. Action: HTTP → Make a request
   URL:               https://client-api.salesfinity.co/v1/contact-lists/YOUR_LIST_ID
   Method:            POST
   Headers:           x-api-key = YOUR_API_KEY
   Body content type: application/JSON
   Body input method: JSON string
   Body:              the JSON from the cURL tab, with the booking's
                      fields and the formatted start time mapped into
                      it, and your tag.

​

Test it

1. Start dialing the list, with your phone ready.
2. Book a meeting on your own booking page, with your own name, email and mobile number.
3. Check that the notification shows, that Next up shows your name, and that your phone rings once the current call is logged. The notes should show the meeting time in the rep’s time zone.
4. Cancel the test booking.

​

Good to know

• Who makes the call. If an SDR confirms every booking, send them all to the SDR’s list. If each host calls their own bookings, give each host a list and send each booking to the host’s, for example with a Formatter → Utilities → Lookup Table step from host email to list ID.
• Booking answers with quotes or line breaks. In a Zapier Custom Request, they break the JSON and the API answers 400. Clean them first, as in Clean up the reply text.
• Meetings that start soon. A booking for the next half hour doesn’t need a confirmation call. Add a filter on the start time if your reps would rather skip those.
• Cancellations. A cancelled booking doesn’t take the person off the list. The rep sees the booking in the notes, so tell reps to check the calendar before they confirm.
• Reschedules. A reschedule can arrive as a new booking: Calendly’s Zapier trigger fires for both. If the person is still on the list, they move to the top again and take the tag, but keep the notes from their first booking. So the old meeting time still shows. Tell reps to check the calendar, or remove the old contact first.