Registro de cambios

Novedades de Orbit

Cada función, mejora y corrección que publicamos en Orbit: primero las versiones más recientes.

¿Prefieres un canal? Suscríbete por RSS para recibir cada nueva versión en tu lector.

Loading Orbit…

Volver al panel

Registro de cambios

Novedades de Orbit

Cada función, mejora y corrección que publicamos en Orbit: primero las versiones más recientes.

¿Prefieres un canal? Suscríbete por RSS para recibir cada nueva versión en tu lector.

Filter

31 de agosto de 2026

Voice AI agents page now answers how agents plug into your existing workflows

The voice AI agents product page now answers the practical question — how an agent integrates into the workflows and systems you already run — and the voice and WhatsApp product pages link to each other for easier evaluation.

**What's new** — The [voice AI agents](/voice-ai-agents) product page now answers the question buyers actually ask when shortlisting: how does a voice AI agent integrate into the business workflows and systems we already run? The answer walks through the integration points — grounding answers in your existing help content through the knowledge base, calling your live systems mid-call through registered tools (order lookup, slot booking, ticket creation), writing post-call summaries and action items back to your CRM or webhook endpoints, and escalating to your team in the same inbox that handles SMS, WhatsApp, RCS, and email.

**Why it matters** — Evaluation pages that only describe capabilities leave the integration question unanswered until a sales call. The [voice AI agents](/voice-ai-agents) and [WhatsApp Business API](/whatsapp-business-api) pages also now link to each other, so a buyer evaluating the combined voice-and-messaging agent setup can move between the two product pages directly.

31 de agosto de 2026

Twilio-alternatives round-up closes with a quotable bottom line

The Best Twilio Alternatives for Voice, SMS, and AI Agents 2026 round-up on the Devotel Orbit site now closes its summary with a one-line bottom-line verdict, so buyers comparing Orbit, Telnyx, Vapi, and Bland AI get a clear recommendation instead of commentary about the page itself.

