July 2026

Release Notes: 2026-07-02 — Tags — Tag Casing Standardization

Tag references now use a consistent lowercase display format while remaining case-insensitive.

Tag Casing Standardization

Location: Targets/RTBs, Webhooks, Call Flows, Call Logs, Custom Tags
​Release Date: July 2 2026

We standardized tag references across the platform so tag examples, picker inserts, and tag displays now follow a consistent lowercase format.

What changed

• Tag references now use a consistent lowercase format across customer-facing UI examples and picker inserts, such as [caller_id], [state], and [zip_code].

• Tag picker and preview behavior was normalized so inserted tag references match what users see in the UI.

• Call log tag displays now follow the same lowercase convention for tag keys.

• Helper text was added where casing could cause confusion, clarifying that tag matching is case-insensitive.

How to use it

• Continue using tag placeholders anywhere tags are supported.

• Lowercase examples are now the standard display format, but existing uppercase or mixed-case placeholders still resolve normally.

• For example, [state], [STATE], and [State] are treated the same.

Impact

This reduces confusion around whether tag casing matters and gives teams one consistent convention to follow across tag-related workflows.

Originally published at https://help.mojaai.com/en/articles/15852273-release-notes-2026-07-02-tags-tag-casing-standardization

---

Release Notes: 2026-07-07 — RTB — Cache Badge

See when RTB steps were served from cache instead of sending a new buyer ping.

RTB Cache Badge

Released: July 7, 2026

MojaAI now shows a sky-blue Cache badge when an RTB step is served from the per-call session cache instead of sending a new buyer HTTP request.

What changed

• Cache indicators now appear in RTB life-log events, RTB step rows, and persisted RTB step details.

• Cached RTB usage is backed by a persisted cache flag so the UI can distinguish cached responses from new RTB pings.

• Operators can more easily confirm when Moja reused a valid buyer response during rerouting.

Where to find it

• Calls → Call details → Life Log / RTB tab

• Inbound RTB → Requests → Steps

Open a call or inbound RTB request that includes RTB activity. Steps served from cache will show a Cache badge.

Why it matters

This gives operators better visibility into RTB cache behavior and helps troubleshoot routing without guessing whether a new buyer ping was sent.

Originally published at https://help.mojaai.com/en/articles/15881037-release-notes-2026-07-07-rtb-cache-badge

---

Release Notes: 2026-07-08 — Blocked Numbers — Bulk Import

Blocked numbers can now be imported in bulk by pasting a list or uploading a file.

Blocked Numbers Bulk Import

Released: July 8, 2026

Blocked numbers can now be imported in bulk instead of being added one at a time.

What changed

• Added an Import block list option for blocked numbers.

• Users can paste a list of numbers or upload a .txt or .csv file.

• The import flow supports previewing the list before import, showing valid numbers, duplicates, and invalid entries.

• Blocks can be applied network-wide or to a specific campaign, with support for permanent or temporary blocking.

How to use it

1. Go to Blocked Numbers → Block Incoming Calls.

2. Click Import block list.

3. Paste numbers or upload a .txt or .csv file.

4. Preview the import, then confirm when ready.

Note

This release supports bulk importing blocked numbers at the network and campaign level. A future linked release will add blocking by buyer, publisher, and target.

Originally published at https://help.mojaai.com/en/articles/15881074-release-notes-2026-07-08-blocked-numbers-bulk-import

---

Release Notes: 2026-07-08 — Call Routing — Pre-Bridge HTTP Checks

Run external validation after route or target selection and before a call connects.

Pre-Bridge HTTP Checks for Call Routing

Released: July 8, 2026

MojaAI now supports configurable HTTP checks that run after a route or target has been selected, but before the call is bridged. This gives teams a way to validate compliance, eligibility, or buyer-specific requirements at the exact point where the platform knows which destination would receive the call.

Why it matters

Some checks should not happen before routing because the selected buyer or target is not known yet. Other checks should not wait until after the call is complete because the result may need to decide whether the call should connect at all.

Pre-Bridge Checks add that missing middle step: MojaAI can select the route first, run the configured external check, then decide whether to connect, reject, fail over, or follow timeout/error handling.

What’s included

• Create and manage Pre-Bridge Checks from Webhooks → Pre-Bridge Checks.

• Configure HTTP request details, timeout handling, response evaluation, and multiple response-field conditions.

• Choose how the call should proceed based on pass, fail, error, or timeout outcomes.

• Assign a Pre-Bridge Check to specific routing plan routes.

• Reuse one check across multiple routes when the same endpoint and rules apply.

• Configure separate checks per route or target when each buyer requires its own endpoint or validation logic.

• Review call life-log details showing the selected route, check result, and routing decision.

Example 1: One shared compliance check

If the same validation endpoint and same pass/fail rules apply across the routing plan, a single Pre-Bridge Check can be created and reused.

Example: A customer wants to validate a TrustedForm or compliance token only after MojaAI has confirmed there is a selected route. In this case, one Pre-Bridge Check can call the customer’s validation endpoint, evaluate the response, and determine whether the call should connect, reject, or fail over.

Example 2: Buyer-specific checks

If each buyer or target requires its own endpoint, credentials, request format, or response rules, create a separate Pre-Bridge Check for each buyer-specific route.

Example routing plan:

• Route 1 → Buyer A → Buyer A validation endpoint

• Route 2 → Buyer B → Buyer B validation endpoint

• Route 3 → Buyer C → Buyer C validation endpoint

Each route can have its own Pre-Bridge Check, allowing MojaAI to send the selected call data to the correct buyer-specific endpoint only after that buyer’s route has been selected.

