Skip to main content

Hi everyone, I need to implement a new project but I’m struggling to determine the most streamline setup. It’s quite complex as there are several Zaps that will be affected. Further details below.

Currently, when a booking is confirmed in Airtable it triggers the events shown in the screenshot below. This zap works well, but I want to send a different Booking Confirmation Email (step 4) only when it is the client’s first booking and then complete all the other steps as per normal.

 

Part of the complexity is that I process bookings for multiple states so the confirmation emails reference different things, and most importantly the calendar invites have different time zones for each state.

I’ve considered creating a single zap for the First Booking confirmation email only, and using a path to setup versions for the different states. I would need to keep the Booking Confirmation zaps as normal so it still triggers for clients who have already booked with us. However, those that receive the separate First Booking email, would still need to enter the existing Booking Confirmation zap so they receive the calendar invite and invoice. I don’t think it’s possible to skip a step and continue to the following one.

The First Booking email is an introduction to our business and provides helpful resources. Return clients don’t need all this information so we don’t want to overload the current Booking Confirmation emails. I don’t want to create an additional zap for an email that provides the introductory information and keep the current booking confirmation zaps as normal, because it will provide a poor customer experience by spamming them with emails and sharing content that isn’t quite tailored to them.

I’d love to hear your suggestions on how this can be implemented. It’s been quite difficult to put into writing, so please let me know if further clarification is required. I really appreciate any comments you have. Thanks!

Hi ​@Apollo, I hope you’re doing well 😊

 

Thanks for sharing the detailed breakdown of your workflow. I think the first step here will be to Identify First-Time Clients. I would suggest:

• Adding a step in your Zap to check if the client has booked before.

• You might want to use the “Find Many Records (With Line Item Support)” action (or another database you’re using to track bookings). This step queries the table for an existing record of the client.

 

The details of how you’d go about setting up this search step will depend on how your database is set up, and how you’d be able to identify if the customer was a First Booking or not.

 

For example, if you create a Record in Airtable for each booking, if only one Record were found in your search step, it would mean that it’s that customer’s First Booking.

 

You could then use Paths by Zapier to segment the workflow based on if the record that triggered the Zap is a First Booking or not.

 

Let me know if this points you in the right direction, and I'll be glad to help you continue to troubleshoot this workflow.

 

Have a good one! 🙌


Hi ​@Apollo,
 
We just wanted to see how everything is going with your Zap. Did Sebastian’s recommendation get the job done? Feel free to reach out if you need further assistance with your Zap. We're glad to address any concerns and assist you.
 
We're looking forward to your response.


Reply