Website

SMS Campaign Limit Warning
No client knows what their SMS daily limits - or if hitting SEND one more time will RESTRICT their account. This is especially painful if the location is sending a campaign. RECOMMENDATION 1: Warn the user that the action is above their current tier. Recommend they reach out to the agency or schedule over longer period of time. 2: Quietly notify the Agency so they can PROACTIVELY help the user. Check out this scenario. *Keep in mind, this follows all best practices GHL provides in SMS v2 ramp up model for every. single. level. WHO 2 year client w/ 200 contacts Sms usage 10-60% daily limit WHAT Big yearly event coming up, so they create a campaign NO WARNING that hitting send will send them to temporary jail 24hr RESTRICTION & WARNING EMAIL FROM GHL GHL DND'd 100 accounts Agency needs to quickly react to client Agency needs to upgrade SMS Tier Agency needs un-DND the contacts that were blocked from this specific campaign (good luck) Agency needs to coordinate with Client to identify contacts and resend the failed 100 sms texts WHY No really... why?! The current ramp up model LITERALLY makes you hit a 24hr ban before you can use the next tier, potentially requires a ton of hand-holding from the agency, and has clients loose faith in this platform. This idea ALSO rocks. I'd hope for both, but prefer Kalel V's suggestion. https://ideas.gohighlevel.com/crm/p/lc-ramp-up-model-v2 Honorable mention: https://ideas.gohighlevel.com/lcphonesystem/p/sms-monthly-limits
1
Duplicate SEO Tags — Remove Legacy + Modern Meta Sets
Quick description (copy-paste): HighLevel’s page builder outputs each SEO field twice: an older meta-tag format and the newer “Element Settings” format. Search engines ignore the duplicate, but tools like Screaming Frog, Ahrefs, and Sitebulb flag every page with “Duplicate meta description / title” warnings. This clutters audits and confuses users. Why it matters Cleaner HTML → smaller payload, faster parse. Accurate third-party audits & no false warnings. Less manual cleanup for agencies migrating to HighLevel. Requested fix Detect when both formats exist and render only one authoritative set (ideally the new format). Provide a toggle in Site Settings for backward compatibility. One change = cleaner codebase, happier SEO teams, and fewer support tickets.Quick description (copy-paste): HighLevel’s page builder outputs each SEO field twice: an older meta-tag format and the newer “Element Settings” format. Search engines ignore the duplicate, but tools like Screaming Frog, Ahrefs, and Sitebulb flag every page with “Duplicate meta description / title” warnings. This clutters audits and confuses users. Why it matters Cleaner HTML → smaller payload, faster parse. Accurate third-party audits & no false warnings. Less manual cleanup for agencies migrating to HighLevel. Requested fix Detect when both formats exist and render only one authoritative set (ideally the new format). Provide a toggle in Site Settings for backward compatibility. One change = cleaner codebase, happier SEO teams, and fewer support tickets.
0
Load More