Use QCMM Email Tokens Safely

Use QCMM email tokens with the correct recipient, customer, subscription, Meeting, billing, and Custom Field context

Insert Tokens from the Editor

The Email editor groups available tokens into Recipient, Customer / Subscription, Meeting / Host, General / Billing, and Custom Fields. Clicking a token inserts its exact placeholder into the subject or body.

Recipient and Customer Identity Are Different

For Customer-recipient templates, {name}, {username}, and {email} refer to the customer. For Administrator or Host templates, those recipient tokens refer to the administrator or Host receiving that copy; {customer_*} tokens continue to describe the customer involved in the event.

Do Not Guess Missing Context

Subscription, Plan, Meeting, Host, billing, and Custom Field values are resolved from the event context. Custom Field tokens use the exact subscription or Meeting booking for the real email. If an event has no applicable subscription context, QCMM leaves that Custom Field token blank rather than borrowing data from another purchase.

Test for Unresolved Tokens

Use Preview and Send Test before publishing changes. Send Test refuses delivery when unresolved tokens remain, which makes it useful for catching placeholders that the selected template context cannot resolve.

Community Discussion

Want to compare QCMM workflows or share practical tips? Visit the QC Memberships & Meetings Community. For private support, bug reports, account-specific entitlement or billing problems, or feature requests, use the QuantaCade support system.