Support & Report a Problem

Path: Sidebar → Support section · Permission: All roles

FRENZY.BOT includes built-in support tools so you can get help, browse documentation, and report problems — all without leaving the dashboard.

At the bottom of the dashboard sidebar, you'll find a dedicated Support section with three options:

Option	What it does
Documentation	Opens the official FRENZY.BOT documentation site (docs.frenzy.bot) in a new tab. This is the guide you're reading now.
Help / Open Ticket	Opens the FRENZY.BOT support portal where you can submit a support ticket, track existing tickets, and browse your ticket history.
Report a Problem	Opens a quick in-dashboard form to report bugs, request features, or flag any issue — without leaving your workflow.

The first two options open external links in a new browser tab. Report a Problem opens a modal dialog inside the dashboard.

Report a Problem

The Report a Problem feature lets you send a structured problem report directly to the FRENZY.BOT support team via email. It's designed to be fast — describe the issue, pick a category, and hit send.

How to access it

Look at the sidebar on the left side of the dashboard.
Scroll down to the Support section (near the bottom, below System Logs).
Click Report a Problem.
A modal dialog will appear over the current page.

Filling out the form

The report form has three fields:

Subject

A short, descriptive title for your issue. This becomes the email subject line and helps the support team triage quickly.

Good examples:

"Widget not loading on checkout page"
"WhatsApp messages delayed by 5+ minutes"
"Feature request: export leads to CSV"

Avoid vague subjects like:

"Help"
"Something is wrong"
"Question"

Message

Describe the problem in detail. The more context you provide, the faster the support team can diagnose and resolve it.

What to include:

What happened — Describe the behavior you observed.
What you expected — What should have happened instead.
Steps to reproduce — How can the support team see the same issue? (e.g., "Go to Settings → Branding → Change logo → Click Save → Logo reverts")
When it started — Did it just start? After a settings change? After an update?
Error messages — Copy any error text you see in the dashboard or browser console.

Check the Activity Logs first

Before reporting, check Activity Logs in the sidebar for recent error entries. Including the error message from the logs in your report dramatically speeds up resolution.

Sending the report

Click the Send Report button. The button will show a loading spinner while the report is being submitted. Once sent:

A success toast notification appears confirming the report was delivered.
The form clears automatically.
The modal closes.

If the email fails to send (e.g., SMTP is not configured on the server), an error toast will appear. In that case, use the Help / Open Ticket link instead to submit your issue through the support portal.

What happens after you submit

Your report is sent as a formatted email to the FRENZY.BOT support team. The email automatically includes:

Field	Description
Reporter	Your name (from your dashboard user profile).
Email	Your email address (for follow-up replies).
Bot ID	The currently active bot — so the team knows which workspace is affected.
Server	The server hostname — helps identify the specific installation.
Category	The category you selected.
Subject & Message	Your description of the problem.

Reply-To is set automatically

If your user profile has an email address, the support team can reply directly to you. Make sure your email is set correctly in your user profile.

When to use each support channel

Situation	Recommended channel
Quick bug report or feature idea	Report a Problem (in-dashboard form)
Complex issue needing back-and-forth	Help / Open Ticket (support portal)
Looking up how a feature works	Documentation (this site)
Urgent or time-sensitive issue	Help / Open Ticket + mark as high priority
Server is completely down / dashboard won't load	Help / Open Ticket from any device (doesn't require dashboard access)

Troubleshooting the report form

Report fails with "Failed to send report"

The server's SMTP (email) settings may not be configured. Ask your system administrator to verify SMTP settings under Settings → Integrations or the server's .env file.
As a workaround, use the Help / Open Ticket link to submit via the web portal instead.

I don't see the Support section in the sidebar

Scroll down — it's at the very bottom of the sidebar navigation, below all other menu items.
If your sidebar is collapsed, click the expand arrow or hover to reveal the full menu.

I submitted a report but haven't heard back

Reports are delivered by email. Check your inbox (and spam folder) for a reply.
If it's been more than 24 business hours, follow up via the Help / Open Ticket portal.

FAQ

Q: Is there a limit to how many reports I can send?

No. Send as many as you need. However, grouping related issues into a single detailed report is more effective than sending multiple short ones.

Q: Can other users on my team send reports?

Yes. The Report a Problem feature is available to all dashboard users regardless of their role or permission level.

Q: Does the report include screenshots?

The current version is text-only. If you need to attach screenshots, use the Help / Open Ticket portal which supports file attachments, or include a link to a screenshot hosted elsewhere (e.g., a shared drive or image hosting service).

Q: Will my report include sensitive data?

The report includes your name, email, bot ID, and server hostname — no passwords, API keys, or conversation data. The message body contains only what you type.

Category	When to use it
Bug / Something Broken	A feature that was working before is now broken, or something behaves unexpectedly.
Feature Request	You'd like a new capability or an improvement to an existing feature.
Billing & Account	Questions about your subscription, invoices, plan limits, or account access.
Integration Issue	Problems with integrations — Telegram, email notifications, webhooks, n8n, or any connected service.
Performance / Speed	The bot, widget, or dashboard feels slow. Response times are higher than expected.
Other	Anything that doesn't fit the categories above.