October 2026

Google Ads — Financial conditions for Upload Targets

Category: Enhancement

Documentation publication date: October 20 2026

Location: Integrations → Google Ads → select an integration → Configuration → Upload Targets → add or edit conditions

What’s new

Set financial conditions separately for each Upload Target using Buyer revenue, Publisher payout, or Converted status.
Compare revenue and payout amounts with equals, not equals, greater than, or less than. For Converted, use equals or not equals with yes or no.
Combine conditions with AND or OR. Financial conditions appear below, and separately from, the tag filter.

How to use it

Open Integrations → Google Ads, select the integration, and open Configuration → Upload Targets.
Add or edit a target’s conditions and find Financial conditions below the tag filter.
Turn on Only upload when financial conditions match.
Choose the source, operator, and value for each condition; combine conditions with AND or OR.
Save the target’s conditions.

Impact and limits

Control which otherwise eligible calls upload to each target based on their financial outcome. For example, require Buyer revenue greater than 0 AND Converted equals yes.
An amount of 0 is a real value; a missing amount is unknown, not zero.
Later financial or converted-status updates do not automatically re-evaluate calls, and already-uploaded conversions are not automatically adjusted.
These eligibility conditions do not change the conversion value source.

See Send call conversions to Google Ads for setup instructions.

Release Notes — October 2 2026 — Enrich incoming calls with Trestle data in Call flows

Category: Feature

Location: Integrations → Integrations → Trestle; Call flows → open a flow → Data Enrichment

Release Date: October 2 2026

What’s new

Connect your organization’s Trestle account and add a Data Enrichment node to a call flow. The node looks up the incoming caller’s phone number and writes selected results into Moja call tags.
Choose Phone Validation, Caller Identification, Reverse Phone, or Real Contact, subject to your Trestle account’s product access.
Test a phone number without placing a call, inspect the returned fields, and map selected values to new or existing custom tags. Saved nodes retain the test sample and mappings so you can resume setup.

How to use it

Open Integrations → Integrations, select Trestle, enter your Trestle API key, and click Connect and validate. Connect the account here first; the call-flow node uses that saved connection.
Open Call flows and select the flow you want to enrich. Add Data Enrichment before the downstream steps that need the returned tags, and connect it into the flow.
Open the node, select Trestle and the lookup type, enter a Test caller ID, and click Test lookup.
In Select data, choose the returned fields you need and click Map selected.
In Map tags, use Create, Auto-match, or Use existing for each field. Review the tag names and display names, then assign the mappings individually or with Assign all.
Click Save node, then save the flow. On incoming calls, available mapped values are written to the call’s tags; missing values are not populated.

Impact

Caller details can become call tags for subsequent configured steps and call-log review, without building a separate HTTP-request mapping workflow.
Enrichment failures do not automatically stop the flow; it continues to the next connected node. Plan downstream handling for missing data.
Trestle access and lookup charges depend on your Trestle account. Connection validation and test lookups may also be billable.

Originally published at https://classic-help.mojaai.com/en/articles/17311751-release-notes-october-2-2026-enrich-incoming-calls-with-trestle-data-in-call-flows

Release Notes — October 6, 2026 — Moja starts with your system’s light or dark appearance

Moja starts with your system’s light or dark appearance

Category: Enhancement

Location: Portal-wide appearance; top-right light/dark toggle

Release Date: October 6 2026

What’s new

If this browser has no saved Moja theme preference, the portal now starts with your system’s light or dark appearance rather than always starting in light mode.
Existing saved light, dark, and system preferences are preserved.
Reporting grids, their toolbars, and the Call Logs column selector use the resolved dark appearance when the system preference is dark.

How to use it

Open Moja in a browser with no saved theme preference. Its initial appearance follows the light or dark preference supplied by your system or browser.
To choose a fixed appearance instead, click the sun/moon toggle at the top right. One click switches the visible theme between light and dark and saves that choice in this browser.
If you already selected light or dark, keep using Moja as usual; this release does not reset that saved choice.

