File Expirations as Triggers for Automations

Hey ​@Robert Manzone!

This is a great idea! Right now, I’ve found that a workaround is to create follow ups around the time that the file is set to expire.

For example:

If a proposal expires 2 weeks after sending:
1 follow up 4 days after contract not signed

1 follow up another 4 days after that if contract isn’t signed

1 follow up another 4 days after that if contract still isn’t signed. In this email, you can reiterate that their proposal is expiring in 2 days

1 follow up 3 days if contract isn’t signed letting them know that the contract has expired. You can also automatically add a tag and label it as “proposal expired” if you’d like!

But it would make building and keeping track of automations smoother if we could have the expiration as a trigger. I’ve added this as an Idea so the HoneyBook team can get an idea of which features would be most helpful for their users. You can upvote the idea here if you’d like: