Support & feature requests
Two tabs, grouped together under Help in the Settings nav: a real two-way support ticket system, and a shared feature request board. API key and webhook management used to live on this page too — they now have their own pages, API keys and Webhooks, under the Developer group instead.
On this page
Support
A ticketing system: a list of your tickets, a new-ticket form, and a reply thread per ticket.
Support Tickets
New ticketReply thread stopped matching after client renamed subject
In ProgressBug · #a1b2c3d4 · 2 replies
A new ticket needs a Subject, a Category (Bug, Billing, Account, Deliverability, or Other), and a Description — no file attachments. Submitting shows "Ticket submitted — we'll respond within 24 hours" and opens straight into the ticket's thread. Status is one of Open (green), In Progress (amber), or Resolved (gray). Replying is a real, two-way thread — your replies show as "You", ForgeSend's as "ForgeSend Support" — and replying to a resolved ticket automatically reopens it.
Feature Requests
A shared board where anyone in a workspace can submit ideas and upvote others'.
Per-variant reply-rate breakdown in Analytics
PlannedUI
A new request needs a Title, a Category (UI, API, Integrations, Deliverability, Enrichment, or Other), and a Description. Submitting it auto-upvotes it for your workspace — upvoting is one vote per workspace, not per person. The list sorts by upvote count first, then most-recent as a tiebreaker. Status is one of Submitted, Under Review, Planned, In Progress, Shipped, or Declined; a status change can come with a short note from ForgeSend, shown inline once a request is Planned or further along.
Where to go next
Next: Settings overview