Messages in Dapple let you communicate directly with individual creators from within a project. A message goes to one creator about one submission — use it for specific, personal communication like requesting additional information, clarifying a submission detail, or notifying a creator of a decision. For contacting multiple creators at once, use Bulk Message instead.
To send a message to a creator in Dapple, open the submission, click the Messages tab, click Compose, write your message (or pick a template), set whether you want to allow replies, and send. The creator gets an email notification with a link back into their Creator Account where the full message thread lives. Every message stays attached to the submission so context never gets lost.
How to send a message
Open the submission you want to message about.
Click the Messages tab — you'll see a chronological history of every message exchanged on this submission.
Click Compose.
Either write your message from scratch in the text field, or click Templates to pick from your saved message templates.
If you're using a template, edit it to fit this specific situation (the placeholders auto-fill with the creator's details).
Set Allow Replies on or off (see below).
Click Send.
Should I allow replies or not?
Allow Replies | When to use it |
On | Open a dialogue — feedback, clarification requests, anything that needs the creator to respond |
Off | Announcements or final decisions — declines, end-of-process notes, anything where you don't want an inbox of replies |
You can change this toggle at any time. Switching it off mid-thread closes future replies but doesn't delete existing ones.
Using message templates
Templates save time and keep your team's communication consistent. From Compose, click Templates to pick from your library. The subject and body auto-fill, and any merge tags (like /CreatorName) populate automatically. You can still edit the message before sending. Full setup: How to Create and Use Message Templates
What does the creator see?
They receive an email notification immediately.
The email contains a snippet of your message and a direct link to their Creator Account.
Clicking the link signs them into Dapple and opens the message thread.
Their reply (if you allowed replies) comes back into the same thread on the submission.
Can creators reply to messages?
Yes if you allow them to. If you toggle on the ability to reply, when a creator receives a message from Dapple, they can reply directly to the message through their Dapple account.
Can I use merge tags in a message?
Yes. Merge tags pull in dynamic data from the submission or creator profile. Commonly used merge tags:
Merge tag | What it inserts |
/OrganisationName | Your organisation's name (from Settings → Organisation) |
/OrganisationLogo | Your organisation's logo (from Settings → Organisation) |
/CreatorName | The name of the creator you're messaging |
/CreatorEmail | The creator's email address |
/CurrentDate | Today's date (in your organisation's time zone) |
/CurrentTime | Current time |
/MyName | Your name (the user sending the message) |
/MyEmail | Your email address |
See what merge tags are and how to use them for the full list.
Can I see if my message has been read?
Yes — you can see the read status of every message you've sent to a creator. Important: creators cannot see the read status of messages they send to you. This asymmetry is intentional — it means creators don't worry about whether you've seen their reply 'yet'.
Bulk messaging multiple creators
To send the same message to multiple creators in one go (e.g. notifying everyone in the Shortlist stage), use the bulk-message flow from the Submissions list. Full guide: How to Send a Bulk Message
What's the difference between a message and a bulk message?
| Message | Bulk Message |
Recipient | One creator | Multiple creators (filtered by stage, status, or tag) |
Context | Tied to a specific submission | Sent across all matching submissions |
Use when | The communication is specific to one submission or creator | You need to notify a group — shortlisted applicants, rejected creators, all entrants |
Merge tags | Supported | Supported |
Delivery | Immediate | Immediate |
When should I use a message rather than a bulk message?
Use a message when... | Use a bulk message when... |
You need more information from a specific creator | You're notifying all shortlisted creators of the next step |
You're confirming a specific submission detail | You're sending a rejection wave to a stage of creators |
The communication references something unique to that submission | The content is the same for everyone in a group |
You want to start a back-and-forth conversation | You're announcing a deadline or event to all applicants |
Is there a character limit for messages?
There is no hard character limit for individual messages. Keep messages concise — creators receive them as emails, and long messages are less likely to be read in full. For longer communications, consider linking to an external document rather than pasting content into the message body.
Creator Notification
After sending:
The creator will receive an email notification about your message
The email contains a direct link to log in to their account and view the message
Your message will be stored in the submission's message history for future reference
Remember that clear communication helps creators understand your feedback and expectations.
Best practice
Use templates for any message you send more than twice — keeps tone consistent and saves time.
Turn Allow Replies off on rejection / decline messages where a back-and-forth isn't useful.
Personalise template messages with at least one specific detail when the situation matters.
Keep messages short and scannable — most creators read on mobile.
Where to go next