How to set it up

To configure a Pre-Bridge Check, you’ll need the external validation endpoint MojaAI should call, including the request method, required headers, request body or query parameters, expected response fields, and the pass/fail rules that determine whether the call should connect, reject, or fail over.

1. Go to Webhooks → Pre-Bridge Checks.

2. Create the check using the endpoint, request details, timeout behavior, and response conditions.

3. Configure the desired outcomes for pass, fail, error, and timeout.

4. Open the relevant routing plan.

5. Assign the Pre-Bridge Check to the route where it should run.

6. If multiple targets require different endpoints or rules, create separate checks and assign each one to the corresponding route.

7. Place a test call and confirm the check runs after target selection but before the call bridges.

Availability: Available now in production.

Originally published at https://help.mojaai.com/en/articles/15878871-release-notes-2026-07-08-call-routing-pre-bridge-http-checks

---

Release Notes: 2026-07-13 — Numbers — Campaign Number Traffic Controls

Enable, disable, pause, or resume traffic for individual numbers attached to campaigns without deleting the attachment.

Campaign Number Traffic Controls

Released: July 13, 2026

MojaAI now gives teams more direct control over traffic for individual numbers attached to campaigns.

What changed

• Campaign-attached numbers can now be enabled or disabled without deleting or detaching the number.

• Attached numbers can be paused or resumed from the Numbers list.

• The Numbers grid now shows whether an attached number is active, paused, or inactive.

• Calls to inactive or paused campaign-number attachments are blocked before routing and recorded with the appropriate reason.

Where to find it

• Go to Campaigns → Number Group to enable or disable a number attached to a campaign.

• Go to Numbers to view attached-number status and use Pause or Resume for eligible numbers.

How to use it

• Use Disable when a campaign-attached number should stop receiving traffic but remain configured for later use.

• Use Enable to reactivate the campaign-number attachment.

• Use Pause or Resume from the Numbers list for a temporary traffic stop on an attached number.

• If the attachment is inactive, enable it before pausing it.

Impact

Teams can quickly stop traffic for a specific campaign number while preserving the number, campaign attachment, configuration, and history for future reactivation.

Originally published at https://help.mojaai.com/en/articles/15925049-release-notes-2026-07-13-numbers-campaign-number-traffic-controls

---

Release Notes: 2026-07-13 — Reporting — Custom Tag Call Log Columns

Use custom call tags as selectable columns in Reporting → Call Log after adding them under Custom Tags.

Custom Tag Columns in Call Log Reporting

Released: July 13, 2026

Custom call tags can now be selected as columns in the Call Log once those tags have been added to the account’s Custom Tags list.

What changed

• Custom tags can be used as selectable columns in Reporting → Call Log.

• Tags that are already coming through on calls do not automatically appear in the column dropdown.

• To make a call tag available as a Call Log column, the tag must first be added under Custom Tags.

• Once added, the tag becomes available for selection in the Call Log column dropdown.

How to use it

1. Go to Reporting → Call Log.

2. Open the column dropdown for the Call Log.

3. If the tag is not listed, go to Custom Tags.

4. Click Create new and add the tag name exactly as it appears on the call.

5. Return to Reporting → Call Log and select the tag from the column dropdown.

Important setup note

If a tag is being created from a call flow, script, or other call logic, users still need to add that tag as a Custom Tag before it can be selected as a Call Log column.

For example, if calls are receiving a tag like voice_agent, the user must add voice_agent as a Custom Tag in the system before it will appear in the Call Log column dropdown.

Availability: Available now in production.

Originally published at https://help.mojaai.com/en/articles/15926889-release-notes-2026-07-13-reporting-custom-tag-call-log-columns

---

Release Notes: 2026-07-13 — Targets/RTBs — Duplicate Conversion Routing

Allow duplicate-conversion calls to route while withholding publisher payout when configured.

Duplicate Conversion Routing: Allow Calls Without Publisher Payout

Released: July 13, 2026

MojaAI now gives teams more control over how duplicate conversions are handled for targets and RTBs.

What changed

• A new duplicate conversion action lets eligible calls continue routing instead of being declined.

• When the new action is selected and a prior conversion matches, publisher payout is withheld for that duplicate conversion path.

• Existing duplicate matching dimensions remain available, including caller, target, publisher, campaign, and buyer matching.

• Target/buyer revenue and conversion tracking remain unchanged for routed calls.

Where to find it

• Go to Targets/RTBs and open a Target or RTB create/edit form.

• In Duplicate Conversion Settings, configure the matching rules.

• Choose whether matching duplicate conversions should decline the call or allow the call while withholding publisher payout.

Impact

This release helps teams continue routing calls when appropriate while protecting publisher payout when a call matches a prior conversion.

Originally published at https://help.mojaai.com/en/articles/15925067-release-notes-2026-07-13-targets-rtbs-duplicate-conversion-routing

---

Release Notes: 2026-07-14 — Platform — Dark Mode Logo Visibility Update

The platform header now uses a higher-contrast MojaAI logo in dark mode.

Dark Mode Logo Visibility Update

Released: July 14, 2026

What changed

• Added a dedicated dark-mode logo variant for the platform header.

• The full logo now switches to the dark-mode asset when the app is using a dark background.

• The existing light-mode logo remains unchanged for light mode.

• The compact mobile logo behavior remains unchanged.

Where to find it

• Open the platform in dark mode.

• The header logo now uses the higher-contrast dark-mode version automatically.

Impact

• The MojaAI logo is easier to see against dark backgrounds.