**What changed** — The [Best Twilio Alternatives for Voice, SMS, and AI Agents 2026](https://orbit.devotel.io/en/compare/best/twilio-alternatives-voice-sms-ai-agents-2026) round-up closes its short-answer summary with a bottom-line verdict: for the voice + SMS + AI agents requirement, an omnichannel platform qualifies, a focused AI-voice tool does not — and published pay-as-you-go rates per destination let buyers compare the assembled multi-vendor cost side by side against one bill. The earlier closing sentence described the page itself; the rankings, vendor list, and feature table are unchanged.

31 de agosto de 2026

Configuration sync for provider metadata

Brings a provider metadata field in sync with the platform configuration spec.

Messaging

One provider metadata field drifted from the platform configuration spec, and
the two could disagree when the messaging provider was probed. This fix brings
the field back in sync with the authoritative configuration layer so every
provider check reports the same value.

31 de agosto de 2026

SMPP bind-owners table self-heal survives catalog probe blips

Dashboard

SMPP traffic depends on the smpp_bind_owners lookup table, and the
platform's post-startup self-heal task is what guarantees it exists. A
transient database connectivity blip during that task's catalog check
previously wedged the table's guaranteed-recovery permanently. The task now
treats an unreadable catalog as "assume absent" and still runs the
table-creation step safely, so SMPP-dependent flows recover instead of
failing on every boot after a blip.

31 de agosto de 2026

New comparison page: Alternatives for small business communications

The compare hub gets a dedicated Alternatives for Small Business Communications page that weighs providers on the two things that matter to a lean team: who owns the carrier network, and whether the AI voice agent is integrated.

**What changed** — The comparison hub at /compare gains a new page,
**Alternatives for Small Business Communications 2026**, that weighs Orbit
against Twilio, RingCentral, Vonage, and Dialpad specifically for a small
business. It flips the usual checklist to the two questions that decide it:
who owns the carrier network your calls and messages ride on, and whether the
AI voice agent is built in or bolted on. Orbit ships both — its own wholesale
switch (carrier of record) and native AI agents — so the page evaluates each
provider against that bar. The page is also linked from the hub's
Small Business segment below, so shoppers and AI answer engines can find it.

31 de agosto de 2026

Reassigning a quality evaluation now recovers when the evaluator list fails to load

On Quality → Evaluations, opening "Reassign" while the server could not return the evaluator workload list previously rendered an empty dropdown with no way to retry — the form was unusable until the whole page was reloaded. The dialog now shows a Retry option and a clear reason when that list fails to load, so you can re-fetch it without losing your place.

Dashboard

When you move an open quality evaluation from one evaluator to another, the Reassign dialog lists every eligible evaluator with their current load. If the request that builds that list failed, the dialog used to render an empty picker offering only the "Select an evaluator" placeholder — nothing conveyed what went wrong, and the only way out was to close the dialog or reload the page.

The dialog now detects that failure and shows a Retry button alongside an explanation. Clicking Retry re-fetches the evaluator list; once it succeeds you pick a new evaluator and reassign as normal. The Reassign button also stays disabled while the list is in this failed state, so a submission cannot fire against an incomplete picker.

31 de agosto de 2026

Push notifications sent from the dashboard now appear in the unified Messages list

Push sends launched through the dashboard's Send Push dialog (or the dedicated push-send API) were only visible on the legacy push log and never showed up in the unified Messages → push list alongside sends from the standard messaging API. Each per-device outcome is now mirrored into the messages log, so dedicated-route sends render there too — one row per device, marked sent, failed, or frequency-capped.

MessagingDashboard

**What changed** — The dedicated push send endpoint used by the dashboard's Send Push dialog previously wrote its per-device delivery outcomes only to the legacy push log. The unified Messages view for the push channel reads the shared message log, so anything sent through the dedicated route was invisible there until a send went through the standard messaging API instead. The endpoint now mirrors every outcome (sent, failed, and frequency-capped skips) into the shared log as well, once per targeted device, while keeping the legacy log updated as before. Delivery behavior and the legacy push management pages are unchanged; a mirrored log entry that cannot be written never delays or fails the send itself.

31 de agosto de 2026

New docs: configure the pre-send policy scanner

A new compliance guide documents the pre-send policy scanner — TCPA, SHAFT, GDPR, DLP, and spam checks — with curl examples for setting the organization-wide scan mode and interpreting violation responses.

DocumentationCompliance

**What's new** — The [pre-send policy scanner guide](/docs/compliance/policy-scanner) now documents the control that checks every outbound message before it dispatches: TCPA quiet hours, SHAFT content, GDPR sender identity, spam-keyword scoring, and DLP (credit cards, Social Security numbers, IBANs, opt-in passport). It explains the organization-wide scan mode — strict blocks a flagged send, warn records it, off skips scanning — with curl examples for the mode endpoint, and shows how POLICY_VIOLATION and the retryable lookup-failure (503) surface in send responses.

**Why it matters** — Compliance posture used to live only in the API reference row and error-code list. Teams setting up their preferred enforcement level, or building the compose-time live lint into a workflow, now have a dedicated guide that covers the DLP privacy model (offsets, never text), the checksum validation that keeps false positives low, and the tenant-owned nature of the control.

31 de agosto de 2026

Password-reset email now renders in the recipient's language

The password-reset email now translates its subject and body into the user's chosen language (Turkish, Arabic, German, French, Spanish) the same way the welcome email does. English remains the fallback for any unrecognized tag.

**What changed** — Users who have picked a non-English locale on the signup
form or settings page used to receive the password-reset email in English
even though the welcome email was translated. The password-reset template
now ships translated copy across the product's six locales (English,
Turkish, Arabic, German, French, Spanish), with English as the fallback
for any unrecognized tag, matching the welcome email behaviour.

31 de agosto de 2026

New guide: what platform as a service is — and what to evaluate before you build on it

A new guide defines platform-as-a-service infrastructure for business communications and gives buyers the need-to-know checklist for evaluating any vendor.

**What's new** — [Platform as a service for communications: what must be true before you build on it](/paas-infrastructure) is an evaluation guide for businesses weighing what their communication stack is built on. It defines the PaaS model in plain terms, lays out a six-point "need-to-know" checklist — owned network, one SLA, native AI, one bill, API plus console, one customer timeline — and applies that checklist side by side to an owned-carrier platform, a reseller platform, and a stitched multi-vendor stack.

**Why it matters** — Most "platform" labels hide a stitched stack underneath, and the seams surface after you've committed. The guide turns the evaluation into yes/no questions any vendor can be asked up front, and links into the [one provider vs multiple vendors](/vendors-comparison), [omnichannel comparison](/omnichannel-comparison), and [carrier-of-record](/compare/carrier-of-record) guides for the deeper cuts of each factor.

31 de agosto de 2026

Public content pages self-heal survives catalog probe blips

Dashboard

Public content pages depend on the orbit_content_pages table, and the
platform's post-startup self-heal task is what guarantees it exists. A
transient database connectivity blip during that task's catalog check
previously wedged the table's guaranteed-recovery permanently. The task now
treats an unreadable catalog as "assume absent" and still runs the
table-creation step safely, so public content page reads recover instead of
failing on every boot after a blip.

