Meta pixel


Contacting Fleet

If you're using a free version of Fleet, you can access free community support by opening an issue in the Fleet GitHub repository.

Customers on a paid tier of Fleet can get in touch directly for commercial support:

Level of impact Response time - premium tier Response time - ultimate tier
Low to medium impact
Email/chat support during business hours
Email: Support email address
Chat: Dedicated Slack channel (confidential)
1 business day 1 business day
High to emergency impact
Expedited phone/chat/email support
Call or text: Fleet support phone number
Email: Emergency support email address
4 business hours ≤1 hour during business hours
≤2 hours outside business hours
Level of impact Type of support
Low to medium impact Chat support during business hours Chat: Dedicated Slack channel (confidential)
Response time: ≤1 business day
High to emergency impact Expedited phone/chat support during business hours
Call or text the Fleet phone number that was provided in the invoice.
Response time: ≤4 hours

Becoming a customer

To close a deal with a new customer (non-self-service), create a GitHub issue using the "Sale" issue template and follow the steps.

An icon indicating that this section has important information

TODO: dedupe between this section and the "Sale" issue template

This workflow outlines the process that sales and customer success can follow when a new deal closes.

  1. (AE) A customer is sent an order form
    • If the customer requires the use of their own legal contract, the account executive (AE) sends that contract to the business operations (BizOps) team for review. Then:
    • If the customer can use DocuSign, the AE sends out the order form. The AE must cc themselves and BizOps on the order so that all parties receive a fully executed copy when signing is complete.
    • If the customer does not use DocuSign, the AE sends out the order form directly to the customer.
      • The AE then sends the paper signed copy to BizOps for Fleet review and execution (via DocuSign by the CEO).
      • BizOps will cc the AE and stay cc’d on the contract when the final copy is sent to the CEO for Fleet execution.
      • Note: The Chief Revenue Officer serves as the backup to BizOps
  2. The Customer and Fleet sign the order form.
    • (AE) The AE adds the fully executed contract to the opportunity record.
    • (AE) The AE marks the opportunity 'Closed Won' and includes the 'Closing Date'.
    • (BizOps) BizOps team member adds fully executed contract to the subscriptions folder (internal drive) in Fleet drive
  3. (AE) The AE creates a 'New Sale Issue'
    • They complete the AE tasks listed at the top of the issue.
    • Then they assign the issue to BizOps and the Head of Customer Success (CS).
    • AE completes the Business Objectives section of the Account Plan located in the Sales> Opportunities> {Account Name} shared google drive folder.
    • Solution Architect completes the Technical Objectives section of the Account Plan located in the Sales> Opportunities> {Account Name} shared google drive folder.
    • AE moves the {Account Name} folder within Opportunities to the Sales> Account Plans folder.
    • The AE schedules a 30 minute internal handoff call with CS and any other related parties to the sale.
    • Prepare to review the following from the Account Plan:
      • Details of the deal
      • Primary contact / their role
      • Desired use cases / desired outcomes
      • Reasons for purchase
      • Previously using Fleet Free?
      • Support tier (Premium or Ultimate)
      • Competitive solutions in place
      • Other relevant technologies in place
      • Any proof of concept (POC) notes that are relevant
      • Customer expectations for timeline
      • Server deployment type
  4. (CS) The CSM kicks off the CS responsibilities in the 'New Sale Issue'
    • Create an “Existing Business” renewal opportunity in (SFDC).
    • Send the customer welcome email (internal drive) & deployment checklist template (internal drive)
    • Create the customer Slack channel
    • Generate the customer license key
    • Share the license key with the customer (7 day link)
    • Schedule the customer onboarding kickoff call
    • Collect deployment details (if not completed during POC)
    • Schedule the recurring customer check-in
    • Owns running the meeting, note taking, TODO follow up, etc.

Fleet's W-9

A recent signed copy of Fleet's W-9 form can be found in this confidential PDF in Google Drive.

Paying Fleet

For customers with hundreds or more hosts, Fleet accepts payment via wire transfer or electronic debit (ACH/SWIFT).

Fleet team members can provide remittance information to customers by exporting "💸 Paying Fleet" into a PDF.

Customer success calls

Scheduling a customer call

To schedule an ad hoc meeting with a Fleet customer, use the "Customer meeting" Calendly link.