• This improves the polish and readability of the main app shell in dark mode.

Originally published at https://help.mojaai.com/en/articles/15935457-release-notes-2026-07-14-platform-dark-mode-logo-visibility-update

---

Release Notes: 2026-07-14 — RTB Pulse — Date & Time Range Controls

RTB Pulse now supports preset and custom date/time windows for live troubleshooting and historical review.

RTB Pulse Date & Time Range Controls

Released: July 14, 2026

What changed

• Added a date and time range picker to RTB Pulse so users can review recent activity or a specific historical window.

• RTB Pulse now supports preset windows including last 1 hour, last 24 hours, last 7 days, last 30 days, and all time.

• Custom date ranges are available when users need to inspect a specific period.

• Changing the date range refreshes the RTB Pulse data window and clears the current selection so the view reflects the newly selected timeframe.

Where to find it

• Go to Targets/RTBs → RTB Pulse.

• Use the Date & time control in the RTB Pulse header to choose a preset or custom range.

• In tuning views, use the Date & time control in the sidebar to adjust the analysis window.

Impact

• Users can review RTB Pulse activity for live troubleshooting or historical analysis without relying on hidden links or hardcoded default windows.

• This makes customer review and internal investigation workflows more consistent.

Originally published at https://help.mojaai.com/en/articles/15935451-release-notes-2026-07-14-rtb-pulse-date-time-range-controls

---

Release Notes: 2026-07-14 — Reports — Summary State and Date-by-Hour Grouping

Summary View now supports hourly and state-level report grouping with improved placement for grouping and layout controls.

Reporting Summary: State and Date-by-Hour Grouping

Released: July 14, 2026

What changed

• Added two new Summary View grouping options: Date by Hour and State.

• Date by Hour groups reporting results into hourly buckets, using the selected timezone when one is applied.

• State groups reporting results by state when state can be resolved from call ZIP data, with unresolved rows grouped as Unknown.

• Moved the Summary View grouping controls into the Summary section and moved the layout controls into the report toolbar for easier access.

Where to find it

• Go to Reports and open Summary View.

• Use the Summary View grouping buttons to select Date by Hour or State.

• Use Analytics First or Summary First in the toolbar to switch which report section appears first.

Impact

• Teams can review call performance by hour or by state without exporting and manually regrouping results.

• The Summary View is easier to navigate because grouping and layout controls are closer to the sections they affect.

Originally published at https://help.mojaai.com/en/articles/15944506-release-notes-2026-07-14-reports-summary-state-and-date-by-hour-grouping

---

Release Notes: 2026-07-14 — Targets/RTBs — Duplicate Conversion Revenue Withholding Options

Route duplicate-conversion calls while withholding buyer revenue, publisher payout, or both when configured.

Duplicate Conversion Routing: Revenue Withholding Options

Released: July 14, 2026

MojaAI now gives teams more granular control over how duplicate-conversion calls are routed and recorded.

What changed

• Two additional duplicate conversion actions are available: Allow call, don’t record revenue and Allow call, don’t record revenue and don’t pay publisher.

• Targets and RTBs can route a matching duplicate conversion while withholding buyer revenue, publisher payout, or both depending on the selected action.

• The platform applies the expanded duplicate conversion actions during routing when a prior conversion match is found.

• Reporting labels describe the selected duplicate conversion action so saved configurations are easier to interpret.

Where to find it

• Go to Targets/RTBs and open a Target or RTB create/edit form.

• In Duplicate Conversion Settings, configure the duplicate conversion matching rules.

• Choose the action that should apply when a prior conversion matches: decline the call, allow without publisher payout, allow without recording revenue, or allow without recording revenue and without publisher payout.

Impact

Teams can continue routing duplicate-conversion calls when appropriate while preventing buyer revenue, publisher payout, or both from being recorded for matched duplicate conversions.

Originally published at https://help.mojaai.com/en/articles/15935394-release-notes-2026-07-14-targets-rtbs-duplicate-conversion-revenue-withholding-options

---

Release Notes: 2026-07-14 — Targets/RTBs — Duplicate Settings UI Clarity

Duplicate settings now separate blocking rules from pre-conversion behavior with clearer labels and in-form guidance.

Duplicate Settings UI: Block Duplicate and Pre-Conversion Clarity

Released: July 14, 2026

What changed

• Merged the duplicate-call and duplicate-conversion controls into a clearer Duplicates flow.

• Renamed Consider Duplicate Settings to Block Duplicate Settings so the setting better describes that matching repeat callers are blocked before pre-conversion rules apply.

• Renamed Duplicate Conversion Settings to Pre-conversion settings to clarify that these options control what happens when a caller previously converted.

• Added an in-form warning when Block Duplicate Settings is enabled, explaining that repeat callers matching duplicate criteria are blocked before pre-conversion settings are evaluated.

Where to find it

• Go to Targets/RTBs and open a Target or RTB create/edit form.

• In Duplicate Settings, use Block Duplicate Settings to define when repeat callers should be treated as duplicates.

• Use Pre-conversion settings to choose what should happen when a prior conversion matches.

• If Block Duplicate Settings is enabled, review the warning before relying on pre-conversion behavior for those same repeat callers.

Impact

• The duplicate-routing setup is easier to understand because blocking rules and pre-conversion rules are separated and labeled more clearly.

• Users get clearer guidance when duplicate blocking may prevent pre-conversion settings from applying.

Originally published at https://help.mojaai.com/en/articles/15945109-release-notes-2026-07-14-targets-rtbs-duplicate-settings-ui-clarity

---

