Give customers a support conversation in the portal and staff a queue with categories, priorities, assignments, private notes and canned replies.

Convert configured inbound support email into tickets or replies. Quarantine unmatched or ambiguous messages for review rather than silently associating them with a customer.

Handle supported ticket attachments through upload, ownership and antivirus scanning checks. Files become downloadable only after the configured scanning workflow accepts them.

Ask service-appropriate questions, show available account checks and suggest useful next steps before escalation. Recorded local state remains distinguishable from an actual remote health check.

Let customers inspect and explicitly attach a bounded, redacted diagnostic summary to a support ticket. Share available evidence without exposing credentials or inventing unavailable logs.

Suggest published articles based on the service, device or problem context while preserving the customer’s ticket draft.

Publish customer help articles and reviewed language variants so routine setup and billing questions can be answered without opening a new ticket.

Show available per-channel reply evidence, including pending, failed or unknown states. A provider accepting a message does not establish that the customer received or read it.

Let customers or staff request a supported translation after explicit review when the feature and AI provider are enabled. Keep the original message visible alongside the translation.

Collect one editable solved or not-solved response on eligible resolved tickets, with an optional comment and staff reporting.

Collect supported usefulness feedback and consented article-to-ticket outcomes so staff can identify help content that needs improvement.

Connect supported community identities, private ticket channels or rooms and two-way conversation relay through configured bridges. Entitlement rules can control supported roles and room grants.

Provide configured pre-sales or support entry points, reusable assistance responses and an inbox for guided conversations.

Add a configured Chatwoot widget to the store and portal for visitor or customer conversations. Account linking uses a one-use code; the supported native relay covers public text rather than private notes or attachments.

Configure Zammad as an alternative support provider when an external ticketing workspace is preferred.

Set support hours, timezone and response targets, calculate deadlines and surface approaching or overdue work in the staff notification workflow.

Escalate unanswered work through configured email rounds and Pushover, alongside supported staff web push. Escalation limits prevent an unbounded series of reminders.

Link permitted tickets to a common incident, review a shared response and track each ticket’s resulting delivery evidence.

Preview eligible ticket selections and status changes, then apply the reviewed scope with per-record outcomes. Staff can also review supported bulk invoice-copy actions.

Publish explicitly authored incident updates in investigating, identified, monitoring or resolved states. A recorded 90-day uptime figure derives from authored major incidents rather than independent monitoring.

Publish customer-facing maintenance context and time windows, with audience preview for the supported reviewed communication workflow.

Offer double-opt-in status notifications and an unsubscribe path, with subscriber checks before supported email delivery.

Let verified customers choose supported email updates for relevant services. Matching published incident scope governs delivery; internal operational alerts are not copied into customer messages.

Display the published service-status context inside a website block so visitors can find incident information from the store.

Publish updates in the portal or through configured email and supported media-app surfaces. Staff can organise audience groups and compose branded custom messages.

Edit supported customer and staff template wording, preview complete emails, send a test and reset defaults. Required sign-in and payment links remain enforced.

Let signed-in customers submit bounded suggestions, vote or withdraw a vote and follow moderated planned or released states. Staff control moderation within their operator.

Manage reusable copy and artwork for websites, announcements and supported media engagement campaigns.

Create supported seasonal schedules on linked media servers, with local timezone inputs and annual scheduling only when the server advertises it.

Author supported dismissible artwork or muted picture-in-picture campaigns for compatible media clients, with scheduling and audience restrictions. Client and server capabilities govern what is rendered.

Connect a configured Anthropic, OpenAI or compatible model endpoint for website and affiliate campaign assistance. Choose the permitted generation and publication autonomy rather than relying on a fixed workflow.

Enable available grounded support assistance and human handoff under configured provider and data controls. It does not execute financial or credential actions for the customer.

Set supported per-feature monthly and per-customer limits, inspect usage and govern parent-funded reseller generation. Provider charges and available models remain external to the platform.

Publish reseller packages alongside service plans. Define available plan grants, credits, commitments, template policy and whether activation is automatic or reviewed.

Review purchased applications, approve or reject eligible reseller lines and recover interrupted activation through a resumable workflow.

Create a reseller workspace and publish its parent-hosted store address after activation. A separate DNS setup is not required for that address; a verified custom domain can be added later.

Give the reseller its own console, business identity and permitted catalogue while preserving the parent’s governance rules.

Let a reseller enter the permitted business workspace from its customer account without maintaining a second independent login.

Track reseller wallet balances, supported credit purchases and daily account-renewal consumption under the configured commercial model.

Record parent-backed consumption, commitments and settlement activity so partner trading remains connected to the supplied services.

Apply configured wholesale floors and FX-aware comparisons, with alerts for below-floor pricing or unavailable conversion evidence.

Control template policy, reseller page generation and permitted parent-funded AI access. Refresh workflows handle diverged site content explicitly.

Keep active, grace, suspended and cancelled workspace states distinguishable, with restricted access and recovery tied to the purchased membership.

Follow authorised customer events across orders, billing, provisioning, plan changes, support and sent-email evidence, with the original recorded timestamps.

Bring permitted customer history, current blockers and next-action evidence into a concise staff summary. Missing records stay explicit rather than being filled in by inference.

