AI Support Assistant for WHMCS Print

AI Support Assistant adds suggested replies, ticket triage, text editing and knowledge base drafts to the WHMCS support interface. It sends the selected ticket context to the AI provider you configure.

Requirements and installation

1. Use WHMCS 8.9 or later and PHP 8.1 or later, with a valid module license.
2. Upload the module to /modules/addons/aiassistant/, preserving the supplied structure.
3. Open WHMCS Addon Modules, activate AI Support Assistant, enter the license key and assign the required administrator access.
4. Open the module settings. Choose OpenAI or Anthropic and enter that provider's API credentials. For a custom OpenAI-compatible provider, enter its base URL, API key and exact model name.
5. Select a model available to your provider account and run the connection test. Direct API usage is billed by the provider separately; a ChatGPT subscription does not include OpenAI API credits.
6. Review context inclusion, supported languages, greeting and signature. Keep Autopilot disabled while testing a non-sensitive ticket.

Working on tickets

• Open a ticket and generate a suggested reply. Check the source summary, verify the answer against the ticket and edit it before sending.
• Use Custom Instructions to revise an existing reply with specific guidance.
• Use the enhancement menu for Improve Writing, Fix Grammar, Shorten, Expand, Change Tone or Translate. These tools also work in the new-ticket editor.
• Use ticket triage for suggested troubleshooting steps and escalation criteria. Check those suggestions before carrying them out.
• Generate a knowledge base draft from a resolved ticket. Remove customer-specific information and verify the instructions before publishing.

The generated reply source summary identifies matched knowledge base articles, products and past-ticket context. It is not a guarantee that the answer is correct. A notice appears when no matching module context was used.

Data sent to your provider

Depending on the operation and your settings, requests can include the ticket conversation, populated support custom fields, matched knowledge base articles, product information, similar closed tickets, and client services, domains or invoice information. Support custom fields can contain sensitive data. Private ticket notes are optional and should be enabled only when needed for reviewed work.

Autopilot excludes private admin notes and other customers' past-ticket excerpts. This does not make ticket data anonymous. Choose a provider and a contractual and privacy basis for sending customer information before using real tickets. Enable only the context you need and check the provider's retention requirements for your chosen model.

Autopilot

Autopilot sends replies automatically through the normal WHMCS cron. Unlike manual suggestions, those replies are not held for approval before sending. Selecting a ticket status for later staff review does not change that.

1. Select a controlled support department explicitly. Leaving the department restriction empty does not restrict replies to a test department.
2. Choose the reply mode, delay and resulting ticket status. Modes cover an initial reply, limited exchanges or unlimited exchanges.
3. Confirm the WHMCS cron is running and test with non-sensitive tickets.
4. Review sent replies before expanding use. Disable Autopilot if its replies need correction.

Troubleshooting

If generation fails, check the provider, model, API credentials, available API credit and connection test, then review the WHMCS activity log. If replies omit documentation, check that knowledge base context is enabled and inspect the source summary. If Autopilot does not reply, check its mode, department selection, delay and cron execution.

When contacting ArkHost support, include the module, WHMCS and PHP versions, the provider name and a redacted error message. Do not include API keys or unredacted customer tickets.