mirror of
https://github.com/empayre/fleet.git
synced 2024-11-06 17:05:18 +00:00
0ea4972920
* uncomment handbook route, disable redirect, add link to top nav * Handbook page, note: most of this is directly copied from the docs, build handbook * added maintainer <meta> tags * handbook styles * handbook broken up into different files * update handbook layout * updating markdown files * handbook layout, adjusted header margins to make room for handbook * handling links to specific sections in markdown compilation * lint fixes * commented out search bar for now * cleaned up page script * update handbook and clean up styles * Delete handbook.md * updated product content from latest version * clean up styles, remove hardcoded image widths * markdown updates * title and description for /handbook, removed commented out route * fix styles on firefox, remove commented logs * lint fix * update class name * fix broken link * updated how hashes are handled in links, adjusted links in handbook * lint fix * updated function names, removed comments, small markdown syntax fix * move handbook link into footer
1.3 KiB
1.3 KiB
Customer succcess
Next steps after a customer conversation
After a customer conversation, it can sometimes feel like there are 1001 things to do, but it can be hard to know where to start. Here are some tips:
For customer requests
- Locate the appropriate 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.)
- Is the issue clear 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 is hoping to meet, please note that in the the issue.
- Make sure the issue has a "customer request" label.
- Post in #g-product with a link to the issue to draw extra attention to the customer request so it is visible ASAP for Fleet's product team.
- 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…")