Impact

First-time use better matches your preferred appearance, with consistent dark styling across the updated reporting controls.
Your existing theme choice stays yours; this is an appearance change, not a change to call handling or billing.

Originally published at https://classic-help.mojaai.com/en/articles/17349559-release-notes-october-6-2026-moja-starts-with-your-system-s-light-or-dark-appearance

Release Notes — October 6, 2026 — New: Connect your AI assistant to Moja

New: Connect your AI assistant to Moja

Category: New Release

Release Date: October 6 2026

Location: Integrations → MCP

Understand your Moja setup through conversation

Moja’s new MCP connection lets a compatible AI assistant read supported configuration from your organization. Instead of opening several pages to inspect buyers, targets, routing plans, and number assignments, you can ask your assistant to retrieve and explain that information.

The connection is read-only. Your assistant can help you understand your setup without changing it through MCP.

What you can do

Inspect campaigns, buyers, and publishers.
Review target settings, RTB settings and groups, and routing plans.
Look up phone-number assignments.
Retrieve call-flow names and identifiers.

Examples to try

These are example prompts, not recorded test results:

Review a buyer’s setup: “List the targets associated with this buyer and summarize their configured settings.”
Inspect routing: “Show the configured destinations in this routing plan.”
Check number assignments: “Which phone numbers are assigned to this campaign?”
Prepare a configuration review: “Summarize this campaign’s configuration and identify the related routing objects I should review.”

The assistant’s answers concern configured settings—not proof of what happened on a live call.

How it works

MCP connects your AI client to Moja through an authorization flow. You register the client, initiate the connection from that client, and approve read-only access to the selected Moja organization.

Registering an app does not grant access by itself. The connection must be authorized separately, and you can revoke that authorization from Moja.

Getting started

Open Integrations → MCP → Setup. Complete authentication setup if the page prompts you.
Select your AI client. Enter an app name and the exact callback URL supplied by that client, then select Register app & get client ID.
In your AI client, enter the Moja endpoint and public client ID displayed by Setup. Select OAuth with moja:read and leave the client secret blank.
Start the connection from your AI client. On Moja’s approval screen, check the organization, app, callback, and read-only scope before approving a request you initiated.
Return to Connections to review the authorization. Ask the assistant a supported configuration question and check Activity for the corresponding tool event.

Manage access

Connections: review authorization status, expiry, and last successful tool use, or revoke a connection.
Activity: inspect retained authorization and tool events.
Setup: disable organization access when all existing authorizations must stop working. Re-enabling access does not restore those invalidated authorizations.

What’s not included

Creating, updating, or deleting Moja configuration through MCP.
Call-performance reporting or recordings.
The contents of call-flow diagrams; this release exposes their names and identifiers.

Client compatibility

Requires a compatible MCP client with OAuth support. Availability may depend on the client’s plan and workspace policy.

Originally published at https://classic-help.mojaai.com/en/articles/17349564-release-notes-october-6-2026-new-connect-your-ai-assistant-to-moja

Release Notes: 2026-10-06 — Google Ads — Upload Target tag filters

Filter eligible calls sent to each Google Ads conversion action using supported call tags.

Choose which call outcomes you send to Google Ads

Category: Enhancement

Location: Integrations → Google Ads → select the integration → Configuration → Upload Targets

Release Date: October 6 2026

Send the right calls to each conversion action

You can now add a tag filter to each Google Ads Upload Target. This lets you send different call outcomes to different conversion actions without changing how Moja determines that a call is converted.

What you can do

Filter using your organization’s custom tags and available system tags, including QAI Disposition for calls analyzed by QAI.
Combine conditions with AND/OR, using equals or not equals.
Use a tag filter alongside minimum connected call length—the call must satisfy both.
See why a target was skipped when its filter did not match.

Examples

Sales only: upload when QAI Disposition equals Sale.
Regional sales: upload when QAI Disposition equals Sale AND Caller State equals CA OR TX, with the state alternatives grouped together.
Exclude voice-agent hangups: use Hangup During Voice Agent Conversation not equals true. Note that “not equals” also passes when the tag is missing.

