Halaman ini untuk saat ini hanya tersedia dalam bahasa Inggris.
AI assistant
Ticket replies, blog posts and legal text generated with your own API key.
The AI assistant is a monthly add-on; you pay for usage directly to your provider: we are not in the middle.
Setup
- Portal → AI assistant → enable the add-on for your panel (active once the invoice is paid).
- Panel → Settings → Integrations → AI assistant:
- Provider: OpenAI, Google Gemini, Anthropic Claude, OpenRouter or DeepSeek.
- API key: from the provider's console (the "Get a key" link is right there). The key is stored sealed and never shown again in the form.
- Model: Fetch models lists what the provider offers; leave it empty to use the provider's default.
- Test the connection to verify the key.
The form warns when a key does not look like the chosen provider's (OpenAI keys start with sk-, Anthropic with sk-ant-, OpenRouter with sk-or-).
What it does
| Where | What it produces |
|---|---|
| Admin → Blog → post | Type a topic, a draft arrives; edit and publish |
| Appearance → Legal | A terms-of-service / privacy-policy draft built from your panel's details |
| Ticket | Draft a reply with AI fills the box; sending stays in your hands |
Ticket mode
| Mode | Behaviour |
|---|---|
| Off | No AI in tickets |
| Draft (default) | A draft appears when staff press the button; nothing is sent unread |
| Automatic | A reply goes out on its own about a minute after the customer writes |
In automatic mode the reply reaches the customer without anyone reading it and cannot be taken back. The model is told to escalate rather than guess in that mode, and is never allowed to offer refunds or compensation but the risk is the panel owner's.
Extra instructions are added to every request: tone, what must never be promised, brand name.
Acting on orders
When a customer opens a ticket they can pick the orders it is about; numbers such as #4821 in the message are linked automatically (own orders only). While drafting, the assistant sees the real state of those orders and may request two things: a refill (when the service supports refill and the order is complete) and a cancel request (when the service allows cancellation and the order is still open). Nothing else (refunds, balance, status changes) is available to it; a request the capability map does not allow is dropped silently.
- In automatic mode the action is applied at once and the reply says so. Every action stays on the ticket as a record.
- In draft mode the action waits in the "AI proposals" box; Approve applies it, Dismiss drops it.
Privacy
Conversation text is not stored. What is recorded: which feature, which provider and model, how many tokens, whether it succeeded. That log is shown as "Usage" on the Integrations page.