GPTalk Pro Assistant

gptalk pro is the latest and optimized version of gptalk that enables intelligent conversations, automated appointment booking, lead tagging, crm field updates, and persistent conversational memory directly inside gohighlevel , without relying on deprecated openai assistant ids what’s included in the new premium action 🔧 core features 7 automated tags intelligent classification of leads and conversations tags are applied automatically based on user intent (interest, confusion, human request, etc ) 5 auto filled custom fields gptalk can automatically populate up to 5 custom crm fields examples name, phone number, interest type, lead source native gohighlevel calendar integration gptalk can book appointments directly into your ghl calendar fully automated scheduling flow without manual intervention important platform change no more assistant id openai has removed persistent assistant ids in its newer versions gptalk pro now uses a uuid based memory system , which provides greater flexibility and scalability how the new memory system works uses a unique identifier (uuid) per conversation or workflow can be any alphanumeric value (hyphens allowed) represents the long term memory of the conversation can be reused across multiple workflows allows gptalk to remember context without relying on deprecated assistant ids important behavior note if you change the uuid, gptalk will treat it as a new conversation and previous memory will not be recalled initial setup flow (required order) step 1 – connect openai apikey to wazzap go to wazzap subaccount panel→ settings general insert your openai api key (or lisa when available) no assistant id is required step 2 – workflow configuration in gohighlevel trigger create a workflow with the trigger customer replied action add gptalk – premium action configure uuid (conversation memory identifier) prompt tags custom fields calendar settings (optional) response delivery add a send sms (or whatsapp) action insert the gptalk response variable generated by the premium action gptalk generates the ai response internally the send sms action is required to send that response back to the contact 🧠 model, temperature & token optimization default model gpt 5 1 adjustable temperature to control creativity vs accuracy conversations are stored internally token usage is approximately 50% lower than previous versions prompts are no longer tied to assistants they are configured directly inside gptalk ✍️ prompt & instructions main prompt (pr) defines the ai behavior and personality additional instructions optional, isolated rules that do not interfere with the main prompt best practice keep additional instructions minimal avoid conflicts between prompt logic and calendar logic 🗓️ calendar integration calendar id required to enable scheduling if empty → scheduling is disabled uses gohighlevel calendars time zone can be set per user or per account supported actions create appointment list appointments reschedule cancel calendar queries work across uuids even if memory id changes, gptalk can still retrieve calendar events 🏷️ tags (tabs / t actions) gptalk uses t values for automated tagging and escalation two mandatory t values “i don’t understand” “human request” behavior after 3 misunderstandings → “i don’t understand” tag applied after 3–5 escalations → human handoff triggered current setup 7 configurable tabs (expandable upon request) tags and actions are now unified (previously separated) 🧩 custom fields (crm mapping) up to 5 custom fields supported field name must match the crm field name exactly (no brackets) each field includes field name description of what to store condition for when the ai should fill it example field gpt phone action save phone number when user provides mobile or home number 🔁 memory identifier behavior (edge cases) changing the uuid creates a new memory context gptalk will not recall previous conversation history calendar data remains accessible regardless of uuid demo flow example user “i’m interested in the bot” interest tag applied automatically user requests a meeting gptalk asks for date, time, and name appointment is created in the ghl calendar name field is updated in the crm user asks “when do i have appointments?” gptalk retrieves calendar events, regardless of memory id lissa model (coming soon) internal ai model designed to be cheaper than openai message based pricing instead of token based credits will be provided to users troubleshooting & deployment notes if the premium action does not appear disconnect and reconnect the crm/sub account if prompts conflict with calendar behavior report the issue to support for prompt logic adjustment token usage and conversation storage have been significantly optimized community posts https //www skool com/wazzap/la premium action de gptalk ya esta disponible v4