September 2026

Release Notes: 2026-09-01 — Targets — Adjustable Ring Timeouts

Adjustable Target Ring Timeouts

*Category:* Enhancement

*Location:* Targets → Create or Edit Target → Routing settings

*Release Date:* September 1 2026

What’s new

Number and SIP Targets now include a *Ring timeout (seconds)* setting in Routing settings.
Set any whole-number timeout from 1 to 120 seconds; new Targets default to 30 seconds.
When the timeout expires, routing can continue to the next configured route instead of leaving the first destination ringing too long.
The saved timeout is also visible in the Target details.

How to use it

Open *Targets*, create or edit a Number or SIP Target, and go to *Routing settings*.
Set *Ring timeout (seconds)* to how long that destination should ring before Moja continues to the next route.
Save the Target. Existing Targets keep 30 seconds until you change them.

Impact

Teams can control how long a static destination gets to answer, preserving more time for later RTB or fallback routes.

Originally published at https://classic-help.mojaai.com/en/articles/16771019-release-notes-2026-09-01-targets-adjustable-ring-timeouts

Release Notes: 2026-09-01 — Voice Agents — Instant Voice Cloning

Instant Voice Cloning for Voice Agents

*Category:* Feature

*Location:* Voice Agents → Create or Edit Voice Agent → Voice

*Release Date:* September 1 2026

What’s new

Create a custom voice directly from the primary Voice picker using one to five audio samples.
Enter a voice name, optionally remove background noise, and confirm that you have the rights and consent required to clone the voice.
After creation, the new voice is added to your organization’s voice list and selected for the Voice Agent immediately when no additional verification is required.
Customer-created voices are restricted to their owning organization and are not exposed to unrelated accounts.

How to use it

Open a Voice Agent, select *Clone a voice* beside the primary Voice field, upload clear single-speaker audio, confirm consent, and create the voice.

Impact

Teams can create and use organization-private branded voices without leaving the Moja Voice Agent workflow.

Originally published at https://classic-help.mojaai.com/en/articles/16771020-release-notes-2026-09-01-voice-agents-instant-voice-cloning

Release Notes: 2026-09-01 — Voice Agents — Reasoning Effort

Model-Aware Reasoning Effort for Voice Agents

*Category:* Enhancement

*Location:* Voice Agents → Create or Edit Voice Agent → Advanced Settings → LLM Configuration

*Release Date:* September 1 2026

What’s new

Voice Agents now show a *Reasoning Effort* selector when the chosen LLM supports it.
Available options come from that specific model, so unsupported effort levels are never offered.
Switching models automatically preserves a valid saved effort or selects the lowest active supported effort when necessary.
Models without configurable reasoning hide the control.

How to use it

*Advanced Settings* must be enabled on the account. If it is not visible, Customer Support can enable it or make the change for you.
Open a Voice Agent, go to *Advanced Settings → LLM Configuration*, and choose a supported LLM.
Set *Reasoning Effort* from the options shown for that model, then save.

Impact

Teams can tune reasoning depth for supported LLMs while keeping Voice Agent configuration valid as model capabilities change.

Originally published at https://classic-help.mojaai.com/en/articles/16771022-release-notes-2026-09-01-voice-agents-reasoning-effort

Release Notes: 2026-09-01 — Voice Agents — Text Normalization

Text Normalization Controls for Voice Agents

*Category:* Enhancement

*Location:* Voice Agents → Create or Edit Voice Agent → Advanced Settings

*Release Date:* September 1 2026

What’s new

Organizations with Advanced Voice Agent Settings can choose how generated text is prepared for speech.
*System Prompt* asks the LLM to format values such as dates, currency, ZIP codes, phone numbers, and identifiers for natural speech.
*ElevenLabs* normalizes generated text after generation, which may improve pronunciation while adding slight latency.
The selected mode persists across edits and is retained when cloning a Voice Agent.

How to use it

*Advanced Settings* must be enabled on the account. If it is not visible, Customer Support can enable it or make the change for you.
Open a Voice Agent, go to *Advanced Settings*, and choose the text-normalization mode.
Save the Voice Agent. The same setting is kept when you clone the agent.

