Send a verification invite

When you start a verification, the console queues a branded invite automatically. This page covers resending, customizing, and tracking it.

Send the invite email

The first invite is sent inline with verification creation. The message is composed from the workflow template’s messaging.invite copy, branded with the snapshot’s effective branding, and queued in the same transaction that wrote the verification record.

The applicant receives a greeting, a CTA button that opens their invite link, and an expiry line.

Automatic reminders

If an applicant is invited by email but does not finish, Checktiv can send automatic follow-up reminders on a cadence you choose. Reminders only go to applicants who still have a step to complete: as soon as the applicant finishes their part, or the verification moves to review, expires, or is canceled, reminders stop on their own.

Reminders are an organization-wide setting. They apply to every verification created with the email invite enabled, whether you create it from the console, the API, a bulk CSV import, or a connected integration. An applicant you reach only by sharing the link directly is never reminded, because there is no invited email on file.

Turn reminders on

Go to Settings, open your Organization page, and find the Applicant reminders section. Switch reminders on and choose a cadence:

• One reminder after 2 days - a single gentle follow-up.
• Two reminders, about 1 day and 2 days after invite - the default.
• Three reminders, starting about half a day after invite - the most active cadence.

The choice applies to all of your verifications at once; there is no per-verification or per-workflow-template override.

How the schedule behaves

• The times above are measured from your latest contact with the applicant, starting with the invite. A manual Re-send invite resets that clock, so the next reminder moves out instead of stacking on top of it.
• Reminders stop once the verification itself has expired (they are never sent past the verification’s own deadline).
• Every reminder gives the applicant a working link: if their invite link has lapsed, the reminder refreshes it automatically, so they never land on a dead link.
• Reminders show up in the applicant’s activity feed and the Email log, next to the original invite.

Copy the invite link

On the new applicant response panel and on the applicant detail page, the applicant URL is shown alongside a QR code. The link points at the verify app’s /v/<code>?o=<otl> resolver; see How an invite link works for what the applicant has to do.

Share the link through any channel you trust. The link is single-use, so the first human click consumes it; see troubleshooting below if a resend lands on “link expired”.

Customize the invite message

You can customize invite copy at two levels:

• Per-workflow-template (durable). Edit the workflow template’s invite subject and body in the workflow template editor. New verifications inherit the new copy. See Create a workflow template.
• Per-send (one-off). The new applicant form has optional “Customize invite email” fields that override the workflow template copy for one send.

When per-send fields are blank, the send falls back to the workflow template’s messaging.invite. When the workflow template has none, it falls back to the platform default copy.

Resend or revoke

Open the applicant detail page and click Send invite (Re-send invite once an invite has been sent or attempted). The endpoint:

• Re-derives the recipient by decrypting the stored email envelope. You cannot pass a different address.
• Reuses the existing invite link if it is still valid; otherwise generates a fresh one inline.
• Refuses the send if the verification has already reached completed, awaiting_review, processing, expired, or cancelled (session_finished).
• Refuses the send while the verification is paused because the account balance could not pay for its next check (session_parked). The message names the next step: add funds in Billing, or follow the steps there for a frozen or locked wallet. The verification then resumes automatically, and you can send the invite. See Payment required for the one paused verification that does not resume.

Two anti-spam guards apply:

• Cooldown. A resend within 60 seconds of the previous send is rejected as rate_limited.
• Daily cap. Five invite attempts per verification in any rolling 24 hours, counting the first invite, whether or not each was delivered. A send over the cap is also rejected as rate_limited, and its message says the limit lifts as those attempts pass 24 hours old. In the meantime, if the detail page shows the link, copy it or its QR code and share it directly; if the link was already used or has expired, generate a new link first.

To revoke an outstanding invite, cancel the verification (which finishes it and rejects further sends). To invalidate an unclicked link without cancelling, regenerate the link from the detail page.

Check the email log

Delivery signals are surfaced on the applicant detail page and in the activity feed. A dedicated Email log lists every outbound email by workflow template, status, and timestamp.

Troubleshooting

• “Link expired” on first click. The invite link is valid for 24 hours from issue. Ask the applicant to self-service on the expired page, or resend.
• Email never arrives. Check the activity feed for kyc.invite.sent. If present, ask the applicant to check spam.
• no_recipient on resend. The verification has no email address on file. Cancel and recreate with one, or share the applicant URL directly.
• Reminders not going out. Automatic reminders only apply when they are switched on in Settings > Organization > Applicant reminders, the verification was invited by email, and the applicant has not finished yet. They also stop once the verification itself has expired.