There is a new section added which is called the footer text

this allows you to add a footer just above the UChat branding which enables you to link to any webpage you'd like. use case could be: 

• let users opt in for free lead magnets
• let users book appointments

• 📩 Utility Message Templates — a new template type available under Chatbot → Contents → Utility Message Templates
• 🔁 Send messages outside the 24-hour window — reach users for transactional/utility purposes (order updates, appointment reminders, support follow-ups) after the standard window expires
• 🔗 Flow integration — use Utility Templates directly inside flows: Start Node → Send Message → Utility Template
• 🛠 Template configuration — predefine variables (e.g., first name), button actions (up to 3 buttons), and flow mapping
• ✅ Replaces deprecated Messenger Tags for post-24-hour messaging scenarios

1. Go to Chatbot → Channels → Facebook integration
2. Connect or reconnect your Facebook page
3. Enable the permission: ✅ Manage and Access Page Utility Messaging

⚠️ If this permission is not granted, Utility Messages will not work.

1. Go to Chatbot → Contents → Utility Message Templates
2. Create a template with your message body, variables, and optional buttons (max 3)
3. Submit for approval — template approval is mandatory before use

• Add a Send Message step in a flow and select your approved Utility Template

⚠️ Important: Utility Messages must NOT be used for marketing purposes. Misuse risks permanent ban from Meta.

• Order confirmations and shipping updates
• Appointment reminders and rescheduling
• Support ticket follow-ups
• Account notifications and alerts

👉 Located at: Chatbot → Contents → Utility Message Templates Documentation: Utility Messaging Templates (Facebook) Video: youtu.be/_Zko5v-wPK4 Published: April 14, 2026 at 6:10 am

{
  "credit": "string",
  "status": "ok"
}

• Automated low-credit alerts — poll the endpoint periodically and send a notification when credit drops below a threshold
• Partner billing dashboards — display live credit balance in a custom partner portal or internal tool
• n8n / Zapier automations — trigger a top-up workflow or Slack alert when credit is running low
• Pairs with the existing POST /partner/workspace/{workspaceId}/topup-points endpoint for a full credit management automation loop (check balance → top up if needed)

• Partners managing multiple workspaces need visibility into their credit balance to avoid service interruptions
• Enables proactive credit management without requiring manual login to the Partner dashboard
• Simple, no-parameter endpoint makes it easy to integrate into any monitoring or automation system

👉 Located at: Partner API Docs → Partner Management → GET /partner/credit-balance Full docs: uchat.com.au/partner-api#/Partner Management Published: March 24, 2026

• 📋 List all agent groups — retrieve all configured groups with a single GET call
• 🔍 View a specific group — fetch full details of one group by its ID
• ➕ Create agent groups — programmatically provision new groups for new workspaces or departments
• ✏️ Update agent groups — rename or reconfigure groups without touching the UI
• 🗑️ Delete agent groups — remove groups via API for cleanup or workspace teardown
• 👥 Update group members — add or remove agents from a group programmatically

• Partner workspace provisioning — automatically create standard agent groups (e.g., Sales, Support, Billing) when setting up new client workspaces via API
• CRM/HR integrations — sync team structure changes from external systems into UChat agent groups automatically
• Automation workflows — dynamically reassign agent groups based on business rules using n8n, Zapier, or custom integrations
• Pairs with the existing POST /subscriber/assign-agent-group endpoint to create a group and immediately assign users to it in a single workflow

• Completes the agent management API surface alongside existing agent assignment, listing, and conversation endpoints
• Enables fully automated workspace setup and team management without manual UI intervention
• Particularly valuable for partners managing multiple client workspaces at scale

👉 Located at: API Docs → Agent Group Full docs: uchat.com.au/api#/Agent Group Published: March 24, 2026 at 6:29 am

• broadcast-whatsapp-template-by-user-id
• broadcast-whatsapp-template-by-tag

{
  "user_id_list": "61412345678,61387625429,61245638917",
  "wa_template": {
    "namespace": "string",
    "name": "string",
    "lang": "string",
    "use_default_values": "yes",
    "params": {
      "HEADER_IMAGE": "https://example.com/image.png",
      "BODY_{{1}}": "text",
      "BODY_{{2}}": "text",
      "QUICK_REPLY_1": "sub flow ns",
      "URL_1": "https://example.com/url"
    }
  },
  "scheduled_time": 1786123679,
  "max_per_minute": 60
}

{
  "tags": ["f123t456"],
  "exclude_tags": ["f123t568"],
  "wa_template": {
    "namespace": "string",
    "name": "string",
    "lang": "string",
    "use_default_values": "yes",
    "params": {
      "HEADER_IMAGE": "https://example.com/image.png",
      "BODY_{{1}}": "text",
      "QUICK_REPLY_1": "sub flow ns",
      "URL_1": "https://example.com/url"
    }
  },
  "scheduled_time": 1786123679,
  "max_per_minute": 60
}

• Enables fully programmatic WhatsApp template campaigns from external systems (CRMs, e-commerce platforms, n8n automations)
• Tag-based targeting allows dynamic audience selection without hardcoding user IDs
• exclude_tags support prevents duplicate sends to users who should be excluded
• Scheduled delivery and rate limiting make it safe for large-scale broadcast operations

