Implement Leadmo accounts and workflow strategy

[svange]

Description

note: we may need to add a delay (maybe 30 seconds) to all messages being sent through sms pipeline. There is a problem I'm not sure how to solve and this might help it... What do we do if somebody responds twice before the bot can respond once? The 30 second delay will protect the database from a corner-case race condition when fetching/writing the session to the DB... but it doesn't solve the problem entirely... I can make it more robust later, but it's non-trivial (need another idempotency table to lock the session in the DB and make the next one wait)...

note: setup account/workflow for testing and come up with testing strategy. When YOU get on the tuner to build an agent, do you want the user you're testing with to be created in YOUR account with your automations? Probably not, those of us making agents probably want to test with a "safe" leadmo account that won't send the user through a bunch of workflows. This will require retooling as currently the tuner creates a user in the account associated with the user's location id and api key.

note: add timezone to context. We probably want to add only essential information to the workflow. The fields I chose are there because they are fields the AI might want to update. In order to do this, we must satisfy the API with all required information (even stuff that hasn't come up in conversation, like city), so the values of those fields are mixed with the AI's change request to make the API call with all user info.

note: think about allowable dispositions for the bot. Perhaps we don't want to expose them all to the bot. Also, I need the list of "known" or "blessed" dispositions and descriptions of each so I can build the appropriate tool(s). (edited)

note: create overflow calendar. With all of these different resources available we may want 2 new leadmo accounts: Woxom AI (for all of the "golden" workflows and overflow calendar) and Woxom AI Testing (for creating users and appointments in the tuner app). With this scheme, we can make changes to the workflow in the Woxom AI Testing account and run thousands of automated tests against the resources in that account, and once the workflow is smoke-tested, we can copy it over to the Woxom AI account (and then clone it to the others). This gives us the flexibility of having a "stable" workflow (for restoring broken pipelines in other accounts) and a "development" workflow (for feature development). (edited)

Possible Solution

Mike is working on this, so validate environment once done

Additional context

No response

Additional context

No response