IntegrationsCalendly
Meeting over, review request on its way.
Calendly reports every booking, Citypicked plans the request for the end of the meeting. You have nothing left to remember after the call.
IntegrationsCalendly
Calendly reports every booking, Citypicked plans the request for the end of the meeting. You have nothing left to remember after the call.
Two steps
The trigger is the new booking in Calendly, the action is Citypicked. You map the fields once.
At booking
In Calendly you can give every event type its own questions. A checkbox gets the consent, a field for the mobile number makes texts possible. You map both in the Zap.
When plans change
Until the meeting ends, the request shows as planned under Requests. If someone cancels, does not show up or reschedules, you cancel it there.
Calendly Standard or higher. Calendly offers the Zapier connection from Standard up.
No. A Zap with one trigger and one action runs on Zapier's free plan.
Nothing extra. Sending through Zapier comes with Pro. Texts use credits as in the app.
Citypicked plans requests up to 30 days ahead. If a meeting is further out, Zapier shows you the error, and you send the request from the app after the meeting.
Yes. In Zapier you can add time to the end time, two hours for example. That takes an extra step, so a Zapier plan with multi-step Zaps.
Your first request goes out in five minutes.