Multi-Subdomain Routing for core QB Features (help / support / feedback)

:rocket: The Problem

Quackback brilliantly combines a Help Center, a Support Inbox, and Feedback Boards. However, forcing us to choose a single subdomain to host it (e.g., only help.domain.com or only feedback.domain.com) compromises the user experience:

• Frustrated users looking for a support ticket on a feedback.yourdomain.com URL is confusing.
• Users wanting to upvote the roadmap on a support. or help. subdomain is similarly unintuitive.

:bulb: The Solution

Allow a single Quackback instance / workspace to map multiple subdomains to specific QB modules as entry points:

• help.yourdomain.com ➔ Routes directly to the Knowledge Base / Help Center.
• support.yourdomain.com ➔ Routes directly to the Ticket Submission Form.
• feedback.yourdomain.com ➔ Routes directly to the public Feature Voting & Roadmap.

:glowing_star: Why This Adds Value

• Enterprise UX: Matches industry standards by sending users exactly where their intent dictates.
• The Ultimate All-in-One: Completely replaces the need to run separate, fragmented tools (like Zendesk + Canny) just to get the right URLs.