Do my custom tools transfer over with a new cloned AI Agent? - I'm expecting to build out on Agency Level for clients and want to easily transfer things over.

Here ya go, Quick update: - International users (mostly brazil) have been on my mind when it comes to rebilling and yes you resellers too - so we have a full oauth stripe integration - Granular subaccount managemenet - SaaS mode, rebilling, hard limits, redirect structure, access control is good to go - Orb booking and double voice is patched and orb will come out of beta into prod - this will lay the path for a suite of orbs and lead magnets to come - Copy bot by ID, duplicate, prevent copy by id, and more assistant management - Call Center -> granular call data with analytics and classification (by things like workflow id) with appointment booking metrics and tracking - Calls will disposition via tag and more robust notes as well as a beefed up post-call webhook with more data and collected information (first name, last name, email, phone, etc) - Extractions, tags, and custom tools have more safety parameters around them and have been beefed up for reliability - Everything is tool tipped and has tutorials attached so you have full context into how, what, when, where - for example importing numbers is a big one, the ball is in twilio park (I created a brand new twilio acct this morning and got errors on calls, twilio needed my indentity before I could make outbound calls <<<<<<) Here is where I need your attention: - Wallet Infrastructure - So, your clients activity will be credited to your agency wallet. Voice mins etc - you will be able to oauth your own stripe and rebilling them to cover cost or make margin on cost per min and, in the future, AI sent messages etc ^^ Just how highlevel works My hope with this is to virtually make it indestructible so we can focus on lead magnets, wow-factor for client acquisition and resources so im taking my time (you can be mad, id rather take the time to make sure everything is good other than putting it out and having to do patch work) tons more. loom below, ill post updates as I finish up Loom: https://www.loom.com/share/8a32704d7b2948da8b2a3d9860fc1b65?sid=cdd79974-a5d5-4cd1-819e-8bb8ddfd3e21

If you want to text and call from ONE phone number WITHOUT tediously switching each subaccount from LC phone over to twilio, then upvote this in ghl ideas. https://ideas.gohighlevel.com/ad-reporting-and-attribution/p/allow-sip-trunking-in-lc-phone This idea is to allow for sip trunking within LC phone itself instead of having to move over to twilio. 🛠️💥 Let's riot at GHLs door. Comment and **TAG** one other person to get as many as possible to upvote this. In the mean time, if you need to get it setup with twilio, here's a post about how you can do it. https://www.skool.com/assistable/phone-numbers-with-v2-prep-for-it-call-text-from-same-number?p=a9bed49a

I set up SIP thinking I could use the same number for both texting and calling. However, I quickly realized that in Assistable, you can’t assign both a text bot and a voice bot to the same phone number. This limitation made my initial setup feel a bit pointless. To simplify, I think it’s better to set up a voice bot on a dedicated Assistable-purchased number, then forward calls from my texting (LC) number to this voice number. This setup isn’t a single, unified phone number, but it’s straightforward and sidesteps the restriction where each bot (voice or text) requires its own unique number. Ideally, if we could change the caller ID on the Assistable voice number to match the LC texting number, it would make the whole experience feel seamless—one number for both calling and texting. Does this logic make sense, or am I missing anything?

I'm getting super organized with a new hire - we are systemizing information (vids, docs, demos) and also overhauling ticketing and user help. Where do you need help so we can create informational vids, docs and click through demos to help?