Skip to content

Conversation

gstout52
Copy link
Contributor

@gstout52 gstout52 commented Sep 2, 2025

Summary

  • Add new troubleshooting section for customer queries about summer 2025 pricing changes
  • Document TRYSTARTER coupon benefits and usage details
  • Include comprehensive timeline of customer notifications for both Starter and Free users
  • Detail changes to Starter tier resource allocation and improvements

Test plan

  • Review support section content for accuracy and completeness
  • Verify formatting matches existing troubleshooting sections

🤖 Generated with Claude Code

- Add new troubleshooting section for customer queries about pricing changes
- Document TRYSTARTER coupon details and benefits
- Include customer notification timeline for Starter and Free users
- Detail Starter tier changes (instances and resource improvements)

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>
@gstout52 gstout52 requested a review from knolleary as a code owner September 2, 2025 19:53
@joepavitt joepavitt changed the title Add summer 2025 pricing and tier changes support section Support Playbook: Add summer 2025 pricing and tier changes support section Sep 3, 2025
gstout52 and others added 2 commits September 4, 2025 15:43
Add additional context about TRYSTARTER coupon and annual billing discount to help support team assist customers with pricing questions.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>
@knolleary
Copy link
Member

Wary of including a coupon in the handbook as it is now publicly disclosed and available for anyone to make use of. It would be better to store coupons in 1Password, or link to them in stripe dashboard to prevent unintended disclosure.

@gstout52
Copy link
Contributor Author

Wary of including a coupon in the handbook as it is now publicly disclosed and available for anyone to make use of. It would be better to store coupons in 1Password, or link to them in stripe dashboard to prevent unintended disclosure.

Good catch. Revised accordingly.

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.

3 participants