@Nick Schmidt 2-5% is actual published reviews man... not just opens or clicks. btw saw ur post in the other group about texting them anyway... terrible idea. twilio a2p 10dlc compliance bots will instantly flag the account and nuke the clients main business number. client loses their number = u lose the client. stick to the email micro commit flow i mentioned earlier. if the n8n backend routing gets too heavy to build just shoot me a dm... ill show u how we set it up :)

@Nick Schmidt because those guys run churn and burn agencies... they dont care if the clients brand gets nuked... att and verizon algorithms will catch those outbound link spikes almost instantly... twilio will flag u for opt-in proof and permanently blacklist the clients actual business number... real architects dont play russian roulette with client assets just for quick reviews... let them risk it... stick to the safe email drip :)

@Suyog S ghl backend runs on stripe. stripe automatically rejects virtual or prepaid cards for recurring saas. it has to be a physical bank card. if u are using a real one then ur bank is blocking the international 3d secure ping... just call ur bank to whitelist it or ask ghl support chat for a manual invoice link. they do it all the time :)

@Dallin Klain ghl is an absolute beast for medspa lead capture. but for the reactivation part, skip the standard sms templates. use ghl webhooks to trigger an ai voice agent instead. let the bot call those dead leads and book them straight into your ghl calendar 24/7. integrating advanced backend logic early on makes hitting that 100k goal a breeze. solid goals man. keep building :)

@Austin Planchard @Javier Rodriguez late to the thread but seeing the replies u never got the actual backend fix. just adding the scope in the dev portal doesnt automatically push to ur active token. u have to completely re-run the oauth authorization flow for that specific sub-account so the new scope gets encoded into the new access token. also native knowledge base endpoints are crazy strict on v2 location-level oauth. if ur mixing v1 agency keys anywhere it instantly throws that 401. prob already figured it out by now but dropping the logic here in case anyone else gets stuck debugging this exact webhook loop.