Message templates let you reuse the same message across many clients — and Liquid variables make each copy personal. Write Hi {{ first_user_first_name }}, once, and every client receives a greeting with their own name.
How it works
Variables live in your template's title and message body, wrapped in double curly braces. When you use the template to message a client, Fidu replaces each variable with that client's information at the moment the message is created.
Hi {{ first_user_first_name }},
Thanks for signing on with us! You can log in to your client portal
any time here: {{ login_link }}
We look forward to working with {{ client_name }}.
The Insert Data link on the message template editor lists every available variable — copy from there rather than typing them by hand.
Available variables
About the client
Variable | Prints |
| The client's display name ( |
| The client's legal name |
| The client's email address |
| The client's phone number |
| The client's description |
| Street address, line 1 |
| Street address, line 2 |
| City |
| State or province |
| Country |
| Postal or ZIP code ( |
About the client's first contact
These refer to the first person attached to the client record.
Variable | Prints |
| First name |
| Last name |
| Full name ( |
| Email address |
| Title |
| Phone number |
Portal link
Variable | Prints |
| Your client portal's web address, as plain text |
| The same address as a ready-made clickable link |
Use {{ login_link }} in message bodies so clients can click straight through; use {{ login_url }} when you want to control the link text or show the bare address.
Good to know
Missing information prints as blank. If a client has no phone number on file,
{{ client_phone }}simply prints nothing. Phrase sentences so a blank won't read oddly, or keep such variables out of templates used broadly.Variables fill in when the message is created. Updating a client's record later doesn't change messages already sent.
A misspelled variable prints as blank, and if the braces themselves are malformed the message goes out with the placeholders unfilled rather than failing — so proofread the first message you send with a new template.
