[ketanyekale]

Summary

www.cometchat.com/contact and www.cometchat.com/support both return 404, and the docs link to them from 12 places on 10 pages. This PR sends each link to the right place based on what the reader needs:

Sales — https://www.cometchat.com/contact-sales, labelled "the CometChat team" (higher limits, premium features)

• moderation/constraints-and-limits.mdx (note + card)
• notifications/badge-count.mdx (premium-feature note + troubleshooting row)
• rest-api/moderation-apis/overview.mdx

Support — https://help.cometchat.com/hc/en-us, labelled "CometChat Support" (troubleshooting, integration questions; same link the public SDK/UI Kit READMEs use)

• ui-kit/flutter/v5/guide-overview.mdx
• ui-kit/flutter/v5/troubleshooting.mdx
• widget/{shopify,squarespace,webflow,wix,wordpress}/integration.mdx

Links that already point to /contact-sales are unchanged.

Test plan

• No bare cometchat.com/contact or /support links remain (git grep)
• /contact-sales returns 200; help.cometchat.com/hc/en-us loads in a browser

🤖 Generated with Claude Code

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
cometchat	🟢 Ready	View Preview	Oct 20, 2026, 4:03 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

[jitvarpatil]

Approving — small, correct, and complete

✅ Verified

• The old links really are broken: www.cometchat.com/contact and /support both return 404, and so does the non-www cometchat.com/contact.
• Sales target works: www.cometchat.com/contact-sales returns 200.
• Support target works in a real browser. Worth noting for anyone who re-checks with a script: help.cometchat.com/hc/en-us returns 403 to curl, which looks like a dead link — but it loads normally in a browser (CometChat Help Center, with a Submit a request path). The 403 is bot protection, so "loads in a browser" was exactly the right test.
• Nothing left behind: main has 12 matches across URL variants (with/without www, trailing slash, anchors, query strings) — matching the "12 places on 10 pages" in the description — and this branch has 0.

✅ The routing is the right call

• Sales for limits and premium features (moderation constraints, the badge-count premium note, the moderation API overview) — those readers need a commercial conversation.
• Support for troubleshooting and integration (the Flutter v5 guides and the five widget integration pages) — those readers need help, and the Help Center's request form is where that happens.

Sending a "raise my limit" reader to support, or a "my widget won't load" reader to sales, is the quiet way a link fix goes wrong; this split avoids both.