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.