What this workflow solves
When a meeting is booked, enroll selected decision makers at the account in a deal-support sequence.
A meeting is just the start. To move a deal forward, you usually need more than one person bought in. The economic buyer, the technical champion, the user. If you're only talking to the contact who booked, the deal stays narrow and brittle. One person leaves, and the deal stalls.
This recipe catches every meeting the moment it gets booked and starts a deal-support motion with other decision makers at the same account, so the relationship widens before the first call even happens.
How the workflow works
- Trigger: Meeting booked
- Paths: Splits decision makers from everyone else
- Decision makers path: Adds the right contacts to a deal-support sequence
- Else path: Creates a follow-up task for the rep
How to set it up
This recipe is built from scratch. Open Workflows, click New workflow, and start with a blank canvas.
- Add a trigger and select Meeting booked. Choose whether the workflow runs for any user's meetings or only meetings booked by you. Add filters for the type of accounts where multi-threading matters most.
- Add a Paths block. Create one path with a filter that identifies decision makers at the account, and leave the Else path for everyone else.
- Under the decision makers path, add an Add contacts to sequence action. Pick your deal-support sequence and choose how leads should be distributed.
- Under the Else path, add a Create one-off task action so the rep follows up directly with other contacts at the account.
- Hit Launch.