Help lives in exactly one place
ForgeFeed is supported through its Discord server and nowhere else. There is no support inbox and no contact form. Spend two minutes on the checklist below and your first reply will answer your actual question.
Discord, and only Discord
No support email, no contact form, no ticket portal. Every question, bug report, and billing query is handled in the ForgeFeed Discord server.
Threads, not DMs
Ask in the public help channel so the answer is searchable. Direct messages are not monitored, and staff will never DM you first.
Best effort, UK hours
A small team, not a staffed helpdesk. Most threads get a first reply within a day, and Pro and Studio servers are triaged first.
Four checks that save you a day
Most support threads are answered by something already written down. Working through these in order is the fastest route to a fix, even before anyone replies.
- 1
Check the docs
Setup, every slash command, and the permissions each one needs are documented. Most questions are answered by the linking walkthrough or the command reference.
- 2
Read the FAQ and changelog
The FAQ covers pricing, private repositories, channel routing, and removal. The changelog lists what shipped recently, which often explains a change in behaviour.
- 3
Re-run the command
Configuration replies are private to you and include the reason a command failed. Run it again and read the response in full before reporting it.
- 4
Then post in Discord
Open a thread in the help channel with the details below. Public threads mean the next person with the same problem finds the answer.
What to put in the thread
A report with these six things usually gets a fix on the first reply. A report without them gets six follow-up questions.
- The exact slash command you ran, including the options you picked
- What you expected to happen and what actually happened
- The repository owner and name, and whether it is personal or an organization
- Roughly when it happened, with your timezone
- A screenshot of the bot's reply, with anything private cropped out
- Your plan: Free, Pro, or Studio
Never paste a secret into the server. ForgeFeed does not need a GitHub password, a personal access token, a Discord token, or card details, and no one on the team will ever ask for one. Crop screenshots before you upload them, and report anyone who asks.
Commit embeds stopped posting yesterday, everything else still works.
Command: /postcommits on acme/webstore (org) into #dev-activity
Expected: an embed on every push. Got: nothing since 20 Aug, ~09:00 BST. PR embeds in the same channel are fine.
Plan: Studio. Screenshot of the reply attached.
Open a thread in the ForgeFeed Discord
The invite below joins the Digital Den community server, which is where ForgeFeed is built and supported. Head to the help channel, start a thread, and include the details above.
Free to join, no account linking required, and you can ask before you install anything.
Not everything belongs in the help channel
Some things have a faster route, and one of them is not ours to handle at all.
Setup and how-to questions
Linking GitHub, registering a repository, choosing channels, or getting a tracker running. Try the docs first, then ask in the help channel.
Read the docsSomething is broken
Missing embeds, a tracker that stopped, a command that errors. Post a thread with the details above and it gets triaged in the order it arrives.
Feature requests
Suggestions go in the ideas channel so other people can weigh in. What is already planned is listed on the changelog page.
See what is plannedBilling, refunds, and cancellations
Pro and Studio are Discord server subscriptions. Discord takes the payment and owns the refund, so billing has to be handled through Discord Support, not through us.
How the plans workSecurity disclosures
Found a vulnerability? Do not post it publicly. Open a thread asking for a private channel and a maintainer will move it out of view.
Security & privacyData and privacy requests
Deletion and access requests are handled in the support server by a maintainer. What is stored and for how long is set out in the privacy policy.
Privacy policyHow support actually works
Yes. The ForgeFeed Discord server is the only support channel. There is no support email address, no contact form, and no ticket portal. Anyone offering one of those is not us.
Support is best effort by a small team in UK time, not a staffed helpdesk with a guaranteed response window. Most threads get a first reply within a day. Pro and Studio servers are triaged first.
No. Direct messages are not monitored and will not get you a faster answer. Post in the help channel so the reply is searchable for everyone else. ForgeFeed staff will never DM you first.
No. Pre-sales questions about plans, permissions, and what ForgeFeed can track are welcome in the support server before you install anything.
Never. ForgeFeed authenticates as a GitHub App and no member of the team will ever ask for a GitHub password, a personal access token, a Discord token, or payment details. Treat any such request as a scam and report it.
Still deciding? Ask before you install.
Pre-sales questions about plans, permissions, and what ForgeFeed can track are welcome in the support server.