Search permitted customer, order, invoice and ticket records and navigate staff tools from a shared search surface.

Save supported order and invoice filters and columns, share views within the operator and retain each recipient’s underlying data permissions.

Assign supported cross-team work to authorised staff with due dates, status, source links and overdue views.

Surface supported ticket, operational and follow-up events through the staff bell and available push preferences.

Allow authorised staff to open an audited, read-only customer view without requesting customer approval. Sessions expire after one hour and retain checks on the staff member’s current authority.

Use stock or custom area-based roles, role-bound API keys and an audit log to govern staff access. Staff passkeys, enrolled two-factor authentication and last-admin protection support administration.

Create and maintain supported customer and billing-profile records, attach private staff notes and inspect linked service, order, invoice and sent-email evidence.

Place supported orders on a customer’s behalf using the catalogue, quote and tax-snapshot workflow. The resulting order awaits payment, after which normal delivery processing applies.

Give authorised staff supported two-factor recovery and portal-session revocation controls, with recorded actions and permissions distinct from ordinary read-only customer viewing.

Review supported date-range reports for new clients, orders, subscriptions, cancellations, collections, refunds and support workload, with defined metrics and separate currency totals.

Download branded business-report PDFs and CSV exports from supported transaction views. Export bounds and the selected reporting window remain visible.

Inspect available recurring-revenue, growth and outstanding-receivable views while keeping document amounts, applied funds and refunds distinguishable.

Project eligible next renewals by date and currency with net, tax and gross values, holds and missing evidence. A projected renewal is not a promise that the money will be collected.

Explore supported product and cohort breakdowns with source records, explicit denominators and imported-history limits. Payment-failure association is not automatically labelled as the cause of churn.

Review recorded account and transcode reservations against configured limits and project exhaustion when sufficient, stable history exists. Unknown or unmetered capacity remains explicit.

Follow recorded purchase, portal sign-in, setup observations and verified first-use evidence, with drilldowns into relevant records. Personal setup checkboxes do not count as verified access.

Inspect supported aggregate stage observations under consent, retention and abuse controls. Unlinked observations are not presented as a tracked visitor funnel.

Enable daily summaries with a local delivery time and timezone for each recipient. The email and accompanying PDF use the configured business identity.

Select an available overview, finance, support or operations edition per recipient. Staff permissions govern which sections can be configured and sent.

Give authorised finance staff recorded successful and failed charge information, unpaid or recovered invoices and available failure explanations and provider codes.

Include configured connector and recorded booking status, outstanding errors and the last recorded successful sync. This is accounting-export evidence rather than a live provider balance.

Send explicitly configured recipients an aggregate edition without requiring a staff account. External email and PDF reports omit customer and invoice identities, payment-failure details and administration links.

Manage recipients separately per operator, disable or remove them and recheck current permission before supported delivery. Delivery records distinguish queueing from transport acceptance.

Review unresolved conditions by severity and age, see the responsible operator or installation and follow permission-appropriate links to the owning workflow.

Track open, acknowledged and resolved incidents with recommended actions, recurrence and delivery history. Route supported alert classes to configured email recipients and signed webhooks.

See recorded step, dependency, progress time and retry or dead-job state for supported background work, with available staff actions instead of automatic replay from a read.

Combine available configuration observations, successful operations, delays, failures and affected resources without exposing stored secrets. Missing evidence is shown as unknown.

Inspect supported application and reported host tasks, recent runs, errors and next due times. Authorised staff can run eligible tasks, adjust cadence or timezone schedules and pause or resume them.

Use background workers and transactional event delivery with retries and dead-letter inspection for supported billing, provisioning and notification workflows.

Deliver supported invoice, refund, order, payment-failure and support events to configured HTTPS endpoints, with signing, attempt history, secret rotation and authorised redelivery.

Expose a generated API reference and role-scoped keys for supported automation. Native staff-client authentication interfaces support configured mobile clients; app distribution is a separate step.

Install approved external plugin binaries for supported media, accounting and channel capabilities, and inspect process health and loaded configuration generations. Plugins are trusted deployment code, not an open tenant app marketplace.

Preview supported customer, service, card and invoice-history imports, inspect durable import runs and compare shadow billing before cutover. Mapping issues and billing holds require explicit review.

Make supported imported invoice records and available archived documents accessible alongside current billing. Historical WHMCS records remain distinguishable from the platform’s newly issued invoice series.

Use the getting-started checklist to configure business identity, numbering, domains, a payment gateway, catalogue, tax, email and service delivery before opening the store.

Use available explicit connection checks and test-email controls for configured integrations and SMTP. A configuration save or discovery check is not presented as proof of a complete customer workflow.

Expose liveness, readiness and protected Prometheus metrics for supported jobs, event delivery, billing, support and accounting workflows.

Run the web, worker and scheduler services with PostgreSQL under your own deployment administration. Supplied container and operational tooling support installation, updates and recovery procedures.

Use encrypted stored credentials, scoped staff access, database tenant boundaries, outbound destination controls and recorded administrative actions. These controls do not imply independent security or regulatory certification.

Enable supported licence verification with offline grace and a restriction on new orders when required by the configured licence policy. Licensing enforcement is optional and does not set commercial pricing or distribution terms.