How to turn support emails into WordPress tickets

Decide whether a new email should create a ticket, whether replies should be added to an existing ticket, and whether customers may use the system without logging in. For most support teams, choose both new tickets and replies, and use a dedicated address such as [email protected].

WordPress core can send email with wp_mail(), but it is not an incoming mailbox-to-ticket system. Do not try to solve this by changing outgoing mail settings or adding a filter to wp_mail.

If you only receive a few support messages, you can leave the mailbox as it is and create each ticket from the support plugin's normal ticket form. Copy the sender's name and email address, use the email subject as the ticket title, paste the message into the description, and attach the original files.

This route costs nothing extra and gives you control, but it is easy to miss a message, lose attachments, create duplicate tickets, or forget to tell the customer where to follow up. Forwarding an email to a normal WordPress address does not automatically create a ticket.

Use a mailbox reserved for support rather than a personal inbox. If several addresses receive support requests, either connect each supported mailbox or forward them to one piped address and record the original forwarding addresses in the ticket system.

Keep the mailbox available for troubleshooting. On a Friday, the most common failure is forwarding being changed or a mailbox filling up while the team assumes tickets are still being created.

Install and activate a ticket system that supports email piping, then open its email or email-piping settings. With a normal mail provider, enter the mailbox address, password, incoming IMAP server, encryption and port supplied by the provider. Secure IMAP commonly uses port 993, but use the provider's exact details.

For Gmail or Microsoft Exchange, use the system's dedicated API or Exchange connection where available instead of guessing at basic IMAP credentials. Gmail API setup may require a Google Cloud project, enabled Gmail API access, OAuth credentials and a scheduled job to check for mail.

Choose whether the connection accepts all emails, new emails only, or reply emails only. Allow guest senders if customers are not expected to register, and decide whether CC recipients should be added to the ticket.

Replies normally need a ticket ID or another identifier in the subject so the system can attach them to the existing conversation. Keep the instruction to reply above the quoted history in notification emails, and decide what happens when somebody replies to a closed ticket.

Send one new message from an external address and confirm that it creates one ticket with the correct sender, subject, body and attachments. Reply to the notification and check that the reply appears in the same ticket rather than creating a second one. Test a CC recipient, an HTML message and a closed-ticket reply if those cases matter to your team.

If tickets arrive late, check the mailbox connection, spam filtering, the email log and the scheduled task that checks for new messages. WordPress cron may run irregularly on a low-traffic site, so a real server cron or external cron service can make polling more reliable.

For a ready-made WordPress workflow, use SupportCandy Email Piping. It converts incoming emails into tickets and lets customers and agents reply from their inboxes. It supports IMAP, Gmail and Microsoft Exchange connections, multiple forwarded addresses, CC importing, email filtering and rules that can set ticket fields from the sender, forwarding address, subject or body.

Install the extension, connect the support mailbox, choose the allowed email types and users, configure reply and closed-ticket notifications, then run the new-ticket and reply tests above. This is the practical choice when customers need support without logging into your site.