Goal

• This story looks at what preventative changes we could make so that users are encouraged to:
  • join an existing account (if applicable) and;
  • use a corporate email.
  • Doing so will hopefully reduce the number of users at the gate that contribute to the unclassified cluster problem outlined below.
• Currently there are two different forms for RH account creation:
  • The existing c.rh.c form has additional information that the form from rh.c does not include (join existing account info and account type)
  • We should leverage the c.rh.c form as our singular path and consider improvements like ensuring the create a RH account with a corporate email does not create a new EBS account if possible

Background

• There are 1981 unclassified clusters. Having clusters in an unclassified state means that Red Hat does not understand what Custom Global Customer Name (GCN) the cluster is associated with. This limits Red Hat’s ability to engage with the owner of the cluster in a meaningful way which decreases chances of revenue generation, retention, and customer success.
• There are several scenarios by which these unclassified clusters can occur. (see image of buckets of users or slide 5 in the deck). This scenario is focused on preventing users from ending up in those scenarios in the first place. 
• Proposed refinements have been presented and further conversations need to occur to see if we can align on a single form (see slide 17 in the deck)
• Colleen/Megan can help with any additional background.

Requirements

• Connect with Heather/James Bailey and find out if there are reasons that the existing account creation workflows are different and see if and how we can align
• For the RH account creation form:
  • Investigate and see if we can always include the "Join an existing account" at the top of every "Create a RH account" form
  • Investigate and see if we can always include the corporate or personal account selection on every form.
  • Investigate what the "Corporate account" type selection actually does? Can we do something with the corporate selection? Could an org admin allow them in? Do we have data on the unclassified cluster accounts? Are they for personal use?

• Identify any other gaps we could be missing.

Resources

• Slide deck: https://docs.google.com/presentation/d/1GJMATzWvLO7UA91dg49lGRXN6K2hxyu5bCHDPCbm97I/edit#slide=id.ge8ef82f34f_0_0