Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating Support goals to reflect Q1 goals #10122

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

abigailbramble
Copy link
Contributor

Updated goals to reflect our discussion around Q1 goals

Updated Q1 goals
Copy link

vercel bot commented Dec 12, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
posthog ✅ Ready (Inspect) Visit Preview Dec 12, 2024 11:28am

contents/teams/support/objectives.mdx Outdated Show resolved Hide resolved
- **Rationale:** More experts = fewer escalations
- **What we'll ship:** Issue coming soon
- **We'll know we're successful when:** Everyone is an expert in something and we have a playbook for learning when we hire next.
### Streamline support workflow by implementing features in ZenHog (Haynes)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My approval isn't needed, but as fly-by feedback: I adore this goal. Love that we're building our own tools and that things that originally came out of a hackathon can continue to improve and become more useful!

- **Rationale:** Business as usual = A good start
- **What we'll ship:** [See issue](https://github.com/PostHog/meta/issues/246)
- **We'll know we're successful when:** We're regularly hitting 90% SLA achievement for Normal+ prio tickets. CSAT doesn't fall below 80%.
### Improve efficiency and consistency of how we use Zendesk (Ben)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the only goal I think needs work - I can't tell what we are actually going to do here, as it's still written in quite a vague/corporate kind of way. Could we have a go at making this a bit more specific?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants