Reply Types
Choose the right message type for every situation. Understanding when to use public replies versus internal notes is essential for effective support.
Public Replies
What They Are
Public replies are messages sent to the customer. They're visible in the conversation thread and delivered via the appropriate channel.
When to Use
- Responding to customer questions
- Providing solutions or information
- Following up on issues
- Confirming resolutions
How to Send
- Open the ticket
- Type in the reply composer
- Ensure Reply mode is selected (not Note)
- Click Send or press
Cmd/Ctrl + Enter
Delivery Channels
Replies go back through the original channel:
| Ticket Source | Reply Delivery |
|---|---|
| Email to customer | |
| Widget | Widget chat & email |
| SMS | SMS to phone |
| Slack | Slack message |
| WhatsApp message |
Internal Notes
What They Are
Internal notes are private comments visible only to your team. Customers never see these.
When to Use
- Recording phone call summaries
- Leaving context for colleagues
- Documenting investigation steps
- Handoff notes between shifts
- Recording decisions or escalations
How to Add
- Open the ticket
- Click Note tab (or press
N) - Type your note
- Click Add Note or press
Cmd/Ctrl + Enter
Visual Distinction
Notes appear differently in the thread:
- π Lock icon
- "Internal" label
- Different background color
- Muted styling
Comparing Reply Types
| Feature | Public Reply | Internal Note |
|---|---|---|
| Visible to customer | β Yes | β No |
| Sent via channel | β Yes | β No |
| Changes status | β Optional | β No |
| In conversation thread | β Yes | β Yes |
| Searchable | β Yes | β Yes |
| Can mention teammates | β Yes | β Yes |
Switching Between Types
In the Composer
Toggle between Reply and Note:
- Click Reply or Note tabs
- Use keyboard:
Rfor reply,Nfor note - Current mode shown in composer header
After Starting to Type
If you started typing in the wrong mode:
- Click the other tab
- Your text is preserved
- Continue in correct mode
Warning on Mode Switch
If you have significant text and switch modes, Relay warns you to prevent accidental loss.
Best Practices
For Public Replies
- Be clear and helpful: Customer is your audience
- Proofread before sending: Can't unsend
- Include relevant details: Don't make customer ask twice
- Set expectations: When will you follow up?
- Use formatting wisely: Help readability
For Internal Notes
- Be detailed: Future you will thank you
- Document decisions: Why you did what you did
- Record external communications: Phone calls, meetings
- Use for handoffs: Clear context for colleagues
- Timestamp external events: "Called customer at 2:30pm"
Mentions in Messages
Mentioning Teammates
Both replies and notes support @mentions:
- Type
@followed by name - Select from dropdown
- Person is notified
In Public Replies
- @mentions notify teammates
- Mention is visible to customer (name only)
- Use for awareness, not private communication
In Internal Notes
- @mentions notify teammates
- Customer never sees the note
- Great for getting colleague input
Attachments in Messages
Adding Attachments
Both types support attachments:
- Drag and drop files
- Or click attachment icon
- Files upload automatically
Public Reply Attachments
- Sent to customer
- Appear in email or chat
- Stored securely
Internal Note Attachments
- Only visible to team
- Useful for screenshots, documentation
- Customer cannot access
Templates and Macros
Using Templates in Replies
Apply saved templates:
- Click template icon in composer
- Select template
- Template text inserted
- Customize as needed
Macros with Both Types
Macros can include:
- Public reply content
- Internal note content
- Or both (reply + note)
See Using Macros for details.
Common Scenarios
Phone Call Documentation
After a phone call:
- Open/create the ticket
- Click Note
- Document call summary:
- What was discussed
- What was agreed
- Next steps
- Add note with timestamp
Escalation Handoff
When escalating to another team:
- Add internal note with context
- @mention the recipient
- Include all relevant details
- Then reassign the ticket
Customer Information for Team
When you learn something important:
- Add internal note
- Example: "Customer mentioned they're on vacation until 12/15"
- Team sees this context
- Customer doesn't see it
Troubleshooting
"Customer saw my internal note"
This shouldn't happenβdouble-check:
- Was it actually a reply, not a note?
- Check the message type indicator
- Review the thread carefully
"Reply didn't send to customer"
Check:
- Customer email is valid
- No delivery errors in activity
- Channel integration is working
"Can't switch from reply to note"
- You may have already sent
- Check if message is in thread
- Start a new message if needed