@Frankie B No, you don't have to wait it out. The limit is a number you set, not a lockout, so raising it turns AI Studio back on immediately. Agency view, open that sub-account, billing, edit the monthly spending limit to something above where you already are and it clears on the next request. No support ticket needed. Only reason you would be stuck until the 1st is if the wallet itself is empty and auto recharge is off, which is a different message. Worth raising the limit and switching auto recharge on at the same time, otherwise this hits again mid month and usually on a day a client is actually using the thing.

@Frankie B Yeah, that would do it. Sep 30 has already come and gone, so if AI Studio is still blocked today the limit reset isn't the issue anymore, the empty wallet is. AI Studio draws from that wallet, so with zero balance and auto recharge off it just stops. Add funds to the sub-account wallet (or ask whoever runs the agency account if they pay for it), then turn on auto recharge with a low trigger, something like 10 dollars, so it doesn't die mid month again. Should work again within a few minutes of the top up.

Inbound webhook trigger in workflows. Once I realized I could fire a GHL workflow straight from n8n or a random form tool and map the payload onto contact fields, I stopped duct taping Zapier in the middle just to get data into the CRM. Way fewer moving parts to debug when something breaks.

The forwarding number thing you read is half right and the half that is wrong is the part worrying you. You do not swap your main number out everywhere. What you do is get a tracking number per source, point each one at the real line, and the customer never notices because the call still rings where it always rang. Different number on Google, different one on the website, different one on the flyers, and now the dashboard tells you which one is actually producing instead of you guessing. On Google specifically, do not just replace the number and hope. Google's own guidance is to put the tracking number in as the primary and keep the real one listed as an additional number. That way your listing still matches the number that is on your website and everywhere else, so you keep the consistency Google cares about and you still get the tracking. For the website, dynamic number insertion is the clean version, where the displayed number changes based on how the visitor arrived, one line of script and you do not have to maintain separate pages. On texts, if you provision the number inside your sub account it is a real number, not a call only forward. Texts land in Conversations and the client replies from there like normal, so nothing is one way. That is the main reason to do it in the platform rather than through a standalone call tracking service, where you genuinely do end up with a calls only number and a client who cannot answer anybody. Just make sure A2P is registered for that sub account first or the texts will look like they sent and quietly go nowhere. One thing worth doing on day one: leave the main line untracked as your control. Makes it obvious when a tracking number breaks, because the volume moves somewhere it should not.

On the phone numbers specifically, stop asking AI tools for them. They are trained mostly on US data and Denmark is not in there in any useful way. The thing you actually want is CVR, the central business register. It is public, it is free, and it is structured. Every registered Danish company sits in there with its branchekode, employee count, address, often a phone number and email, and importantly the ledelse records, which give you the actual names of directors and owners. There is a proper API you can register for through Erhvervsstyrelsen, and cvrapi.dk is the easier wrapper if you just want to get moving this week. That gives you something no scraped list will: you can filter by industry code and employee band before you ever pick up the phone, so you are calling 60 companies that genuinely match instead of 600 that might. Proff.dk is decent for filling gaps, and allabolag.se is the Swedish equivalent if you do end up working Malmo. On the legal side I would not take my word or anyone else's here. My understanding is Denmark is stricter than most of the EU because it applies the unsolicited email rule to companies and not just consumers, which is exactly why your read felt different from the usual advice. Worth twenty minutes with a Danish lawyer before you build a whole market move around it. Registering a Swedish entity to email into Sweden is fine, but the rules follow the recipient, not where you incorporated. It does not unlock Denmark.

Waqas is asking the sharper version of this one. The mess for me was never tasks living outside the CRM. It was that somewhere around 40 workflows nobody could say what would break if one got deleted. GHL gives you no dependency view, so a workflow that only ever gets fired by another workflow's webhook looks exactly like a dead one in the list. What fixed it was boring. Every workflow name now starts with a prefix for what actually triggers it. TRG for anything a form or inbound message starts, SUB for anything only ever called by another workflow, ADM for internal cleanup stuff nobody outside the team touches. Renaming took one afternoon and after that the list is the documentation. Before deleting anything I open it and look at the enrollment history tab. Nobody in for 90 days, it goes. The genuinely useful case is the opposite one, where people are still entering a workflow you were sure was dead. That is almost always an old form still live on a page everyone forgot about. Rebuilding a snapshot into a clean sub-account once a year is the other thing worth doing, mostly because you are forced to look at every piece as it imports.