Remove mailto:support@statsig.com links and standardize support/Slack references#3969
Conversation
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
xhuang-statsig
left a comment
There was a problem hiding this comment.
apply updates consistently across all instances; replace any hardcoded support@statsig.com
|
|
||
| <Info> | ||
| For gates with 0% or 100% rollout, by default we don't forward exposure to your warehouse. If you need them, please contact our [support team](mailto:support@statsig.com), your sales contact, or via our slack channel. | ||
| For gates with 0% or 100% rollout, by default we don't forward exposure to your warehouse. If you need them, please contact our support team, your sales contact, or via our slack channel. |
There was a problem hiding this comment.
for all instances of via our slack channel.
change to our Slack community
guides/migrate-from-mixpanel.mdx
Outdated
| If you're unsure how to approach Mixpanel migration, please reach out to our team. We have worked with other Mixpanel customers in the past to help them switch over to Statsig. | ||
|
|
||
| We're always happy to discuss your team's individual needs or any other question you have - drop us a line at [support@statsig.com](mailto:support@statsig.com) or reach out on our [slack community](https://statsig.com/slack). | ||
| We're always happy to discuss your team's individual needs or any other question you have - drop us a line at support@statsig.com or reach out on our [slack community](https://statsig.com/slack). |
There was a problem hiding this comment.
all instances - remove drop us a line at support@statsig.com
replace with reach out to our support team, your sales contact, or via our slack community
guides/migration-overview.mdx
Outdated
| ## Get Help | ||
|
|
||
| Our team has helped many customers move off other tools so that everything is in Statsig. For tailored guidance, contact [support@statsig.com](mailto:support@statsig.com) or join our [slack community](https://statsig.com/slack). | ||
| Our team has helped many customers move off other tools so that everything is in Statsig. For tailored guidance, contact support@statsig.com or join our [slack community](https://statsig.com/slack). |
There was a problem hiding this comment.
replace contact support@statsig.com or join our slack community.
with
reach out to our support team, your sales contact, or via our slack community
…k community consistently Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Description
Removes all
mailto:support@statsig.commarkdown hyperlinks and standardizes support contact language across 23+ doc files:[support team](mailto:support@statsig.com)→support teamdrop us a line at support@statsig.comandcontact support@statsig.comwithreach out to our support team, your sales contact, or via our [Slack community](...)via our slack channelwithvia our [Slack community](https://statsig.com/slack)Post-change grep confirms zero remaining
mailto:support@statsig.comreferences and zero remaining unlinked "slack channel" references.Human Review Checklist
access-management/guide.mdxstill uses[Slack channel](pre-existing link, not changed) — confirm if this should also become[Slack community]access-management/projects.mdxlinks tohttps://statsig.com/communityinstead ofhttps://statsig.com/slack— pre-existing, confirm if intentionalBest practice checklist
Questions?
Reach out to Brock, T̶o̶r̶e̶,̶ or Logan on Slack!
Link to Devin run | Requested by: @xhuang-statsig