These are configuration examples, not results from a customer account.

How it works

Filters narrow which otherwise-eligible calls are sent to each Upload Target.
Equals requires the tag to be present; not equals also passes when it is missing. Comparisons ignore case.
Filters are evaluated when the upload runs, at least six hours after the call. Tags added after that run do not change the recorded decision.
A nonmatching filter skips that target rather than counting as an upload failure. Upload Targets without filters retain their current behavior.

Getting started

Open Integrations → Google Ads, select the integration, and open Configuration.
In Upload Targets, add a target or edit an existing one.
Under Only upload when the call’s tags match, choose tags and build your conditions. Custom tags appear first.
Save the Upload Target.
Review delivery status or a historical backfill preview for filter-related skip explanations.

To remove filtering, clear the filter and save the target.

Important limits

Only calls analyzed by QAI receive the QAI Disposition tag; this release does not populate that tag on older calls.
A deleted or renamed custom tag makes its saved filter invalid, so that Upload Target is skipped until you update the filter.
Custom tag names must contain only letters, digits, and underscores to appear in the picker.
This release does not add numeric comparisons, tag-presence operators, or Meta Ads filtering.

Originally published at https://classic-help.mojaai.com/en/articles/17433301-release-notes-2026-10-06-google-ads-upload-target-tag-filters

Release Notes: 2026-10-07 — Admin — Editor role for day-to-day setup

Admins can assign an Editor role for operational configuration and reporting without billing or member management.

What’s new

Admins can assign an Editor role for day-to-day operational configuration and reporting.
Editors can work with campaigns, numbers, buyers, publishers, targets, routing plans, call flows, Voice Agents, and supported integration settings.
Editors can access reporting, including QAI analysis and RTB Pulse where those are already enabled.
Billing, member invitations and role changes, Audit log, organization API keys, and other Admin-only tools remain restricted.
Editor access applies across the organization—it does not restrict the user to selected campaigns.

How to use it

Sign in as an Admin and open Admin → My account → Organization.
To invite someone, choose Invite, enter their email, select Editor, and send the invitation.
To update an existing member, open their role menu and select Editor.
The user can then sign in to configure and review operations without receiving Admin billing or membership controls.

Impact

Teams can delegate operational work without sharing full Admin access.
Existing Admin, Member, Publisher, and Buyer access is unchanged.

Originally published at https://classic-help.mojaai.com/en/articles/17453055-release-notes-2026-10-07-admin-editor-role-for-day-to-day-setup

Release Notes: 2026-10-08 — Revedup — Control publisher pricing by campaign

Optional campaign integration: enroll campaigns so Revedup can price outbound RTB publisher quotes while buyer billing stays on the original bid.

Revedup integration: control publisher pricing by campaign

Category: Feature

Location: Campaigns → Create or Edit Campaign → Revedup Integration; Integrations → Revedup

Release Date: October 8 2026

Revedup is now available as an optional campaign integration. On an enrolled campaign, Moja can send each outbound RTB bid to Revedup for a pricing decision before the network quotes the publisher. The buyer’s original bid is still what the buyer is billed. Unenrolled campaigns are unchanged.

What’s new

Revedup can price outbound RTB bids on campaigns you enroll. Existing campaigns stay off until they are enrolled.
Revedup may pass the buyer’s bid through, replace the quote with a set amount, or multiply the bid. The resulting amount is what the network uses to quote the publisher and to pick a winner in an RTB group.
If Revedup cannot return a usable decision in time, Moja uses the original buyer bid so the call can still route.
Buyer billing stays on the original bid. Publisher quotes on enrolled campaigns use the Revedup amount when a decision is applied.
Failover to another buyer is scored as a new attempt, not a reuse of the earlier decision.
Organization admins can store the Revedup API Key and Score Path under Integrations → Revedup → Configuration.
Each campaign form has a Revedup Integration panel with Enroll in Revedup. The enroll control stays off and disabled until the organization is configured.
Network users can review scored traffic on Integrations → Revedup → Reporting.