Impact

Teams can choose the pronunciation-versus-latency approach that best fits their scripts and customer data.

Originally published at https://classic-help.mojaai.com/en/articles/16771025-release-notes-2026-09-01-voice-agents-text-normalization

Release Notes: 2026-09-01 — Voice Agents — Live LLM Catalog

Live LLM Catalog for Voice Agents

*Category:* Enhancement

*Location:* Voice Agents → Create or Edit Voice Agent → LLM Model

*Release Date:* September 1 2026

What’s new

The LLM picker now uses the current catalog of models available to Voice Agents instead of a fixed list.
Newly available models can appear without waiting for a separate Moja catalog update.
Models are grouped by provider and retain readable names and model details.
A saved model that is no longer available remains visible as *Legacy / Unavailable* so unrelated edits do not silently replace it.
If the live catalog is temporarily unavailable, Moja uses its most recent safe catalog or fallback list so the form remains usable.

How to use it

Open a Voice Agent and use the *LLM Model* picker.
Select a current model, or leave a *Legacy / Unavailable* saved model in place if you are not changing it.

Impact

Teams get faster access to current Voice Agent models without losing existing configurations.

Originally published at https://classic-help.mojaai.com/en/articles/16771026-release-notes-2026-09-01-voice-agents-live-llm-catalog

Release Notes: 2026-09-01 — Voice Agents — Live TTS Model Family

Live TTS Model Family Options for Voice Agents

*Category:* Enhancement

*Location:* Voice Agents → Create or Edit Voice Agent → TTS Model Family

*Release Date:* September 1 2026

What’s new

The TTS Model Family picker now uses the live supported catalog, including availability, recommendation, and deprecation labels.
New Voice Agents default to Flash; Turbo remains available and is clearly marked Deprecated.
Voice Style controls appear from each family’s actual capabilities rather than a fixed model-name rule.
Existing legacy selections remain visible, and unrelated edits no longer silently change the saved TTS model.
Safe cached and fallback catalogs keep the form usable during temporary catalog failures.

How to use it

Open a Voice Agent and use the *TTS Model Family* picker.
Choose Flash for new agents, or keep an existing family if you are not changing speech settings.

Impact

Voice Agent speech-model choices stay current while preserving existing configurations and exposing the right controls for each family.

Originally published at https://classic-help.mojaai.com/en/articles/16771027-release-notes-2026-09-01-voice-agents-live-tts-model-family

Release Notes: 2026-09-01 — Voice Agents — Clone From Detail Page

Clone Voice Agent from the detail page

Clone Voice Agent From the Detail Page

*Category:* Enhancement

*Location:* Voice Agents → open an existing agent → top-right *Clone Voice Agent*

*Release Date:* September 1 2026

What’s new

A *Clone Voice Agent* action is now available on the Voice Agent detail page, not only from the list.
The new agent defaults to {name} - Copy; you can rename it before confirming.
The clone copies the settings currently shown on the page, including unsaved edits: prompt, voice, extra voices, personality, LLM, conversation flow, and active/inactive status.
Assigned phone number, tools, and knowledge base are not copied. AI disclosure stays off on the new agent until you enable it.

How to use it

Open *Voice Agents* and click an existing agent to open its detail page (not the create page).
In the top-right of that page, next to the Active/Inactive badge and *Delete Voice Agent*, click *Clone Voice Agent*.
Keep the default {name} - Copy or rename it, then confirm. Moja opens the cloned Voice Agent after create.

Impact

Teams can duplicate a known-working production agent into a test or variant without rebuilding it from the list.

Originally published at https://classic-help.mojaai.com/en/articles/16773149-release-notes-2026-09-01-voice-agents-clone-from-detail-page

Release Notes: 2026-09-02 — Campaigns — Publisher integration guide from Inbound RTB

Open a prefilled publisher integration guide from a saved inbound RTB row.

Publisher integration guide from Inbound RTB

Category: Enhancement
Location: Campaigns → open a campaign → Inbound RTB publishers → book icon next to the endpoint URL
Release Date: September 2, 2026

