Configure how Tiger Membership sends member and admin email — both the delivery transport (system mail or SMTP) and the per-event templates (welcome, receipts, renewals, payment failures, cancellations). Every message renders inside a branded HTML shell built from your business identity.
Where: WP Admin → Tiger Membership → Settings → Emails.
Mail delivery
Choose System default (your server’s PHP mail) or SMTP for reliable delivery through a provider. SMTP is strongly recommended — shared hosts often have unreliable or unauthenticated PHP mail that lands in spam.
| Field | Notes |
|---|---|
| Transport | System default / SMTP |
| Provider preset | One click prefills host/port/encryption — Gmail, Outlook 365, SendGrid, Mailgun, Postmark, Amazon SES, Brevo, Zoho, or Custom |
| Host / Port | e.g. smtp.sendgrid.net / 587 |
| Encryption | TLS (587) / SSL (465) / None |
| Username / Password | Provider credentials — the password is stored encrypted and never sent back to the browser |
| From name / From email | The sender identity members see |
| Send test email | Sends a real message and surfaces the exact provider error if it fails |
Email templates
Every lifecycle event has an editable template rendered in the branded HTML shell. Each has a subject + body with merge tags, a live Preview (opens the rendered message in a frame), and a Send test button.
| Event | Sent to |
|---|---|
| Welcome | Member — on signup |
| Payment receipt | Member — on every successful, non-zero payment (initial or renewal). Zero-amount admin comps and proration credits are skipped. |
| Trial ending | Member — a daily cron notifies each trialing member once, roughly three days before the trial converts |
| Payment failed | Member — on a failed charge (dunning) |
| Card expiring | Member — before a saved card expires |
| Cancelled | Member — on cancellation |
| Admin notices | Admin — new member, cancellation, and payment failed |
Merge tags
Bodies support merge tags such as the member’s name, plan name, amount and site name; the Preview fills them with sample data so you can see the finished layout before sending. The From name and From email set on this screen apply to every message.
How to configure SMTP
- Set Transport to SMTP.
- Pick your Provider preset — host, port and encryption fill in automatically.
- Enter the Username and Password (an API key for most providers).
- Set the From name and From email to an address on a domain you control.
- Click Send test email and confirm it arrives, then Save.
Troubleshooting
The test email fails or never arrives.
The Send test button surfaces the provider’s exact error — read it. The usual causes are a wrong password/API key, a blocked port (try 465/SSL if 587/TLS is filtered), or a From email on a domain the provider hasn’t verified.
Members aren’t receiving lifecycle emails.
Trial-ending notices run on WordPress cron — if your site gets little traffic, cron may lag. Also confirm the relevant template is not empty and that your transport passes the test above.
Emails land in spam.
Switch from System default to authenticated SMTP and use a From email on the same domain that sends the mail, so SPF/DKIM align.