Add lead follow up to communications (#17237)

This commit is contained in:
Drew Baker 2024-04-15 21:11:30 -04:00 committed by GitHub
parent 5692598143
commit b45079e261
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -71,6 +71,13 @@ Fleet uses advertising to spread awareness through a broader audience and foster
### Events
It's important for Fleet to engage at [events](https://docs.google.com/spreadsheets/d/1YQXAX2Q_WnGkAwMYjMbQpV3nbCj7gOBbv7Y0u4twxzQ/edit#gid=1931288160). This provides an opportunity to directly engage with potential users and contributors, build relationships, gather feedback, and create a stronger sense of community and trust.
#### Event lead follow-up
Eventgoers are expecting a timely follow-up from Fleet based on the conversations that they had at the event. It is up to Head of Demand to make sure this process is followed.
1. Once a list of badge scans is available, Fleeties that attended the event are to add any follow up notes that note buying situation, amount of endpoints, level of interest, and general talking points.
2. Within 3 business days of returning from the event, attendees will set up a debrief meeting with the demand team to discuss follow-up.
3. Demand will determine appropriate follow-up to each potential lead, and sales will be notified of actions needed immediately following.
### Podcast
Fleet has created the [ExpedITioners podcast](https://expeditioners.podbean.com/) to open discussions and help IT and security professionals get ahead of the curve and prepare themselves and their organizations for what lies ahead.
<!-- TODO: Find a way to link to the meetings section below and make it make sense-->