When you send an identity verification request, the email and SMS are often the first thing the individual sees. Personalising those messages — greeting them by name, using your organisation or group’s business name — makes the request look legitimate and easier to act on.
Use the same placeholder in every request and let the wording adapt to each person — for example, greeting them by first name or including your organisation name automatically.
Each verification request has two message fields: Email message (the body of the request email) and SMS message (the text sent to the individual’s mobile when you choose Use mobile number to send the request with a link).
Both fields support placeholders written as {{binding_name}}. We replace them with real values when the notification is sent, using the individual’s details and the sender details of the account sending the request — including organisation or group branding when Send on behalf of is set.
While you compose or preview a request, placeholders appear exactly as you typed them. They are replaced when the email and SMS are created at send time.
Notes: Write placeholders exactly as shown below, with no spaces inside the curly braces. {{token}} is especially strict — if it is missing or mistyped, we will not insert a start link in the SMS.
Use these in the Email message field when creating a verification request.
Binding | Inserts |
|---|---|
| Full name of the individual |
| First name of the individual (first word of their full name) |
| Last name of the individual (the remaining words after the first) |
| Email address of the individual |
| Mobile number of the individual |
| Name of the sender |
| Email address of the sender |
| Contact number of the sender |
| Business name of the sender's organisation or group |
Example email message:
Hi {{first_name}},
{{sender_business}} has requested an identity verification. The process takes a few minutes, and is conducted by Annature on behalf of {{sender_business}}.
Please click start verification below to begin.
You do not need {{token}} in the email. We always include a Start verification button (and a backup link) in the email, separate from the message you write.
Notes: Line breaks in the email message are kept in the sent email. Sender details come from the account sending the request. If an administrator selects Send on behalf of a group, we use that group’s branding where it is configured (business name, email, and contact number).
Use these in the SMS message field when Use mobile number to send the request with a link is selected.
Binding | Inserts |
|---|---|
| Full name of the individual |
| First name of the individual (first word of their full name) |
| Last name of the individual (remaining words after the first) |
| Email address of the individual |
| Name of the sender |
| Email address of the sender |
| Contact number of the sender |
| Business name of the sender's organisation or group |
| A shortened link to start the verification on their phone |
{{token}} is the binding that inserts the start link. Include it wherever you want that link to appear in the SMS — usually at the end of the message. If you do not include {{token}}, we will not send a link, and the individual will need to start the request from the email they receive.
Example SMS message:
{{sender_business}} has requested an identity verification. This takes a few minutes - start here: {{token}}
Notes: {{token}} is SMS only. In previews it appears as typed; at send time we replace it with a shortened verification link. If you choose Use mobile number for two-factor authentication (OTP), the SMS message field is not used. The individual receives a one-time code instead of a verification link.
Sender placeholders ({{sender_name}}, {{sender_email}}, {{sender_number}}, and {{sender_business}}) are taken from the account sending the request and your organisation settings.
When Send on behalf of a group is selected, we use that group’s configured branding where it is available — for example, the group business name instead of the organisation name. The sender’s own name still comes from the account sending the request.
