Overview
Wrangler is a lightweight support desk. Customers open tickets from your site, staff work them here in the control panel, and everyone gets emailed when something changes.
The shape of it
A ticket has a subject, a status, a priority, an optional queue, and a requester — either a
logged-in member or a guest identified by name and email. Every ticket carries a human
reference like WR-0042.
A ticket holds messages, in order. A message is from the customer, from staff, or from the system. Staff messages can be marked as an internal note, which stays in the control panel and is never shown to the customer or included in any email.
Statuses
| Status | Means |
|---|---|
| New | Nobody has looked at it yet. |
| Open | Being worked on. |
| Pending | Waiting on the customer. A customer reply flips it back to Open automatically. |
| Closed | Done. |
How a ticket moves
- A visitor submits the form on your site. The ticket opens as New.
- They get an acknowledgement email. A guest's email contains a private link to their ticket.
- Your staff notification recipients get an alert.
- Staff reply here. A public reply emails the customer; an internal note emails nobody.
- The customer replies from their link, or by answering the email if email replies are on. If the ticket was Pending it becomes Open, and the assignee (or the staff list, if nobody is assigned) is emailed.
- A ticket left Pending long enough can close itself. See Auto-close and cron.
Every change is recorded in the ticket's history, shown in the thread alongside the messages.
What else is here
- Saved replies for answers you give often.
- Custom fields on the submit form — order number, product, anything.
- Email replies, so customers can answer from their inbox.
- Slack posts when tickets open, customers reply, or tickets are assigned.
- A customer view of everything one person has sent you, and CSV export of any list.
- A lost link form that emails a customer their ticket links again.
- Extension hooks for developers. See Developer hooks.
What Wrangler does not do
No attachments other than images, no SLA or business-hours tracking, no satisfaction ratings, and no merging of tickets. Those are deliberate omissions, not oversights.