31 de agosto de 2026

Inbox now fully localized in Spanish

The shared Inbox now renders in natural Spanish end to end instead of mixing in English labels. Nearly two hundred inbox strings — folders, macros, copilot, call cards, SLA banners, CRM context, filters — were showing English copy to Spanish-speaking teams.

Inbox

**What's new** — Teams whose workspace language is Spanish used to see a mixed-language Inbox: close hints, folder descriptions, macro editors, copilot menus, call cards, SLA banners, CRM context panels, and composer labels like "Ad attribution" or "Lifecycle" still rendered in English. The inbox now translates all of those into natural Spanish, matching what the rest of the dashboard already does.

31 de agosto de 2026

New glossary definition for number warm-up

The glossary at /glossary added a new "what is number warm-up" page covering carrier trust ramps on fresh 10DLC long codes, short codes, and alphanumeric sender IDs — with an on-page FAQ and links to the related IP warmup, A2P 10DLC, and throttling definitions.

Messaging

The CPaaS glossary (/glossary) now defines **number warm-up** — also called sender registration warm-up or 10DLC warm-up — the gradual traffic ramp on a newly registered sender rather than sending at full volume from day one.

The new page explains why carriers gate cold senders (a sudden burst with no delivery history reads as spam-like, so the volume gets filtered), how the warm-up differs from IP warmup (an email asset) and from brand vetting (The Campaign Registry's screening of the 10DLC brand), and what Orbit surfaces while a number warms: the warming phase (initial → ramp → steady → verified), today's daily_cap versus current_day_count, the 15-day progression forecast, and the 429 WARMING_QUOTA_EXCEEDED refusal that stops an over-cap send before it reaches the carrier. Pacing guidance is specific: split early volume across warming numbers or an already-warmed sender, and never retry-loop a refused send before the midnight-UTC cap reset. The definition frames warming as the carrier-side trust mechanism it is, with an on-page FAQ and related-term links to IP warmup, sender reputation, A2P 10DLC, and throttling.

31 de agosto de 2026

The contacts screen now reads in full German for German-language operators

Operators working in German saw English labels across the whole contacts area — list filters, contact detail, the CSV import wizard, duplicate merging, segments, bulk actions, lifecycle stages, AI memory, and the right-to-erasure panel. Every one of those strings now renders in German too, not just the already-local settings copy.

Contacts

German-language operators had a mixed-language contacts experience: the settings screens spoke German, but nearly the entire contacts surface — the list, the detail panel, the CSV import wizard, the merge-duplicates flow, segments, bulk actions, lifecycle stages, the AI memory view, and the GDPR right-to-erasure panel — showed English labels on controls and empty states alike.

That gap is closed. Choosing German in your account settings now renders the whole contacts area in German, and the English fallback only appears if a new label lands before its translation has been added. Genuine loanwords and product terms (Import, Tag, Segment, SMS, Audit) read the same in both locales, which is by design.

31 de agosto de 2026

Transactional emails now declare the document language for screen readers

Every transactional email Devotel Orbit sends (password resets, billing alerts, usage reports and the rest) now declares its language in the document markup, so screen readers and browser translation tools handle the message with the correct pronunciation rules instead of guessing.

Every email Devotel Orbit sends is built on one shared layout. That layout previously rendered the document without any language declaration, so assistive technology (screen readers, browser speech) and browser translation tools had to guess the reading language — for recipients whose device language is not English, that guess could produce wrong pronunciation or skipped translation prompts.

The layout now declares the document language explicitly, defaulting to English (en) and accepting a per-send override so a template rendered for a known recipient locale declares it. Emails look and read exactly as before; the change is in the document markup that accessibility and translation tooling rely on.

31 de agosto de 2026

New documentation: the outbound message DLP scanner, its data classes, and strict mode

The compliance section of the docs now explains the outbound message DLP scanner end to end — what it detects, why checksum validation keeps strict mode safe, how a finding becomes a block, and how it differs from the transcript data scrubber.

Documentation

**What's new** — The docs compliance section now has a dedicated page on the outbound message DLP scanner: the data classes it detects (full card numbers, US Social Security numbers, IBANs, opt-in passport numbers), why checksum validation keeps strict mode safe to leave on, how a finding raises a block verdict or auto-redacts before dispatch, its privacy posture (findings carry offsets and a category, never the matched text), and how it differs from the write-time transcript data scrubber. The HIPAA and PCI-DSS pages now link to it, so regulated teams land on the enforcement control, not just the posture narrative.

**Why it matters** — If you enforce PCI-DSS, HIPAA, or GDPR on the message lane, the posture pages described the obligation but not the control that actually blocks regulated data at send time. The new page closes that gap with the categories, modes, and verdicts your organization configures.

31 de agosto de 2026

Make a Call recovery buttons now take you to the right page instead of looking unresponsive

Buttons inside the "Make a Call" dialog that point you elsewhere ("Buy a Number" when you own no calling numbers, "View my numbers" while a number awaits carrier verification, "Add Funds" on an empty balance) previously navigated without closing the dialog, so the route change happened behind the open overlay and the screen looked frozen. Clicking one now closes the dialog and takes you there on the first click.

VoiceDashboard

When you open the dialer ("Make a Call") without a usable setup, it explains what to fix first: you own no calling numbers ("No voice numbers available"), your number is still pending carrier verification, or your balance is too low to start the call. Each case offers a button that points at the fix: "Buy a Number", "View my numbers", or "Add Funds".

The bug: clicking one of those buttons changed the page underneath but left the dialog open on top of it, so the new screen arrived covered by a dimmed, untouchable overlay and the button looked like it did nothing. Clicking any of them now also closes the dialog, so you land on the Buy, Numbers, or Billing page ready to act.

31 de agosto de 2026

Dialer campaign stats now show a retry prompt instead of misleading zeros when the fetch fails

On the dialer campaign detail page, a failed live-stats fetch made every gauge (total, dialing, connected, failed, DNC, 24-hour outcomes, and more) render zeros, reading like an empty campaign. The page now shows a "Couldn't load campaign stats" message with a Retry button instead, and gauges only render once real numbers arrive.

VoiceDashboard

On a dialer campaign's detail page, the strip of stat gauges (contacts total, pending, dialing, connected, failed, DNC blocked, timezone blocked, exhausted, callbacks scheduled, wrong number, archived, plus last-24-hour voicemail and no-answer counts) polls every 10 seconds while a campaign is running. If that fetch ever failed — a dropped connection, a brief API hiccup — each gauge quietly fell back to zero, making a live campaign look exactly like one with no activity at all.

The page now tells the difference: a failed fetch renders a "Couldn't load campaign stats" prompt with a Retry button, and the gauges render only once real numbers have arrived. You can no longer mistake a fetch failure for an empty campaign while a campaign is dialing.

31 de agosto de 2026

New guide: cost-center chargeback rollup

A dedicated guide walks the chargeback loop: tag sends with a cost-center label, then read the department-first rollup that shows allocated vs untagged spend, per-channel splits, and each department's share of the period.

DocumentationBilling

**What changed** — Cost-center attribution previously had two sentences under
the usage endpoint. The new
[cost-center chargeback guide](https://docs.orbit.devotel.io/guides/cost-center-chargeback)
walks the full loop: tag a send with metadata.cost_center, read the
department-first rollup at GET /api/v1/billing/chargeback-rollup (allocated
vs untagged totals, per-channel splits, each department's share of the
period), and slice one tag with the group_by=cost_center axis on
/api/v1/billing/usage-by-channel. It covers access (billing-role), the
untagged bucket, and the monthly statement exporter.

31 de agosto de 2026

BYO fee pointer now shows cents as whole cents

The "BYO fee: <n>¢ per transaction" pointer on the Connection Mode page mislabeled its rate — a 1¢ default rendered as "0.01¢". Sub-dollar rates now show whole cents, and rates of 100¢ or more show as dollars.

Dashboard

**What changed** — The per-transaction fee pointer we added next to each
"Your own connection (BYO)" badge on Settings → Subaccounts → Channel
connection mode divided the fee (stored in cents) by 100 but still labeled
the result with the "¢" sign. The 1¢ platform default therefore read
"0.01¢", and a 150¢ Devotel-set rate read "1.50¢". Sub-dollar rates now
render as whole cents (for example "BYO fee: 1¢ per transaction"), and any
rate of 100¢ or more falls back to two-decimal dollars (for example
"$1.50"), so the number always matches its unit.

Showing 20 of 400 · 380 more

This page lists the 400 most recent of 12757 releases. Subscribe via RSS to get each new release as it ships.

Filter

31 de agosto de 2026

Voice AI agents page now answers how agents plug into your existing workflows

31 de agosto de 2026

Twilio-alternatives round-up closes with a quotable bottom line

31 de agosto de 2026

Configuration sync for provider metadata

Brings a provider metadata field in sync with the platform configuration spec.

Messaging

31 de agosto de 2026

This page lists the 400 most recent of 12757 releases. Subscribe via RSS to get each new release as it ships.