What's new in Orbit

Until now, a person who completed sign-up on a white-label partner's own domain was left with a standalone workspace that had no connection to the provider whose brand they signed up under. The first-run step that follows sign-up now places that workspace before it asks for a name: when the domain belongs to a white label, the new workspace is attached under it as a tenant and inherits the provider's branding. The person who signed up stays the owner of their workspace and is never seated inside the provider's own organization.

When the domain belongs to an ordinary organization instead, the person who signed up joins it as a member and the empty workspace created during sign-up is retired, the same outcome those domains already had. On a white-label domain the first-run page resolves the placement before showing the workspace naming form; a sign-up that already landed in an organization goes straight to the dashboard, and if the placement cannot proceed the page shows a short message with a way to sign out and start again.

Only a fresh, untouched workspace is placed: one that has not been renamed, topped up, or shared with teammates. A workspace already in use is left exactly as it is, so revisiting an old sign-up link later cannot disturb a working workspace. The standard first-run experience on the main Devotel Orbit domain is unchanged.

Opening Developer → Connected Apps used to leave the browser tab showing a generic label, so the tab didn't tell you which page you were on. The tab now reads "Developer | Connected Apps", consistent with the rest of the Developer section, and the title is translated in every supported language.

The Inbox channel filter row no longer covers its first or last option with decorative fade overlays. Scroll to either end to read and select the complete channel label.

Every workspace gets one free trial number. Once it has been used, claiming a
second one is correctly refused — but until now the refusal showed a generic
"too many requests, please wait a few seconds" notice. That wording described a
temporary rate limit, while the real reason is permanent: the free trial is a
one-time benefit, so waiting never makes another claim possible.

The Numbers page (and the other claim entry points) now show the true
explanation: your one free trial number has already been used, and you can add
another number by purchasing a dedicated one.

Genuine rate limits are unchanged — when a request really is being throttled
and the server says how long to wait, you still see the countdown toast.

The guide's send examples previously showed template_name and template_params on an SMS send without saying that server-side template lookup happens on only five channels. A new "Server-side rendering vs caller-resolved channels" section under Channel-specific rules lists both groups, and the worked send example now states plainly that on caller-resolved channels template_name alone will not deliver the template — resolve it on your side and put the rendered text in body.

On the Verifications page, the Success Rate card shows your success percentage inside a circular gauge. The number was set one size too large for the circle, so values like "100%" came close to touching the ring's edge. The number now renders one step smaller and sits centered with comfortable spacing, consistent with the figures elsewhere in the stats row. The percentage itself is unchanged — only the type size moved.

The conversation history table lists conversations from every agent, but a CSV export is produced for one agent at a time. Until now, with "All Agents" selected the Export CSV button simply looked disabled and gave no explanation. The filter bar now shows "Select an agent to export its conversations" beside the button whenever no agent is chosen, and the hint disappears the moment you pick one — at which point the export runs as before.

In an IVR flow, a DTMF Input step ends when the caller presses its finish key. If the caller pressed the finish key without entering any digits first, the step treated it as no answer and played the prompt again, up to three times. The finish key now always ends the step and the call continues to the next step in your flow. Timeouts with no input still repeat the prompt as before.

Opening Developer → Marketplace used to leave the browser tab showing the generic "developer | Orbit" label, so the tab didn't tell you which page you were on. The tab now reads "Developer | Marketplace", consistent with the rest of the Developer section, and the title and page description are translated in every supported language.

**What changed** — On a number's Inbound routing tab, the Call recording section offered Off, All calls, Inbound only and Outbound only. A number that followed your organization's recording setting was shown as Off, and once you picked a mode there was no way to hand the number back to the organization setting. The section now starts with an Organization default option that names the setting it follows, for example "Organization default (All calls)", and the collapsed section reads "Org default · All calls" instead of "off". Choosing Organization default and saving removes the number's own setting. The same option is available when you apply routing to several numbers at once from the Numbers list.