What’s new

The previous copy-plus-help-article action is now a publisher integration guide shortcut.
On a saved inbound RTB row, open the guide picker. Publisher and campaign names are already filled in.
Caller ID stays required. You can add First name, Last name, ZIP code, and/or State as extra required fields.
Open the guide in a new tab, or copy the shortcut. The guide is for setup and local validation only — it does not send a live bid request.

How to use it

Open the campaign, find a saved inbound RTB publisher, and click the book icon next to the endpoint URL (Open publisher integration guide).
Confirm publisher and campaign labels. Leave Caller ID required; select any extra fields you need.
Click Open publisher guide, or Copy shortcut to send the same link.

Impact

Each campaign can hand publishers a prefilled integration guide instead of a generic help article.

Originally published at https://classic-help.mojaai.com/en/articles/16794021-release-notes-2026-09-02-campaigns-publisher-integration-guide-from-inbound-rtb

Release Notes: 2026-09-02 — Google Ads — Explicit destination routing

Route Google Ads call conversions to explicit destinations.

Google Ads integrations now use explicit destinations instead of one implicit default conversion action.

What’s new

Each destination pairs a linked Google Ads account with a specific conversion action.
Create named routes and assign one or more destinations to each route. A converted call can be delivered independently to every destination selected by its route.
Choose one active fallback destination for calls that do not match a named route. If no active fallback is configured, uploads pause rather than being sent to an ambiguous account or action.
Routes can be selected by assigning a snippet or by using the route’s copyable moja_ga_route URL parameter. An unknown or disabled route key fails closed and does not silently fall back.
Routing is frozen when the conversion becomes eligible. Later destination or route edits apply to future conversions and do not retarget already queued deliveries.
Delivery health shows results by route and destination, including delivered, validated, failed, pending, retrying, and unroutable totals plus the latest provider error when available.

How to use it

Open Integrations → Google Ads, select an installed integration, and find Destination routing above the available conversion actions.
Add or activate a destination by selecting the linked account and conversion action. Moja validates the pairing before it can be used.
Mark one active destination as the fallback. Linking an account or discovering an action alone does not send conversions there.
Create a named route, select one or more active destinations, and optionally assign a snippet.
For URL-based routing, copy the generated moja_ga_route parameter and add it to the appropriate landing-page or ad URL. Calls without a valid explicit route use the configured fallback.
Use delivery health to review destination-level outcomes and identify paused, unroutable, or failed uploads.

Impact

Teams can intentionally send different call conversions to different Google Ads accounts and conversion actions—or fan one conversion out to several selected destinations—without relying on an ambiguous default.
Independent delivery state prevents a failed destination from causing a successful destination to be resent.
Validation and fail-closed routing reduce wrong-account uploads while making configuration and provider failures visible.

Originally published at https://classic-help.mojaai.com/en/articles/16828285-release-notes-2026-09-02-google-ads-explicit-destination-routing

Release Notes: 2026-09-03 — Account — Reveal and Copy Existing API Key

Organization admins can reveal and copy an existing Moja API key without rotating it.

Reveal and Copy an Existing Moja API Key

Category: Enhancement
Location: Admin → My Account → Profile
Release Date: September 3 2026

What’s new

Organization admins can now reveal an existing active Moja API key without generating or rotating it.
The key remains masked by default. Use the eye control to reveal or hide the full value, or copy it while it remains masked.
Newly generated keys appear in the same field and remain available to reveal and copy.
Revoked keys cannot be revealed or copied; the existing Generate New Key action remains available.

How to use it

Open Admin → My Account → Profile as an organization admin.
Use the Moja API section on that page. Select the eye icon to reveal the current key, select it again to hide the value, or use Copy to copy the full key without rotating it.

Impact

Admins can recover the organization’s active API key for an integration without disrupting existing clients by replacing the key.

Originally published at https://classic-help.mojaai.com/en/articles/16801498-release-notes-2026-09-03-account-reveal-and-copy-existing-api-key

Release Notes: 2026-09-08 — Reporting — Call Log export play or download recording links

Choose whether Call Log CSV recording links download or play in the browser.

