SignedXVerification Message Bindings
Personalise the email and SMS sent when you create an identity verification request.
When creating an identity verification request, the email message and
SMS message support placeholders (bindings) written as {{binding_name}}.
SignedX replaces each placeholder with the recipient's or sender's actual
details when the request is sent, so a single message personalises for every
recipient — addressing them by first name, including your business name, and so
on.
How bindings work
A verification request has two customisable message fields:
- Email message — the body text of the verification email
- SMS message — the text sent when you deliver the request by mobile with a link
Placeholders resolve from the recipient's details (name, email, mobile) and from the sending account. While you are composing the message, placeholders display exactly as typed; they are replaced with real values at send time. Placeholders must match the exact format shown, with no interior spacing.
Placeholders for email messages
| Binding | Inserts |
|---|---|
{{name}} | Full name of the individual |
{{first_name}} | First name of the individual (first word) |
{{last_name}} | Last name of the individual (remaining words) |
{{email}} | Email address of the individual |
{{mobile}} | Mobile number of the individual |
{{sender_name}} | Name of the sender |
{{sender_email}} | Email address of the sender |
{{sender_number}} | Contact number of the sender |
{{sender_business}} | Business name of the sender's organisation or group |
For example:
Hi {{first_name}},
{{sender_business}} has requested an identity verification. The process takes a
few minutes, and is conducted by SignedX on behalf of {{sender_business}}.
Please click start verification below to begin.Line breaks in the email message are preserved. Sender placeholders resolve
from the requesting account's details. You do not need a {{token}}
placeholder in the email message — a Start verification button is
always included automatically.
Placeholders for SMS messages
SMS messages support the same recipient and sender bindings, plus {{token}}
for the verification link. {{mobile}} is not available, because the SMS is
already sent to that number.
| Binding | Inserts |
|---|---|
{{name}} | Full name of the individual |
{{first_name}} | First name of the individual (first word) |
{{last_name}} | Last name of the individual (remaining words) |
{{email}} | Email address of the individual |
{{sender_name}} | Name of the sender |
{{sender_email}} | Email address of the sender |
{{sender_number}} | Contact number of the sender |
{{sender_business}} | Business name of the sender's organisation or group |
{{token}} | A shortened link to start the verification (SMS only) |
For example:
{{sender_business}} has requested an identity verification. This takes a few
minutes - start here: {{token}}The verification link placeholder appears literally while you compose the message and is converted to a shortened link when the SMS is sent. It is not used when the request is delivered as a one-time passcode (OTP) instead of a link.
Sending on behalf of a group
Sender placeholders ({{sender_name}}, {{sender_business}}, and the rest)
resolve from the account sending the request. When you use Send on behalf
of to send as a group, SignedX substitutes that group's configured branding
where it is available.