WordPress agencies and freelancers face a critical question: how should they structure support pricing to stay competitive while protecting margins? Per-ticket models can unlock recurring revenue, but only if you price them right and communicate value clearly.
Why Per-Ticket Support Works for WordPress Shops
Per-ticket pricing removes the guesswork from ongoing maintenance. Instead of clients asking for "unlimited" support at a flat monthly rate (and burning your hours), you charge per issue resolved. This creates natural boundaries while staying attractive to cost-conscious business owners who don't need daily intervention.
The model works especially well for WordPress because the work is predictable: theme customizations, plugin conflicts, database optimizations, security patches, and backup management all fit neatly into discrete tickets.
Typical Per-Ticket Pricing Ranges
Most WordPress development agencies charge between $75 and $250 per ticket, depending on geographic location, expertise, and included scope.
Here's a realistic breakdown:
- Junior freelancers or support-only shops: $50–$100 per ticket (best for simple updates, plugin activation, content fixes)
- Mid-level agencies: $100–$175 per ticket (includes troubleshooting, minor code edits, configuration changes)
- Expert consultants: $175–$300+ per ticket (performance audits, security hardening, complex integrations, custom functionality)
A "ticket" should be defined clearly—typically a single issue or task that takes 1–2 hours. If a client's problem requires 4+ hours, you should upgrade to a project scope instead.
Setting Your Ticket Scope & Time Limits
Vague ticket definitions destroy margins. Before offering per-ticket support, write down what's included:
- Included: Bug fixes, plugin updates within WordPress core versions, password resets, spam cleanup, minor CSS tweaks
- Not included: Complete theme rebuilds, adding new pages or features, custom code development (quote as project), emergency 24/7 response
- Time cap: 2 hours maximum per ticket; anything beyond requires a change order
This prevents clients from bundling 10 tasks into one ticket and expecting a $100 resolution for $400 worth of work.
Minimum Ticket Packages & Volume Discounts
Selling individual tickets creates friction. Most clients prefer buying in blocks:
- 5-ticket package: $85 per ticket ($425 total, 15% discount)
- 10-ticket package: $80 per ticket ($800 total, 20% discount)
- Monthly retainer (15 tickets + priority response): $1,200–$1,500
Packages push larger commitments and predictable revenue. A client with a 10-ticket balance is stickier than one buying ad-hoc.
Preventing Support Creep
Per-ticket models fail when scope isn't enforced. Set boundaries:
- Use a ticketing system (Freshdesk, Zendesk, or Help Scout) so clients see status and you track time accurately
- Require requests via ticket system, not Slack or email side-channels
- Reply with a scope estimate before starting; if it exceeds your definition, ask the client to approve a higher tier
- Track actual hours—after a few months, you'll know if your pricing matches reality
If you consistently finish tickets in 45 minutes, you're underpriced. If tickets regularly hit 3 hours, your scope is too broad.
When to Upgrade Clients to Retainers
Some clients will outgrow per-ticket pricing. If someone buys packages monthly and still runs short, move them to a maintenance retainer at $500–$2,000/month.
A retainer bundles tickets, adds priority response windows (24–48 hours vs. 5 days), and includes proactive work like security scans and core updates. It's more stable for both sides.
Listing & Visibility
Positioning per-ticket support effectively matters—especially when competing against agencies offering flat-rate retainers. Listing your specific pricing and scope on platforms like Mercoly helps business owners find exactly what they need, win leads looking for that model, and understand your service range upfront.
Frequently Asked Questions
Q: Should I include hosting or domain management in per-ticket support? No—keep hosting separate. Hosting issues (server downtime, backups, SSL) should be their host's responsibility, or charge an additional small fee ($25–$50/ticket) if you're handling vendor communication on their behalf.
Q: What if a client reports a bug in custom code we built 2 years ago? Set a support window in your contract (typically 90 days post-launch). After that, bug fixes are either billable tickets or part of a paid retainer—don't absorb legacy support for free.
Q: Can I use per-ticket pricing for enterprise clients? Enterprise clients rarely want per-ticket. They prefer fixed monthly retainers or project-based SLAs. Reserve per-ticket for SMBs with predictable, lightweight needs.
Start with clear definitions, test your rates against actual hours logged, and adjust quarterly—that's the fastest path to sustainable WordPress support pricing.