Call Log export: play or download recording links

What’s new

Call Log CSV export now lets you choose how recording links behave.
Download file remains the default.
Open / play in browser is a new export-time option.
The CSV still has one Recording URL column. The choice is made when you export, not as two columns.
Links still expire after 7 days. Rows with no recording, or no recording access, stay blank.
In-app Call Log playback is unchanged.

How to use it

Open Reporting → Call Logs.
Set your date range and filters, then click Export.
In the export dialog, choose Download file (default) or Open / play in browser.
Export the CSV.
Open a Recording URL from the file: download saves the audio; play opens it in the browser as audio.
Excel and Sheets may ignore in-browser play; acceptance is a click in Chrome or Firefox.

Impact

You can export a sheet that downloads recordings, or one that plays them in the browser, without changing the rest of the export.
Existing download exports keep working unless you pick play.

Originally published at https://classic-help.mojaai.com/en/articles/16861280-release-notes-2026-09-08-reporting-call-log-export-play-or-download-recording-links

Release Notes: 2026-09-08 — Targets — RTB Bid TTL warning when buyer expiry isn’t mapped

Warning when Bid TTL thresholds are set without a mapped buyer expiry field.

RTB Bid TTL: warning when buyer expiry isn’t mapped

What’s new

If you set a minimum bid TTL (or min/max TTL on an RTB group) and the buyer response does not map an expiry or TTL field, Moja now shows a warning.
The warning is informational. You can still save a setup that uses default TTL only.
When expiresAt or ttlSeconds is mapped, the warning does not appear.

How to use it

Open Targets and create or edit an RTB target.
Go to Bid TTL Settings and set a minimum remaining TTL.
Check Response Mapping for a buyer expiry or TTL field.
If none is mapped, read the warning on Bid TTL Settings and on Response Mapping, then map the buyer field or keep default TTL on purpose.
On an RTB group, the same warning can appear at group level and on each target that has a TTL threshold without a mapped expiry.

Impact

You can tell whether Moja is using a buyer-provided bid expiry or falling back to default TTL, before you assume freshness is enforced from the buyer.

Originally published at https://classic-help.mojaai.com/en/articles/16861281-release-notes-2026-09-08-targets-rtb-bid-ttl-warning-when-buyer-expiry-isn-t-mapped

Release Notes: 2026-09-11 — Targets/RTBs — Repeat Caller Rules

Repeat Caller Rules are clearer on Targets and outbound RTBs. Prior-conversion lookback is a fixed 30 days.

Repeat Caller Rules Are Clearer on Targets and Outbound RTBs

Category: Enhancement
Location: Targets → Create or Edit Target → Repeat Caller Rules · Targets/RTBs → Create or Edit Outbound RTB → Repeat Caller Rules
Release Date: September 11 2026

What’s new

Duplicate-call and prior-conversion settings now sit together under Repeat Caller Rules.
Block Repeat Calls uses clearer labels: Count as a repeat after and Look back this many days, plus a live summary of the rule.
Previously Converted Callers now states the prior-conversion window is a fixed 30 days. Only Block Repeat Calls still has a configurable lookback.
The form states that Repeat Call Blocking runs first. If it blocks the caller, the Previously Converted Caller rule is not evaluated.
Routing, payout, and saved values are unchanged.

How to use it

Open a Target or an outbound RTB and go to Repeat Caller Rules.
Turn on Block Repeat Calls, choose when a call counts as a repeat, set the lookback days, and confirm the summary matches the rule you want.
Use Previously Converted Callers to choose what happens when a matching conversion is found in the last 30 days. Caller is required; Target, Publisher, Campaign, and Buyer are optional match fields.
Save the Target or RTB.

Impact

Repeat-caller setup is easier to read, and the 30-day prior-conversion window is no longer easy to confuse with the configurable Block Repeat Calls lookback.

Originally published at https://classic-help.mojaai.com/en/articles/16919897-release-notes-2026-09-11-targets-rtbs-repeat-caller-rules

Release Notes: 2026-09-15 — Targets/RTBs — Agent Availability Eligible HTTP Statuses

