August 2026

Release Notes: 2026-08-04 — Inbound RTB — Fixed Publisher Payouts with Buyer-Specific Durations

Inbound RTB: Fixed Publisher Payouts with Buyer-Specific Durations

Inbound RTB: Fixed Publisher Payouts with Buyer-Specific Durations

Category: Enhancement

Location: Campaigns → Inbound RTB Publishers

Release Date: August 4 2026

Static publisher payout mode can now keep a fixed dollar payout while each buyer supplies its own billable-duration requirement.
Configure the publisher row with a static payout and a call-length condition; you no longer enter a separate duration for that static row. Moja uses the winning buyer’s billable duration to determine when the publisher payout is earned.
Buyer bid responses retain their individual durations, so a single campaign can use the same fixed publisher payout across buyers with different duration thresholds.

Impact

Teams can support hybrid economics such as a fixed $30 publisher payout while one buyer requires 95 seconds and another requires 100 seconds—without forcing every side of the transaction into the same payout mode.

Originally published at https://help.mojaai.com/en/articles/16202096-release-notes-2026-08-04-inbound-rtb-fixed-publisher-payouts-with-buyer-specific-durations

Release Notes: 2026-08-04 — Numbers — Custom Names and Reusable Labels

Numbers: Custom Names and Reusable Labels

Numbers: Custom Names and Reusable Labels

Category: Feature

Location: Numbers

Release Date: August 4 2026

What’s new

Add a custom name to each tracking number and organize numbers with reusable, organization-wide labels.
Create labels under Numbers → Labels, then edit a number to assign its name and labels. You can also select multiple rows in the Numbers list and add or replace names and labels in bulk.
Search by number name or label text, filter the Numbers list by one or more labels, and include Name and Labels in CSV exports.
Campaign number selectors now show the number together with its name and labels, making similarly formatted numbers easier to identify before assignment.

How to use it

First create the reusable labels you need under Numbers → Labels.
Return to Numbers to edit one number or select several rows for bulk assignment. Use add mode to preserve existing labels or replace mode to set the selected numbers to a new label set.

Impact

Teams can identify, group, search, export, and assign large number inventories using their own operational naming conventions instead of relying on digits alone.

Originally published at https://help.mojaai.com/en/articles/16202098-release-notes-2026-08-04-numbers-custom-names-and-reusable-labels

Release Notes: 2026-08-05 — Reporting — Call Summary Total Billable Minutes (TBM)

Call Summary shows Total Billable Minutes (TBM) instead of raw TCL when billing data is available.

Call Summary: Total Billable Minutes (TBM) replaces TCL

Category: Enhancement
Location: Reporting → Call Logs → Call Summary
Release Date: August 5 2026

Admin and member Call Summary now shows Total Billable Minutes (TBM) instead of raw Total Call Length when billing data is available.
TBM is the sum of per-call minutes rounded up to the nearest minute — the same minutes used to calculate Cost — so summary duration lines up with how calls are billed.
Call log grid still shows Total Call Length only (no TBM column). Buyer and publisher summary views are unchanged.
If billable minutes are not returned, Call Summary falls back to TCL.

Impact
Teams reconciling usage and cost can trust Call Summary duration against billable minutes instead of raw talk time.

Originally published at https://help.mojaai.com/en/articles/16226226-release-notes-2026-08-05-reporting-call-summary-total-billable-minutes-tbm

Release Notes: 2026-08-05 — Voice Agents — Conversation Summaries and Transcripts in Call Details

Call Details includes Voice Agent Conversations with summaries and full transcripts.

Voice Agent Calls: Conversation Summaries and Transcripts in Call Details

Category: Enhancement
Location: Reporting → Call Logs → Call Details → Voice Agent Conversations
Release Date: August 5 2026

Call Details now includes a Voice Agent Conversations tab for calls that used a voice agent, bringing the conversation record into the same view as Call Life, Tags, and RTB details.
Open a call from Reporting → Call Logs, select Voice Agent Conversations, and expand a conversation to load its details. Each entry identifies the voice agent and conversation time.
Review the conversation summary, whether the call was marked successful, and the full agent-and-caller transcript in a chat-style view. Transcript turns can include their time into the call, interruption status, source medium, and available processing timings.
Calls without a stored conversation show a clear empty state, while conversation-list and detail failures are isolated to the tab instead of breaking Call Details.

