> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orbit.devotel.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Evaluating call-tracking alternatives

> A tenant-owned checklist for scoring call-tracking vendors (CallRail, Invoca, Devotel Orbit) on number ownership, attribution, and consent, plus the FAQ on when not to move.

# Evaluating call-tracking alternatives

Call-tracking evaluations come down to one question: who owns the attribution pipeline. This page gives you the checklist that separates a rented vendor pool from tenant-held DIDs, parity rows for CallRail and Invoca against Devotel Orbit, and an FAQ for deciding when a move is not worth making.

## 1. The gaps buyers hit first

* **Self-serve numbers.** Can you provision inbound DIDs per source and campaign yourself, from your own account, without a vendor ticket?
* **Insights dashboards.** Does per-source call attribution live in the same account as your SMS, voice, and agent analytics, or in a separate silo?
* **Org-owned attribution ladders.** Can you show an auditor how each number maps to its source, with a consent record, using objects in the organization's own account?

Orbit closes these gaps with three tenant-owned surfaces: the coverage catalog for self-serve inbound DIDs ([Buy numbers](/guides/buy-numbers)), the [Call tracking & DNI](/guides/call-tracking-dni) guide for pools and attribution, and the [Compliance](/compliance/opt-out-suppression) surfaces for consent and quiet-hours gates.

## 2. Tenant-owned checklist

Score every candidate on the shortlist (CallRail, Invoca, Orbit, or the rest) against these rows: number ownership, source mapping, read-side attribution, consent posture, channel adjacency, and auditability. A seller passes when the answer is "in your account," not "behind our dashboard."

* **Number ownership.** Tenant-held inbound DIDs you can port, not a vendor-rented pool.
* **Source mapping.** Pool configuration in the organization's own account, exportable, not a vendor-side setting.
* **Read-side attribution.** Rollups resolved from tenant objects at read time, not baked vendor reports.
* **Consent posture.** Per-pool tenant-controlled recording consent, not vendor policy.
* **Channel adjacency.** Tracking pools on the same account as the numbers and voice they attribute, not separate procurement per channel.
* **Auditability.** API export of pool configuration and assignments, not support tickets.

## 3. Sellers of call tracking vs Orbit: parity and divergence

| Seller        | Number inventory                | Attribution model                   | Consent posture        | Posture                  |
| ------------- | ------------------------------- | ----------------------------------- | ---------------------- | ------------------------ |
| CallRail      | Rented from CallRail's pool     | Vendor-side mapping and reports     | Vendor-managed         | Diverges on ownership    |
| Invoca        | Rented from Invoca's pool       | Conversation analytics plus reports | Vendor-managed         | Diverges on ownership    |
| Devotel Orbit | Tenant-provisioned inbound DIDs | Pool-config-owned, resolved at read | Tenant-owned, per pool | Tenant-owned attribution |

## 4. Adoption playbook

Follow the [Call tracking & DNI](/guides/call-tracking-dni) guide end to end: create one pool per source, assign tenant-held DIDs, wire the DNI resolve snippet on your site, set per-pool consent posture, and verify the attribution read under Insights against a test call per DID. Constraints and quotas are in the [Tracking pools & DNI](/guides/tracking-pools-dni) guide.

## 5. When NOT to move (FAQ)

**Should we move away from CallRail or Invoca?**
Not if the program is small and static, marketing is the only consumer, the rented pool's contract beats the cost of a DID inventory at your volume, or no audit will ever ask for chain-of-custody. Run the checklist above; it exists so a vague "we should own this" feeling does not turn into a migration.

**Do we have to give up the incumbent tool while we evaluate?**
No. Tracking pools are additive: provision tenant-held DIDs, run them alongside the incumbent, and retire the old pool only if the checklist confirms ownership has moved.

## Related references

* [Call tracking & dynamic number insertion (DNI)](/guides/call-tracking-dni)
* [Tracking pools & DNI (constraints and quotas)](/guides/tracking-pools-dni)
* [Buy numbers](/guides/buy-numbers)
* [Compliance (opt-out & suppression)](/compliance/opt-out-suppression)