Release Notes: 2026-07-15 — Blocked Numbers — Scope Expansion

Blocked number management now supports more specific blocking scopes and bulk imports across additional platform records.

Blocked Numbers Scope Expansion

Released: July 15, 2026

What changed

• Blocked numbers and country codes can now be managed beyond network-wide and campaign-level blocking.

• Teams can add blocks for publishers, buyers, targets, RTB formulas, routing plans, RTB groups, and call flows.

• Bulk import now supports the expanded blocking scopes, so larger block lists can be applied without one-by-one entry.

• The page now includes searchable scope-specific selectors, refresh controls, and quick links to open the selected related record.

Where to find it

• Go to Blocked Numbers.

• Choose the scope tab you want to manage, such as Network Wide, Campaign, Publisher, Buyer, Target, RTB Formula, Routing Plan, RTB Group, or Call Flow.

• For non-network scopes, select the specific record before adding or importing blocked numbers.

Originally published at https://help.mojaai.com/en/articles/15951039-release-notes-2026-07-15-blocked-numbers-scope-expansion

---

Release Notes: 2026-07-15 — Publishers — Publisher Active Toggle

Publisher records now include an active toggle that can stop related number and inbound RTB traffic without deleting existing configuration.

Publisher Active Toggle

Released: July 15, 2026

Overview

• Moja now supports a publisher-level active toggle that lets operators stop traffic from a publisher with one control while preserving the publisher’s existing configuration.

• When a publisher is marked inactive, Moja blocks traffic tied to that publisher across both static/publisher numbers and inbound RTB traffic. Re-activating the publisher restores eligible traffic without deleting numbers, endpoints, or campaign setup.

What’s new

• Publishers now have an Is Active checkbox in the publisher form.

• Turning a publisher inactive stops calls tied to that publisher’s static/publisher numbers.

• Turning a publisher inactive blocks inbound RTB pings and claimed inbound RTB calls for that publisher.

• Child records now show inherited inactive messaging so operators can see when traffic is blocked because the parent publisher is inactive.

• Numbers tied to inactive publishers show a clear PUBLISHER INACTIVE status.

• Campaign number groups and inbound RTB publisher rows label inactive publishers and explain that traffic is blocked until the publisher is reactivated.

How to use it

• Go to Publishers and open the publisher record.

• In the Status section, clear Is Active to stop that publisher’s traffic.

• Save the publisher.

• Review affected records in Numbers, Campaigns → Number Group, or Inbound RTB to see inherited inactive messaging.

• Re-enable Is Active and save when the publisher should resume eligible traffic.

Impact

This gives operators a fast kill switch for publisher traffic during quality reviews, compliance holds, billing/payment issues, fraud concerns, troubleshooting, or temporary pauses — without removing publisher configuration or rebuilding setup later.

Customer teaser

Moja now includes a publisher-level active toggle, giving teams a fast way to stop all traffic from a publisher while keeping the existing setup intact. When a publisher is inactive, related number and inbound RTB traffic is blocked, and affected records clearly show that the publisher is the reason traffic is paused.

Originally published at https://help.mojaai.com/en/articles/15951268-release-notes-2026-07-15-publishers-publisher-active-toggle

---

Release Notes: 2026-07-16 — Routing Plans — Pre-bridge Payout Modifier

Pre-bridge checks can now adjust publisher payout when a check passes.

Pre-bridge Payout Modifier

Released: July 16, 2026

Pre-bridge checks can now adjust publisher payout when a check passes, giving teams more control over payout handling for validated calls.

What changed

• Routing plan routes now have an explicit Pre-bridge check enable/disable section.

• When a pre-bridge check is enabled, users can turn on Modify publisher payout on pass for that route.

• The payout modifier can replace the payout with either a percentage-based value or a static payout amount.

• The form validates that a check is selected when pre-bridge is enabled and that modifier details are provided when payout modification is enabled.

Where to find it

1. Open or create a Routing Plan.

2. In a route row, enable Pre-bridge check.

3. Select the check under Check configuration.

4. To adjust payout when the check passes, enable Modify publisher payout on pass.

5. Choose Percentage or Static amount, then enter the payout value.

Note: The payout modifier only applies when the pre-bridge check passes and the call connects.

Originally published at https://help.mojaai.com/en/articles/15972178-release-notes-2026-07-16-routing-plans-pre-bridge-payout-modifier

---

Release Notes: 2026-07-22 — Reporting — Call Life Timeline and Preconverted Check Grouping

Call Life has a clearer timeline, grouped preconverted checks, a side detail panel, and better inbound RTB support.

Call Life: Cleaner Timeline, Grouped Preconverted Checks, and Faster Detail

Released: July 22, 2026

Category: Enhancement

Location: Reporting → Call Log → Call Life

What changed

• Call Life has a clearer timeline layout with grouped repeated/preconverted check events so long life logs are easier to scan.

• A side detail panel surfaces event detail quickly without losing your place on the timeline.

• Improved support for inbound RTB activity inside Call Life.

• Show all / hide all and related timeline controls behave more reliably.

Where to find it

• Open Reporting → Call Log, open a call, then open Call Life.

• Use the timeline and detail panel to inspect routing, checks, and RTB-related events.

Impact

• Faster diagnosis of what happened on a call, especially busy preconverted-check and inbound RTB paths.

Originally published at https://help.mojaai.com/en/articles/16044970-release-notes-2026-07-22-reporting-call-life-timeline-and-preconverted-check-grouping

---

Release Notes: 2026-07-22 — Reporting — Call State Tags and Voice Agent Funnel

