New — the AI auto-responder now answers tickets on its own. See how it works

A ticket queue that keeps itself tidy

Every conversation tracked from open to resolved, statuses that update themselves as people reply, and new tickets handed to whoever actually has room to take one.

See pricing
Ticket list screenshot

Status on autopilot

A reply from either side moves the ticket to the right stage without anyone touching a dropdown.

Fair assignment

Random, round-robin or least-loaded, with a cap on how many open tickets each agent can hold.

Your own fields

Show, hide, reorder and require fields, or add text, number, email, long-answer and dropdown fields.

Three ways to log in

One-time code, magic link, or password — none of which need an existing WordPress account.

Emails at every step

Seven notification templates you can rewrite and brand with your own logo and footer.

Embeds anywhere

A theme-free portal that drops into an iframe on any site, WordPress or not.

Ticket stages

Eight stages, and you rarely set them by hand

When your team replies the ticket moves on; when the customer replies it comes back to you. The queue reflects reality without anyone maintaining it.

Open

Just arrived and not yet picked up by anyone.

Waiting

The customer is waiting on your team to reply.

In progress

Your team replied — now you are waiting on the customer.

On hold

Parked on purpose, usually pending something outside support.

Resolved

Answered, and the auto-responder will not touch it again.

Reopened

The customer came back after it was resolved.

Cancelled

Withdrawn or no longer relevant.

Closed

Finished and archived out of the working queue.

Worth knowing: “Waiting” means the ball is in your court, and “In progress” means you're waiting on the customer. It reads backwards compared to some help desks — but it means a glance at the queue tells you what your team owes today.

Assignment

Nobody gets buried, nobody gets skipped

Pick how new tickets are handed out, then set a limit on how many open tickets any one agent can hold. Once someone is at capacity, the queue routes around them.

Round-robin
Tickets go around the team in turn, so the load spreads evenly over a week.
Least-loaded
The next ticket goes to whoever currently has the fewest open ones.
Random
Simple and unpredictable — fine for small teams where everyone handles everything.

Prefer to triage by hand? Switch auto-assignment off entirely and assign from the ticket screen.

Agents page with capacity badges

Submission & login

Customers don't need a WordPress account

Three login methods, all of which work for someone who has never registered on your site — because asking a frustrated customer to create a password is how tickets go unsent.

One-time code
We email a short code, they type it in. The default, because it works on any device.
Magic link
One click from their inbox and they are in — the same links sit inside notification emails.
Password
Standard email-and-password login, for customers who already have one.

The form

Ask for what you actually need

Show, hide, reorder and require the built-in fields, then add your own — text, number, email, long answer or dropdown. No code, no form plugin.

Reorder fields by dragging, and mark any of them required
Add custom text, number, email, long-answer or dropdown fields
Four urgency levels — low, medium, high and severe — chosen by the customer
Guest submission for customers who have no account at all

The details

Everything the ticket module ships with.

Content type
Tickets are WordPress posts; replies are comments. No custom database tables.
Stages
Eight: open, waiting, in progress, on hold, resolved, reopened, cancelled, closed.
Automation
Agent reply moves to in progress; customer reply moves to waiting. Toggleable globally.
Assignment
Random, round-robin or least-loaded, with a per-agent open-ticket cap. Can be disabled.
Roles
Manager, Agent and Customer, each with mapped WordPress capabilities.
Agents screen
Every agent with open and total counts, plus a capacity badge.
Form fields
Six built-in fields (title, description, product, reason, urgency, order) can be shown, hidden, reordered and required — title and description are always on. Add unlimited custom text, number, email, long-answer or dropdown fields.
Urgency
Four levels: low, medium, high and severe, set by the customer on the form.
Attachments
Agents and managers can upload files on a ticket or a reply. The public customer role ships without WordPress upload permission, so customer-side uploads are off by default.
Login methods
One-time code (default), magic link, or password.
Emails
Seven templates — login code, magic link, new ticket to customer and agent, agent reply, customer reply, resolved — each with its own header, subject and body, plus placeholders for site, customer, agent and ticket details.
Embedding
Theme-free ticket portal for iframes, plus shortcodes for the customer’s own list, the full queue, the submit form and standalone login.
Migration
One-click import from Awesome Support, SupportCandy and JS Help Desk.

Let the AI take the easy ones

Most queues are full of questions your docs already answer. On the Pro plan, the auto-responder handles those before anyone on your team opens them — and stays quiet on everything else.

See how the auto-responder works

Common questions

No. Every plan, including the free one, allows unlimited agents and unlimited tickets. Pricing is per site, so growing the team never changes your bill.

Start taking tickets this afternoon

Unlimited agents, unlimited tickets, on the free plan.

Import my tickets