Set up support departments, ticket email import and piping in WHMCS

WHMCS includes a full helpdesk. Customers can open tickets in the client area or simply email a support address, and replies go back by email. Setting up departments and email import correctly means no customer message is ever lost. This guide covers departments, the two ways of importing email and helpful extras.

Before you start

• A mailbox per department, for example support@example.com and billing@example.com.
• The WHMCS cron running every 5 minutes, which imports email. See WHMCS cron and automation.

Create a department

1. Go to Configuration → System Settings → Support Departments.
2. Click Add New Department.
3. Enter the Department Name (for example Technical Support), a description and the department Email Address.
4. Tick the staff members assigned to it. Only assigned staff see its tickets and get notifications.
5. Options:
   • Clients Only – reject emails from unknown senders (reduces spam).
   • Pipe Replies Only – only accept replies to existing tickets by email.
   • No Autoresponder – do not send the "ticket opened" confirmation.
   • Hidden – staff-only department.

Import email: POP3/IMAP or OAuth (recommended)

1. In the department form, open Mail Import (or POP3 Importing Configuration).
2. Choose the connection: standard IMAP/POP3 with host, port (993 for IMAP SSL), user name and password, or Google / Microsoft OAuth.
3. Click Test Connection, then Save Changes.

The cron logs in, imports new messages as tickets or replies and deletes them from the mailbox. Use a dedicated mailbox that people do not read in their own email client.

Import email: piping

Piping hands each message straight to WHMCS as it arrives, without waiting for the cron. On cPanel, create a forwarder under Email → Forwarders → Add Forwarder, choose Advanced Options → Pipe to a Program and enter the path to crons/pipe.php. Piping requires WHMCS and the mailbox on the same server, so mail import via IMAP is easier for most setups.

Predefined replies

Go to Support → Predefined Replies and create categories and answers for frequent questions (nameserver changes, password resets). Staff insert them with one click when replying. Merge fields like [NAME] personalise them.

Escalation rules

Configuration → System Settings → Escalation Rules automate actions on ageing tickets, for example: if a High priority ticket has had no reply for 2 hours, move it to Senior Support, notify a manager and add a note. Escalations run with the cron.

Ticket statuses and notifications

• Configuration → System Settings → Ticket Statuses lets you add statuses like Awaiting Developer and choose which count as active or awaiting reply.
• Each admin sets their own notification preferences under My Account.
• Close inactive tickets automatically in Automation Settings.

Troubleshooting

• Emails not becoming tickets: check Utilities → Logs → Ticket Mail Import Log. Common causes: wrong password, IMAP disabled, cron not running, or the sender rejected by Clients Only.
• Loops with autoresponders: WHMCS ignores auto-replies, but make sure the department address is not also a recipient of your own notifications.
• Spam tickets: enable Clients Only or add spam filters under Support → Spam Control.

Next steps

• Configure SMTP for outgoing mail.
• Create staff roles and 2FA.
• Edit ticket email templates.