Skip to main content

​
Evaluating alternatives

Readers choosing a vendor land on evaluation content before integration content. This hub is the organized entry point for every alternatives page in docs: each one scores the candidates on the same tenant-owned checklist, so you can compare pages to each other, not just vendors to vendors.

​
Why this hub exists

A decision-stage reader does not start with a quickstart; they start with “is this vendor ours?” Scattering that material across unrelated guides strands the reader. The hub exists so every alternatives page is one link away from every other, and the scoring format stays uniform as the catalog grows.

​
Checklists already in docs

  • Evaluating call-tracking alternatives — scores call-tracking vendors (CallRail, Invoca, Devotel Orbit) on number ownership, attribution, and consent; starts from the gaps buyers hit first.
Add pages here as they ship. A checklist page belongs in this hub from the day it lands, not after the next survey.

​
The tenant-owned checklist format

Every alternatives page scores the candidates on the same axes, so the field stays comparable across pages:
  • Number ownership — tenant-held inventory you can port, not a vendor-rented pool.
  • Attribution ownership — mapping and rollups resolved from objects in your own account.
  • Consent posture — per-workspace consent controls you own, not a vendor policy.
  • Auditability — API export of configuration and assignments, not support tickets.
Keep the shape consistent across new pages; a reader who has done one checklist should be able to run the next without re-reading the format.

​
Comparison pages on the marketing site

For narrative comparisons — pricing anecdotes, per-vendor position papers, and per-archetype round-ups — the marketing site carries the compare surface: In-depth brand pages (Devotel Orbit versus Twilio, Sinch, Vonage, Telnyx, Plivo, Infobip, MessageBird, and the rest) resolve under /compare/<vendor> — the Evaluating call-tracking alternatives page’s parity table is the same checklist applied to its own shortlist.

​
When not to migrate — the FAQ convention

Every alternatives page ends with a “when NOT to move” FAQ, not a CTA. The checklist exists so a vague “we should own this” feeling does not turn into a migration; keep the FAQ in the same tone — it tells the reader when the incumbent is right, which is what makes the rest of the page credible.