Understand Custom Field Fulfillment Update Emails

Understand QCMM Custom Field fulfillment update email routing and recipient-specific visibility for Customer, Administrator, and Host copies

Fulfillment Updates Are Their Own Event

QCMM exposes Custom Field Fulfillment Updated as a Plan-aware email event. It can route to Customer, Administrator, and Host recipients when those recipients are valid for the underlying fulfillment context.

Customer Visibility Is Enforced

Customer-recipient messages use customer-safe Custom Field visibility. Internal-only fulfillment changes do not become customer-visible simply because an email template contains a Custom Field token.

Administrator and Host Context Is Separate

Administrator and Host copies use their own recipient identity while retaining the customer/event context through {customer_*} and the exact subscription or Meeting booking. Host delivery is tied to an applicable Host context rather than sent to an arbitrary address.

Custom Templates Remain Additive

Max / All Access sites can add published Custom templates for the fulfillment event and scope them by Plan. Matching trigger, recipient, and Plan rules are evaluated independently, so a Custom template supplements rather than replaces the Core notification family.

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.