Tie inbound calls to a resolved identity and feed them into analytics — measure the channel that usually goes dark.
Inbound Call → Analytics turns inbound phone calls into resolved identities in your analytics in real time. It runs as two infrastructure products in sequence: User from Call captures the caller's number and resolves it to a known identity, then User to Analytics writes the resolved identity into your analytics.
Each product runs its own resolution and draws on the data it needs, so a resolved caller produces several metered events. You're billed only on OK results — Ingesting, Graphing, and Decisioning are included, and you pay on egress, per event, for what activates.
You activate Products — the IaaS lines below. The DaaS lookups each Product triggers are included with it; they're listed here so the full cost is visible.
| ProductID | Product | Type | UsageID | Usage | OK status |
|---|---|---|---|---|---|
| 8020 | User from Call | IaaS | 881 | Action Call | Success |
| 8104 | User to Analytics | IaaS | 1041 | Use Case Analytics | Success |
You switch on Products — the IaaS lines. The DaaS lookups they trigger come bundled; there's nothing separate to activate.
DaaS rates appear so the full cost is visible. On direct API access, where Products aren't bundled, the same rates apply à la carte.
A call bills only on an OK outcome — Success for a Product event, Match when a lookup returns data. No Match and Exception aren't charged. How pricing works →
We'll map it to your stack and the usage you'd expect.