How do verification reminder emails work? When do they get send and how frequently?

darrin

08 Jan 2026 — 1 min read

When a consumer starts Token of Trust verification but does not finish, Token of Trust can send reminder emails to prompt them to complete verification.

By default, reminders follow a fixed schedule and are not otherwise configurable at this time.

FAQ

How many reminder emails are sent, and when?

Two reminders total:

First reminder: 1 hour after the consumer fails to complete verification.
Second reminder: 1 additional hour later (2 hours after the first point above).

After the second reminder, we stop sending reminders.

Can we change the reminder timing or number of reminders?

Not currently. The reminder schedule is fixed.

Can a client turn reminders off?

Yes. Reminders can be disabled per apiClient.

What controls whether reminders are sent?

options.emailUntilVerified (boolean) on the apiClient.

enabled: (the default) reminders are queued automatically (per the fixed schedule above).
disabled (or missing): reminder flow short-circuits and no reminder emails are sent.

What happens internally when `options.emailUntilVerified` is disabled?

The reminder branch short-circuits:

We skip generating the “resume” URL.
We do not tag the Mailchimp list with emailUntilVerified.
The follow-up send path does not fire.

When enabled, those reminders are queued automatically.

Where is this implemented in code?

The flag is retrieved in multiple places. One known reference:

website/modules/steps/sendFinalReviewStatus/sendFinalReviewStatus-routes.node.js (lines 530–610)

This flag tells review workflows whether we keep sending reminder emails until the end user completes verification.

Quick troubleshooting

A client says “users aren’t getting reminders”

Check:

The apiClient has options.emailUntilVerified set to enabled or has no setting (this is the default).
The consumer actually started verification but did not complete it.
Enough time has passed for the 1-hour and 2-hour reminders.

A client says “stop emailing our customers”

Action:

Set options.emailUntilVerified = disabled for that apiClient.

Notes / limitations

Reminders are only on/off today (no custom cadence, no custom count).
Maximum reminders sent per verification attempt: 2.

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)

FAQ