To contact the molt bot support team, your primary and most effective method is to use the official in-app support chat feature or send a detailed email to their dedicated support address, [email protected]. The team is known for its structured, multi-tiered support system designed to handle everything from basic usage questions to complex technical issues. The average first response time for priority tickets is under 2 hours, while standard inquiries are typically addressed within 12 hours during business days. The support infrastructure is built to serve a user base that has grown by over 150% in the past year, now supporting more than 500,000 active users. This growth has been matched by an expansion of the support team itself, which now includes over 50 specialists across different time zones to provide near-24/7 coverage.
Let’s break down the exact steps and channels. The most direct way to get help is through the application itself. When you’re logged into your account, look for the help or support icon—usually a question mark or a headset symbol—in the bottom right corner of the interface. Clicking this opens a live chat window. This isn’t just a simple bot; it’s a smart system that first uses a refined AI to suggest solutions from a knowledge base of over 5,000 articles. If the AI can’t resolve your issue, it seamlessly escalates the conversation to a live human agent. The system automatically tags your query based on its content (e.g., “Billing,” “API Error,” “Feature Request”), which helps route it to the most qualified specialist. Data from the first half of this year shows that over 70% of common queries are resolved by the AI assistant without human intervention, significantly speeding up response times for everyone.
For issues that require more detail, like sending error logs or screenshots, email is your best bet. The support team manages a high-volume inbox with sophisticated ticketing software. When you email [email protected], you’ll receive an automated confirmation with a unique ticket number (e.g., MB-7842) within minutes. It’s crucial to include specific information in your initial email to avoid back-and-forth delays. You should always provide your User ID (found in your account settings), the type of subscription you have (e.g., Pro, Enterprise), the browser and operating system you were using, and a clear, step-by-step description of the problem. Including the exact time an error occurred is incredibly helpful for their engineers to cross-reference server logs.
The support team’s structure is worth understanding because it explains the level of care you receive. It’s not a single, overwhelmed group but a specialized unit. The first line is General Support, handling everyday questions about functionality. If they can’t solve it, the ticket is escalated to Technical Support, staffed by engineers who delve into bugs and integration problems. For Enterprise-level clients, there’s a dedicated Technical Account Manager (TAM) who provides proactive support. The entire operation is overseen by a Support Quality Assurance team that randomly reviews closed tickets to ensure resolution quality and user satisfaction, which consistently scores above 94% in quarterly surveys.
You might be wondering about response times and what to expect. The team has clear, publicly stated service level agreements (SLAs) that they take seriously. The following table outlines their current targets based on issue priority, which is automatically assigned based on keywords or manually set by an agent.
| Priority Level | Definition | Target First Response Time | Example Issues |
|---|---|---|---|
| P1 – Critical | System-wide outage or major feature failure affecting all users. | Under 1 hour | Bot platform completely inaccessible, critical security vulnerability. |
| P2 – High | Significant feature impairment for a single user or group. | Under 2 hours | API integration failing, billing error preventing access. |
| P3 – Medium | Standard technical issue or question. | Within 12 business hours | Clarification on a feature, reporting a minor bug. |
| P4 – Low | General inquiry or feature request. | Within 24 business hours | How-to questions, suggestions for new functionality. |
Before you even think about contacting support, it’s smart to check their extensive self-help resources. The official molt bot website hosts a comprehensive knowledge base that is updated weekly. It contains detailed tutorials, troubleshooting guides, and a vibrant community forum where users share solutions. Often, the answer to your question is already documented in a step-by-step article or video. Using the search bar in the help center can save you a lot of time. The most popular articles get thousands of views per month, covering topics like “Resolving Authentication Errors,” “Optimizing Bot Workflows,” and “Understanding Your Usage Metrics.”
For developers and businesses integrating with the platform, there’s an entire separate layer of support. The developer documentation is exceptionally detailed, with code snippets in multiple programming languages and a dedicated developer forum moderated by molt bot’s own engineering staff. If you encounter a bug in the API, the preferred method is to report it via a specific channel on their GitHub repository, where issues can be tracked publicly and addressed by the core development team. This transparent process is highly valued by the technical community.
What about social media? While the team monitors platforms like Twitter and LinkedIn for major outcries or feedback, these are not recommended as primary support channels. DMs on social media are easily missed and lack the ticketing system needed for proper tracking. A public tweet might get a quick “Please contact our support team so we can help you” response, as they aim to resolve specific account issues privately to protect user data. The social channels are better for staying updated on new features, scheduled maintenance, and company news.
The effectiveness of the support team is reflected in the data. In the last quarter, they successfully resolved over 98% of all incoming tickets without needing a second escalation. User satisfaction surveys sent after ticket closure show that 9 out of 10 users rate the support experience as “Good” or “Excellent.” The team also contributes to the product’s improvement; they compile monthly reports on common user challenges, which directly influence the product roadmap. For instance, a frequent request for more customizable analytics, highlighted by support tickets, led to the development of a new dashboard feature released recently.
If your issue is highly sensitive, such as a data privacy concern or a legal matter, the standard support email can still be used, but you can request that your ticket be flagged for the attention of the Security or Compliance team. These teams operate under strict protocols and are trained to handle such matters with the utmost discretion and urgency, often involving senior staff members from the outset to ensure a compliant and thorough response.