System call-state tags let you report Voice Agent and post-agent progress without recordings; Call Summary VA columns use the same signals.

Call State Tags: Report Voice Agent Progress Without Recordings

Released: July 22, 2026

Category: Enhancement

Location: Reporting → Call Log (tags / filters); Reporting → Call Summary → Voice Agent metrics

Why this matters

• When calls are not recorded, ops still need to know how far a Voice Agent call got—and what happened after handover—using data on the call itself.

• Call Summary Voice Agent columns are more accurate because they are driven from those same stage signals instead of thin post-call guesses.

What changed

System call-state tags on the call

• Moja now writes positive stage tags during the call for the Voice Agent path, buyer/target path, and RTB attribution where applicable.

• These are system tags on the call log—available for Call Log review, filtering, and reporting—without requiring a recording.

Tag reference

Tag	Meaning
LAST_VOICE_AGENT_ATTEMPTED	VA node entered
LAST_VOICE_AGENT_REACHED	VA actually connected
LAST_VOICE_AGENT_HANDOVER	Handover confirmed
LAST_VOICE_AGENT_FINISHED	VA finished (incl. after tool-call handover)
LAST_BUYER_ATTEMPTED / LAST_BUYER_REACHED	Buyer/target dial / answer
BUYER_FAILURE_REASON	Why buyer path failed (no bid, busy, no-answer, etc.)
LAST_RTB_GROUP / LAST_RTB_FORMULA + ping timing tags	RTB attribution

What you can answer with these tags

• Did the Voice Agent get attempted / actually connect?

• Did handover complete?

• After the agent path, was a buyer attempted or connected?

• If not, what failure class was recorded?

• Which RTB group/formula was last in play (when RTB applies)?

Call Summary Voice Agent columns (built on the same tags)

• VA Conn / VA No Conn and related % columns use the Voice Agent–eligible call set more consistently.

• Post-agent outcomes split cleanly across: VA Buyer Conn, VA Buyer No Conn, VA No Buyer, VA Dropoff Before RTB, VA Empty Handover.

• VA Buyer Conn % uses connected ÷ (connected + buyer no-connect + no buyer). Dropoff and Empty Handover stay out of that percentage.

• VA No Buyer and related totals were corrected so No Buyer does not incorrectly stay at zero.

• Column header tooltips explain each Voice Agent metric in product.

Where to find it / How to use it

• Single-call / state reporting: Reporting → Call Log → open a call → review system tags (and Call Life for the timeline).

• Use Call Log filters on call tags to build views such as “agent reached, no buyer connected.”

• Rollup metrics: Reporting → Call Summary → Voice Agent columns; hover headers for definitions.

• Calls from before these stage tags existed keep prior Call Summary behavior where tags were not present. New traffic after this release uses the tag-based funnel.

Important scope note for conversation steps

• These system tags track platform stages (agent / handover / buyer / RTB), not every line inside the Voice Agent script.

• In-script steps (for example ZIP check → silence vs invalid vs success) are still captured when your Voice Agent collects and hands over those fields as tags. Configure those collection tags on the agent if you need step-level reporting beyond platform stages.

Impact

• Customers can report on Voice Agent and post-agent call state without relying on recordings.

• Call Summary Voice Agent performance metrics are trustworthy enough for day-to-day ops.

• Clearer separation of agent reach, handover, buyer attempt/connect, no buyer, and dropoff.

Originally published at https://help.mojaai.com/en/articles/16052899-release-notes-2026-07-22-reporting-call-state-tags-and-voice-agent-funnel

---

Release Notes: 2026-07-22 — Reporting — Metric Tooltips on Report Pages

Report pages include tooltips on key metrics and headers so column meanings are clearer in-product.

Reporting: Metric Tooltips on Report Pages

Released: July 22, 2026

Category: Enhancement

Location: Reporting

What changed

• Report pages now include tooltips on key metrics/headers so column meanings are clearer in-product.

Where to find it

• Open Reporting and hover a metric/header that shows the new tooltip affordance.

Impact

• Less guesswork when reading report columns.

Originally published at https://help.mojaai.com/en/articles/16044971-release-notes-2026-07-22-reporting-metric-tooltips-on-report-pages

---

Release Notes: 2026-07-23 — Call Flow Editor — Longer Flow Names

Longer Call Flow names are easier to read while editing.

Call Flow Editor: Longer Flow Names Are Easier to Read

Released: July 23, 2026

Category: Enhancement

Location: Call Flows → Call Flow Editor

What changed

• The Call Flow name field is now wider so longer names remain visible while editing.

• The field expands responsively on larger screens while still fitting beside the Back and Save controls.

• If a name is still too long to fit, hovering over the field shows the complete name.

How to use it

• Open a Call Flow in the editor.

• Review or edit the flow name in the header as usual.

• Hover over a truncated name to view the complete title.

Impact

• Makes it easier to confirm that you are editing the correct Call Flow.

• Reduces confusion when multiple flows use longer, similarly structured names.

Originally published at https://help.mojaai.com/en/articles/16058718-release-notes-2026-07-23-call-flow-editor-longer-flow-names

---

Release Notes: 2026-07-23 — Call Life: Improved Readability and Diagnostic IDs

Faster handoff of diagnostic IDs during support investigations.

Call Life: Improved Readability and Diagnostic IDs

Released: July 23, 2026

Category: Enhancement

Location: Reporting → Call Log → Call Life

What changed

• Call Log ID and Trace ID are now shown near the top of Call Life when available, with copy controls for faster support and troubleshooting.

• Call SID remains visible when it differs from the Call Log ID.