Documenting a customer call

When we do prospect calls, add the customer's name in both the google doc title and the heading, ex. "Charlie (Fleet)." This makes it easier when searching for the document later.

How to conduct a customer meeting

Before a customer call (48hrs)

  • Check the calendar invite 48hrs before the meeting to determine if the customer has accepted the invitation.
  • If the customer has not accepted the invitation, reach out to confirm attendance (e.g., EAs, email, Slack).
  • Test the Zoom Meeting link to make sure that it is working.
  • Make sure that agenda documents are attached and accessible to meeting attendees (as appropriate to the situation).

Day of the customer call

  • Join the meeting two to three minutes before the start time.

Missed customer call

  • If the customer does not join the call after three minutes, contact the customer with
    • Slack, if we have a shared channel.
    • email, using the email address from the calendar invite.
    • LinkedIn, send a direct message.
    • phone, try finding their number to text and/or call (as appropriate to the device type: landline vs. cell phone).
    • an alternative date and time. Suggest two to three options from which the customer can choose.
      • Confirm that contact information is accurate and that the customer can receive and access meeting invites.

Customer support service level agreements (SLA's)

Fleet Community Edition

Impact Level Definition Preferred Contact Response Time
All Inquiries Any request regardless of impact level or severity Osquery #fleet Slack channel No guaranteed resolution

Note: If you're using Fleet Free, you can also access community support by opening an issue in the Fleet GitHub repository.

Fleet Premium

Impact Level Definition Preferred Contact Response Time
Emergency (P0) Your production instance of Fleet is unavailable or completely unusable. For example, if Fleet is showing 502 errors for all users. Expedited phone/chat/email support during business hours.

Email the contact address provided in your Fleet contract or chat with us via your dedicated private Slack channel
≤4 hours
High (P1) Fleet is highly degraded with significant business impact. Expedited phone/chat/email support during business hours.

Email the contact address provided in your Fleet contract or chat with us via your dedicated private Slack channel
≤4 business hours
Medium (P2) Something is preventing normal Fleet operation, and there may or may not be minor business impact. Standard email/chat support ≤1 business day
Low (P3) Questions or clarifications around features, documentation, deployments, or 'how to's'. Standard email/chat support 1-2 business days

Note: Fleet business hours for support are Monday-Friday, 7AM-4PM Pacific Time, excluding current U.S. federal holidays during which responses may be delayed for Medium and Low impact issues.

Fleet Ultimate

Impact Level Definition Preferred Contact Response Time
Emergency (P0) Your production instance of Fleet is unavailable or completely unusable. For example, if Fleet is showing 502 errors for all users. Call or text the emergency support phone number in your Fleet contract.

Email via the emergency support email address provided in your contract.
≤1 hour or ≤2 hours outside of business hours
High (P1) Fleet is highly degraded with significant business impact. Expedited phone/chat/email support during business hours.

Email the contact address provided in your Fleet contract or chat with us via your dedicated private Slack channel
≤2 hours or ≤4 hours outside of business hours
Medium (P2) Something is preventing normal Fleet operation, and there may or may not be minor business impact. Standard email/chat support ≤1 business day
Low (P3) Questions or clarifications around features, documentation, deployments, or 'how to's'. Standard email/chat support ≤1 business day

Note: Fleet business hours for support are Monday-Friday, 7AM-4PM Pacific Time, excluding current U.S. federal holidays during which responses may be delayed for Medium and Low impact issues.

Flow of communication in the event of an emergency (P0) request

Screen Shot 2022-12-05 at 10 22 43 AM

Customer support workflow for Slack + Zendesk

This section outlines both the automated workflows and manual triggers associated with Fleet's Slack integration to Zendesk. The purpose of this integration is to:

  • Provide Fleet with better service level agreement (SLA) tracking on requests (especially those submitted outside of business hours)
  • Better track threads for issues that require advanced troubleshooting
  • Consolidate support requests into a single-source, searchable system for faster issue resolution in the future

There are three different situations when a customer support request could result in a ticket being created in Zendesk. They are as follows:

  1. When a request has been submitted outside of business hours via Slack automation
  2. When a Fleet staff member has flagged an issue that requires advanced troubleshooting and determines that they want to move it into Zendesk for management
  3. When any Fleet user submits a support request via email

Workflow when a request is submitted outside of business hours:

  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. (Zendesk) Search for an existing Zendesk ticket by the Slack thread ID or create one if it does not exist.
  4. (Slack) If a new Zendesk ticket was created, reply to the Slack message in a thread.
    • Hi @username, it's currently outside Fleet's support hours. (6am - 4pm PT). We've created a support ticket based on your message, and a Fleet team member will respond as soon as possible. If you have more questions or comments, feel free to reply in this thread, and we'll add them to the ticket.
  5. (Zendesk) If an existing Zendesk ticket was found by the search, add the Slack message to the existing ticket as a new comment.

Things to note:

  • New customer channels that the automation will run in must be configured manually. Submit requests for additions during automation office hours.
  • New tickets created from thread replies will contain a link to the slack thread, but will only have the new message.
  • This zap does not support file uploads and attachments. Tickets created for messages with images attached will not have the attachments, and the automation will not run if someone uploads a file without a message.

Workflow when a request is submitted outside of business hours:

Screen Shot 2022-12-01 at 11 39 54 AM

Customer support process

This section outlines Fleet's customer and community support process.

  • The customer support engineering (CSE) team handles basic help desk resolution and service delivery issues (P3 and P4) with assistance from L2 on-call and the solutions architecture team as needed.
  • The CSE team handles in depth technical issues (P1 and P2) in conjunction with L2 on-call.
  • The CSE team handles expert technical product and services support in coordination with the L2 and L3 on-call technicians.

Whenever possible, the resulting solution should be documented as an update to an existing FAQ guide or new documentation article.

The support process is accomplished via on-call rotation and the weekly on-call retro meeting.

The on-call engineer holds responsibility for responses to technical Slack comments, Slack threads, and GitHub issues raised by customers and the community, which the Customer Success team cannot handle.

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.

The weekly on-call retro at Fleet provides time to discuss highlights and answer the following questions about the previous week's on-call:

  1. What went well?

  2. What could have gone better?

  3. What should we remember next time?

This way, the Fleet team can constantly improve the effectiveness and experience during future on-call rotations.

What to include in a support request

  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

Fleet responses to customer support issues

When a customer encounters an unexpected error on, it is important that we contact them quickly to resolve the issue.

If you need to reach out to a customer to resolve an error, you can use one of the templates below. The full list of response email templates is available in this Google doc.

Error while purchasing a Fleet Premium license

"Hi [company name] team, I just noticed you ran into an error signing up for a license key on

I’m so sorry about that! Were fixing the issue now and I’ve refunded your payment and bumped your license to add an additional three hosts for the year as well.

I’ll let you know when your account is sorted and follow up with instructions to access your Fleet Premium licenses.

Thanks for bearing with us, please don’t hesitate to reach out if you have any questions about this, Fleet, osquery, or anything else!"

Error while running a live query in Fleet Sandbox

"Hey there, the team and I just noticed you experienced a 500 error that may have affected your experience running a live query on

I wanted to personally apologize for our mistake and let you know we're looking into the problem. We’ll provide an update on the underlying fix and track an (anonymized) bug on so you can follow the progress in the open.

Thank you for trying Fleet!"

Documenting customer requests in GitHub

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.
  • "+" 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.
  • Is the issue straightforward and easy to understand, with appropriate context (default to public: declassify into public issues in fleetdm/fleet whenever possible)?
  • Is there a key date or timeframe that the customer hopes to meet? If so, please post about that in #g-product with a link to the issue, so the team can discuss it before committing to a time frame.
  • 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…")?

Assistance from engineering

Customer team members can reach the engineering oncall for assistance by writing a message with @oncall in the #help-engineering channel of the Fleet Slack.


Responding to a request to change a credit card number

You can help a Premium license dispenser customers change their credit card by directing them to their account dashboard. On that page, the customer can update their billing card by clicking the pencil icon next to their billing information.

Algolia crawler errors

At least once every hour, an Algolia crawler reindexes the Fleet website's content. If an error occurs while the website is being indexed, Algolia will block our crawler and respond to requests with this message: "This action cannot be executed on a blocked crawler".

When this happens, you'll need to manually start the crawler in the Algolia crawler dashboard to unblock it. You can do this by logging into the crawler dashboard using the login saved in 1password and clicking the "Restart crawling" button on our crawler's "overview" page](

No further action is needed if the crawler successfully reindexes the Fleet website. If another error occurs while the crawler is running, take a screenshot of the error and add it to the GitHub issue created for the alert and @mention eashaw for help.

Customer codenames

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.

Generating 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.

Customer contracts

Fleet's subscription agreement is available at

Fleeties can find a summary of contract terms in the relevant customer's Salesforce opportunity.

Standard terms

For all subscription agreements, NDAs, and similar contracts, Fleet maintains a standard set of terms and maximum allowable adjustments for those terms.

Exceptions to these maximum allowable adjustments always require CEO approval, whether in the form of redlines to Fleet's agreements or in terms on a prospective customer's own contract.

Non-standard NDAs

To get a non-standard NDA (a non-disclosure agreement from another party) signed, request a legal review.

Reviewing subscription agreement

To quickly get help doing a legal review of a prospect subscription agreement, with or without redlines:

  1. Visit
  2. Select "Contract signature or legal review"
  3. Follow the instructions in the "Submitting this request" section

If the prospect/customer/partner is originating the request for signature:

  1. Communicate to the prospect that the Fleet signatory is Mike McNeil, CEO and share his email.
  2. Mike will create the github issue mentioned above when he gets request
  3. Mike will forward to business operations for review
  4. Business operations will notify Mike and the requestor (via GitHub comment w/ at-mention) when ready for signature
  5. Mike will sign and close the issue. (This sends a notification to the requestor automatically.)

Customer DRI change

Sometimes there is a change in the champion within the customer's organization.

  1. Get an introduction to the new DRIs including names, roles, contact information.
  2. Make sure they're in the Slack channel.
  3. Invite them to the Success meetings.
  4. In the first meeting understand their proficiency level of osquery.
    1. Make sure the meeting time is still convenient for their team.
    2. Understand their needs and goals for visibility.
    3. Offer training to get them up to speed.
    4. Provide a white glove experience.

Contract glossary

Term Definition
Effective date The start date for the subscription service.
Close date The date the last party to the contract signed the agreement.
Invoice date The date that Fleet sent the invoice to the customer.


The Fleet sales team embodies our values in every aspect of our work. Specifically, we continuously work to overperform and achieve strong results. We prioritize efficiency in our processes and operations. We succeed because of transparent, cross-functional collaboration. We are committed to hiring for and celebrating diversity, and we strive to create an environment of inclusiveness and belonging for all. We embrace a spirit of iteration, understanding that we can always improve.


Outreach software

At Fleet we use Outreach for sending emails to community members based on triggers or as part of campaigns. To get access to Outreach ask for a license in #g-business-operations Internal video(Internal doc).

Outreach one-pager

Our one-pager offers a summary of what Fleet does. It can help stakeholders become familiar with the company and product while also being a useful tool the Growth team uses for sales outreach. Find Fleet's outreach one-pager here.

Intro deck

Fleet's intro deck adds additional detail to our pitch. Find it in pdf.

Intro video

Fleet's intro video shows how to get started with Fleet as an admin. Find it on YouTube.


You can find a copy of Fleet's SOC 2 report in Google Drive. In its current form, this SOC 2 report is intended to be shared only with parties who have signed a non-disclosure agreement with Fleet.

You can learn more about how Fleet approaches security in the security handbook or in Fleet's trust report.

Our lead handling and outreach approach

Fleet's main source for prospects to learn about the company and its offerings is our website, There are many places across the website for prospects to ask for more information, request merchandise, try the product and even purchase licenses directly. If the user experience in any of these locations asks for an email address or other contact information, Fleet may use that contact information for follow-up, including sales and marketing purposes. That contact information is for Fleet's sole use, and we do not give or sell that information to any third parties.

In the case of a prospect or customer request, we strive to adhere to the following response times:

  • Web chat: 1 hour response during working hours, 8 hours otherwise
  • Talk to an expert: prospects can schedule chats via our calendar tool
  • All other enquiries: 1-2 days

Web chat on-call

The web chat will be monitored by an on-call rotation. If you are unable to answer a technical/product question, ask the Solution Consultant (SC) in #sales. If the SC is unavailable, post in # help-engineering / #help-product accordingly. Transition to the next week on Friday night into Saturday (e.g. Carlos’s shift starts at 12am on 1/21 for the week of 1/23) Respond “in-thread” in Slack “_from-prospective-customers”. In-channel reminders for the next person starting their on-call shift are automated with notifications issued every Monday at the beginning of the day.

Fleet employees can find other expectations for action and response times in this internal document

Salesforce lead status flow

To track the stage of the sales cycle that a lead is at, we use the following standardized lead statuses to indicate which stage of the sales process a lead is at.

Lead status Description
New Default status for all new leads when initially entered into Salesforce. We have an email or LinkedIn profile URL for the lead, but no established intent. The lead is just a relevant person to reach out to.
New enriched Fleet enriched the lead with additional contact info.
New MQL Lead has been established as a marketing qualified lead, meeting company size criteria.
Working to engage Fleet (often Sales development representative-SDR) is working to engage the lead.
Engaged Fleet has successfully made contact with the lead
Meeting scheduled Fleet has scheduled a meeting with the lead.
Working to convert Not enough info on Lead's Budget, Authority, Need and Timing (BANT) to be converted into an opportunity.
Closed nurture Lead does not meet BANT criteria to be converted to an opportunity, but we should maintain contact with the lead as it may be fruitful in the future.
Closed do not contact Lead does not meet BANT criteria for conversion, and we should not reach out to them again.
SAO Converted Lead has met BANT criteria and successfully converted to an opportunity.

At times, our sales team will reach out to prospective customers before they come to Fleet for information. Our cold approach is inspired by Daniel Grzelak’s (Founder, investor, advisor, hacker, CISO) LinkedIn post. The following are the keys to an engaging cold approach. Since cold approaches like these can be easily ignored as mass emails, it’s important to personalize each one.

  • Research each prospect.
  • Praise what’s great about their company.
  • Avoid just stating facts about our product.
  • State why we would love to work with them.
  • Ask questions about their company and current device management experience.
  • Keep an enthusiastic and warm tone.
  • Be personable.
  • Ask for the meeting with a proposed time.

Here is another LinkedIn post with an example of a great personalized cold outreach.

Importantly, when we interact with CISOs or, for that matter, any member of a prospective customer organization, we adhere to the principles in this LinkedIn post. Specifically:

  • Be curteous
  • Be honest
  • Show respect
  • Build trust
  • Grow relationships
  • Help people

Sales team writing principles

When writing for the Sales team, we want to abide by the following principles in our communications.

Maintain naming conventions

Maintain naming conventions so people can expect what fields will look like when revisiting automations outside of Salesforce. This helps them avoid misunderstanding jargon and making mistakes that break automated integrations and cause business problems. One way we do this is by using sentence case where only the first word is capitalized (unless it’s a proper noun). See the below examples.

Good job! ✅ Don't do this. ❌
Bad data Bad Data

Be explicit

Being explicit helps people to understand what they are reading and how to use terms for proper use of automations outside of Salesforce. In the case of acronyms, that means expanding and treating them as proper nouns. Note the template for including acronyms is in the first column below.

Good job! ✅ Don't do this. ❌
Do Not Contact (DNC) DNC

Salesforce contributor experience checkups

In order to maintain a consistent contributor experience in Salesforce, we log in to make sure the structure of Salesforce data continues to look correct based on processes started elsewhere. Then we can look and see that the goals we want to achieve as a business are in line with our view inside Salesforce by conducting the following checkup. Any discrepancies between how information is presented in Salesforce and what should be in there per this ritual should be flagged so that they can be fixed or discussed.

  1. Make sure the default tabs for a standard user include a detailed view of contacts, opportunities, accounts, and leads. No other tabs should exist.

  2. Click the accounts tab and check for the following:

  • The default filter is Customers when you click on the accounts tab. Click on an account to continue.
  • Click on a customer and make sure billing address, parent account, LinkedIn company URL, CISO employees (#), employees, and industry appear first at the top of the account.
  • "Looking for meeting notes" reminder should appear on the right of the screen.
  • Useful links section should include links to Purchase Orders (POs), signed subscription agreements, invoices sent, meeting notes, and signed NDA. Clicking these links should search the appropriate repository for the requested information pertaining to the customer.
  • Additional information section should include fields for account (customer) name first, account rating, LinkedIn sales navigator URL, LinkedIn company URL, and my LinkedIn overlaps. Make sure the LinkedIn links work.
  • Accounting section should include the following fields: invoice sent (latest), the payment received on (latest), subscription end date (latest), press approval field, license key, total opportunities (#), deals won (#), close date (first deal), cumulative revenue, payment terms, billing address, and shipping address.
  • Opportunities, meeting notes, and activity feed should appear on the right.
  1. Click on the opportunities tab and check for the following:
  • Default filter should be all opportunities. Open an opportunity to continue.
  • Section at the top of the page should include fields for account name, amount, close date, next step, and opportunity owner.
  • Opportunity information section should include fields for account name, opportunity name (should have the year on it), amount, next step, next step's due date, close date, and stage.
  • The accounting section here should include: up to # of hosts, type, payment terms, billing process, term, reseller, effective date, subscription end date, invoice sent, and the date payment was received.
  • Stage history, activity feed, and LinkedIn sales navigator should appear at the right.
  1. Click on the contacts tab and check for the following:
  • Default filter should be all contacts. Open a contact to continue.
  • Top section should have fields for the contact's name, job title, department, account name, LinkedIn, and Orbit feed.
  • The second section should have fields for LinkedIn URL, account name, name, title, is champion, and reports to
  • Additional information should have fields for email, personal email, Twitter, GitHub, mobile, website, orbit feed, and description.
  • Related contacts section should exist at the bottom, activity feed, meeting notes reminder, and manager information should appear on the right.
  1. Click on the leads tab and check for the following:
  • Default filter should be all leads. Open a lead to continue.
  • There should be fields for name, lead source, lead status, and rating.


The following table lists the Customer's group's rituals, frequency, and Directly Responsible Individual (DRI).

Ritual Frequency Description DRI
Overnight customer feedback Daily Check Slack for customer feedback that occurred outside of usual business hours. Kathy Satterlee
Customer Slack channel monitoring Daily Continuously monitor Slack for customer feedback, feature requests, reported bugs, etc., and respond in less than an hour. Kathy Satterlee
Customer follow-up Daily Follow-up and tag appropriate personnel for follow-up on customer items in progress and items that remain unresolved. Kathy Satterlee
Internal follow-up Daily Go through Fleet's internal Slack channels to check for any relevant new information or tasks from other teams. Kathy Satterlee
Customer voice Weekly Prepare and review the health and latest updates from Fleet's key customers and active proof of concepts (POCs), plus other active support items related to community support, community engagement efforts, contact form or chat requests, self-service customers, outages, and more. Kathy Satterlee
Stand-up Weekly Meet with the Engineering team three to four times a week to share information and prioritize issues. Kathy Satterlee
Customer request backlog Weekly Check-in before the 🗣️ Product Feature Requests meeting to make sure that all information necessary has been gathered before presenting customer requests and feedback to the Product team. Kathy Satterlee
🗣️ Product Feature Requests Weekly Present and advocate for requests and ideas brought to Fleet's attention by customers that are interesting from a product perspective. Kathy Satterlee
Customer meetings Weekly Check-in on how product and company are performing, provide updates on new product features or progress on customer requests. These are private meetings with one meeting for each individual commercial customer. Kathy Satterlee
Release announcements Every three weeks Update customers on new features and resolve issues in an upcoming release. Kathy Satterlee
Sales huddle Weekly Agenda: Go through every open opportunity and update the next steps. Alex Mitchell
Salesforce contributor experience checkup Monthly Make sure all users see a detailed view of contacts, opportunities, accounts, and leads. Nathan Holliday
Lead pipeline review Weekly Agenda: Review leads by status/stage; make sure SLAs are met. Alex Mitchell
Dripify review Daily Review responses to Dripify sequencing, respond to standard messages, escalate urgent messages in #help-CEO. Brad Macdowall

Slack channels

The following Slack channels are maintained by this group:

Slack channel DRI
#g-customer-experience Zay Hanlon
#fleet-at-* (customer channels) Kathy Satterlee
#g-sales Alex Mitchell
#_from-prospective-customers Alex Mitchell