Add a lightweight floating "Text Us" bubble for the sub-account's public site — similar placement/style to the existing Web Chat widget, but instead of opening an in-page chat conversation, it shows a short form (name, mobile phone, message). Submitting it creates a Contact and kicks off a outbound SMS via the sub-account's Twilio number, so the visitor and business are now texting directly rather than chatting inside the widget. Source tagged (e.g. source: "sms-widget") separate from Web Chat and form submissions in reporting. The bubble should support a subtle idle animation, a configurable accent color (matching the color picker already used for Web Chat), and an optional hover tooltip. Submission optionally triggers a workflow, reusing the same capture/trigger pipeline Web Chat and forms already use. Unified conversation inbox. Example ringbot.io

I would like the ability to create and sell individual courses without requiring the course to be attached to a community. Currently, courses appear to be available only as part of a community. However, many businesses sell self-paced courses as standalone digital products. I would like to be able to: Create a standalone course with modules and lessons Set an individual price for the course Give customers access automatically after purchase Sell multiple courses separately Offer free or paid courses Create a basic sales page for each course The sales page would not need to be overly complicated, but it would be helpful to include a course title, description, image, video, pricing information, curriculum overview, and purchase button. This would make it possible to use LeadStack for traditional digital course sales in addition to memberships and communities, similar to the course functionality available in platforms such as GoHighLevel.

Feature request — mobile comms parity (email logging + human calling) Loving the CRM. Two gaps are blocking us from fully running our agency on it, plus one bigger-picture ask. 1. Email logging / two-way email (highest priority) Right now email is send-only — inbound replies and anything we send from our personal Gmail never reach the CRM, so "last contacted" goes stale and time-based automations misfire. Requesting a BCC-to-CRM dropbox address (BCC a unique address from any email client → it matches the contact and logs to their thread). Bonus: full inbound so replies thread like SMS. 2. Human calling from the Twilio number We can text from our Twilio number via the Inbox, but there's no way to place or receive a live human call on it — voice is only AI (Vapi) or forward-to-cell. Requesting either an in-app softphone (Twilio Voice SDK) or a click-to-call bridge (rings our cell, connects to the client, shows the Twilio number as caller ID, and logs the call). 3. Native / app-store mobile app The PWA is solid on Android but limited on iOS. Do you have (or plan) an official store-listed mobile app we could rebrand, before we consider wrapping it ourselves? Happy to share more detail on any of these.

Stripe isnt an option for me, ive been. looking into Whop.

Hi, Today all user-facing strings are hardcoded in English iirc. Two levels would unlock non-English markets, by priority: 1. OUTBOUND MESSAGES & SEEDED DEFAULTS (critical, small scope): the ~25-30 hardcoded outbound messages (missed-call SMS, welcome email/SMS presets, WhatsApp starter templates, booking/quote emails, review request, AI receptionist greetings) plus seeded defaults (contact form labels, "30-minute consultation", deal currency USD, default timezone). These are sent to our clients' own customers — an English SMS from a French tradesman's business breaks the product promise. A per-sub-account or per-agency locale setting for these templates/seeds would be enough. 2. APP UI (larger, second step): extracting UI strings into locale files (next-intl or similar) so agencies can ship the dashboard in their market's language. Also worth noting: "Reply STOP to opt out" is US CTIA wording — For example, France requires "STOP au 36180", other markets differ. A localizable compliance string would cover this. Best,

DocuSign, PandaDoc, and the rest charge per envelope and per seat. Those fees scale with every client you add. GoHighLevel bundles documents, but you are still renting the whole platform.

Creating a review funnel where 5 star reviews get sent to sub account's GMB page and 4 stars and below are sent to subaccount for internal feedback and/or Automated responses to google reviews when a sub account receives a new review on GMB page.

I havent got this far yet but i would assume the AI bot should be able to book into the calender or have access to this and offer optons. If so then being be able to pull from a calender giving true time slots and availbility.

Easiest i can think of would be plan level limits and logging of AI usage and phone minutes. More important for usage that. is charged to the saas owner (VAPI, AI assitant, AI bots). Twilio can and should be billed to client via their subaccount id guess for A2P reasons etc..

Not seeing any spam protection within the forms - honeypot field is easy and free. Maybe even google capctha keys to be added to a subaccount or for specific forms.

forms for gathering estimate / quotes normally are multistep to break up the info needed to collect. I do like the forms where they have tiles to select optosn rather than. dropdown and radio buttons. Thsi multistep form woudl also tackle the perosn. asking for a review gating form.