• Weighted-routing statistics are displayed using the same structured route tables as other routing events.

• Text throughout the timeline and event detail panels is larger and easier to read.

• Long campaign names, IDs, outcomes, and other values now wrap instead of being cut off.

• Summary controls remain usable on narrower screens.

How to use it

• Open Reporting → Call Log, select a call, and open Call Life.

• Copy the Call Log ID or Trace ID from the summary when sharing a call for investigation.

• Open routing events to review eligible routes and weighted-routing statistics.

Impact

• Faster handoff of diagnostic IDs during support investigations.

• Easier review of detailed and long Call Life values without truncated information.

Originally published at https://help.mojaai.com/en/articles/16058288-release-notes-2026-07-23-call-life-improved-readability-and-diagnostic-ids

---

Release Notes: 2026-07-23 — Numbers: Export Numbers and Associated Campaign Data

Teams can audit their number inventory and campaign assignments outside Moja.

Numbers: Export Numbers and Associated Campaign Data

Released: July 23, 2026

Category: Feature

Location: Numbers

What changed

• The Numbers page now includes a CSV export for your phone-number inventory and its associated configuration.

• The export follows the current search and sort applied on the Numbers page.

• Both organization and publisher number views are supported where available.

What’s included

• Phone number

• Associated campaign and publisher

• Attachment status, including Active, Inactive, Paused, and Publisher Inactive

• Number and order status

• Number pool

• Phone type and provider

• Order date

• Relevant record IDs

How to use it

• Open Numbers.

• Apply any search or sorting needed.

• Select Export to download the results as a CSV.

Impact

• Teams can audit their number inventory and campaign assignments outside Moja.

• Removes the need to manually copy numbers and their associated campaign information from the portal.

Originally published at https://help.mojaai.com/en/articles/16058287-release-notes-2026-07-23-numbers-export-numbers-and-associated-campaign-data

---

Release Notes: 2026-07-24 — Voice Agent Reporting: Applied-Tag Counts and Mid-Conversation Hangups

Reporting teams can classify Voice Agent outcomes more accurately, audit collection-tag coverage, and isolate caller hangups during the agent conversation using structured call data.

Voice Agent Reporting: Applied-Tag Counts and Mid-Conversation Hangups

Released: July 24, 2026

Category: Enhancement

Location: Reporting → Call Logs (system tags)

What changed

• Voice Agent calls now record two additional system tags so teams can distinguish what happened during the latest Voice Agent conversation without reviewing recordings or reconstructing the result from life-log events.

• Use the tags in call-log reporting, filters, exports, or downstream webhook/reporting workflows to answer whether the agent applied any collection tags and whether the caller disconnected while still speaking with the agent.

• The applied-tag count also supports cleaner funnel analysis: a handover with collected data can be separated from an empty handover when no buyer was reached.

Tag reference

• LAST_VOICE_AGENT_TAGS_APPLIED_COUNT — number of custom tags applied during the most recent Voice Agent conversation; 0 means none were applied.

• HANGUP_DURING_VOICE_AGENT_CONVERSATION — true when the inbound caller disconnected while the Voice Agent step was still active; false when the Voice Agent conversation ended or handed over cleanly.

Scope

• These tags describe platform-level Voice Agent processing state. They do not identify where a caller stopped inside an agent’s scripted conversation; use agent collection tags at handover when step-level reporting is needed.

Impact

• Reporting teams can classify Voice Agent outcomes more accurately, audit collection-tag coverage, and isolate caller hangups during the agent conversation using structured call data.

Originally published at https://help.mojaai.com/en/articles/16075606-release-notes-2026-07-24-voice-agent-reporting-applied-tag-counts-and-mid-conversation-hangups

---

Release Notes: 2026-07-29 — Advanced Caps — Clearer Bid-Reduction Labels

Advanced Caps now clarify whether bid reduction changes publisher payout or buyer-side revenue.

Advanced Caps: Clearer Bid-Reduction Labels

Category: Enhancement
​Location: Campaigns and Targets/RTBs → Advanced Caps
​Release Date: July 29 2026

• The former Lower Bid action now identifies which side of the call economics it changes.

• Campaign and publisher caps show Reduce Publisher Bid / Payout and explain that the publisher payment is reduced.

• Target, buyer, and RTB Formula caps show Reduce Buyer Revenue / Target Payout and explicitly state that publisher payout is not reduced.

Impact

Teams can configure caps with a clear understanding of whether the action changes publisher payout or buyer-side revenue, reducing costly routing and margin mistakes.

Originally published at https://help.mojaai.com/en/articles/16142818-release-notes-2026-07-29-advanced-caps-clearer-bid-reduction-labels

---

Release Notes: 2026-07-29 — Billing — Complete Invoice History

Load and review complete invoice history, including older and overdue invoices.

Billing: Access Your Complete Invoice History

Category: Enhancement
​Location: Account → Billing → Invoice History
​Release Date: July 29 2026

• Organization admins can now load older invoices beyond the first page of billing history in batches of 25.

• Use Load more invoices to continue through the full available history instead of being limited to the newest invoices.

• Past-due open invoices are labeled Overdue, while paid, open, void, and uncollectible statuses remain visible.

• Hosted invoice and PDF links remain available for older records as they load.

Impact

Admins can review and act on older invoices—including overdue invoices—without asking support to retrieve records hidden beyond the recent-history window.

Originally published at https://help.mojaai.com/en/articles/16142807-release-notes-2026-07-29-billing-complete-invoice-history

---

Release Notes: 2026-07-29 — Billing — Prorated Activations and Aligned Renewals