Choose which HTTP responses keep an Agent Availability Check eligible. Non-eligible responses fail closed.

Control Which Agent Availability Responses Keep a Route Eligible

Category: Enhancement
Location: Targets/RTBs → Create or Edit Target or RTB → Agent Availability Check
Release Date: September 15 2026

What’s new

Agent Availability Checks now let you select the HTTP response codes that are eligible for response-field evaluation.
Non-eligible responses—including 400, 404, and server errors by default—now make the route unavailable instead of allowing the call through without evaluating the response.
Timeouts, network errors, and lookup errors also fail closed.
The configuration test shows the returned HTTP status, whether that status is eligible, and whether the call would be blocked. Eligible responses are still evaluated against the configured response mapping.

How to use it

Open Targets/RTBs, then create or edit a Target or outbound RTB and enable Agent Availability Check.
Under Eligible HTTP status codes, select the responses your availability endpoint uses for a parseable result. The default eligible responses are successful HTTP statuses.
Configure the response-field mapping that determines availability for eligible responses.
Select Test Configuration to review the returned status, status eligibility, mapped result, and whether the route would be blocked before saving.

Impact

Calls no longer route by default when the availability endpoint returns an unexpected error response or cannot be reached.
Customers whose endpoints intentionally use a nonstandard response code can explicitly allow that code and continue evaluating its response body.
Call Life records the HTTP status for passed and failed availability checks, making routing decisions easier to diagnose.

Originally published at https://classic-help.mojaai.com/en/articles/16959928-release-notes-2026-09-15-targets-rtbs-agent-availability-eligible-http-statuses

Release Notes: 2026-09-15 — Admin — Multiple Organization API Keys

Organization admins can create, reveal, copy, and revoke multiple named API keys.

Create and Manage Multiple Organization API Keys

Category: Feature
Location: Admin → My Account → Profile
Release Date: September 15 2026

What’s new

Organization administrators can now create multiple named API keys instead of relying on one shared credential for every integration.
Each key has its own name, identifying prefix, creation time, and active or revoked status.
Active keys can be revealed or copied individually. Creating a new key does not replace existing keys, and revoking one key does not disable the organization’s other active keys.
Existing API keys remain available as the organization’s legacy key. All keys retain the same organization-wide API access and share the organization’s existing rate limit; this release does not add per-key permissions.

How to use it

Open Admin → My Account → Profile as an organization administrator and find the API Keys section.
Create a key, enter a descriptive name for the integration or system that will use it, then copy the credential into that integration.
For rotation without downtime, create and install the replacement key first, confirm it is working, and then revoke the old key.
Use Reveal or Copy on an active key when needed. Revoked keys remain listed for history but cannot authenticate, be revealed, or be copied.

Impact

Teams can separate credentials by integration and revoke or rotate one credential without interrupting unrelated API consumers.
Keys remain organization-owned rather than user-owned, so creating additional keys does not change endpoint access or multiply the organization’s rate-limit allowance.

Originally published at https://classic-help.mojaai.com/en/articles/16959929-release-notes-2026-09-15-admin-multiple-organization-api-keys

Release Notes: 2026-09-16 — Targets/RTBs — Zip Exists Advanced Filter

Advanced Filtering can route on whether a ZIP code is present without a ZIP list.

Route Calls Based on Whether a ZIP Code Is Present

Category: Enhancement
Location: Targets/RTBs → Create or Edit Target or RTB → Advanced Filtering
Release Date: September 16 2026

What’s new

Advanced Filtering now includes a Zip Exists condition for routing based on whether a call has a ZIP code, without maintaining a ZIP list.
The Exists option keeps a route eligible only when a ZIP is present. Does Not Exist keeps it eligible only when the ZIP is absent.
Existing ZIP Code list filters continue to support matching specific ZIP values and are unchanged.

How to use it

Open Targets/RTBs, then create or edit the Target or outbound RTB whose eligibility you want to control.
Open Advanced Filtering, add a condition, and select Zip Exists.
Select Exists to require a ZIP or Does Not Exist to accept only calls without one. No ZIP values or file upload are needed for this condition.
Save the Target or RTB. Calls that do not meet the selected ZIP-presence condition are excluded from that route.