Impact
Operations and reporting teams can inspect what happened during a voice-agent interaction directly from the call record, making qualification outcomes, caller responses, interruptions, and handoff context easier to audit without switching systems.

Originally published at https://help.mojaai.com/en/articles/16226227-release-notes-2026-08-05-voice-agents-conversation-summaries-and-transcripts-in-call-details

Release Notes: 2026-08-07 — RTB — Bid Expiration and TTL Controls

Inbound RTB routing can now account for how long a buyer’s bid remains valid.

RTB Bid Expiration and TTL Controls

Category: Enhancement
Location: Targets/RTBs → RTB Formulas and Targets/RTBs → RTB Groups
Release Date: August 7 2026

Inbound RTB routing can now account for how long a buyer’s bid remains valid, helping prevent accepted bids from being passed downstream after—or just before—the buyer’s routing window expires.

What changed

RTB Formulas now include Bid TTL Settings where you can set a default bid TTL and a minimum remaining TTL required to accept a bid.
RTB Groups now support minimum and maximum bid TTL controls, including formula-level overrides when different formulas need different limits.
Buyer expiration values are recognized in ISO timestamps, Unix seconds or milliseconds, and relative TTL seconds. Retreaver response mappings can pass the buyer’s expires_at value through as expiresAt.
Bids below the configured minimum TTL are rejected instead of being treated as usable; bids above a group maximum are constrained to the configured window.
Routing allocation is limited to the bid’s remaining lifetime, and expired duplicate-response cache entries are no longer replayed.

How to use it

Open an RTB Formula and configure its default TTL for responses without buyer expiration data, plus the minimum remaining TTL required for acceptance.
Open an RTB Group to set the group-wide minimum and maximum TTL. Add formula overrides when one formula needs stricter or broader limits than the group default.
For Retreaver buyers, map the buyer response’s expires_at value to expiresAt so Moja can preserve the buyer-provided expiration.

Impact

Publishers receive fewer stale accepted bids, while sellers gain explicit control over which bids have enough time remaining to route and connect successfully.

Originally published at https://help.mojaai.com/en/articles/16257503-release-notes-2026-08-07-rtb-bid-expiration-and-ttl-controls

Release Notes: 2026-08-12 — Ask AI+ — Account Assistant

Ask AI+ now includes an Assistant.

Ask AI+ now includes an Assistant
Category: Feature
Location: Reporting → Ask AI+
Release Date: August 12, 2026

Ask AI+ now includes an Assistant: a conversational way to understand account performance, investigate what happened, and manage supported portal work without moving through every screen manually.

Tell it the result you need. The Assistant can examine the relevant account data, explain what it found, link you to the records involved, and prepare supported changes for your approval.

Reporting and performance analysis
• Ask questions about performance across campaigns, targets, RTB formulas, routing plans, publishers, and calls—then follow the answer to the relevant portal records.
• Use it for aggregate questions that need more than a total: “Which RTB formulas received traffic but did not produce completed calls?” or “Which targets were eligible but not selected?”
• Supported answers can include charts, tables, and direct portal links.

Troubleshooting and investigation
• Investigate a specific call or uncover the pattern behind a broader delivery issue: “Why did call [call ID] fail?” or “What do the failed calls for this campaign have in common?”
• The Assistant uses available account and call-history evidence to explain what it found rather than guessing at a cause.
• A call ID, portal link, object name, campaign, target, RTB formula, routing plan, phone number, or date range makes an investigation faster and more precise.

Account management and portal changes
• Tell the Assistant the outcome you need—not the sequence of portal screens. It can find the relevant records, gather the required details, and prepare the supported change.
• It supports the same supported account changes you would otherwise make manually in the Moja portal, including work across campaigns, routing plans, targets, RTB formulas, number settings, webhooks, call flows, IVRs, voice agents, QAI configuration, and blocked numbers.
• Before anything changes, Ask AI+ presents a confirmation card with the proposed action and affected records. Select Yes to apply it or Cancel to discard it.

Getting the best results
• Start with the business question or desired outcome, add a time range when performance matters, and name the record when you know it.
• Keep unrelated work in separate conversations, give the Assistant time to check the relevant records, and review confirmation cards carefully—especially when an action affects multiple records.

