See exactly how your WhatsApp messages perform without leaving your automation. WhatsApp statistics is now built into Workflows, so you can track the full delivery lifecycle of every message a workflow sends and drill into individual message details, all in one place.

👀 What's new

📊 Detailed message status tracking

• Full message lifecycle: Monitor total sent, pending, delivered, read, and failed messages for a workflow's WhatsApp action, the same statuses Meta reports back for every message.

🗓️ Custom date range analysis

• Pick your window: View statistics for a specific time period to evaluate performance for a given campaign or send window.

🔍 Individual message details

• Message-level breakdown: Open any message to see recipient information and precise timestamps.

📤 Export functionality

• Take the data with you: Export statistics for further analysis or reporting.

🔄 Real-time updates

• Refresh in place: Pull the latest status with a refresh button, no full reload needed.

👷 How it works

1. Go to Automation and select the workflow with a WhatsApp action.
2. Click the WhatsApp action and select Statistics.
3. View the statistics and individual message details.
4. Use the date range selector to customize your view.
5. Open all statistics and click Export to download.

Why this matters

WhatsApp message delivery is not guaranteed: messages can sit pending, fail, or go undelivered, and until now that outcome lived outside your automation. Surfacing delivered, read, and failed counts against the workflow that sent them means you can spot a drop in delivery or a spike in failures at the source, and export the detail when you need to dig in or report it.

Resources

• WhatsApp workflow statistics support article

AI template generator for WhatsApp

Create WhatsApp message templates from a plain description, right inside AXCRM. Describe your use case, like a payment reminder or a delivery update, and AI drafts a template aligned with Meta's rules, complete with GHL variables you can personalize before you submit.

> Describe what you want to say and get a drafted, pre-categorized template you can review and submit, instead of building it field by field.

What's new

AI drafting from a plain description

• New entry point: Under Create Template, choose AI Template.

• Describe, don't build: Give your scenario and audience, and AI drafts the template for you, complete with GHL variables ready to personalize.

Built-in categorization and checks

• Auto categorization: AI classifies the draft as Utility, Marketing, or Authentication, the same categories Meta uses to apply its messaging rules.

• Inline validation: As you draft, you get recommendations on length, formatting, and policy fit before you submit to Meta.

Fully editable before submit

• You stay in control: Edit the copy, variables, and CTAs, then submit to Meta for approval when it looks right.

How to use

1. Go to CRM → WhatsApp → Templates → Create Template → AI Template.

2. Describe your use case and audience.

3. Review the AI-drafted template, its category, and the validation hints.

4. (Optional) Edit copy, variables, and CTAs.

5. Submit for Meta approval.

Why this matters

Meta applies different messaging rules by template category, and Utility templates are not subject to the same per-user marketing frequency limits that Marketing templates are. Getting the category and formatting right before you submit means fewer surprises at approval and send time. The AI template generator drafts with that categorization built in and flags formatting or policy issues while you write, so review happens up front instead of after a rejection.

Open CRM → WhatsApp → Templates, choose AI Template, and draft your next template from a description.

We've rebuilt the WhatsApp Templates and Template Folders experience on our latest design system, giving you a cleaner, faster, and more intuitive way to manage templates at scale. Find, organize, and restructure your template library with far less friction.

What's New

🔄 One-Click Refresh (No Full Page Reload)

• Refresh just the templates: A new refresh button updates your templates and folders in place, so you can pull the latest state (including fresh Meta approval statuses) without reloading the entire page. Faster, and you keep your spot.

🗂️ Real Folder Navigation

• Enter directories directly: Open a folder and work inside it, instead of treating folders as a flat label. Navigation now feels like a real directory structure.
• Folder-scoped views: Inside a folder, the Templates tab shows only that folder's templates and the Folders tab shows only its subfolders. Nested organization is finally practical and predictable.
• See where each template lives: The templates list now shows whether a template sits inside a directory, so you always know how things are organized.

🔍 Filters and Sorting

• Filter templates: Narrow the list by Status, Language, Last edited, and Category. Previously there was no filter support, which made finding the right template slow on large accounts.
• Sort templates: Order by Template name, Language, Category, Last edited, or Status. You now control how you explore and review your library.

