Fanhaven sends transactional and marketing emails to your fans on behalf of your artist. Email Templates let you customize these messages to match your brand voice and visual identity.
Types of emails
Transactional emails
Automatically sent in response to specific actions:
| Email | When it’s sent |
|---|
| Purchase receipt | After a POS or online purchase |
| Refund confirmation | After a refund is processed |
| Order shipped | When a shipped order has tracking info |
| Mobile order ready | When a mobile order is ready for pickup |
| Fanpass welcome | When a fan signs up for Fanpass |
| Reward earned | When a fan earns a reward |
Marketing emails
Sent through the Campaigns system:
Customizing templates
Navigate to Advanced → Email Templates in the dashboard.
What you can customize
| Element | Description |
|---|
| Logo | Your artist’s logo in the email header |
| Colors | Brand colors for buttons, links, and accents |
| Footer text | Custom text in the email footer (social links, legal text) |
| Reply-to address | Where fan replies are directed |
Email receipt customization
The purchase receipt is the most commonly seen email. Customize it from Advanced → Email Receipt:
- Header branding — Logo and banner image
- Message text — A custom message below the receipt details
- Social links — Links to the artist’s social media profiles
- Support contact — Where fans should reach out with order issues
Preview and test
After making changes to any template:
- Click Preview to see how it looks
- Send a test email to yourself
- Check rendering on both desktop and mobile email clients
Always test emails on mobile — the majority of fans will read them on their phone. Make sure images load, links work, and text is readable.
Best practices
- Keep branding consistent — Emails should feel like they come from the artist, not a third-party tool
- Be concise — Transactional emails should communicate the essential information quickly
- Include support info — Always give fans a way to reach out if they have questions
- Test after changes — Any template edit should be followed by a test send
