DocsSet up Makli
Test Makli and switch it on
Test Makli on sample and real tickets without posting anything, choose how replies reach clients, and switch Makli on.
Test on a sample ticket
In the Client Portal, open Test Makli, write or paste a ticket and run it. Makli shows what it would reply and which actions it would take.
Test on real tickets
In WHMCS, open any ticket and press Test Makli in the Makli panel. Makli works the ticket as it would for real and shows its reply and actions. It does not post a reply, send an email or change anything. This is the best way to see how Makli handles your real support before it answers anyone.
Not happy with an answer? Use the thumbs in the panel to tell Makli what was wrong. Your correction becomes a lesson (see Lessons).
Choose how replies reach clients
| Setting | What happens |
|---|---|
| Draft for staff (default) | The reply waits in the Makli panel on the ticket. Your team can edit it, Send now, Insert into reply box or Discard it. Nothing is posted on the ticket until then. |
| Send to the client | The client gets Makli's reply straight away. |
| Internal note | Makli does everything it is allowed to do, but posts its reply as a staff-only note. This is useful for a review period. |
On the addon's Ticket Handling tab you also choose:
- which tickets Makli works on: new tickets, client replies and which departments;
- who replies are posted as;
- Makli's working hours;
- clients Makli should leave to your team;
- what happens when Makli hands a ticket over.
Switch Makli on
When setup is complete, switch Makli on from the Client Portal's Setup or Dashboard, or from the addon's Dashboard. Many teams start with drafts for a week, then move to sending once they trust the answers.
Last updated 17 November 2026