I've tried putting strings and exceptionally long numbers in my zip field for my beer app. Just returns an error message. I'm sure this could be used for redirects. We would probably create a separate middlewear file for just this.
You don't need to include the status code. That's just window dressing.
Project update: 50% complete with the Job scheduling. I am successfully moving jobs out of the job database to the queue, if they are a recurring job (happens tomorrow), I refactor the new job date to be for tomorrow at the same time. Next step is running through the job queue, and checking for jobs happening within the next 5 minutes, and pretty much doing the same thing.
once I am done with this process (which should wrap up almost all of that code), I am going to write up the trello docs, and move on to some interface design stuff/logo/colors etc.
I don't really like assumptions. I'd rather be certain that the concierge is available by them checking in. This way, from a legal standpoint, they've entered into a brief agreement that they are willing to take calls.
general logic is that the scheduler is going to be checking for a concierge to add to a call within 1/2 hour of the call, maybe sooner (we can change that if we need to), if there is a concierge available (available:true), we set them up for the call.