OneClickClawDocs
$

Support Tickets

Last updated: March 2026

When you need help beyond what the documentation or chatbot can provide, you can open a support ticket directly from your dashboard. Our support team (and our AI assistant Jeroen) will respond based on your plan's response time.

Creating a support ticket

To create a new ticket, go to the Support section in your dashboard and click New Ticket. Fill in the following details:

1

Choose a category

Select the category that best describes your issue: Server Issue, Billing, Account, Feature Request, or Other. This helps us route your ticket to the right team.
2

Write a subject and description

Give your ticket a clear subject (minimum 5 characters) and describe the issue in detail (minimum 10 characters). The more context you provide, the faster we can help.
3

Link a server (optional)

If your issue is related to a specific server, select it from the dropdown. This gives our team instant access to your server diagnostics when reviewing the ticket.
4

Attach a file (optional)

You can attach one file (up to 10 MB) to help illustrate the issue. Accepted formats include images (PNG, JPEG, GIF, WebP), documents (PDF, TXT, CSV), and archives (ZIP).

Tip

Before creating a ticket, the form will suggest relevant documentation articles based on your subject. Check if your answer is already available in the docs.

The support inbox

Your support inbox displays all your tickets in a Kanban-style board with three columns:

Support Inbox — Kanban Board

Open

New tickets and tickets awaiting a response from the support team. Yellow status dot.

In Progress

Tickets being actively worked on or awaiting your reply. Blue pulsing dot.

Resolved

Completed tickets that have been closed. Green status dot.

Each ticket card shows the ticket number, subject, a short preview of the description, the category badge, and when it was last updated. If there is an unread reply, a blue pulsing dot highlights the card.

Jeroen: your AI support assistant

When you create a ticket, our AI support specialist Jeroen will review your issue and send an initial response within a few minutes. Jeroen has full knowledge of the OneClickClaw platform and can help with most common questions about server setup, billing, channels, and troubleshooting.

  • Fast first response: Jeroen typically replies within 2 minutes of ticket creation.
  • Context-aware: If you linked a server to your ticket, Jeroen can see your server diagnostics, subscription plan, and active configuration.
  • Human handoff: If your issue requires human attention, a team member will follow up. Jeroen never blocks you from reaching a human.

Note

Jeroen only responds if a human team member has not already replied. Once a human responds, Jeroen steps back and the conversation continues with the support team.

Ticket conversation

Click any ticket to open its full conversation thread. You will see all messages in chronological order, with clear labels showing who sent each message. You can reply directly from the thread, attach additional files, and see the current ticket status and priority.

You can also close a ticket when your issue is resolved, or reopen it if the problem comes back.

Response times by plan

Response times depend on your subscription tier:

PlanSupport ChannelTarget Response Time
StarterAI Chat (25 credits/mo)48 hours
HobbyistAI Chat (25 credits/mo)24 hours
ProAI Chat (25 credits/mo)4 hours

All plans receive Jeroen's AI-powered first response within minutes. The response times above refer to human follow-up when needed. Pro tier tickets are automatically elevated to high priority.

Tips for faster resolution

  • Be specific: "My Telegram bot stopped responding at 14:00 today" is much more helpful than "bot broken."
  • Link your server: This gives the support team instant access to diagnostics without back-and-forth.
  • Include screenshots: A screenshot of the error message or unexpected behavior saves a lot of explanation.
  • Check the docs first: Many common issues are covered in the FAQ and troubleshooting articles.