Okay, sometime today / tonight - v2.1 be pushed, afterwards the message and call filter will be pushed to stop rate limit and filter for quality traffic. There will be an migration guide for those to switch over from Stripe Express to Stripe Oauth. And a minute-to-wallet interrogation guide as well. Before reaching out to support, see if your concern is addressed in the patch notes. We'll be standing by closely all day today / tomorrow to ensure clean and easy transition. Here are the patch notes: ## Platform / infrastructure: - We now have a pre-processing env for messages and calls to filter out duplicate messages caused from GHL double installs - messages will only come through twice - We now process only active, paid workspace sub-accounts - all other data will be filtered to clean up rate limiting and processing - should make everything generally faster and more reliable (messages not showing etc) - Autopilot settings now active - sleep timeout, max responses etc, keep an eye out for stops based on these metrics - Call handling and re-checking - we now do a "double-take" on calls to ensure timestamps and information is accurate and accurately collected and displayed - Billing - billing a "double-take" to ensure information and limits are accurate because they are more heavily enforced with this update, example if sub-account limit is 3 but there are 4, we have time and creation settings to disallow this but will require action on your part before limits are automatically placed, calls will not process if there is no wallet balance / wallet auto-pay (post-v2.1 push to ensure easy transition) - Minutes -> wallet conversion, we will buy back minutes (from direct accounts) to fill your wallet initially so there is no down time - More error handling on the GHL and LLM side - .... and more ## Agency / Subaccount Management: - Edit permissions (tab viewing) has been patched and updated to hide and automatically re-route home page for sub-account (defaults to all) - Edit account (new) edit the information pulled via oauth like location name, address, website etc, we use this to build a profile for assistant creation (defaults to oauth information) - Manage limits (patch & new) has been patched and expanded upon - Allow for unlimited or define a hardset limit for assistants, messages, calling time (in mins), and phone number purchasing (defaults to unlimited on all) - Access control & security (patch and new) has been expanded upon ensuring data is safe, secure and only accessible by people you want it to be - invite members (clients or other users) to the sub-account and manage access control (remove) ---- *** For initial push, this will be defaulted to allow all, in the future this will be defaulted to only invited members - Connection options (new) create and manage connection to sub-accounts with the connection menu - Create / manage connection at the agency level or sub-account level, allow external sub-accounts to be added an connection to be reset at the account level (defaults to agency connection) - Re-billing (patched & new) connection switched from stripe express to stripe oauth meaning you will connect your own stripe account rather than creating a stripe account through express. Rebilling & subscription management are managed separately for wallet billing, a client can be rebilled without a subscription, a client can have a subscription without rebilling and either / or / both

:)

So, going through some restructuring for this release - it was brought up some call errors, I usually keep an eye on error rates and calls are flowing So I took a deeper look to see what it was - so, a call will get a classification of error for a couple of things like dial no answer (the most common one, just means the number didnt answer), inactivity (someone answers and just stays quiet on a contact initiates setting), busy tone (number doesnt exist or is a company name that is busy), dial failed (phone number doesnt exist or verizon tone), etc etc etc so, now that I have realized this - I will have deeper analytics to let you know exactly what happened with the call. We will also tag the contact with disposition so you can trigger WF - we store it but it the classificaiton shows also, I saw something about the disparity of mins - check the recording, its down the MS - while the call view portal may show 1 min, its a round up from the ms above 30 secs. This is just for that view, the actual amount credited is all done in MS from the twilio call 18 secs here & there adds up - trussst me hahah -- Just thought I would let you know that and working to get that more transparent in the portal and actionable in GHL I have a ton of fun stuff coming up

After talking with businesses from different niches and types (SaaS, SMMA, AI Automation, Enterprise) - we have decided to go the GHL-type route with billing with transactional things like voice minutes being credited to a wallet and payed down via auto-pay / manual pay / min credits And subscriptions being a added bonus for those wanting to use it as a saas to overwrite subacct snapshot limits

I was trying to resync a calendar and it wasn’t working so I’m trying to reset my oauth and it’s just going in a circle. I tried to redo it four or five times now and it’s just doing the same thing. Is there an update happening right now on assistables end?