Five releases shipped this week: the contact PII vault gains a dashboard console so tokenizing an identifier no longer needs a script, the numbers lookup console now returns a fraud-score verdict in one click, the knowledge-gap miner suggests how to close each gap it reports, a live call can capture a card payment over a masked keypad end to end, and the smart-send API arms a real per-message fallback chain. Each is live today; the sections below are the operator version of the week's changelog entries.
What shipped this week
Tokenize and recover contact PII from the dashboard
The PII vault has answered API calls for a while, but an ad-hoc batch meant scripting the endpoints server-to-server. Integrations > CDP gains a PII vault tab with two flows. Tokenize converts emails, phone numbers, SSNs, or national IDs into deterministic tokens scoped to your account — the same value always maps to the same token, so records for one person collapse to a single key you can segment and activate on while the cleartext stays out of downstream audiences. Detokenize opens the sealed envelopes back to the original value when you genuinely need it; that path is restricted to owner and admin roles, and every call is recorded by counts only — never the identifiers, tokens, or envelopes. Route: dashboard → integrations → cdp. Docs: PII vault.
Score a number's fraud risk from the lookup console
POST /numbers/lookup/trust-package fused the carrier dips into one verdict, but until now you had to wire it yourself. The Numbers → Lookup console carries a Trust & risk package card: enter an E.164 number, hit Score, and get back a 0–100 fraud score with a decision — allow, review, or deny — plus the underlying signal rows (line-type, SIM-swap date, reachability, roaming, optional carrier reputation) and the machine-readable reasons. The query is billed once through the existing lookup channel, and when individual carrier dips do not answer, the card shows a "No signal" amber state instead of a misleading green. Route: dashboard → numbers → lookup. API: numbers/lookup.
The knowledge-gap miner now tells you how both kinds of gap close
The Knowledge Gap Report and the per-agent Knowledge gap miner already clustered the questions your AI agent could not answer, and left you to guess the remedy. Each cluster now shows a suggestion chip computed from its own evidence: a cluster whose conversations escalated to a human is a missing topic, tagged "suggested: add article"; a cluster that only triggered low-confidence phrasing is a response-quality gap, tagged "suggested: add exemplar"; both tags appear when the evidence carries both. Hover the chip for the one-line reason. The one-click draft-article flow is unchanged. Route: dashboard → agents → <agent> → knowledge. Docs: Knowledge gap miner guide.
Take a card payment mid-call over a masked keypad
A caller who wants to pay by card on a phone call cannot click a hosted link, and reading card numbers out loud defeats the purpose. The secure-payment loop is now complete end to end: the agent starts a session from Voice → Your call → Take Payment, the platform pauses SIPREC recording and masks the caller's keypad tones for the capture window, and the payment provider tokenizes the card while Orbit stores a masked summary — last four digits, brand, an opaque token reference. On completion or cancel, recording resumes and the keypad unmasks. A submit that offers a full card number where last-four belongs returns a validation error at the API edge instead of touching the call. Route: dashboard → voice → your call. Docs: Secure payment capture.
Arm a real fallback chain per message on smart-send
POST /messages/smart-send picked the best channel and left the router's ranking unused — a terminal undelivered DLR stopped at the first channel. A new optional cascade_policy object on POST /messages/smart-send and POST /messages/route-preview wires the chain back in: declare fallback_channels (say ["whatsapp", "viber", "sms"]), suppress fallback with auto_fallback: false, or pass segment hints to use the learned per-segment cascade ranking. The caller's explicit order wins over the router default, and channels that make no fallback sense (voice, fax) are filtered off at the edge. Route-preview returns the resolved chain so a dashboard can show exactly what a terminal DLR will escalate through. API: messages/smart-send.
Operator takeaways
Three actions are worth the minutes they take this week.
- Tokenize the identifiers you pass downstream. Open Integrations > CDP → PII vault, tokenize emails and phone numbers before they reach a downstream audience, and restrict envelope recovery to owner/admin — the sealed envelope is the audit-clean way back to cleartext when you genuinely need it.
- Run the trust card on a risky-looking inbound before calling back. Paste the number into the Numbers → Lookup Trust & risk card; the 0–100 score plus the SIM-swap and roaming rows read faster than five separate dips, and the amber "No signal" state tells you when the carriers answered nothing.
- Test the suggestion chip on your three biggest gaps. In Agents → Knowledge gap miner, open the largest cluster and follow the chip — add the article when the topic is missing, add a QA-approved exemplar when the phrasing is weak. Close the biggest chip every week and the report shrinks on its own.
Where this shows up
All five ship this week and are live now:
- Integrations > CDP → PII vault — tokenize and detokenize from the browser.
- Numbers → Lookup — the Trust & risk package card.
- Agents → <agent> → knowledge — suggestion chips on every knowledge-gap cluster.
- Voice → Your call → Take Payment — the complete secure-payment loop.
- API → messages/smart-send —
cascade_policyon smart-send and route-preview.
The canonical release history stays at orbit.devotel.io/en/changelog — the entries above mirror the week's publish there.