Skip to content

Commit d536b06

Browse files
committed
Update Contact Us page to mention support for paid customers
1 parent 6fb6460 commit d536b06

File tree

1 file changed

+19
-4
lines changed

1 file changed

+19
-4
lines changed

resources/contact-us.mdx

Lines changed: 19 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,16 +2,31 @@
22
title: "Contact Us"
33
---
44

5-
### Found a bug or need help?
5+
## Need help or have questions?
6+
7+
### Discord community
68

79
Join our [Discord](https://discord.gg/powersync) server where you can browse topics from our community, ask questions, share feedback, or just say hello :)
810

11+
12+
### Support for Pro, Team & Enterprise customers
13+
14+
If you are a customer on our Pro, Team or Enterprise (Cloud or Self-Hosted) [plans](https://www.powersync.com/pricing), you can contact us using the support details provided to you during onboarding.
15+
16+
You are also welcome to use our [Discord](https://discord.gg/powersync) community for questions, but please note that [support SLAs](https://www.powersync.com/legal/commercial-license-and-services-agreement#appendix-c) (Team and Enterprise plans) are not available for Discord support.
17+
18+
19+
## Found a bug?
20+
921
Bugs can be logged as [GitHub issues](https://github.com/powersync-ja) on the respective repo.
1022

11-
### Feedback or ideas?
1223

13-
[Submit an idea](https://roadmap.powersync.com/tabs/5-roadmap/submit-idea) via our public roadmap or [schedule a chat](https://calendly.com/powersync/powersync-chat) with someone from our product team.
24+
## Feedback or ideas?
25+
26+
* [Submit an idea](https://roadmap.powersync.com/tabs/5-roadmap/submit-idea) via our public roadmap
27+
* Or [schedule a chat](https://calendly.com/powersync/powersync-chat) with someone from our product team.
28+
1429

15-
### Pricing or commercial questions?
30+
## Pricing or commercial questions?
1631

1732
Please [shoot us an email](mailto:[email protected]) to get in touch.

0 commit comments

Comments
 (0)