Checking delivery status on sent SMS and prechecking line type

Charles Evans

09 Sep 2025 — 1 min read

We have made a couple changes to the way SMS works on the Token of Trust side. These updates improve the overall deliverability rate of our verification invitation system.

Prechecking SMS phone number line type before sending, and falling back to email

Right before we send a SMS message in our system, we first check what the line type of the phone number is (such as landline, voip, fixed, mobile). We are only going to attempt to try to send to mobile and voip, as the other two will not be able to receive SMS. We fall back to email verification when this is the case.

Listening to see if the SMS message actually got delivered

Once we send the SMS, we now listen for a callback from our SMS provider to let us know if the message actually got delivered to the intended place. Previously we were only checking if the message got properly queued to be sent, which caused issues such as the message being sent but then failing to deliver.

Read more

Approach: Improve Bot Discoverability with Search and Team Scoping

1. Global Bot Search Bar What: * Add a persistent search input at the top of the bot directory. * Search should match: * Bot name * Short description * Tags / keywords * Owner or team (optional enhancement) 2. Role-Based Bot Filtering What: * Automatically filter bots based on the user’s authenticated role, team, or department.

Browse & Search Licenses

Overview This deliverable introduces a searchable License List page within OpsConfig. The page allows operators to browse and locate licenses using substring search across key identifiers, while ensuring all sensitive data remains masked according to the ClientConfig API response rules. The feature is read-only and intended to support operational visibility

License Details (View‑Only)

Overview The License Details (View‑Only, Masked) feature provides operations users with a secure, read‑only view of license‑specific client configuration data. Configuration is fetched via the ClientConfig API and rendered exactly as returned, with all sensitive fields masked. No unmasking or editing capabilities are provided. Scope & Goals

How do you setup identity or age verification so that only certain locations need to get verified?

Answer: Use Location-Based Identity Verification. This is enabled via the locationRestrictions.requiresVerification attribute in your application configuration to define which countries and regions require verification. Summary Token of Trust now supports location-based verification requirements through the locationRestrictions configuration. This feature allows you to specify which geographic locations (countries and regions)