↔️ Flexible Reorganization

• Move folders and templates across levels: Nest a folder inside another, pull a folder back out to a parent level, or move templates between folders. Restructure your library however your operation grows.

🎨 Modern, Polished Interface

• Rebuilt on our latest design system: Both the templates screen and the folders screen have a cleaner, more structured, and more satisfying look aligned with current product standards.

Why This Matters

Template libraries get messy fast as WhatsApp usage scales. Without filters, sorting, scoped navigation, and clear folder visibility, even locating or reorganizing a template becomes frustrating. This revamp turns one of your most-used WhatsApp surfaces into a fast, organized workspace.

• Faster discovery of the right template
• Clearer organizational context at a glance
• Intuitive navigation across nested folders
• Better control over large template libraries
• Refresh in place without losing your view
• A more modern, polished experience

Open your WhatsApp Templates and try filtering, sorting, or moving a folder, the new structure shows up immediately.

We've shipped a set of WhatsApp improvements that make template selection more reliable, let you author right-to-left languages directly in the CRM, and show you exactly when Meta compliance affects a template, before a send fails.

What's New

✅ Cleaner, Faster Template Selection

• Approved-only dropdowns: Everywhere you pick a WhatsApp template, in Conversations, Bulk Actions, and Workflow WhatsApp actions, you now see only approved templates. No more selecting a template that would later fail during sending.
• Faster loading: These dropdowns now fetch only the lightweight data they need instead of full template documents, so template pickers load quicker and feel lighter, even in heavy, memory-intensive screens.

⌨️ RTL Authoring, Right in the CRM

• Type Arabic, Urdu, and Hebrew natively: Create and edit right-to-left templates directly in the template forms. No more drafting in an external editor and pasting in. This pairs with the WhatsApp AI template generator for faster RTL creation.

📱 Better Phone Numbers Tab

• Fixed scrolling and pagination: The WhatsApp Phone Numbers tab no longer overflows the page. Content now scrolls cleanly and is paginated, which is especially helpful on smaller screens with long lists.

Why This Matters

WhatsApp template management gets more reliable and transparent. You spend less time troubleshooting failed sends and more time messaging customers.

• Fewer avoidable send failures from selecting non-approved templates
• Faster, lighter template pickers across every send surface
• Native RTL authoring for Arabic, Urdu, and Hebrew, no external editors

Head to your WhatsApp templates and try authoring or selecting one, the difference shows up right where you send.

We've updated our email delivery logic so that three critical email types are no longer skipped when a contact is marked as Do Not Disturb (DND):

1. Payments (Invoices)
2. Calendar notifications
3. System Notifications

Why this change?

Previously, marking a contact as DND would also block these transactional and time-sensitive emails meaning important information like invoices, calendar updates, and system alerts could go undelivered. Since these emails are essential for account and operational continuity (not marketing or promotional in nature), we've exempted them from DND rules to ensure contacts never miss critical communications.

Note:

This change only applies to the three email types listed above. All marketing and promotional emails continue to fully respect DND settings as before — this is not a blanket bypass of the DND preference.

We didn't just add AI to Ad Manager, we made campaign management conversational.

With the new Ad Manager × Ask AI integration, you can create, manage, and analyze Meta and Google Ads simply by describing what you want to achieve. From campaign creation to performance insights, Ask AI helps you get more done without navigating multiple screens.

What’s New

1. Create campaigns conversationally - AskAI can collect campaign requirements, configure the supported settings, and create campaigns for review. Supported campaign types include:

• Meta: Lead Generation, Website Traffic, Engagement, and Sales

• Google: Search and Demand Gen

Campaigns are created as drafts and are published only after explicit user approval.

1. Manage existing campaigns - Users can ask AskAI to:

• List and filter campaigns across supported platforms

• Review campaign details and performance

• Edit supported campaign settings

• Clone, pause, resume, or delete campaigns

• Republish campaigns after making changes

• Confirmation is required before publishing or performing destructive actions.

1. Create and manage audiences - AskAI supports key audience workflows, including:

• Meta: Custom, lookalike, website, Page engagement, lead-form, and Smart List-based audiences

• Google: Customer Match, website visitor, lookalike, interest, custom, and Demand Gen audience segments

