Message templates in Dapple are reusable email patterns you create once and use repeatedly when messaging creators. Set them up in Settings → Message Templates, give each one a name, subject, and body with merge tags for personalisation, then pick from them anywhere you compose a message. Templates save time, keep team tone consistent, and let you send personalised bulk messages at scale.
Why use templates?
Benefit | Why it matters |
Time efficiency | Instead of writing similar emails over and over, pick a template and tweak. |
Team consistency | All team members communicate in the same tone, style, and structure — important for brand and creator trust. |
Personalisation at scale | Merge tags (/CreatorName, /OrganisationName) auto-fill each recipient's details, so bulk messages still feel personal. |
Bulk-message ready | You can't reasonably bulk-message without templates. Templates make 50-creator sends as easy as 1-creator sends. |
Audit trail | Standardised messages are easier to review for legal/compliance and easier to update across the team. |
How to create a message template
Open Settings → Organisation Settings.
Open the Message Templates tab — you'll see your existing templates.
Click Add a new template.
Name the template descriptively — e.g. 'Submission Accepted', 'Shortlist Notification', 'Additional Info Request'.
Set the subject line. Keep it clear, concise, and specific.
Write the message body.
Add merge tags for personalisation — type / to bring up the available tags (/CreatorName, /CreatorEmail, /OrganisationName, /MyName, etc.).
Review and save.
How to use a template when sending
Open the submission → Messages tab → Compose.
Click Templates to see your library.
Pick the template you want.
The subject and body auto-fill. Merge tags replace with the actual creator's details.
Edit anything that needs tweaking for this specific creator.
Set Allow Replies as needed.
Send.
Available merge tags
Merge tags personalise templated messages with creator and organisation details. Common ones:
/CreatorName — the creator's name
/CreatorEmail — their email
/OrganisationName — your organisation's name (from Settings → Organisation)
/MyName — your own name (the sender)
/MyEmail — your own email
/CurrentDate — today's date
/CurrentTime — current time
Full merge tag reference: What Are Merge Tags and How to Use Them
Templates we recommend setting up first
Template name | When you'll use it |
Submission received | Sent automatically (via Stage Automation) when a new submission lands. Confirms receipt. |
Longlist / Shortlist notification | Sent when a creator advances. Often used in bulk after a review cycle. |
Rejection / Not selected | Sent when a creator is declined. Short, kind, sign off cleanly. Turn off Allow Replies. |
Additional information request | Sent when you need the creator to clarify or provide more material. |
Payment request | If you handle post-submission fees or follow-on costs. |
Reminder to complete | For draft reminders, sent when a creator started but didn't finish. |
Tips for writing good templates
Keep it scannable — short paragraphs, clear next step. Most creators read on mobile.
Use the creator's name early (via /CreatorName) — instantly feels less templated.
End with a clear action — 'Reply here', 'Click here to see your submission', 'No further action needed'.
Review and refresh templates once a year — keep tone and language current.
Don't add the organisation logo as a merge tag if your logo is already set in Settings → Organisation. Both will render in the email and look broken.
Where to go next