Skip to main content

​
Welcome to Orbit by Devotel

Orbit is the Agentic Customer Communication (ACC) platform — CPaaS, CCaaS, AI agents, and a customer data layer behind one API and one dashboard. You send and receive on sixteen channels, automate the journeys between them, and pay for it from the same wallet. This page orients you: what the platform does end to end, which docs group covers which job, and where to start depending on how you work.

​
What Orbit does

For API-first teams, the shortest path through the platform looks like this:
  1. Get a sandbox key in Settings > API keys. Test keys (dv_test_sk_ prefix) work immediately — no carrier registrations, no approval queue.
  2. Send from the sandbox. Every channel shares one endpoint shape: POST /messages/<channel> for SMS, email, WhatsApp, RCS, Viber, and the rest. Sandbox sends are simulated and free. Voice uses POST /voice/calls with a per-call DSL you control.
  3. Read delivery status. Poll the message record or subscribe to webhooks signed with HMAC-SHA256.
  4. Provision a number and register your sender identities — US 10DLC, sender IDs, and India DLT each have their own pipeline under Numbers.
  5. Go live. Swap to a dv_live_sk_ key after the go-live checklist, and real traffic bills against your wallet.
For support and CX teams, the same building blocks run the other direction: inbound messages and calls land in the shared inbox and team chat, AI agents answer or route them, and every touchpoint rolls up into a single customer profile (CDP) your campaigns and flows can target.

​
Surface map

​
Choose your path

Two ways in, same platform underneath.

API-first

Send your first message in five minutes, then read the API reference and pick up an SDK. Every dashboard action has an equivalent endpoint.

Dashboard-first

Sign up, create a test API key under Settings > API keys, and watch sandbox sends in the delivery log before you write a line of code.

​
Get unstuck

If a send, a call, or a webhook is not doing what you expect, do not guess from the front door. The Troubleshooting Hub collects the failure modes readers actually hit — undelivered messages, signature failures, SMPP status codes — each with the check to run first. Route-map the incident against the operator observability map, which shows which surface (delivery log, webhook event, analytics) tells you what.

​
Vocabulary

The Glossary defines every term the platform throws at you, with Orbit-specific behavior attached. Three you’ll meet in your first hour:
  • DLR — the delivery receipt a carrier returns after you submit a message. Until it lands, your message sits in submitted_no_receipt.
  • Inbox — the shared workspace where inbound messages and calls land, whether a human, an agent, or a flow answers them.
  • CDP — the customer data platform: one profile per contact that your campaigns, segments, and agents all read from and write to.

​
What’s new

Every platform change — new endpoints, breaking API changes, deprecations, dashboard updates — lands on the Changelog, which points you at the canonical, always-current release history. Scan it before you upgrade a dependency or wonder why a response shape moved.

​
Where the sandbox lives

The Sandbox is the zero-cost proving ground: simulated sends, no carrier registrations, no approval queue. Your key tells you which world you’re in — dv_test_sk_* keys route to the sandbox gate and bill nothing; dv_live_sk_* keys send real traffic and bill the wallet. Before you swap prefixes, walk the go-live checklist: test key minted, delivery log reviewed, sender identities registered. Orbit gives you tenant-owned compliance controls; the obligations behind them stay yours. Country and sender registration requirements, consent capture, opt-out handling, quiet hours, and recording-consent rules are all documented per jurisdiction under Compliance — including opt-out suppression and the country requirement matrices. Legal indexes the public legal surfaces and the attribution notices. Read these before your first live send, not after your first carrier block.

​
Where to go next