Impact
• Ask AI+ is now an operating layer for the portal: understand what happened, investigate why, and make the needed change—with confirmation.

Originally published at https://help.mojaai.com/en/articles/16382806-release-notes-2026-08-12-ask-ai-account-assistant

Release Notes: 2026-08-12 — QAI — Disposition System Tag

QAI dispositions are available through a system tag.

QAI Dispositions are now available as a system tag
Category: Enhancement
Location: Reporting → Call Logs → Tags
Release Date: August 12, 2026

What’s new
• When QAI selects a disposition for a call, Moja now writes that result to the read-only QAI_DISPOSITION system tag.
• The tag value is the selected disposition, such as qualified, and stays aligned with the current QAI evaluation—no separate tag setup is required for each disposition.
• If a call is re-evaluated, the tag updates to the new selected disposition. If no disposition matches, the tag is removed rather than leaving an obsolete result behind.

Impact
• Teams can use the QAI disposition consistently alongside other call tags for reporting, filtering, and downstream workflows—without manually copying the result from QAI analysis.

Originally published at https://help.mojaai.com/en/articles/16382842-release-notes-2026-08-12-qai-disposition-system-tag

Release Notes: 2026-08-12 — RTB — Test placeholder values

RTB test requests now prompt for unresolved placeholder values before sending.

Test RTB requests with placeholder values before you send them

Category: Enhancement
Location: Targets/RTBs → create or edit an RTB → test a request
Release Date: August 12, 2026

RTB test requests now recognize unresolved bracketed placeholders across your request, including [ZIP], [STATE], [CALLER_ID], common caller-ID variants, and custom tags.

When you select Send and a required placeholder has no value, Moja opens one editable test-value prompt instead of sending an incomplete request. Standard examples are prefilled for ZIP, state, and caller ID; custom placeholders require a value you choose.

Edit any suggested value to test the routing scenario you actually need.
Test values are substituted into the outbound request so you can verify the exact request your buyer receives.
Literal values do not trigger the prompt.
You can still continue with unresolved placeholders when that is intentional.

This makes RTB testing less dependent on manual request editing and makes missing test inputs visible before they produce a confusing failure.

Originally published at https://help.mojaai.com/en/articles/16401208-release-notes-2026-08-12-rtb-test-placeholder-values

Release Notes: 2026-08-20 - Campaigns - Static receive DIDs for Inbound RTB

Inbound RTB publishers can deliver accepted calls to a stable receive DID.

Static receive DIDs for Inbound RTB

Category: Feature
Location: Campaigns - select a campaign - Inbound RTB Publishers
Release Date: August 20, 2026

What’s new

Inbound RTB publishers can now ping Moja for bid and payout context, then deliver the accepted call to a stable receive DID instead of dialing a different dynamic number for every response.
Choose Static DID — single active bid when each caller should have one active winning bid. Moja returns a bid ID, rejects another active ping for the same caller during the reservation window, and matches the incoming call by the selected DID and caller number.
Choose Static DID — multi-bid confirm when a publisher needs to collect multiple bids for the same caller. The publisher confirms the selected bid ID before transferring the call; Moja supersedes the other pending bids and matches the call to the confirmed reservation.
Existing dynamic Inbound RTB delivery remains available and unchanged.

How to use it

Open a campaign’s Inbound RTB Publishers configuration, select a static receive mode, and choose the purchased number that will receive calls for that publisher slot.
For single-active-bid mode, send the accepted caller to the configured DID within the bid window.
For multi-bid mode, confirm the chosen bid before sending the call. A call without a confirmed bid does not qualify for Inbound RTB routing in this mode.

Impact

Publishers and call centers can use a stable transfer number while Moja preserves the matched request, route, payout, duration, campaign, and publisher context in call and Inbound RTB reporting.

Originally published at https://help.mojaai.com/en/articles/16540476-release-notes-2026-08-20-campaigns-static-receive-dids-for-inbound-rtb

Release Notes: 2026-08-20 - Reporting - Ask AI bounded time periods

Ask AI reporting now uses clear, bounded time periods.

Ask AI reporting now uses clear, bounded time periods

Category: Enhancement
Location: Reporting - Ask AI
Release Date: August 20, 2026

