Fresh vs cached verification results
Not every check needs to hit the upstream provider again. Understanding freshness saves money and keeps results fast.
What a cache hit is
When a record was verified recently and the result is still within the service TTL, phoneveriflo can serve the stored result instead of submitting a new request. Cache results are stored encrypted, keyed per tenant, and every result carries freshness metadata (checked_at, fresh_until).
What a fresh check is
A record that has never been verified, whose cached result expired, or that you explicitly need re-checked is submitted for new processing. Only fresh checks consume upstream capacity.
How you pay
Your preflight separates the list into duplicates, invalid rows, cache hits, and fresh checks — then freezes a quote with per-tier fresh and cache prices. You approve that quote; the worker bills only what actually ran, at the frozen prices. A queue delay that expires a cached row never raises your bill: it is re-checked fresh but still billed at the frozen cache price.
Choosing a service TTL
Services define a cache TTL (capped at 90 days, configurable by your workspace). High-churn data — signup checks, activity signals — deserves short TTLs; stable data like carrier line type can be cached longer.