Skip to main content

​
Command palette walkthrough

The command palette gets you to any console in the Devotel Orbit dashboard without leaving the keyboard. One search box, opened from any page, reaches every hub, console, and settings page, and it also searches your live data: contacts, conversations, calls, numbers, segments, and agents. This guide maps what the palette reaches, the shortcut model behind it, and what an empty result means. For the server-side mechanics (ranking, partial failure, isolation), see Global search fan-out.

​
Open, navigate, close

The palette opens over the page you are on, and nothing changes underneath until you pick a result. Picking a result takes you to that console or record: the palette is destination navigation, not a data surface of its own (see Limits).

​
When a search returns nothing

The empty state, “No results found.”, has three causes worth telling apart:
  1. Nothing in your workspace matches. Live search is scoped to your organization’s data, so a record that lives in another workspace can never appear. Matching on live data is also prefix-anchored: mai finds “Main Street Logistics”, while a mid-word fragment like ain does not.
  2. The query is shorter than two characters. One-character queries are not sent. Type at least two characters before reading the result.
  3. A search backend degraded. When a pillar fails, the palette says so rather than pretending the data is absent: a quiet notice under the hits when some results did load, or a selectable retry row when nothing loaded. Select that row to run the search again.
If a term you expect still returns nothing, try the console’s own vocabulary. Rows match their visible label and their alias terms in your locale, so the right surface appears even where the translated label differs from the English one.

​
What the palette reaches

As you type, rows come from two places: records from your live data, and the built-in catalog of pages, actions, and settings below.

​
Your data

A name, number, or email queries your workspace through the unified search endpoint and returns ranked records: A selected record opens the same page you would reach through its console.

​
Audience consoles

​
Numbers consoles

​
Hubs and consoles

Deeper surfaces ride along under their hub: agent squads, model presets, prompt templates, and the knowledge base under AI; macros, social mentions, and coaching under Inbox.

​
Reading the result groups

Results group under headings, so you can always tell what a row is:
  • Recent shows the pages you opened last when the box is empty.
  • Suggested offers destinations inferred from your query.
  • The search group holds your live records.
  • actions starts a task instead of opening a list: Create Contact opens the contact create dialog, New Campaign lands on the campaign create page, and Buy Number, New Flow, View Invoices, View Logs, Manage API Keys, and Webhook Tester each open their flow directly.
  • navigation holds the hubs and consoles from the tables above.
  • settings holds the settings tree: Profile, General, Team, API Keys, Webhooks, Security, and the rest.
  • Help and Docs match in-app help articles and this documentation.

​
The keyboard shortcut model

Outside the palette, Orbit uses a two-key leader model in the GitHub and Linear style: press g, release, then press a letter. The sequence works from any page as long as focus is not in a text field and no dialog is open, and each binding appears as a badge on its palette row, so the palette doubles as the reference card for the chords. Two rules keep the model honest:
  • A destination whose mnemonic letter is already taken carries no chord. AI, Verification, and KPI Alerts are reached by typing their name in the palette, never by a chord that would advertise the wrong destination.
  • Every palette row shows the same translated label as the nav rail in every dashboard locale, so a chord you learn in one locale lands on the page your rail names in any other.

​
Where your searches land: Search Analytics

Every query you type is recorded under the global surface and shows up in Insights, under Search Analytics, beside the per-surface searches: top queries, zero-result terms, and click-through. When you open a live record from the palette, the click is attributed to the exact query you typed, so click-through reflects what operators actually opened. Use the dashboard to spot the terms your team types and the ones that return nothing, then decide whether a rename, an alias, or a training note fixes them. See Read Search Analytics for the panels and Global search fan-out for what gets recorded.

​
A first morning with the palette

  1. Press Ctrl+K and type churn. The Audience consoles Churn risk and Propensity segments surface, because their labels and alias terms (retention, propensity, lifetime value) match. Press Enter on Propensity segments to open /audience/propensity-segments.
  2. Press Ctrl+K again and type short. SMS Short Codes appears. Enter opens /numbers/short-codes.
  3. For the consoles you open every day, skip the palette: press g then n from any page to land on Numbers.

​
Limits

  • The palette navigates; it does not export. There is no CSV out of the search box. Export lives in each console: conversation export in Interactions, audience export in Audience, billing records in Billing.
  • Live results are capped per pillar. A query returns at most a handful of records per pillar (five by default, ten at most), so a common prefix shows the strongest matches rather than every row. For the full list, open the console and use its filters.
  • Matching is prefix-anchored. Mid-word fragments do not match live data.
  • Two characters minimum. Shorter queries are not sent.

​
See also