Create add-on only purchase mailer
Provision failure label
provision failurenew addon standalone subscription
Problem
Today, when a customer purchases an add-on product, such as Storage
or CI Minutes
, that is NOT purchased in the same transaction as a SaaS subscription, they do not receive any confirmation via email. This is not a great customer experience, because they have no confirmation that the purchase went through.
Proposal
Setup a new mailer for add-on only purchases that HAVE a linked Namespace:
- Provides a confirmation to customers that their additional purchase was successful, in a way that makes it clear this was an update/add-on to an existing subscription.
- Gives the customer an audit trail to follow in email.
If there is no linked Namespace, we should instead send the unlinked SaaS purchase mailer.
Add the new mailer to the mailers doc.
NOTE: This a separate use case from the existing Subscription Update mailer created in #5058 (closed).
Proposed Template
Hi Courtney👋
Thanks for your GitLab purchase! We appreciate your loyalty as a GitLab customer!
Your purchase will be automatically applied to your namespace on the start date listed below. Here are the details of your purchase:
1. `product name`
2. `term start date`
2. `term end date`
3. `quantity`
If you require any assistance, contact GitLab support.
Thanks,
The GitLab Team
Note: keep the existing link to GitLab Support (https://about.gitlab.com/support/#contact-support) in the last line.
Technical Requirements
- Send this mailer when:
- Purchase is of an add-on product (i.e.
Storage
,CI Minutes
,Code Suggestions
)
- Purchase is of an add-on product (i.e.
- Namespace is already linked/associated with this purchase.
- Ensure the newer version of the template design is used, consistent with the current New Subscription SaaS purchase email
Result
- Customer receives an email confirmation when they purchase a standalone add-on product.
Affected issues
- https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/6748
- https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/6759
Availability & Testing
Adding a mailer, should be accompanied by several tests.
- Mailer Specs
- Mailer Subject
- Mailer To/From (multiple To's? If so, which is first?)
- Mailer Body?
- When is this Mailer activated? Only during update? During creation?