CS Add-on: Connect with Sales CTA - Usage Quotas
Summary
Help connect current Code Suggestions beta users with Sales from within the SaaS app
Context
As we transition Code Suggestions from beta to Paid GA, we have the opportunity to convert beta users to the paid add-on for the feature. To start, existing paid (Premium and Ultimate) SaaS customers will only be able to purchase the add-on through Sales (we'll refer to this as sales-assisted
) - with the ability to purchase via Self-managed, GitLab Dedicated, and Webstore coming later.
Problem
The current path a user must take to connect with Sales to facilitate the purchase of the Code Suggestions add-on requires the user to go outside of the product (email, Marketing site form, etc).
Solution
From discussion in &11218 (comment 1512797558), this issue will be dedicated to connecting Contact Sales modal to the CTA on the Code Suggestions tab (new page implemented in https://gitlab.com/gitlab-org/gitlab/-/issues/422629) and ensuring information submitted via the form is delivered to the corresponding systems successfully.
Technical Implementation Requirements
Building from the work in https://gitlab.com/gitlab-org/gitlab/-/issues/422629 that's added a new Code Suggestions
tab on the /usage_quotas page:
- Clicking
Contact Sales
CTA triggers Sales form submission modal - Form populates known information about the customer
- Upon successful submission of the form, data is passed via API call to Marketo
- Modify existing hand-raise PQL code in customers.dot to capture this code suggestions hand-raise PQL
-
product interaction
value passed to Marketo has value ofRequested Contact-Code Suggestions Add-On
and additionally we send these fields:company
,first name
,last name
-
Contact Sales
button remains active after successful form submission - User can dismiss the form submission modal
- Feature flag options:
- Per #421952 (comment 1523226604): Place behind shared feature flag (#422132 (closed))
Separate feature flag to control this behaviour in case we need to turn it on and off (for testing or in case of failures)