Meta pixel

Customer Success

This handbook page details processes specific to working with and within this department.


Role Contributor(s)
VP of Customer Success Zay Hanlon (@zayhanlon)
Infrastructure Engineer Robert Fairburn (@rfairburn)
Customer Support (CSE/CSA) Kathy Satterlee (@ksatter)
Grant Bilstad (@Pacamaster)
Dale Ribeiro (@ddribeiro)
Ben Edwards (@edwardsb)
Brock Walters (@nonpunctual)
Customer Success Manager (CSM) Jason Lewis (@patagonia121)
Michael Pinto (@pintomi1989)

Contact us

  • To make a request of this department, create an issue and a team member will get back to you within one business day (If urgent, mention a team member in the #g-customer-success).
    • Any Fleet team member can view the kanban board for this department, including pending tasks and the status of new requests.
    • Please use issue comments and GitHub mentions to communicate follow-ups or answer questions related to your request.


The customer success department is directly responsible for ensuring that customers and community members of Fleet achieve their desired outcomes with Fleet products and services.

Assign a customer codename

Occasionally, we will need to track public issues for customers and prospects who wish to remain anonymous on our public issue tracker. To do this:

  1. The team member creating the issue will choose an appropriate minor planet name from this Minor planets page (alphabetical).
  2. Create a label in the fleetdm/fleet and fleetdm/confidential repos which can be attached to current and future issues for the customer or prospect. As part of the label description in the fleetdm/confidential repo, add the customer or prospect name. This way, we maintain a confidential mapping of codename to customer or prospect.

Prepare for routine customer meeting

Before a routine customer call, the CSM prepares an agenda including the following items:

  1. Customer and Fleet expected attendees
  2. Release notes for the latest version of Fleet
  3. Update notes for which version of Fleet the customer is running (if self-hosted)
  4. Follow ups to the agenda from the previous call or Slack
  5. Provide updates to open feature requests (can be done monthly or quarterly)
  6. Provide updates to open bug reports

Conduct a quarterly business review (QBR)

Business reviews are conducted quarterly or bi-annually to ensure initial success criteria completion, ongoing adoption, alignment on goals, and delivery of value as a vendor. Use the meeting to assess customer priorities for the coming year, review performance metrics, address any challenges and showcase value in upcoming and unutilized features.

  1. Work with your champion to schedule the business review at a time thier stakeholders are available (typically 90 days after kickoff and again, 90 days before renewal).
  2. Collect usage metrics from the usage data report (internal Fleet document) and the following:
    • Optionally schedule a health check with day to day admins prior to the QBR to better understand how the product is being used and which features have been adopted.
    • Have a support engineer collect data on open and closed bugs from the previous quarter and highlight any P0 or P1 incidents along with a summary of the postmortem (search Unthread and GitHub for issues tagged with the customer codename and ':bug').
    • Summarize status updates for open feature requests and highlight delivered feature requests.
    • For managed cloud customers, reach out to #help-infrastructure to collect information on cloud uptime and any outages or alarms.
    • Provide one slide with information on the latest Fleet release and any upcoming big ticket features which can be found on the product board and current release board for #g-mdm and #g-endpoint-ops
  3. After the business review, save the presentation as a PDF and share it with your customer.

Create customer support issue

Locate the relevant issue or create it if it doesn't already exist (to avoid duplication, be creative when searching GitHub for issues - it can often take a couple of tries with different keywords to find an existing issue). When creating a new issue, make sure the following:

  • Make sure the issue has a "customer request" label or "customer-codename" label.
    • Occasionally, we will need to track public issues for customers that wish to remain anonymous on our public issue tracker. To do this, we choose an appropriate minor planet name from this Wikipedia page and create a label which we attach to the issue and any future issues for this customer.
  • "+" prefixed labels (e.g., "+more info please") indicate we are waiting on an answer from an external community member who does not work at Fleet or that no further action is needed from the Fleet team until an external community member, who doesn't work at Fleet, replies with a comment. At this point, our bot will automatically remove the +-prefixed label.
  1. Required details that will help speed up time to resolution:
    • Fleet server version
    • Agent version
      • Osquery or fleetd?
    • Operating system
    • Web browser
    • Expected behavior
    • Actual behavior
  2. Details that are nice to have but not required. These may be requested by Fleet support as needed:
    • Amount of total hosts
    • Amount of online hosts
    • Amount of scheduled queries
    • Amount and size (CPU/Mem) of the Fleet instances
    • Fleet instances CPU and Memory usage while the issue has been happening
    • MySQL flavor/version in use
    • MySQL server capacity (CPU/Mem)
    • MySQL CPU and Memory usage while the issue has been happening
    • Are MySQL read replicas configured? If so, how many?
    • Redis version and server capacity (CPU/Mem)
    • Is Redis running in cluster mode?
    • Redis CPU and Memory usage while the issue has been happening
    • The output of fleetctl debug archive
  • Have we provided a link to that issue for the customer to remind everyone of the plan and for the sake of visibility, so other folks who weren't directly involved are up to speed (e.g., "Hi everyone, here's a link to the issue we discussed on today's call: …link…")?

Contact the developer on-call

The acting developer on-call rotation is reflected in the 📈KPIs spreadsheet (confidential Google sheet). The developer on-call is responsible for responses to technical Slack comments, Slack threads, and GitHub issues raised by customers and the community, which the CSE team cannot address.

  • To reach the developer on-call for assistance, mention them in Fleet Slack using @oncall in the #help-engineering channel.
    • Support issues should be handled in the relevant Slack channel rather than Direct Messages (DMs). This will ensure that questions and solutions can be easily referenced in the future. If it is necessary to use DMs to share sensitive information, a summary of the conversation should be posted in the Slack channel as well.
An icon indicating that this section has important information

Note: Additional help can be obtained by messaging a Solutions Consultant in the #help-solutions-consulting channel.

  • An automated weekly on-call handoff Slack thread in #g-engineering provides the opportunity to discuss highlights, improvements, and hand off ongoing issues.

Onboard a customer success team member

Manage automation of customer slack

  1. A new message is posted in any Slack channel
  2. (Zapier filter) The automation will continue if the message is:
    • Not from a Fleet team member
    • Posted outside of Fleet’s business hours
    • In a specific customer channel (manually designated by customer success)
  3. (Slack) Notify the sender that the request has been submitted outside of business hours and provide them with options for escalation in the event of a P0 or P1 incident.
  4. (Zapier) Send a text to the VP of CS to begin the emergency request flow if triggered by the original sender.
An icon indicating that this section has important information

Note: New customer channels that the automation will run in must be configured manually. Submit requests for additions to the Zapier administrator.

Generate a trial license key

  1. Fleet's self-service license key creator is the best way to generate a proof of concept (POC) or renewal/expansion Fleet Premium license key.

  2. Legacy method: create an opportunity issue for the customer and follow the instructions in the issue for generating a trial license key.

Respond to messages and alerts

Customer Support and 24/7 on-call Engineers are responsible for the first response to Slack messages in the #fleet channel of osquery Slack, and other public Slacks.

  • The 24/7 on-call is responsible for alarms related to and Fleet Managed Cloud, as well as delivering 24/7 support for Fleet Premium customers. Use on-call runbooks to guide your response. Runbooks provided detailed, step-by-step instructions to quickly and effectively respond to and resolve most 24/7 on-call alerts.
  • We respond within 1-hour during business hours and 4 hours outside business hours. Note that we do not need to have answers within 1 hour -- we need to at least acknowledge and collect any additional necessary information while researching/escalating to find answers internally.

Maintain first responder SLA

The first responder on-call for Managed Cloud will take ownership of the @infrastructure-oncall alias in Slack first thing Monday morning. The previous week's on-call will provide a summary in the #g-customer-success Slack channel with an update on alarms that came up the week before, open issues with or without direct end-user impact, and other issues to keep an eye out for.

  • First responders: Robert Fairburn, Kathy Satterlee

Escalation of alarms will be done manually by the first responder according to the escalation contacts mentioned above. A suspected outage issue should be created to track the escalation and determine root cause.

  • Escalations (in order): » Eric Shaw ( » Zay Hanlon » Luke Heath » Mike McNeil

All infrastructure alarms ( and Managed Cloud) will go to #help-p1. When the current 24/7 on-call engineer is unable to meet the response time SLAs, it is their responsibility to arrange and designate a replacement who will assume the @oncall-infrastructure Slack alias.



The following stubs are included only to make links backward compatible.


Please see Handbook/customer-success#respond-to-messages-and-alerts

An arrow pointing upBack to top