👉 Located at: API Docs → Sending → broadcast-whatsapp-template-by-user-id / broadcast-whatsapp-template-by-tag Published: March 24, 2026 at 6:28 am

• 🗂 New field type: Long JSON — stores large JSON objects as a custom user field value, beyond the size limits of the standard JSON field type
• 🔢 Up to 10 Long JSON fields per workspace — a dedicated allocation separate from other field type limits
• 🤖 AI Agent Messages migrated to Long JSON — the system field used to store AI Agent conversation history has been automatically migrated from the standard JSON type to Long JSON, enabling longer conversation histories to be stored reliably
• 📄 Accessible and editable via the standard User Fields interface alongside all other custom field types

1. Go to Settings → User Fields (or any interface where custom fields are managed)
2. Click + Add Field
3. Select Long JSON as the field type
4. Name the field and save
5. You can create up to 10 Long JSON fields per workspace

• AI Agent Messages can now store much longer conversation histories per user without hitting JSON field size limits
• Partners and power users who store complex nested data (product configurations, form responses, CRM sync payloads) have a dedicated, larger field type to use
• The automatic migration of AI Agent Messages means no action is required — existing conversation histories are preserved and now more scalable

👉 Located at: Settings → User Fields → + Add Field → Long JSON Documentation: User Fields — Long JSON Published: March 24, 2026 at 6:24 am

• 🌐 New trigger: User Ended Web Chat — fires when a visitor ends a web chat session via the webchat widget
• 🔄 Replaces the now-deprecated Guest Chat Ended trigger (still available but marked as deprecated)
• ⚡ Available in Automation → Triggers → + Trigger → select "User Ended Web Chat"
• 🔗 Works with all webchat widget types (Chat Button, Embedded Chat, etc.)

1. Go to Automation → Triggers
2. Click + Trigger (top-right)
3. Scroll to the web chat section and select User Ended Web Chat
4. Connect it to a flow — this flow will run automatically when a user ends a web chat session

• Send a follow-up message or survey after a web chat session ends
• Update a custom user field (e.g., last_chat_ended_at) when the session closes
• Trigger a re-engagement flow if the user didn't complete a key action during the chat
• Notify an agent or CRM when a visitor exits without converting

• Enables post-chat automation — a common requirement for lead capture, CSAT surveys, and re-engagement sequences
• Supersedes the deprecated Guest Chat Ended trigger with a more accurate, user-scoped event
• Closes the web chat automation loop: trigger on open → interact → trigger on close

👉 Located at: Automation → Triggers → + Trigger → User Ended Web Chat Note: Guest Chat Ended is now deprecated — migrate existing triggers to User Ended Web Chat Published: March 13, 2026

• 🤖 New setting: Default AI Provider — found at AI Hub → Settings (gear icon in the AI Hub submenu)
• 🔌 Select from any supported AI provider: OpenAI, Anthropic (Claude), xAI (Grok), Groq, and more
• 🧩 Set a specific Model within the chosen provider (e.g., gpt-4.1 for OpenAI)
• 📋 A Default model hint is shown below the model field (e.g., "Default model: gpt-4o-mini") to indicate the fallback when no model is specified
• 💾 Click Save to apply — takes effect immediately across all AI features that use the default provider

1. Go to AI Hub in the left sidebar
2. Click Settings (gear icon, bottom of the AI Hub submenu)
3. Under Default AI Provider, select your preferred provider from the dropdown (e.g., OpenAI)
4. Enter a specific Model name if desired (e.g., gpt-4.1) — leave blank to use the provider default
5. Click Save

• AI Intent Recognition — uses the default provider when no override is set on the intent node
• AI Tasks — uses the default provider when no specific provider is set on the AI Task
• Additional AI features may inherit this default in future updates

• Centralises AI provider configuration — set it once in AI Hub Settings and all AI features use it consistently
• Eliminates the need to configure a provider on every individual AI Intent node or AI Task
• Makes it easy to switch all AI features to a new provider or model in a single change
• Pairs with the Partner AI Key settings (OpenAI, xAI, Groq) for a fully managed AI stack across partner workspaces

• 🔑 New Partner Setting: Groq — found under Whitelabel Settings below the OpenAI and xAI partner key sections
• 🔄 Toggle Enabled/Disabled to activate the partner Groq key as the default for all client workspaces
• 🛠 Manage API Key button — add, update, or rotate the Partner Groq API key at any time
• 🤖 When enabled, all client workspaces use the partner's Groq key by default — no per-client Groq key setup required
• ⚡ Powers Groq-based features across client workspaces including AI Agents, AI Tasks, and the new Groq whisper-large-v3-turbo audio transcription

1. Go to Whitelabel Settings in the left sidebar
2. Scroll to the Groq section (below OpenAI and xAI)
3. Toggle the switch to Enabled
4. Click Manage API Key to enter your Groq API key
5. All client workspaces will now use your partner Groq key as their default — no per-client configuration required