Phone number activations now prorate the partial period and align later renewals to the organization billing anchor.

Phone Number Billing: Prorated Activations and Aligned Renewals

Category: Enhancement
​Location: Account → Billing → Invoice History
​Release Date: July 29, 2026

• Phone numbers added between billing dates now receive a calendar-day prorated charge for their first partial billing period.

• After that partial period, recurring monthly number charges align with the organization’s normal subscription billing date instead of renewing separately based on each number’s activation date.

• The same alignment applies whether the organization’s usage invoices run weekly or monthly: number renewals are consolidated on the invoice containing the monthly subscription anchor.

• Each active number is calculated independently, so numbers activated on different dates receive the correct individual proration before joining the shared renewal schedule.

Impact

Billing admins receive more predictable invoice timing, fewer scattered number-renewal dates, and a fair partial-period charge when a number is added mid-cycle.

Originally published at https://help.mojaai.com/en/articles/16150302-release-notes-2026-07-29-billing-prorated-activations-and-aligned-renewals

---

Release Notes: 2026-07-29 — Call Flows — Node Configuration on the Canvas

See each Call Flow node’s saved configuration directly on the canvas.

Call Flows: See Each Node’s Configuration on the Canvas

Category: Enhancement
​Location: Call Flows
​Release Date: July 29 2026

• Call Flow nodes now display their most important saved setting directly on the canvas—for example, the selected Voice Agent, Routing Plan, Target, RTB, linked Call Flow, or HTTP request.

• Nodes with several settings show up to five details. Hover over a node to see the complete configuration.

• Unconfigured nodes clearly indicate that setup is still required.

Impact

Builders can confirm what each node does without opening every node individually.

Originally published at https://help.mojaai.com/en/articles/16142880-release-notes-2026-07-29-call-flows-node-configuration-on-the-canvas

---

Release Notes: 2026-07-29 — RTB Reporting — Search and Copy Controls

Find RTB requests by partial ID and copy complete troubleshooting values and JSON payloads.

RTB Reporting: Faster Request Search and Copy Controls

Category: Enhancement
​Location: Reporting → Inbound RTB Requests / Outbound RTB Requests
​Release Date: July 29 2026

What’s new

• Inbound RTB request search now accepts a request-ID fragment, so you can find a record without entering the complete ID.

• Outbound RTB rows now provide copy controls for full request IDs, inbound request IDs, and caller IDs—even when the displayed value is truncated.

• Expanded outbound details add copy controls for the request ID, step URL, and response error.

• RTB JSON dialogs now include a control to copy the complete formatted payload.

Impact

• Support and operations teams can correlate inbound and outbound RTB activity faster.

• Exact troubleshooting values can be copied without manually selecting truncated text.

• Complete JSON payloads are easier to move into support cases and engineering investigations.

Originally published at https://help.mojaai.com/en/articles/16147836-release-notes-2026-07-29-rtb-reporting-search-and-copy-controls

---

Release Notes: 2026-07-29 — RTB Templates — CallGrid SIP and PSTN Setup

Configure CallGrid RTB destinations faster with a new SIP and PSTN template.

RTB Templates: CallGrid SIP and PSTN Setup

Category: Enhancement
​Location: Targets/RTBs → RTB Templates
​Release Date: July 29 2026

• A new CallGrid — Standard RTB template preconfigures the CallGrid bid URL, caller ID, state, ZIP, payout, duration, and destination mapping.

• By default, the template maps CallGrid’s SIP endpoint response.

• Select Request PSTN number to add pstn=true and map the returned phone number instead.

• Enter the CallGrid Campaign ID, review the generated configuration, and use the template as the starting point for the RTB target.

Impact

Teams can configure CallGrid RTB destinations faster and choose SIP or PSTN delivery without manually building response mappings.

Originally published at https://help.mojaai.com/en/articles/16142827-release-notes-2026-07-29-rtb-templates-callgrid-sip-and-pstn-setup

---

Release Notes: 2026-07-29 — Routing Plans — Scheduled Routing Strategies

Automate recurring routing strategies by day, time, and timezone.

Routing Plans: Schedule Routing Strategies by Day and Time

Category: Enhancement
​Location: Targets/RTBs → Routing Plans
​Release Date: July 29 2026

What’s new

• Routing Plans now support recurring weekly schedules. You can automatically change which destinations receive traffic—and the priority and weight of those destinations—based on the day and time.

• Each schedule uses a selected timezone, so routing windows follow the business hours that matter to your operation rather than an individual user’s timezone.

• Each named time window has its own route set. Scheduled routes support Targets, IVRs, RTB Targets, RTB Groups, and SIP Targets, including route priority, weight, and pre-bridge settings.

• Default routes remain active whenever no scheduled window matches, keeping calls covered outside configured hours.

How scheduling works

• Add recurring windows for one or more days of the week and define the start and end time for each window.

• Arrange windows in priority order. If two windows overlap, the window higher in the schedule takes precedence.

• Use the weekly coverage chart to see scheduled periods, identify gaps, and spot overlapping windows before saving the plan.

• At call time, Moja evaluates the active window and applies that window’s route set automatically. When no window is active, Moja uses the Default route set.

Ways to use it

• Increase traffic to buyers that perform best during specific hours.

• Use one routing strategy during business hours and another overnight or on weekends.

• Send calls to staffed IVRs or SIP destinations only when those teams are available.

• Adjust destination priority and weighting around recurring performance patterns without manually editing the Routing Plan every day.

Getting started

• Open Targets/RTBs → Routing Plans and edit the Routing Plan you want to schedule.