How to use it

Get the organization key and score path from Revedup. Moja stores the values you enter; it does not issue the key.
Open Integrations → Revedup. Organization admins open the Configuration tab, enter API Key and Score Path, then Save (or Update if a key is already stored).
Open Campaigns, create or edit a campaign, and find Revedup Integration (alongside the other tracking integrations on the campaign form).
When the organization is configured, turn on Enroll in Revedup and save the campaign. Enrollment is per campaign and defaults to off.
If the organization is not configured, Enroll in Revedup stays disabled. The campaign form tells you Revedup is not configured for this organization and to reach out to Moja to get started on Revedup setup and configuration.
Optional, after enrollment is on: turn on Allow negative margin if a Revedup quote that would pay the publisher more than the buyer bid should be applied. Leave it off to keep that quote from being used.
After a campaign is enrolled, place or allow live RTB traffic on that campaign as you normally would. Unenrolled campaigns continue to use buyer bids without Revedup.
Network users can open Integrations → Revedup → Reporting to review scored legs. Publisher and buyer call views do not include the Revedup-adjusted quote.

Impact

Networks can use Revedup on selected campaigns without changing buyer billing or unenrolled traffic.
Publisher payouts that are a percentage of the quote follow the Revedup amount when a decision is applied. Static publisher payouts are not repriced from the adjustment.
Campaign enrollment and organization key setup are available in the portal. Existing campaigns remain unenrolled until you turn Enroll in Revedup on and save.

Quick examples (illustrative — not live test results)

The organization key is saved under Integrations → Revedup → Configuration. A campaign is edited, Enroll in Revedup is turned on, and the campaign is saved. A buyer returns $10. Revedup returns a set quote of $12. The network quotes the publisher from $12. The buyer is still billed $10.
The same campaign is enrolled, but Revedup does not return a usable decision. The network quotes from the original $10 bid and the call can still route.
A second campaign is left with Enroll in Revedup off. Its RTB bids are never sent to Revedup.
Allow negative margin is off. Revedup returns a quote that would pay the publisher more than the $10 buyer bid. The network quotes from the original $10 bid instead.

What’s not included

Automatic enrollment of existing campaigns.
A change to how buyers are billed.
A guaranteed improvement in margin. Revedup may pass the bid through, raise the quote, lower the quote, or fail open to the original bid.
Publisher or buyer call views that show the Revedup-adjusted quote. Network Revedup reporting is on Integrations → Revedup → Reporting.

Originally published at https://classic-help.mojaai.com/en/articles/17505806-release-notes-2026-10-08-revedup-control-publisher-pricing-by-campaign

October 8 2026 — V4 Turbo joins the Voice Agent speech-model options

Category: Enhancement Location: Voice Agents → open or create an agent → Voice Release Date: October 8 2026

What’s new

V4 Turbo is available as an optional speech-model family, marked New in the picker.
Flash remains the recommended default. Existing agents are not automatically switched.
V4 Turbo supports Stability and Similarity controls, but not the Speed slider, Expressive mode, or suggested audio tags.

How to use it

Open Voice Agents and create an agent or edit an existing one.
In Voice, open the speech-model picker and select V4 Turbo.
Keep or select a voice, then save the agent.
Place a test call to assess the voice on that agent before using it more broadly.

Impact

Teams can choose V4 Turbo for individual agents without changing the models used by other agents.

Originally published at https://classic-help.mojaai.com/en/articles/17680744-v4-turbo-joins-the-voice-agent-speech-model-options

Release Notes: 2026-10-12 — Integrations MCP — Read-only call reporting

Connected MCP clients can read call logs, RTB requests, webhook history, and account configuration without edit permission.

Read-only call reporting and deeper account inspection through MCP

Category: Enhancement
Location: Integrations → MCP → Setup and Connections; reporting requests run in your connected MCP client
Release Date: October 12 2026

What’s new

