Skip to content

Add spot engagements to CSE engagement model

Martin Brümmer requested to merge cse-spot-engagements into master

Why is this change being made?

I recently have started to support the EMEA team with "Spot Engagements". Opposed to our regular, more complex engagements that will require a number of customer calls and a more in depth timed and scoped project, "Spot Engagements" represent individual, typically single customer call engagements. They are meant to unblock specific adoption impediments that exceed the technical knowledge of CSMs, can not simply be handled by async Q&A, are not in scope for support and do not warrant a PS engagement.

Spot engagement fill a lot of gaps in our CS and support offering and are relatively quick for the CSE to resolve. They provide more "depth" to account teams, because they can leverage the CSE as technical resource for problems that are limited in scope and do not warrant an engagement request and separate scoping and review. They also provide a growth opportunity for CSMs, as they can gain experience on these technical topics during the CSE engagement.

Author Checklist

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail
  • If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
    • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

Merge request reports