Get help with Abhi
Use this page for setup questions, operational issues, safety reports, and app review contact. Server-specific records are handled inside authenticated support workflows.
Public surface
operations context
Channels
Support routes
Start with the channel that matches the issue. Urgent safety or access problems should include enough context for owner review without exposing secrets.
Ask the community
Fastest for setup, module configuration, command behavior, and Discord permission questions.
Open docs first
Email support
Best for billing, account ownership, private server context, refunds, data requests, or sensitive details.
support@abhi.gg
Report an incident
Use for abuse, unsafe automation, unauthorized access, broken moderation flows, or platform-risk issues.
Include timestamps
Request details
What to include
Clear context helps us separate Discord-side issues, bot runtime issues, billing provider delays, and dashboard configuration mistakes.
Discord server ID and a short description of the affected feature.
Command name, dashboard page, or public URL involved in the issue.
Approximate time of the incident, timezone, and whether it is still happening.
Screenshots with private member data redacted whenever possible.
Discord support server
Discord App Directory publishing requires a support server field in the Developer Portal. Keep that invite pointed to your official support server, and use this page as the durable public support URL.
Before you reach out
A little context saves a lot of back-and-forth.
Abhi support is easier when we can separate Discord permissions, dashboard state, worker delays, and account administration quickly.
Confirm the bot is still in the server and has the expected Discord permissions.
Check whether the issue affects commands, dashboard controls, or both.
Use the public status page to rule out a known incident.
Redact private member data before sharing screenshots.