Your connected MCP client can now read call logs, call summaries and individual call life logs, plus inbound and outbound RTB requests, summaries and request details.
Inspect webhook delivery history and account change history alongside the configuration behind a call. Additional reads cover Voice Agent prompts, settings, knowledge-base documents and conversations, IVRs, QAI results, call tags and profiles, and RevedUp reports.
Date-ranged reporting requests default to the last 30 days. You can request up to 366 days; longer ranges are returned in separate, non-overlapping 30-day windows, newest first.
Access remains read-only and scoped to the connected organization. Credential values are removed from returned configuration and report data.

How to use it

Open Integrations → MCP → Setup, then click Copy endpoint and add that endpoint to a compatible MCP client with OAuth support.
Sign in to Moja, check the organization shown on the consent screen, and click Approve read-only access. For an existing connection, refresh your client’s available tools if the new reads do not appear.
Ask for a specific report, such as “Summarize call revenue, payout and profit by campaign for the last 30 days,” or “Show inbound RTB requests for this campaign, then inspect one request’s life log and allocations.”
For a longer date range, ask your client to follow every next_cursor until has_more is false. Cursors expire after one hour; restart the request if a cursor expires.
Open Integrations → MCP → Connections to review connections or revoke access.

Impact

Investigate call outcomes, bidding activity and webhook deliveries from one connected client, with account configuration available for context.
Review Voice Agent setup and call analysis without giving the client permission to edit settings or pause traffic.
When combining summary windows, add counts and money totals, then recompute rates from those totals. Do not add unique-caller counts across windows: the same caller may appear in more than one window.

Originally published at https://classic-help.mojaai.com/en/articles/17572061-release-notes-2026-10-12-integrations-mcp-read-only-call-reporting

Release Notes: 2026-10-12 — Campaigns — Per-minute inbound RTB rate limits

Inbound RTB publisher Rate Limit now uses 1 to 10 requests per minute, with legacy Hour and Day settings kept visible until you correct them.

Per-minute rate limits in inbound RTB campaign settings

Location

Campaigns → Create or Edit Campaign → Inbound RTB Publishers → Rate Limit

Release Date

October 12 2026

What’s new

Each inbound RTB publisher’s Rate Limit accepts a whole number from 1 to 10 requests per minute.
New publisher rows default to 10 requests per minute. Hour and Day are no longer options for new settings.
Older settings above 10 or using Hour or Day remain visible at their stored value and unit. They must be deliberately corrected before saving; they are not silently converted.

How to use it

Open a campaign and go to Inbound RTB Publishers.
Set the publisher’s Rate Limit to a whole number from 1 to 10 requests per minute.
For a legacy Hour or Day setting, click Use requests per minute, enter a valid rate, resolve the warnings, and save.

Impact

Configure publisher request rates with one consistent unit and clear validation.
Review older settings without losing sight of their original values.
This changes the campaign form—not outbound buyer throttles or the runtime enforcement policy.

Originally published at https://classic-help.mojaai.com/en/articles/17638330-release-notes-2026-10-12-campaigns-per-minute-inbound-rtb-rate-limits

Release Notes: 2026-10-13 — Reporting — Updated Ask AI example questions

Ask AI example questions now emphasize revenue, campaign pressure, and buyers who dropped calls. Where Nell is enabled, the page title is Nell.

Updated example questions on Ask AI

Location

Reporting → Ask AI

Release Date

October 13 2026

What’s new

Example questions emphasize revenue, campaign pressure, and buyers who dropped calls.
Where Nell is enabled, the page title is now Nell rather than Nell (Pilot).
Nell examples also cover preparing a publisher-disable action and creating a campaign for confirmation.

How to use it

Open Reporting → Ask AI.
Select an example question or enter your own.
Actions prepared by Nell still require an Admin’s confirmation before they are applied.

Impact

Suggested questions better reflect common revenue and buyer investigations.
This updates examples and page wording. It does not enable Nell for additional accounts or change account permissions.