• Turn on Scheduled routing and select the schedule timezone.

• Add and name each weekly time window, choose its days and hours, then configure the routes, priorities, and weights for that window.

• Review the weekly chart for gaps or overlaps and keep a valid Default route set for every period not covered by a scheduled window.

Impact

Teams can automate recurring routing decisions, respond more precisely to hourly buyer performance and staffing patterns, and reduce the operational risk of daily manual route changes.

Originally published at https://help.mojaai.com/en/articles/16147685-release-notes-2026-07-29-routing-plans-scheduled-routing-strategies

---

Release Notes: 2026-07-29 — Voice Agents — Updated At

See when each Voice Agent was last saved from the Voice Agents list view.

Voice Agents: See When Each Agent Was Last Updated

Category: Enhancement
​Location: Voice Agents
​Release Date: July 29 2026

• The Voice Agents list view now includes an Updated At column showing when each agent was last saved.

• Created At and Updated At both use your preferred portal timezone, so the dates remain consistent.

• You can sort, show or hide, and export the new column with the rest of the list view.

How to use it

Open Voice Agents and sort by Updated At to find recently changed agents or confirm that a configuration save occurred.

Originally published at https://help.mojaai.com/en/articles/16142799-release-notes-2026-07-29-voice-agents-updated-at

---

Release Notes: 2026-07-29 — Webhooks — Target and RTB outgoing webhooks

Attach existing outgoing webhooks to individual targets and RTB formulas.

Outgoing webhooks can now be attached directly to individual targets and RTB formulas, giving you precise control over which destination activates a webhook during call routing.

What’s new

• Attach an existing outgoing webhook to one or more targets or RTB formulas.

• When routing dials a configured destination, its webhook subscriptions become active for that call.

• Only the webhooks associated with the selected destination are triggered.

• Campaign-level outgoing webhooks continue to work as before.

• If routing fails over to another target, webhooks attached to that destination become active when it is dialed.

Why it matters

Campaigns with multiple buyers or routing destinations no longer need to apply the same webhook behavior across the entire campaign. Each target or RTB formula can use the appropriate webhook configuration.

Getting started

1. Go to Webhooks → Outgoing Webhooks and create or configure the outgoing webhook as usual.

2. Open the relevant target or RTB formula.

3. In Outgoing Webhooks, select the existing webhook you want to attach.

4. Save the target or RTB formula.

Originally published at https://help.mojaai.com/en/articles/16141227-release-notes-2026-07-29-webhooks-target-and-rtb-outgoing-webhooks

---

Release Notes: 2026-07-30 — Dynamic Payouts — Publisher Conditions

Dynamic publisher payouts now support their own call-outcome and duration conditions.

Dynamic Payouts: Set Publisher Payout Conditions by Call Outcome or Duration

Category: Enhancement
​Location: Campaigns → Number Groups / Inbound RTB Publishers
​Release Date: July 30, 2026

• Dynamic publisher payouts can now use their own payout condition while still calculating the payout amount as a percentage of the buyer or target payout.

• Choose Call length — connected, Call length — incoming, Call successfully connected, or Call converted for dynamic payouts in campaign Number Groups and Inbound RTB publisher settings.

• For a call-length condition, enter the required duration in seconds. The publisher payout is withheld when the call does not reach that threshold.

• The publisher’s configured condition takes precedence over the buyer or target condition, so publisher qualification rules can be managed independently from buyer revenue rules.

Impact

Teams can keep percentage-based publisher payouts while requiring the call outcome or connected duration that matches the publisher agreement, reducing manual payout corrections and preventing payment on calls that do not qualify.

Originally published at https://help.mojaai.com/en/articles/16150366-release-notes-2026-07-30-dynamic-payouts-publisher-conditions

---

Release Notes: 2026-07-30 — QAI — Granular Control

QAI profiles can now be managed and assigned to selected traffic from the QAI Analysis Control area.

QAI Granular Control

Category: Enhancement
​Location: QAI Analysis → Control
​Release Date: July 30, 2026

QAI configuration has moved into a new Control area under QAI Analysis. Instead of applying one account-wide QAI setup, you can now create and manage separate QAI profiles for specific traffic.

What changed

• QAI setup is now organized into reusable profiles, each with its own analysis configuration and traffic assignment.

• A profile can be attached to specific campaigns, publishers, buyers, targets, RTB formulas, or RTB groups.

• You can set a call-sampling percentage, active date range, priority, and whether the profile is enabled.

• If more than one profile applies to a call, the highest-priority profile is used.

Where to add or update questions

1. Go to QAI Analysis → Control.

2. Select New profile or edit an existing profile.

3. Open Analysis setup.

4. Add a QAI category, standalone questions, and dispositions with their related questions.

Questions support text, Yes/No, and multiple-choice answers. This lets you tailor both the questions asked and the outcomes tracked for the traffic selected in that profile.

How this helps

Use separate profiles to analyze a new campaign, publisher, buyer, target, or RTB without changing QAI for the rest of your account. You can also pause a profile or schedule it for a defined testing period.

Setup order after this release: account enablement (by Moja) → Control profile + attachments + sample % → Analysis setup on the profile → verify transcript on new calls → dispositions. Campaign-only disposition setup is not sufficient by itself.

If analysis is empty with no error, check enabled Control profiles and attachments before rewriting questions. See QAI Quick Start, QAI Prerequisites: Account, Control, and Recordings, and Troubleshooting.

Originally published at https://help.mojaai.com/en/articles/16150365-release-notes-2026-07-30-qai-granular-control

---