👀 What's New?

• Google Lead Form submissions now record the correct Session Source as Paid Search (previously stored as "Paid Social").
• Session Source includes the full Campaign, Ad Group, and Ad details.
• A new contact activity — "Google Lead Form Submission" — has been introduced for this submission type.
• The activity snippet captures Campaign, Ad Group, Ad, and Form name so you can see exactly which ad and form drove the lead.

👷 How It Works:

1. Run a Google Ads campaign that uses Lead Forms and connect it to HighLevel as you do today.
2. When a prospect submits the Google Lead Form, the contact is created or updated inside HighLevel automatically.
3. Open the contact and check the Activity panel: Session Source should be "Paid Search". Campaign / Ad Group / Ad should have been populated from the originating Google Ads entity.
4. In the contact's Activity timeline, you'll see the new "Google Lead Form Submission" entry containing Campaign, Ad Group, Ad, and Form name.

🌟 Why It Matters:

1. Accurate paid-channel reporting — Google Lead Form leads are no longer miscategorised as Paid Social, so dashboards, and source breakdowns finally reflect reality.
2. Full campaign visibility — Marketers can see the exact campaign, ad group, ad, and form behind every lead.
3. Cleaner activity timelines — A dedicated activity type makes it easy to filter, segment, and automate workflows for Google Lead Form leads.
4. Better automation triggers — Workflows can branch on the new activity type to deliver a tailored follow-up.

📝 Notes:

1. The fix applies to new submissions going forward. Historical contacts retain their original attribution.
2. No setup changes required — the corrected attribution and new activity apply automatically.
3. Available wherever Google Ads' Lead Form integrations are supported.

👀 What’s New?

• New Widget Placement control introduced at the top of the Style tab:

1. Sticky – floating widget on page corner (default)
2. Embedded/Inline – renders Voice AI widget inside website content

• Added Display Mode selection for embedded widgets:

1. Avatar – static visual representation
2. Visualiser – dynamic voice-based visual cues

• Introduced Interface Size customization (Small, Medium, Large) for Visualiser mode.
• Real-time preview updates based on placement and display selection.
• Inline widget now shows CTA below avatar/visualiser (e.g., “Call us here”).

👷 How It Works:

1. Navigate to Sites > Chat Widget > Style tab.
2. Select Widget Placement: Sticky or Embedded/Inline.
3. For Embedded:

• Choose Display Mode (Avatar or Visualiser)
• If Visualiser is selected > user can choose to configure the Interface Size.

4. Customize remaining available styling options.
5. Copy code via Get Code:

• Sticky > floating script
• Embedded > inline embed snippet (div/iframe)

6. Paste code into your website where you want the widget to appear.

🌟 Why It Matters:

1. Enables non-intrusive Voice AI experiences embedded directly into website layouts.
2. Unlocks design flexibility for landing pages, funnels, and content-driven sites.
3. Introduces visual interaction patterns (visualiser) for more engaging voice experiences.
4. Lays the groundwork for highly customisable Voice AI widgets across different use cases.
5. Supports better conversion-focused placements vs generic floating widgets.

⏭️ What’s Next?

• Enhanced customisation and personalisation with new visualiser options.

📝 Notes:

1. Some customisation options (like widget position & contact form toggle) are disabled in Embedded mode of voice AI widgets.
2. Display Mode variations are currently optimised for Voice AI experiences.
3. Multiple embedded widgets can be used across the same site.

What's New

Call Transcript Tool (Built-in)

The AI Agent action now includes a built-in Call Transcript tool that gives the agent access to a contact's call history. The tool works internally with no configuration required, simply reference call transcripts in your agent prompt (e.g., "Use this contact's call transcripts to summarize their concerns") and the agent retrieves and uses them automatically.

This builds on the previously released conversation history tool The agent now has access to both past chat conversations and call transcripts, providing a more complete view of every contact interaction.

Feedback Flow in Execution Logs

You can now submit structured feedback on every AI Agent run directly from the execution logs. Flag what went wrong, note what worked well, and share specifics for each run. All feedback is used to improve the AI Agent's accuracy, evaluation quality, and goal alignment over time.

Bug Fixes and Stability Improvements

Resolved few bugs across the AI Agent action to improve reliability and overall experience.

Why This Matters

The Call Transcript tool makes the AI Agent significantly more context-aware. Instead of operating only on chat history or static contact fields, it can now factor in voice interactions, making its decisions, responses, and actions more grounded in real customer context. The feedback flow closes the gap between what the agent does and what you expect, enabling faster iteration and fewer deviations.

What's New

Call Transcript Tool (Built-in)

The AI Agent action now includes a built-in Call Transcript tool that gives the agent access to a contact's call history. The tool works internally with no configuration required, simply reference call transcripts in your agent prompt (e.g., "Use this contact's call transcripts to summarize their concerns") and the agent retrieves and uses them automatically.

This builds on the previously released conversation history tool The agent now has access to both past chat conversations and call transcripts, providing a more complete view of every contact interaction.

Feedback Flow in Execution Logs

You can now submit structured feedback on every AI Agent run directly from the execution logs. Flag what went wrong, note what worked well, and share specifics for each run. All feedback is used to improve the AI Agent's accuracy, evaluation quality, and goal alignment over time.

Bug Fixes and Stability Improvements

Resolved few bugs across the AI Agent action to improve reliability and overall experience.

Why This Matters

The Call Transcript tool makes the AI Agent significantly more context-aware. Instead of operating only on chat history or static contact fields, it can now factor in voice interactions, making its decisions, responses, and actions more grounded in real customer context. The feedback flow closes the gap between what the agent does and what you expect, enabling faster iteration and fewer deviations.

What's New

Call Transcript Tool (Built-in)

The AI Agent action now includes a built-in Call Transcript tool that gives the agent access to a contact's call history. The tool works internally with no configuration required, simply reference call transcripts in your agent prompt (e.g., "Use this contact's call transcripts to summarize their concerns") and the agent retrieves and uses them automatically.

This builds on the previously released conversation history tool The agent now has access to both past chat conversations and call transcripts, providing a more complete view of every contact interaction.

Feedback Flow in Execution Logs

You can now submit structured feedback on every AI Agent run directly from the execution logs. Flag what went wrong, note what worked well, and share specifics for each run. All feedback is used to improve the AI Agent's accuracy, evaluation quality, and goal alignment over time.

Bug Fixes and Stability Improvements

Resolved few bugs across the AI Agent action to improve reliability and overall experience.

Why This Matters

The Call Transcript tool makes the AI Agent significantly more context-aware. Instead of operating only on chat history or static contact fields, it can now factor in voice interactions, making its decisions, responses, and actions more grounded in real customer context. The feedback flow closes the gap between what the agent does and what you expect, enabling faster iteration and fewer deviations.