Conversations are logged into HighLevel's Conversations tab as a custom "Website Chat" channel β no real texts sent.
Checking Live Chat SSOβ¦
The Live Chat panel signs staff in via HighLevel's Custom Page SSO (not the shared portal login) so it can't inherit another staffer's session when someone switches users inside HighLevel. Requires SSO enabled on this app's Custom Page in HighLevel's developer portal β paste the Shared Secret it generates below.
Bots
Loadingβ¦
New bot
Conversational: free-text chat, powered by Gemini. Guided: a Drift-style button flow you build below β no AI, no free text.
π€ Conversation setup
Same four-path shape as the Prime49 announcement: Path A β an existing partner checks Prime49 eligibility. Path B β a prospect applies to become a partner. Path C β a merchant sees a static message. Path D β everything else, answered from the Knowledge section below. Click a path to expand it.
GENERAL β HIGHLEVEL
Shared across all paths β used whenever the bot creates/updates a contact. Each path below has its own calendar/form β no shared default anymore.
Instead of showing your stored wording exactly as typed, Gemini rewrites it warmer/more conversational for each visitor before it's shown (lightly personalized with their name once known). Adds a real Gemini call β and a small delay β to EVERY message in this bot's flow, not just Path D. Off by default; your stored wording is always the fallback if a rewrite ever fails.
Save this bot once first, then build its flow steps inside Path A / Path B below.
Path A β I am a PPT Partner
Path A enabled
Off = this menu option is hidden from chat visitors. Its setup below stays saved β flip it back on anytime.
Visitor gives a Partner ID β bot checks Prime49 eligibility β eligible books using this path's own calendar/form below; not eligible gets the option below that.
Only offered if they agree β never enrolled silently.
Booking (Path A's own calendar/form)
"Book the appointment itself" only works with Calendar (not Form) selected above, and calls HighLevel's real Calendars API β verify a test booking lands correctly before relying on it.
π§ Guided flow steps for Path A
Path B β I am interested in becoming a partner
Path B enabled
Off = this menu option is hidden from chat visitors. Its setup below stays saved β flip it back on anytime.
Leave blank to skip qualifying and just collect contact info when they're ready.
Guided bots decide qualification via "Mark qualified"/"Mark not qualified" steps in the flow builder below, not free-text criteria.
Fallback calendar (Path B's own β separate from Path A's)
Used to auto-book when someone qualifies but no rep ends up assigned (no reps configured, or every ranked rep is fully booked).
Follow-up
If a visitor gave contact info but stops replying, sends one SMS nudge (via their HighLevel contact) after the quiet period below. Checked hourly.
π§ Guided flow steps for Path B
Your series of qualifying questions. Each button's "Then" decides if it qualifies/disqualifies (point it at the next question to continue, or straight at a Mark qualified/Mark not qualified step to end it there); "Assign rep" optionally pins a specific rep from the list above the moment that button is picked.
Path C β I am a merchant
Path C enabled
Off = this menu option is hidden from chat visitors. Its message below stays saved β flip it back on anytime.
Purely informational β no lookup, no survey. The bot just replies with this message.
Path D β General questions (Knowledge Base)
Path D enabled
Off = the "I have a question" menu option is hidden from chat visitors. The Knowledge base below stays saved β flip it back on anytime.
Everything that isn't Path A/B/C β answered from the Persona above plus whatever's in the Knowledge section below (once this bot is saved), which you can add to manually or by crawling a website. The bot still steers the conversation back toward becoming a partner or upgrading to Prime49 rather than just answering trivia forever.
Shipment lookup β verification code settings
Used by "Look up shipment/deployment/return" flow steps (or the conversational bot's shipment tools). Email is always tried first automatically when one is on file β this SMS fallback only fires when there's no email but there IS a phone + HighLevel contact. This app has no direct SMS-send integration, so SMS works by setting a custom field on the contact with the code, then firing this workflow β build a HighLevel workflow whose only job is to text {{contact.<field name>}} to the contact.
Other steps (rarely needed β a step shared by more than one path, or one that doesn't belong to either)
Embed snippet
Paste this on any page (Webflow, GoHighLevel, your own site) β a chat bubble appears in the bottom-right corner.
Auto-embed on Webflow
Pushes the snippet above directly into a connected Webflow site's footer code and publishes β no manual pasting. Uses the same Webflow connection already set up for announcements.
Knowledge (what it can answer from)
Crawl a website
Follows links on the same domain and pulls out useful facts automatically β no manual pasting. Capped for reliability (max 15 pages per run).
Test it
π Stats β
"Booked" only counts the bot's own auto-book flow (it books directly via the Calendars API and we know for certain it succeeded). Widget/link bookings aren't tracked here β there's no confirmation webhook wired up for those yet.
Loadingβ¦
Chat history
Loadingβ¦
Add step
Pushed to the contact once one exists for this visitor. Needs a HighLevel sub-account selected above.
Route by outcome (leave a route blank to just end the flow there):