Impact

Teams can keep calls without ZIP data away from routes that require it while leaving those calls eligible for destinations that accept them.
ZIP eligibility is evaluated before the route is selected, avoiding unnecessary attempts to destinations whose ZIP requirements are not met.

Originally published at https://classic-help.mojaai.com/en/articles/16973105-release-notes-2026-09-16-targets-rtbs-zip-exists-advanced-filter

Release Notes: 2026-09-17 — SIP Headers for Call Tags and ZIP Routing

Inbound X- SIP headers can become call tags and source ZIP/state for routing.

Use Inbound SIP Headers for Call Tags and ZIP-Based Routing

Category: Enhancement
Location: Custom Tags; Targets/RTBs → Create or Edit Target or RTB → Advanced Filtering
Release Date: September 17 2026

What’s new

Inbound calls can now turn supported X- SIP headers into call tags automatically, making source-provided data available for routing and reporting without adding the same SIP mapping to individual Targets.
Header names are normalized by removing the X- prefix and replacing hyphens with underscores. For example, X-Custom-Route-Tag maps to Custom_Route_Tag.
Source-provided ZIP and state values now remain authoritative through caller-location enrichment and can be used by ZIP/state filters and configured outbound RTB fields. A later explicit tag update still takes precedence.
Custom header names are accepted only when the corresponding Custom Tag already exists for the organization. Writable ZIP/state system tags are supported; unknown custom tags and protected system tags are ignored.

How to use it

For a custom value, open Custom Tags and create the tag name that the inbound header will produce. For example, configure Custom_Route_Tag for an incoming X-Custom-Route-Tag header.
Configure the inbound SIP source to send string-valued X- headers. Use a supported ZIP header such as X-ZIP or X-CALLER-ZIP, and a supported state header such as X-STATE or X-CALLER-STATE, when routing should use source-provided location.
Open Targets/RTBs, then create or edit the destination whose eligibility should use the value. In Advanced Filtering, add the applicable ZIP, state, or tag condition and save.
If an outbound RTB request needs the value, use the existing ZIP, state, or matching tag field in that RTB configuration. Moja applies the normalized inbound value during call routing.

Impact

Publishers using an external voice or SIP workflow can pass ZIP, state, vertical, and other approved call context into Moja once at call entry instead of maintaining duplicate mappings across Targets.
ZIP-sensitive routing can follow the caller location supplied by the source rather than falling back to the phone number’s NPA-NXX location, reducing out-of-area routing when the caller’s number and actual location differ.
Organization-level allowlisting and protected system tags prevent arbitrary inbound headers from changing unsupported or read-only call data.

Originally published at https://classic-help.mojaai.com/en/articles/16985749-release-notes-2026-09-17-sip-headers-for-call-tags-and-zip-routing

Release Notes — September 17, 2026 — Safer Google Ads routing and historical recovery

Safer Google Ads setup, routing, and historical recovery.

Safer Google Ads setup, routing, and historical recovery

Google Ads integrations now separate Upload Targets, Traffic Rules, and the routing policy for unmatched calls, helping multi-account setups direct eligible calls to the intended account and conversion action.

What’s new

Choose strict routing with no default destination, or select a Default Destination for unmatched calls. Multi-account defaults require an ownership confirmation and are not used as failover after a rejected upload.
New and migrated integrations remain Paused until routing has been reviewed. The Overview shows readiness, Enhanced Conversions for Leads status, and recovery guidance.
Historical Call Recovery provides a frozen preview of eligible calls, routing results, and destination counts before you queue a scope.
Delivery reporting includes routing source and Traffic Rule context for each Upload Target.

How to use it

Open Integrations → Google Ads, choose an integration, and open Configuration.
Create or review Upload Targets and Traffic Rules.
Set the routing policy: No Default Destination, or Send Unmatched Calls to a Default Destination.
For earlier eligible calls, open Configuration → Historical Call Recovery, create a preview, review the frozen scope, then queue it.

Impact