AskAI can also retrieve the available audience sources and help users select the right option without manually locating IDs.

1. Access campaign resources - AskAI can retrieve supporting resources required during campaign setup, including:

• Meta Pages and Instagram accounts

• Meta datasets, pixels, lead forms, and conversation forms

• Google conversion actions, conversion goals, and campaign assets

• Keywords, interests, locations, languages, and demographic targeting options

1. Understand campaign performance - Users can request performance data for campaigns, ad groups or ad sets, ads, and keywords over a selected date range. AskAI can present the results as:

• Performance summaries

• Metric breakdowns

• Trend graphs

• Campaign improvement suggestions

1. Connect advertising accounts - AskAI can guide users through the Ad Manager account-connection and authorisation flow for supported advertising platforms. Existing Ad Manager permissions, subscription rules, account access, and platform compliance requirements continue to apply.

User Control and Safeguards

AskAI is designed to assist users without making critical advertising decisions independently.

• Campaigns are saved as drafts by default.

• Publishing always requires explicit approval.

• Deleting campaigns, removing Pages, and disconnecting accounts require confirmation.

• Meta Special Ad Category requirements are enforced.

• Existing role and permission checks continue to apply.

• Unsupported actions redirect users to the relevant Ad Manager interface.

How to use this feature

• Open Ask AI in AXCRM

• Describe the advertising task you'd like to complete

• Provide any additional details requested

• Review the generated campaign or proposed action

• Approve the action to complete it

Example prompts:

"Create a Meta lead generation campaign."

"Build a Google Search campaign for my website."

"Show my active campaigns."

"How can I improve this campaign?"

Why it matters

• Launch campaigns faster with AI-guided setup

• Manage campaigns, audiences, and reporting from one conversation

• Reduce manual navigation across Ad Manager

• Stay in control with draft-first creation and approval-based publishing

• Simplify advertising workflows for agencies and businesses

Notes

• Supports Meta Ads and Google Ads

• Campaigns are created as drafts and require approval before publishing

• Destructive actions (delete, disconnect, publish) always require confirmation

• Existing Ad Manager permissions and platform compliance rules continue to apply

• LinkedIn Ads, Workflows, Templates, and Snapshots are not included in this release

What’s New?

Abandoned Checkouts page has been redesigned with the High-Rise UI and new tools to help store owners find, manage, and export abandoned checkout data more efficiently.

• Export CSV: Select individual, multiple, or all records on the current page and export customer, cart, product, activity, and recovery details.
• Search & Filters: Search by customer name or email, and use Add filter to filter by Email Status, Recovery Status, or Date Range.
• Configure Notifications: Quickly access Abandoned Cart Notification Settings from the new CTA.
• Improved Experience: Updated empty states, loading states, pagination, and responsive design.
• Shareable Recovery Link: Open an abandoned checkout to copy and share its checkout URL directly with the customer, helping them quickly return and complete their purchase.

How to Use It?

1. Go to Payments > Orders > Abandoned Checkouts.
2. Search or filter the required records.
3. Select the checkouts and click Export CSV.
4. Use Configure Notifications to manage abandoned cart notifications.

Key Points to Note:

• Export is enabled only after selecting at least one record.
• Select All applies to the current page.
• Exports with more than 5,000 records will be delivered by email.

Images:

Documents and Contracts templates can now carry multiple signer roles — buyer, seller, witness, or any custom role you define. When a document goes out through a Workflow, every role is automatically populated and routed for signature, no manual re-entry required.

The Challenge

You send agreements that need more than one signature — a buyer and a seller, a client and a co-signer, a tenant and a guarantor. Until now, templates only supported a single signer, so you were stuck manually adding each person’s details every time you sent a document, or working around it with clunky duplicate templates.

Our Solution

Define signer roles directly on your template — up to 6 per template — and assign fields (like signature or date) to each one. When you send that template through a Workflow, AXCRM automatically pulls in the roles you’ve set up. Missing a detail? You can fill it in — or override any role’s name, email, or phone number — right at the workflow level, without touching the template.

How This Supercharges Your Business

• Save Time: No more manually re-adding signer details for every multi-party agreement you send.

