Cool thank you appreciate it! For now, I was planning to provide the prompt to help the community 🙂 . I will say that I used the node.js moment module to help with the parsing, validating, manipulating, and formatting dates. Also, in the make.com structure for the availablity check logic, I created two streams of logic, one for the specific date and another for the 90 day window calculations. Ultimately, the goal is to have a common function between them that does both. Also, before starting any calculations on entry into the webhook request, I call a custom server method to validate the appointmentRequest parameter value to resolve 2023 dates, changing ordinal days to cardinal days (e.g. 20 first to 21, etc.), etc. Yeah, I've easily made hundreds of calls getting this appointment setter to work very reliably. Takes tons of testing and patience 😄 🙏 . Also for the verifyUserInfo, I was using an airtable User table to authenticate the user and restricting them to only place 3 calls. This is necessary if planning to share the phone number for demo purposes. So here I go into my custom server method after webhook request, and try to make sense of them speaking the access word; if correct, call count is incremented. If not, then I give them one more chance by asking them to spell it out. Worst case, they can always call again hehe. Even doing this they are still using prompt tokens but at least you can track them and worst case shut off the demo Voice Assistant for a couple hours, update your code logic to include a ban webhook response message to scare them off, or maybe just directly call them up since you have the phone number and cordially resolve any issues 😄. Also, the phone call number they say is just a placeholder in that a SMS message is actually going to their real phone number (blanked out in the demo video and specified as the alternate phone number).