Originally published at https://classic-help.mojaai.com/en/articles/17638332-release-notes-2026-10-13-reporting-updated-ask-ai-example-questions

Release Notes: 2026-10-14 — Integration hub — Welcome page for new accounts

The integration hub now opens on a Welcome page with a first-campaign checklist and walkthrough before publisher RTB setup.

A clearer starting point for new Moja accounts

Location

Integration hub → Welcome; Publisher tab

Release Date

October 14 2026

Overview

The integration hub now opens on a Welcome page, giving new users a first-campaign checklist and walkthrough before they move into publisher RTB setup.

What you can do

Follow written first-campaign steps and watch an embedded walkthrough.
Open the existing Publisher RTB integration guide from the Publisher tab.
Switch the hub between light and dark appearance; the choice is remembered in your browser.

How it works

The hub’s main page is Welcome. The Publisher tab contains the RTB integration guide.
Older publisher links containing ?url= or #url= are forwarded to the Publisher page.
The walkthrough player loads on Welcome rather than on unrelated hub pages.

Getting started

Open the integration hub and review the Welcome checklist.
Watch the walkthrough, then select Build your first campaign to open the portal.
Use Publisher in the header when configuring or validating a publisher integration.

Examples

A new user follows the campaign walkthrough before opening the portal.
A publisher goes directly to Publisher for endpoint instructions and validation.
A returning user changes the hub’s appearance with Toggle theme.

Limitations

This is the integration hub, not a replacement for portal navigation.
It does not create campaigns, numbers, or RTB formulas automatically.
Its appearance setting applies to the hub only.

Originally published at https://classic-help.mojaai.com/en/articles/17638333-release-notes-2026-10-14-integration-hub-welcome-page-for-new-accounts

October 20 2026 — Voice Agent metadata: organize agent variants and compare their performance

Category: New Release Location: Voice Agents → Metadata tags; Reporting → Summary View, Advanced Filters and Call Logs Release Date: October 20 2026

Compare groups of Voice Agents without relying on individual agent names. Metadata categories and tags let you describe agents by experiment, offer, voice style, or another classification, then use those labels in Reporting to compare results and inspect the underlying calls.

What’s new

Organize metadata using an optional category and a tag value—for example, Experiment / A or Offer / Medicare. Existing uncategorized labels remain supported.
Group Reporting summaries by Metadata tag or Metadata category.
Narrow Call Logs and Call Summary using metadata filters, including exact-match, exclusion, contains, and does-not-contain rules.
Open a metadata summary metric to inspect its calls while retaining the selected tag or category.
Display Voice Agent Metadata Tag and Voice Agent Metadata Category in Call Logs using the Columns picker. These columns are hidden by default.

How it works

Metadata describes the agent—not information collected from a caller. Adding a label does not change the agent’s voice, prompt, routing, or qualification behavior.
Reporting uses the linked agent’s currently saved metadata. Changing an agent’s labels can therefore change how earlier linked calls appear in metadata reports.
Untagged identifies linked agents without metadata; Uncategorized identifies labels without a category.
Agents can have multiple labels. A call may appear in more than one metadata group, so adding group totals does not necessarily produce a distinct-call total.

Quick examples

Label separate agents Experiment / A and Experiment / B, then compare their available performance metrics.
Use Offer / Medicare and Offer / Auto to organize agents by offer and investigate the calls behind each group.
Use Voice style / Conversational as your own classification—not an automatic analysis of the voice.
Review Untagged and Uncategorized groups to identify labels that need organizing.

Getting started

Open an agent under Voice Agents. In Metadata tags, enter a value and optionally a category, then add the label.
On an existing agent, metadata additions and removals save separately from Update Voice Agent. Check the saved labels before using them for comparison.
Open Reporting, select a date range, and choose Metadata tag or Metadata category in Summary View.
For a narrower view, apply a Voice Agent metadata filter in Advanced Filters.
Open a summary metric to inspect its calls, or enable the metadata columns in Call Logs.

Access and limitations