• Reduce Errors: Role values set on the template auto-populate, cutting down on missed or mistyped signer info.

• Stay Flexible: Override any role’s details per-workflow, so one template can serve many different deals.

• Scale Complex Deals: Real estate, contracting, and services businesses can now route agreements needing multiple signatures (e.g., buyer + seller + witness) in a single send.

How to Get Started

1. Build your template: Open your Proposal/Estimate template and define signer roles (name, email, phone) and assign at least one fillable element to each role. Roles can have static or custom values which get resolved when the document is sent — choose based on your use case.

2. Assign a Contact field: Make sure at least one fillable element is assigned to “Contact” — this is required for the Workflow send action to work.

3. Select your template in a Workflow: Add the “Send Document” action and choose your multi-role template — roles will auto-populate.

4. Override if needed: Adjust any role’s name, email, or phone at the workflow level — these values take precedence over the template defaults.

5. Send: Launch the workflow — each signer receives their document in the order and role you’ve defined.

What’s Next?

We’re continuing to build out signing order controls and expanding role-based automation across more document types — so stay tuned for even more control over how multi-party agreements move through your pipeline.

Good to Know

• Up to 6 roles can be added per template; roles are local to that specific template.

• Roles only populate automatically when the document is sent via a Workflow (not from manual send).

• At least one fillable element must be assigned to “Contact” for the Workflow send action to function.Role details set at the workflow level override the template’s default values.

• If a required role email is missing, you’ll be prompted to complete it before sending. Duplicate emails across roles will trigger an alert.

• Currently available on Web.

Overview

The Workflow AI Builder now tracks every iteration it creates. Each AI build or edit produces an artifact card in the chat, and any of them can be restored in a single click.

What's New

• Artifact card for every AI iteration: Every build or edit from the AI Assistant produces a card inline in the chat, at the point where the change was made.
• Current version indicator: The card matching the canvas carries a purple border, so the active iteration is always identifiable.
• One-click restore: Open the three-dot menu on any older card and select "Restore this version." The canvas reverts instantly.
• Bidirectional and non-destructive: Restoring an older iteration keeps newer ones restorable. Iterations can be moved between freely, and none are destroyed.
• Unsaved indicator: When auto-save is off for the location, cards display an "Unsaved" pill until the workflow is saved manually. The pill does not appear when auto-save is on.
• Synced with Version History: "Show in version history" opens the Version History tab, where AI and manual versions appear in one unified timeline. Version History remains the single source of truth for version numbering.

How to Use

1. Prompt the AI Assistant to build or edit your workflow.
2. An artifact card appears in chat with a purple border marking it as the current version.
3. Prompt another change. The new card takes the border, and the previous card gains "Restore this version" in its three-dot menu.
4. Use the three-dot menu on any card to restore that iteration or open it in Version History.

Why This Matters

AI edits previously had no recovery path - a removed trigger or an overwritten action config meant rebuilding by hand. Tying every AI iteration to a restorable artifact makes the assistant safe to experiment with: bold edits can be attempted, compared, and rolled back without leaving the conversation or losing work. Routing those iterations into the same timeline as manual versions keeps Version History authoritative rather than splitting AI and human changes into parallel histories.

Overview

Workflows imported through a snapshot now display an "Explain This Workflow" pill at the top of the builder. One click opens the AI Assistant with a full breakdown of what that workflow does.

What's New

Explain This Workflow pill — Appears at the top of every workflow brought in via snapshot.

One-click explanation — Opens the AI Assistant with a complete explanation of the workflow's triggers, actions, and branching logic.

Dismissible — The pill can be dismissed once and will not reappear on that workflow.

How to Use

1. Open any workflow imported through a snapshot.
2. Click the "Explain This Workflow" pill at the top of the builder.
3. Review the explanation in the AI Assistant panel.
4. Ask follow-up questions about specific steps, or describe the changes you want and let the AI Builder apply them.

Why This Matters

Snapshot workflows are inherited, not built — users open them with no context on what they do or why. Surfacing the explanation at the point of import closes that gap before it turns into a support request, and connects the workflow directly into the AI Assistant and AI Builder. What was previously a passive import becomes an entry point for understanding, questioning, and editing automation in place.