WIP Update source/handbook/marketing/marketing-operations/index.html.md
Why is this change being made?
Lead status makes little sense as "web portal purchase." It was a stop gap and is just overstating leads.
How will this merge request impact page speed?
Should not have an effect
Does this MR meet the acceptance criteria?
Assign to DRI
I am DRI
Conformity
Yes
Merge request reports
Activity
@darawarde - to confirm, because there is both a lead and a contact created for a web portal purchase, the current solution was an SDR just changed the lead status to 'web portal purchase.' The new process you have proposed here is that the SDR now needs to convert this lead to a contact and then merge it with the contact that was also created for this purchase.
Problems I see:
- All web portal purchase contacts are not owned by sales admin or an SDR and therefore an SDR won't be able to follow this process as they won't have the ability to merge.
- Why are we adding this manual step for an SDR when we should work on eliminating the creation of this lead?
@EWhelchel looping you in.
We are also working on fixing the problem - its on the list of things the growth/fulfillment team have on their backlog. I just want the leads to go away since they aren't real. And I was thinking if the SDR is already manually switching the lead status to Web Portal Purchase its only another step or 2 to merge into the contact. Technically, they should be duduping as they get new MQLs and merging if they find duplicates, so this did not seem like extra work.
Added that to the related issue https://gitlab.com/gitlab-com/sales-team/field-operations/systems/-/issues/672
@bethpeterson Definitely will want to delete this MR, but wanting to share with you in case its easier to see what I was thinking!
ditto to my comment above for @RobRosu - Ringlead may make this moot.
added handbook label
assigned to @RobRosu
unassigned @darawarde