**Why it matters** — A recording mode set on a number always wins over the Eligibility setting under Voice → Calls → Recording Settings. A number set to Off is not recorded and does not play the consent announcement to callers, even when your organization records all calls. When a number has its own setting, the section now says that it overrides the organization setting and what that means, so this is visible before a call is missed. Numbers you never changed keep following the organization setting, and nothing changes for numbers that already have a mode chosen on purpose.

Choosing Available or Away from the softphone's availability control could fail with an error and leave your status unchanged, because your browser session was never added to the agent roster that queue routing reads from.

The dashboard now adds you to the roster when it loads and checks in every 30 seconds while the tab stays open. Status changes save the first time, including on a brand-new account. You still start as Offline, so calls are only routed to you once you choose Available. If your role doesn't allow availability changes, the softphone works as before without the background check-ins.

Declining an incoming call from the softphone pop-up, or from the mobile app, ends the call for the caller. Until now, the Call Log on the Voice → Calls page listed that call as Successful, so it was counted alongside calls you actually took. Declined calls now keep the Declined status in the Call Log. Calls you accept are unchanged.

**What changed** — On a call queue's Members tab, the Skills field in both the "Assign an agent" form and the Edit membership dialog used to be a plain text box where you typed skills separated by commas. You had to remember each skill's exact identifier, and a typo was saved as-is. The field is now a searchable multi-select listing every active skill in your Skill Catalog by name and identifier. Search by either, pick as many as you need, and remove one with its close button. If the catalog has no active skills yet, the field says so and links straight to the Skill Catalog. If the catalog can't be loaded, the field shows the error and a Try again link.

**Why it matters** — An agent only receives calls whose required skills match the skills on their queue membership, so a single misspelled skill quietly kept that agent out of routing. Choosing from the catalog keeps memberships in step with the skills your queues actually require. Skills already saved on a membership that are no longer active in the catalog stay in place, marked "Not in catalog", so you can decide whether to remove them or add them back to the catalog. Nothing is dropped without you seeing it.

On the Verification page, the content inside each tab previously began
almost immediately below the tabs bar, which made the page feel cramped.
Each tab panel now carries the same top spacing as the content on other
tabbed dashboard pages, so the tabs and the panel content read as clearly
separated sections.

The Verification page tab now reads “Verification | Orbit”

Call details used to include a "Screen recordings" section on every recorded call, even when no desktop capture had been made—and for many teams there is no way to start one from the call console, so the section only ever showed an empty note.

Now the section appears only when at least one screen recording was captured for the call. Captured recordings still show everything you need for quality review and audits—length, sync with the call recording, consent basis, and retention—in both the full call page and the quick-look side panel. Calls without a capture simply no longer show the section.

The Event sources page under Developer now sets its browser tab title to "Developer | Event sources", the same section-first style used across the Developer area. Previously the tab showed the bare page name with the app suffix, which made it hard to pick out when you have several Orbit tabs open.

When you opened Developer → Connected Apps with the panel language set to Spanish, the page heading and surrounding copy translated, but the list of grantable permissions — each permission's name and its description, plus the role label and the consent-screen preview rows — stayed in English. Those entries are served by the OAuth scope catalog and the consent preview, which return English copy; the page rendered that copy directly instead of routing it through the translation catalog. The permission list now resolves each entry through the panel's locale, with the scope's identifier and a localized role label shown alongside, so the whole page reads in the selected language.

Telegram templates are not rendered when sending a message. The creation dialog now makes that limitation clear, and the Templates page no longer offers a test-send action for them. You can still manage existing Telegram template records while composing regular Telegram messages directly.

When you set up fallback channels on a new campaign, Voice is no longer a selectable option. If a chain ever advanced to a Voice entry, the follow-up send had no delivery path to run through and the message was marked as failed — leaving the recipient uncontacted with no warning at setup time. Voice now shows as "unavailable as a fallback" in the picker, and any existing campaign that already lists a Voice fallback row keeps that row visible but disabled so you can review and remove it.