Version History in AI Builder
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
- Prompt the AI Assistant to build or edit your workflow.
- An artifact card appears in chat with a purple border marking it as the current version.
- Prompt another change. The new card takes the border, and the previous card gains "Restore this version" in its three-dot menu.
- 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.
"Explain This Workflow" discovery pill in Snapshot imported workflows
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
- Open any workflow imported through a snapshot.
- Click the "Explain This Workflow" pill at the top of the builder.
- Review the explanation in the AI Assistant panel.
- 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.
🎉 Smarter Drip Campaigns with Review Date Range Targeting
✨ What's New
Instead of targeting reviews by a fixed review age, you can now define an exact Review Date Range when creating a drip campaign.
Before launching the campaign, you'll also see:
- The total number of eligible reviews.
- Whether any reviews match your selected filters.
- Validation that prevents creating empty campaigns.
Existing age-based campaigns will continue to work without any changes.
💡 Why You'll Love It
- Target specific batches of historical reviews with precision.
- Preview campaign impact before launching.
- Avoid empty campaigns and unnecessary processing.
- Clear review backlogs more efficiently using Reviews AI.
Go to Reputation -> Settings -> Reviews AI -> Drip Campaign to enable this:


Reach out to us directly at to drop your feedback.
🎉 Choose Your Sender for Review Requests
✨ What's New
You can now set a default phone number (SMS & WhatsApp) and email address for review requests at the location level. The selected sender is automatically used across:
- Manual review requests
- Campaigns
- Workflows
💡 Why You'll Love It
- Build trust by sending requests from a familiar number or email.
- Deliver a more consistent, branded customer experience.
- Eliminate confusion caused by system-selected sender identities.
- Improve the professionalism and credibility of your review requests.
Go to Reputation ->Settings -> Email (Phone/WhatsApp) Review Request to check this out:


Reach out to us directly at to drop your feedback.
Introducing separate rebilling configuration for Conversation AI and Voice AI
We have introduced product-level billing separation for Conversation AI and Voice AI.
Previously, both Conversation AIÂ and Voice AI usage was billed under the legacy Conversation AI product. Following the product split, the legacy product has been separated into two distinct products.
- Conversation_AI
- VoiceAI
What's changed?
- Conversation AI and Voice AI usage is now tracked and billed separately.
- Both products are displayed independently across billing usage and rebilling sections.
- Agencies can configure separate rebilling settings for each product.
- Rebilling settings applied to one product will not automatically apply to the other.
