Match inbound callers to verified postal addresses for follow-up direct mail — no form, no friction.
Inbound Call → Postal turns inbound phone calls into verified postal addresses 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 Postal resolves the identity to a verified postal address.
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 |
| 8111 | User to Postal | IaaS | 1111 | Use Case Postal | Success |
| DaaS | 557 | ↳ Phone to DPV | Match | ||
| DaaS | 542 | ↳ Address to DPV | Match | ||
| DaaS | 552 | ↳ Email to DPV | Match | ||
| DaaS | 575 | ↳ Hash Email to DPV | Match | ||
| DaaS | 554 | ↳ Email to Name | Match | ||
| DaaS | 559 | ↳ Phone to Name | Match | ||
| DaaS | 562 | ↳ Address to Name | Match | ||
| DaaS | 577 | ↳ Hash Email to Name | Match |
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.