docs: add support contact (support@falkordb.com) and Support page#485
docs: add support contact (support@falkordb.com) and Support page#485dragnot wants to merge 1 commit into
Conversation
The docs previously had no instructions for opening a support ticket and never mentioned support@falkordb.com. Cloud tier pages advertise Community/24x7/Dedicated support without telling users how to reach it. - Add new top-level support.md page (nav_order 1000) with the support email, what to include in a ticket, Discord for community help, and info@falkordb.com for sales/general inquiries. - Add a 'Getting Support' section linking to support@falkordb.com on each cloud tier page (free, startup, pro, enterprise). More tier-specific SLA details to be added in a follow-up. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
📝 WalkthroughWalkthroughThis PR adds a centralized support documentation structure. A new ChangesSupport Contact Documentation
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
support.md (1)
31-31: 💤 Low valueEnsure file ends with newline.
Standard practice for text files is to end with a newline character. This helps with version control diffs and some tooling.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@support.md` at line 31, Add a trailing newline character at the end of support.md so the file ends with a single newline; open support.md and ensure the final line is terminated with "\n" (no other content changes required).
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@support.md`:
- Line 26: Update the Discord invite link text "https://discord.gg/ErBEqN9E" in
the support page to point to a non-expiring (permanent) invite; open the server
settings in Discord, create a new invite with "Never" expiration and optionally
enable a max number of uses, then replace the existing invite URL in the support
content with the newly generated permanent invite URL and verify the link
resolves.
---
Nitpick comments:
In `@support.md`:
- Line 31: Add a trailing newline character at the end of support.md so the file
ends with a single newline; open support.md and ensure the final line is
terminated with "\n" (no other content changes required).
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 3953e7cd-c74b-45e5-84e8-5c027a4dac66
📒 Files selected for processing (5)
cloud/enterprise-tier.mdcloud/free-tier.mdcloud/pro-tier.mdcloud/startup-tier.mdsupport.md
|
|
||
| ## Community Support | ||
|
|
||
| For general questions, usage help, and discussion, join the FalkorDB community on **[Discord](https://discord.gg/ErBEqN9E)**. |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Verify the Discord invite link is accessible
curl -sL -w "%{http_code}" -o /dev/null "https://discord.gg/ErBEqN9E"Repository: FalkorDB/docs
Length of output: 60
Ensure the Discord invite link is configured to never expire.
The Discord link (https://discord.gg/ErBEqN9E) is currently accessible. However, ensure it is set to never expire in the Discord server settings to maintain reliable access in the documentation.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@support.md` at line 26, Update the Discord invite link text
"https://discord.gg/ErBEqN9E" in the support page to point to a non-expiring
(permanent) invite; open the server settings in Discord, create a new invite
with "Never" expiration and optionally enable a max number of uses, then replace
the existing invite URL in the support content with the newly generated
permanent invite URL and verify the link resolves.
1 participant
Summary
The docs currently have no instructions for opening a support ticket, and
support@falkordb.comis not mentioned anywhere. The cloud tier pages advertise Community / 24/7 / Dedicated support but never tell readers how to actually reach support. This PR closes that gap.Changes
support.md(nav_order 1000, permalink/support/) — single source of truth for support contact:support@falkordb.com).info@falkordb.comfor sales / general inquiries.cloud/free-tier.md,cloud/startup-tier.md,cloud/pro-tier.md,cloud/enterprise-tier.md— added a short "Getting Support" section to each tier page with the support email and a link to the new Support page. Pro and Enterprise sections call out their support level (24/7 and Dedicated).Tier-specific SLAs and additional details will be added in a follow-up PR.
Testing
N/A — documentation-only change. No code, build, or test impact.
Memory / Performance Impact
N/A.
Related Issues
None.
Summary by CodeRabbit