Existing Voice Agent and Reporting permissions apply. No additional API key or external integration is required.
Calls need a linked Voice Agent to appear under its metadata. Saving labels does not create missing call-to-agent associations.
Labels are not immutable call-time experiment assignments and do not establish a controlled A/B test.
Exclusion filters can retain calls without a linked agent; their results are not necessarily a population of other tagged agents.
This release describes Call Summary and Call Logs—not matching metadata support in every chart, QAI view, or VA Pulse.
Metadata does not change payouts, billing rules, or cap settings.

Impact

Organize agents with a shared vocabulary instead of encoding every classification in their names.
Compare agent groups, then move from summary results to the underlying calls.
Keep descriptive agent labels separate from information collected during conversations.

Originally published at https://classic-help.mojaai.com/en/articles/17680746-voice-agent-metadata-organize-agent-variants-and-compare-their-performance

Release Notes — October 20 2026 — Voice Agent version history

Voice Agent version history: compare settings and restore an earlier version

Category: New Release

Location: Voice Agents → Open an existing agent → Version history Release Date: October 20 2026

Review how your Voice Agent’s settings changed and return to an earlier saved configuration without rebuilding it from memory.

What’s new • Browse recorded versions with version numbers, change titles, author, and time. The current version is marked Main · Live. • Compare a selected version with its previous version or the current live settings. • Use Overview for changes grouped by section, including side-by-side prompt and greeting changes. Use JSON for a settings-level comparison. • Restore an earlier supported configuration. Each restore creates a new version rather than deleting later history.

What’s included in version history Version history covers more than prompt edits. It records supported behavior settings across: • Prompt and greeting • Voice settings • Model settings • Conversation flow • Data-collection configuration

How it works • Changes to supported behavior settings are recorded as versions. The first recorded change also retains the preceding settings as a baseline. • Restoring a version restores those supported behavior settings—not the entire agent. • Restored settings still pass current validation. If the agent changes while you are reviewing history, refresh and compare again before restoring.

Quick examples • Compare an edited prompt with its previous version. • Review changes to voice, model, conversation flow, or data collection alongside prompt changes. • Restore an earlier supported configuration after an unwanted edit while retaining a record of the restoration.

Getting started

Open an existing Voice Agent and click Version history.
Select a version and choose Previous or Live for comparison.
Review the differences in Overview or JSON.
If you have editing permission, select Restore this version, review the proposed changes, and confirm.
Reload the agent and check the restored settings before making further edits.

Access and limitations • Restore follows the same authorization checks as editing the agent. • Only recorded versions are available; this does not promise a complete history of edits made before recording began. • Not restored: agent name, description, active/inactive state, assigned phone numbers, knowledge-base documents, tools, or retrieval settings. • This does not introduce branches, draft publishing, A/B traffic splits, multi-person approval, or per-version call reporting.

Impact • Understand prompt and other behavior-setting changes without manually reconstructing earlier configurations. • Recover supported settings while preserving a traceable version history.

Originally published at https://classic-help.mojaai.com/en/articles/17681215-voice-agent-version-history-compare-settings-and-restore-an-earlier-version

Reporting date ranges are limited to 31 days per request

Category: Enhancement Location: Reporting → date picker and Call Log; QAI Analysis → Reports Release Date: October 15 2026

What’s new

Call Log requests and exports accept date ranges of up to 31 days.
The date picker explains the limit, hides longer presets, and prevents oversized selections.
Older report links with longer ranges open the final 31 days of that range, with a notice.
Direct over-limit call-log requests receive an explanatory error rather than being silently shortened.

How to use it

Select a reporting window of no more than 31 days.
For longer history, review or export consecutive windows.
Check the displayed dates when opening an older saved link.
Use the date picker under QAI Analysis → Reports for QAI reporting.

Impact

Bounds individual call-log requests and makes the supported window explicit.
The shared Reporting picker applies its selected window to the summary and charts too. This is not a blanket 31-day restriction on every summary/reporting API.
Older call history is not deleted by this change.

Classic Help article: 17678938.