Use email placeholders safely
Insert placeholders in templates, assign the template to the right scenario and avoid visible raw placeholders
→ Open email templates in SimpliServ
Placeholders like {{customer.name}} are replaced with data from the current context when the email is sent. A template sent from a contact does not automatically know the fields of an invoice or a ticket.
Context first
Contact
Name, email and contact details, if maintained on the customer.
Ticket/order
Order number, status, device or custom ticket fields only if the email is sent from the matching record.
Invoice/proposal
Number, amount, due date and public links only in the right document context.
Safe workflow
Assign the scenario
Under Template assignments you define which template applies to which scenario (e.g. invoice, proposal, 1st dunning notice, appointment invitation). Without an assignment, Use default template applies, i.e. the system template. A fitting template name alone is not enough.
Use the picker
In the template dialog you insert placeholders via Placeholders into the subject, body or custom HTML. The picker shows all available placeholders, not just those of the scenario. So check yourself that the placeholder fits the context, and don't type paths by hand.
Test with complete data
Create a test contact and document with phone number, address, amount and optional fields, and open the email from there. The send dialog already shows subject and message filled with real values.
Decide on empty values
What should happen when a field is empty? Phrase the text so it still reads well without the value, or make the field mandatory on the customer. Never send an email with a visible raw placeholder.
Treat URL and payment placeholders as confidential. Don't copy example or test links into a production template.
Symptoms
{{...}}stays visible → placeholder unknown, misspelled or in the wrong context. SimpliServ leaves placeholders it cannot resolve unchanged.- Field empty → the record has no value.
- Wrong value → contact or record mixed up.
- Invalid link → template used outside the intended send action.
Related topics
How is this guide?