Hey there! There are multiple ways to do this, and it all depends on your initial trigger (ideally you want to limit the number of times the Slack message is sent to two per day - as this will solve your issue outright),  but:

If you want to delay the trigger based on the sender’s availability - I actually think you might need to manage state here (ie. use Zapier’s storage to determine whether the message meets the two-hour criteria) https://zapier.com/apps/storage/help

If you want to delay the trigger based on the zap itself triggering, you would need to use the Zapier Schedule feature - Yes.  https://zapier.com/apps/schedule/integrations

If you want to ensure that a recipient doesn’t get more than two per day - I think you might be best using another app (like a CRM or Airtable) to manage state and sending eligibility

Hi @deliveryman! @Saastronomical has some great solutions here

Just to add a little more detail to the first, would you could do is have a Zap that collects all of the availability and puts it somewhere - you could use Storage or Digest to do this, depending on the complexity of the information. Digest is a little easier to use, so lets assume that we use that, the Zap would look like this:

• Trigger: Slack
• Action: Digest - Append Entry and Schedule Digest (set to manually release the digest)

Then you would have a Zap that releases the digest, which would look like this:

• Trigger:  Schedule by Zapier (set the Zap to trigger when you want the text to be sent
• Action: Digest - Release Digest
• Action: Twilio - Send message

I hope that makes sense - let us know if you have any questions!