Why it matters
Most community platforms leave support to email or a separate tool.
When your members hit a problem, where do they go? On most community platforms, the answer is an email address, a contact form, or a completely separate help desk product with its own login, its own branding, and its own subscription fee.
mobieusHelp changes that equation. The help desk lives inside the same tenant as the community. Members use the same account. Staff see the same member profiles. Tickets carry the same identity context as forum posts and course enrollments. No more cross-referencing email addresses across disconnected systems.
What the help desk actually includes
mobieusHelp handles everything from simple member questions to multi-department enterprise support workflows.
Ticket management
Every support request becomes a ticket with a unique ID, status lifecycle (open, in progress, answered, closed), priority level, assignment, and full conversation history. Staff can add internal notes that members never see, attach files, and reference previous tickets. The ticket view shows the complete interaction timeline so any agent can pick up where another left off.
SLA plans
Create unlimited SLA plans that define expected response and resolution times. Assign SLAs at the department, help topic, or ticket filter level. When a ticket approaches its SLA deadline, the system escalates with priority alerts and overdue notifications. Transient SLAs let you override timing when a ticket transfers between departments or changes help topics.
Multi-department routing
Set up departments for billing, technical support, onboarding, moderation, or any workflow your community needs. Tickets route to the right department automatically based on help topic selection, email address, or filter rules. Agents can work across multiple departments with department-specific roles and permissions. The refer function lets agents share ticket visibility across departments without transferring ownership.
Automation and ticket filters
Define rules that trigger on ticket creation or update. Conditions can match on email address, help topic, subject keywords, custom field values, or source channel. Actions include: auto-assign to a specific agent or team, set priority, apply an SLA plan, reject the ticket, send a canned response, or route to a department. Filters run in order, so you can build layered workflows that handle common patterns before a human touches the ticket.
Knowledge base
Build a searchable library of help articles that members can browse before opening a ticket. Articles can be public-facing (self-service) or internal-only (agent reference). Organize by category and topic. When a member searches for help, relevant articles surface before the ticket form, reducing ticket volume for common questions.
Canned responses
Pre-write replies for frequently asked questions and common workflows. Canned responses support dynamic variable substitution (member name, ticket ID, community name) and can include file attachments. Scope them globally or per-department. Agents select a canned response, customize it if needed, and send in seconds instead of retyping the same answer.
Custom fields and forms
Define custom fields for tickets (text, textarea, dropdown, checkbox, radio, date). Link forms to specific help topics so the right questions appear when a member selects "Billing question" vs. "Technical issue." Custom fields are searchable, filterable, and available in automation rules. Internal-only fields let staff track data that members never see.
Customer self-service portal
Members can submit tickets, check status, view history, and search the knowledge base from a branded portal. They sign in with their existing community account. No separate registration. The portal shows open tickets, archived tickets, and relevant help articles so members can help themselves before escalating.
Email integration
Accept tickets via email with two integration methods. Email piping delivers tickets in real time as they arrive. POP3/IMAP polling checks the mailbox on a schedule. Both methods support auto-routing to departments based on the receiving email address. Members can reply to ticket emails, and the reply threads into the existing ticket conversation.
Agent collision prevention
When two agents open the same ticket simultaneously, the system prevents them from sending conflicting responses. Ticket locking ensures that only one agent drafts a reply at a time. This prevents the embarrassing "two different people answered your question with two different answers" scenario that plagues shared-inbox setups.
The plugin and extension ecosystem
The support platform behind mobieusHelp has a mature plugin architecture. Extensions are available for authentication, integrations, storage, and workflow enhancements. Tenant admins on Sovereign can request specific plugins for their deployment.
Notable extensions include:
- LDAP and Active Directory. Authenticate agents and members against your organization's directory. Supports multiple domains and attribute syncing.
- OAuth authentication. Generic OAuth provider support for single sign-on with external identity systems.
- Slack integration. Send ticket notifications to Slack channels so your team sees new tickets, updates, and assignments without leaving their chat workflow.
- S3 attachment storage. Store ticket attachments in Amazon S3 instead of local disk for organizations with large attachment volumes or compliance requirements.
- Password policy management. Enforce password complexity, expiration, and reuse rules for staff accounts.
How it fits the community
The key difference between mobieusHelp and a standalone help desk is identity continuity. When a member opens a support ticket, the agent sees the same profile that appears on forums, courses, knowledge base articles, and messaging. The agent knows the member's role, their community activity, their course enrollments, and their subscription status without switching to another system.
This is not just a convenience. It is the difference between "I see your email address" and "I see your entire relationship with this community."
Who it is for
Creators with paid communities
Handle member billing questions, access issues, content requests, and onboarding problems from inside the community instead of a disconnected inbox.
Organizations with member networks
Run structured support workflows with departments, SLAs, escalation rules, and custom forms for member services, IT, HR, or partner support.
Agencies managing multiple communities
Each tenant gets its own help desk with its own branding, its own departments, and its own SLA configuration. No cross-tenant data leakage.
Pricing and availability
| Tier | Help desk | Agents |
|---|---|---|
| Starter | Not included | N/A |
| Pro | Included | Unlimited |
| Creator Plus | Included | Unlimited |
| Sovereign | Included + API access | Unlimited |
There is no per-agent fee. Every Pro, Creator Plus, and Sovereign tenant gets the full help desk with unlimited agents, unlimited tickets, and unlimited SLA plans.
mobieusHelp and mobieusLearn are the two products included together from Pro. If you also teach or certify members, the mobieusLearn deep dive covers how the LMS fits the same community.