What changed

When a historical reporting question does not include a date range, Ask AI now analyzes the rolling last 30 days and states that period in its answer.
You can request an explicit reporting period up to and including six calendar months. Requests longer than six months are declined before a data query runs rather than silently shortened or split.
Follow-up questions retain the period already established in the conversation unless you specify a different one.
Current configuration questions and exact-record lookups remain exempt when a date filter would change the meaning of the request.

How to use it

Ask a reporting question normally and omit the period when the last 30 days is appropriate.
Include a specific range such as in the last 90 days or from May 1 through July 31 when you need a different window.

Impact

Historical questions return against a predictable period, follow-ups stay consistent, and broad requests cannot trigger unnecessarily expensive full-history scans.

Originally published at https://help.mojaai.com/en/articles/16539471-release-notes-2026-08-20-reporting-ask-ai-bounded-time-periods

Release Notes: 2026-08-21 — Reporting — RTB Pulse buyer outcomes

RTB Pulse now classifies buyer response outcomes in Tuning summaries.

RTB Pulse now explains buyer response outcomes

Category: Enhancement
Location: Reporting → RTB Pulse → Tuning
Release Date: August 21, 2026

What’s new

RTB Pulse now separates transport failures from the business outcome returned by a buyer, so a successful connection that returns “no target” is no longer grouped with an endpoint that never responded.
Open an endpoint in Tuning to see a Summary-first percentage breakdown for the last 24 hours, 7 days, or 30 days across six outcomes: Accepted, No target, Rejected, Ping Shield, No response, and Other.
Recommendations now reflect the dominant outcome mix. This helps distinguish buyer availability, duplicate protection, source rejection, and configuration or rate-limit responses from genuine timeout or connection failures.
Endpoint health now distinguishes idle, paused, degraded, and critical behavior. An endpoint receiving meaningful traffic with no responses is no longer shown as idle.

How to use it

Open Reporting → RTB Pulse, select Tuning, then choose an endpoint.
Review the Summary outcome mix and switch between 24-hour, 7-day, and 30-day periods to see whether the dominant buyer response is persistent or recent.
Use the outcome-specific recommendation to decide whether to investigate availability, traffic quality, duplicate pings, endpoint configuration, or transport health.

Impact

Teams can diagnose outbound RTB performance from the operational summary instead of interpreting raw response bodies or treating every non-bid result as the same failure.

Originally published at https://help.mojaai.com/en/articles/16555870-release-notes-2026-08-21-reporting-rtb-pulse-buyer-outcomes

Release Notes: 2026-08-25 — RTBs — Control outbound ping volume by buyer

Per-formula outbound RTB ping rate, in-flight cap, and cooldown.

Control outbound RTB ping volume by buyer

Category: Feature
Location: Targets/RTBs → RTBs → select an RTB formula
Release Date: August 25, 2026

What’s new

Each RTB formula can now limit how many outbound pings Moja sends during a minute, hour, or day without reducing traffic for the entire publisher or campaign.
Set a maximum number of simultaneous in-flight requests to prevent one buyer endpoint from receiving more concurrent pings than it can handle.
Enable buyer cooldown to temporarily stop new pings after a configured number of consecutive buyer rate-limit responses, duplicate-shield responses, or timeouts. Other eligible formulas can continue competing while one formula is throttled.
Leave these settings blank or disabled to preserve unlimited outbound ping behavior.

How to use it

Open Targets/RTBs → RTBs, select an RTB formula, and configure its outbound ping rate and period, in-flight request cap, or cooldown threshold and duration.
Use the minute, hour, or day rate window to match the buyer’s accepted ping volume. Pair it with the in-flight cap when the endpoint also limits concurrent requests.
Use cooldown when repeated buyer-side rate limits, duplicate protection, or timeouts should pause that formula briefly instead of continuing to send requests.

Reporting and impact

In outbound RTB reporting, the By Buyer view now distinguishes pings Moja intentionally skipped because of the configured throttle from buyer HTTP 429 responses, duplicate-shield responses, and buyer timeouts.
Ask AI follows the same distinction, so teams can tell whether Moja protected a configured limit or the buyer rejected an actual request.
Teams can protect buyer relationships and endpoint capacity without pausing the buyer, removing it from routing, or slowing unrelated RTB traffic.