Multi-account routing fails closed rather than silently sending unmatched or invalidly routed calls to another account.
Older calls require an explicit historical-recovery preview and confirmation.

Originally published at https://classic-help.mojaai.com/en/articles/17068671-release-notes-september-17-2026-safer-google-ads-routing-and-historical-recovery

Release Notes — September 29, 2026 — Voice Agent metadata tags

Tag Voice Agents with metadata and filter the list.

Tag Voice Agents with metadata and filter the list

Each Voice Agent can store metadata tags on the agent configuration, separate from tags collected during a call. The Voice Agents list can show those tags and filter or search by them. Cloning a Voice Agent copies its metadata tags.

What’s new

Metadata tags live on the Voice Agent configuration.
The Voice Agents list can display, filter, and search those tags.
Cloning copies metadata tags to the new agent.

How to use it

Open Voice Agents and select an agent.
Add or edit metadata tags, then save.
Return to the Voice Agents list and filter or search by those tags.

Impact

Teams running many Voice Agent variants can classify and find agents by test group or characteristic without relying only on agent names.

Originally published at https://classic-help.mojaai.com/en/articles/17229496-release-notes-september-29-2026-voice-agent-metadata-tags

Release Notes: 2026-09-29 — Google Ads — Connected call length conditions

Set a minimum connected call length for each Google Ads Upload Target.

Google Ads Upload Targets can require a minimum connected call length

Category: Enhancement

Location: Integrations → Google Ads → Upload Targets; Integrations → Google Ads → Traffic Rules

Release Date: September 29 2026

What’s new

Each Google Ads Upload Target can require a minimum connected call length before that conversion is uploaded.

Connected call length is the time after the buyer answers — the same Call Length value on the call log, and the same length used for conversion and payout.

Only the targets a completed call meets are uploaded. Targets below the minimum are skipped with a reason, not treated as Google upload failures.

Traffic Rules show each target’s condition and preview which targets an example call length would meet.

Delivery stats and historical-recovery preview list skipped targets separately from Google upload failures.

Targets with no minimum (0:00) keep the previous behavior.

How to use it

Open Integrations → Google Ads and select an integration.

Select the Configuration tab.

Open Upload Targets. When adding a target, or when editing an existing target’s condition, set Connected call length using minutes and seconds.

0:00 means no minimum. Use the up/down controls or type the length; 0:59 rolls to 1:00.

Open Traffic Rules on that integration to see each target’s condition. Enter an example call length to preview which targets would be eligible or below the minimum.

Save the target or rule. The condition applies to completed calls that have not been processed yet, including recent calls still waiting. Calls already processed keep their existing upload decisions.

Use historical recovery as usual; preview and execution apply the same connected-call-length check.

Impact

A short connected call no longer uploads to every selected conversion action. Each action only receives calls that meet its own minimum.

Changing a minimum does not retract conversions Google already accepted.

Call-minute billing and other usage meters are unchanged.

Originally published at https://classic-help.mojaai.com/en/articles/17250465-release-notes-2026-09-29-google-ads-connected-call-length-conditions

Release Notes: 2026-09-29 — Reporting — Voice Agent billable minutes

Review rounded Voice Agent minutes in Call Summary.

Call Summary now shows billable Voice Agent minutes

Category: Enhancement

Location: Reporting → Call Summary → VA TBM

Release Date: September 29 2026

What’s new

Call Summary includes a VA TBM column showing total billable Voice Agent minutes.

Each call’s Agent Connected Length is rounded up to the next whole minute before the minutes are added together.

The totals row includes those minutes. Agent Connected Length remains available separately in Call Logs.

How to use it

Open Reporting → Call Summary.

View the VA TBM column. If it is hidden, enable it from the Columns menu.

Use the column and totals row to review Voice Agent minutes for your selected reporting period and grouping.

Impact

Teams can review rounded Voice Agent minutes without manually converting and rounding each call’s connected seconds.

This is a reporting update only. It does not change billing rates, payment collection, or the existing TBM calculation.

Originally published at https://classic-help.mojaai.com/en/articles/17252552-release-notes-2026-09-29-reporting-voice-agent-billable-minutes