Originally published at https://help.mojaai.com/en/articles/16626236-release-notes-2026-08-25-rtbs-control-outbound-ping-volume-by-buyer

Release Notes: 2026-08-25 — Reporting — Defer Inbound RTB sections

Inbound RTB Life Logs and Statistics Summary load on scroll.

Reporting loads faster by deferring Inbound RTB sections

Category: Enhancement
Location: Reporting
Release Date: August 25, 2026

What’s new

Opening Reporting no longer waits on Inbound RTB Life Logs or Inbound RTB Statistics Summary before Summary and Call Logs are usable.
Those RTB sections load when they are scrolled into view, instead of blocking the first page load.
Deep links that land on Inbound RTB Life Logs still load that section immediately.

Impact

High-volume teams can use call reporting without waiting on unused RTB widgets.

Originally published at https://help.mojaai.com/en/articles/16626237-release-notes-2026-08-25-reporting-defer-inbound-rtb-sections

Release Notes: 2026-08-27 — Inbound RTB — Call Flow on live allocated calls

Attach a Call Flow on an Inbound RTB row so Voice Agents and other live-call nodes can run after the publisher dials the reserved number.

Run Inbound RTB calls through a Call Flow (Voice Agent and other live-call nodes)

Category: New feature
Location: Call Flows; Campaigns → select a campaign → Inbound RTB Publishers
Release Date: August 27, 2026

What this solves

Inbound RTB used to pick a buyer and connect the call straight to that destination. You could not put a Voice Agent (or other nodes that need a real phone call) in front of that destination. That is now possible.

How it works (two different moments)

Publisher ping (no caller on the line yet): Moja still uses the campaign’s existing Call Flow or Routing Plan to choose a buyer and reserve a number. Nothing new is required here.
Live call (publisher dials that reserved number): if you attach a Call Flow on the Inbound RTB row, that Call Flow runs instead of sending the caller straight to the winning destination. This is where Voice Agent, Switch, If, Hangup, and Allocated Number belong.

You use both: the campaign path to win the bid, and a second Call Flow attached on the Inbound RTB row to handle the actual call.

What’s new

Each Inbound RTB publisher row can attach its own Call Flow. Leave it empty to keep today’s behavior (campaign routing only).
New Call Flow node: Call allocated number. It dials the destination that already won the ping. You do not pick buyers again on that path.
That node has Processed and Failover. Connect them only if you want something after that dial (another node or hangup). If you want the call to end with the buyer, you can leave them empty.
Switch nodes always show a Default path when no condition matches.
Live calls that claimed an allocation get the system tag INBOUND_RTB_ALLOCATION.

How to set it up

Keep your current campaign Call Flow or Routing Plan. That is still what answers the ping and chooses the buyer.
Create a second Call Flow under Call Flows for after the caller is on the line. Do not create or pick this flow as the campaign’s main route type. You attach it later on the campaign page, in Inbound RTB Publishers.
In that second flow: Start → Voice Agent (and any If/Switch you need) → Call allocated number when the call should go to the winning Inbound RTB destination. Use a Routing Plan node only when you want a different destination (for example fraud / outbound-dialer traffic), not for the original winning buyer.
Open Campaigns, select the campaign, go to Inbound RTB Publishers, and attach that second Call Flow on the Inbound RTB row. That picker is what turns this on. Empty = campaign routing only.

Example (fraud screen, then winning buyer)

Start → If (Inbound RTB request) → Voice Agent → Switch

Not fraud / Default → Call allocated number (the buyer that already won)
Fraud → Routing Plan (hangup, or a buyer who will take those calls)

Do not

Put Voice Agent only on the campaign Call Flow and expect Inbound RTB pings to talk to it. Ping has no caller yet.
Replace Call allocated number with another Routing Plan when you still want the original winning destination.
Attach the campaign’s ping Call Flow on the Inbound RTB row unless that flow is actually what should run on the live call.

Impact

Teams can screen, qualify, or branch an Inbound RTB call with Voice Agents and other live-call nodes, then connect good traffic to the destination that already won, without changing how the ping chooses a buyer.

Originally published at https://help.mojaai.com/en/articles/16668607-release-notes-2026-08-27-inbound-rtb-call-flow-on-live-allocated-calls