A web application firewall vendor lives and dies by trust. Customers hand you the keys to their traffic, and when a rule blocks a legitimate checkout or misses an attack, the first place they go is your support queue. This guide explains how to choose a shared support team for WAF and website security providers, so product and operations leaders can compare options on the things that matter in this niche: false-positive handling, rule-tuning questions, incident-time surge, staff vetting, access controls and service levels.
Nothing here guarantees a result, and every vendor's product is different. Use it as a framework, then ask any provider for an itemised quote against your own requirements. If you want to see how a pooled model works in practice, our shared support plans page explains how we scope it.
Why security vendors need a different kind of support
General helpdesk outsourcing is built around password resets and how-to questions. A WAF or website security provider has a different mix of tickets, and the cost of a poor answer is higher.
- False-positive tickets: a customer reports that a legitimate form, API call or admin action is being blocked. The agent must collect the request details, the rule that fired and the affected path without asking the customer to repeat themselves.
- Rule-tuning questions: customers ask whether to switch a rule from block to log, add an exception or tighten a policy. These need careful, accurate answers and a clear point where the agent hands over to your security engineers.
- Incident-time surge: when a new vulnerability is published or an attack campaign starts, ticket volume jumps within hours and customers are anxious.
- Sensitive context: tickets often contain logs, IP addresses, headers and sometimes credentials pasted by mistake.
- Reputation risk: a vague or wrong reply about whether a site is protected can damage the relationship far more than a slow reply about a billing question.
What a shared support team actually is
In a shared model, a pool of trained agents supports several client companies, and each client gets a defined share of that team's capacity instead of hiring and managing its own staff. The benefit is flexibility: coverage across time zones, a bench that can absorb a busy week, and no need to recruit for every shift. The trade-off is that the agents are not exclusively yours, so you need to look closely at how knowledge, access and confidentiality are handled. Our shared team support for web hosting and security companies is one example of this structure.
Step 1: Define your ticket types before you talk to vendors
Sort your recent tickets into groups and decide what a shared team may resolve alone, what it may triage, and what must go straight to your engineers.
- Resolve alone: onboarding questions, DNS and proxy setup guidance, dashboard navigation, report requests, known-issue replies.
- Triage and escalate: suspected false positives, rule exception requests, unexplained traffic changes.
- Engineer-only: custom rule authoring, anything that changes a customer's protection posture, and active attack response decisions.
This split becomes the backbone of your runbooks and of your service level discussion. A vendor who cannot engage with it in detail has probably not supported a security product before.
Step 2: Test how they handle false positives
Ask the vendor to walk through a false-positive ticket from first message to closure. A good answer includes a structured intake template (URL, method, timestamp, request ID, rule or signature identifier, expected behaviour), a clear rule about never advising a customer to disable protection wholesale, and a defined handoff to your rule owners. Ask how the agent confirms that the exception worked and how that fix is recorded so the same ticket is not rebuilt from scratch next month.
Step 3: Plan for incident-time surge
Surge is where shared teams are tested. Ask these questions directly.
- How do you add capacity when a vulnerability disclosure drives a spike, and how quickly can it be switched on?
- Who writes and approves the holding statement and macros during an incident, you or them?
- How are customers told apart by priority, for example an active attack versus a general question?
- What is the escalation path to your on-call engineers, and what is the agent allowed to say before they respond?
Step 4: Check security vetting of support staff
Your support agents will see customer logs and configuration details, so treat them as part of your security perimeter. Ask for a written description of the vetting process rather than a reassuring sentence. Look for background checks appropriate to the country of employment, signed confidentiality agreements, security awareness training on a regular schedule, and a clear offboarding process that removes access the same day someone leaves the team. Ask whether the people on your account are named and stable, or whether tickets are routed to whoever is free.
Step 5: Insist on tight access controls
Least privilege matters more than any promise. The agents should have the minimum access needed to do the job.
- Role-based access to your helpdesk and admin consoles, with read-only views by default.
- No standing access to customers' origin servers or credentials.
- Single sign-on and multi-factor authentication on every tool, with accounts you can revoke yourself.
- Audit logs showing who viewed or changed what, available to you on request.
- Managed devices or controlled workspaces, with clear rules on screenshots, copying data and personal equipment.
- A procedure for scrubbing credentials that customers paste into tickets by accident.
Step 6: Read the service levels carefully
An SLA for a security vendor should say more than "we reply within a set time." Look for separate commitments for first response and for resolution or handoff, different targets by severity, coverage hours that match your customers' time zones, and what happens when a target is missed. Ask how performance is reported and how often you review it. Avoid agreements that promise outcomes the support team cannot control, such as a guaranteed block rate, since that depends on your product and not on the helpdesk.
Vendor evaluation checklist
Use this list when you shortlist providers. Each item should be answered in writing.
- Has the team supported a security, hosting or infrastructure product before, and can they describe the ticket types in detail?
- Do they have a structured process for false-positive intake and handoff?
- Can they explain how capacity is added during an incident surge?
- Are staff vetting, confidentiality terms and training documented?
- Is access role-based, revocable by you and fully logged?
- Are severity levels, response targets and escalation paths written into the agreement?
- Who owns the knowledge base, macros and runbooks if you leave?
- Is there a trial period or a small starting scope before a long commitment?
- Is the quote itemised, with onboarding, coverage hours and surge cover shown separately?
- Will you get a named point of contact for account reviews?
Comparison table: shared, dedicated and in-house support
| Criteria | Shared team | Dedicated outsourced team | In-house team |
|---|---|---|---|
| Cost structure | Lower and scaled to the share of capacity you use | Higher, because staff are reserved for you | Highest fixed cost: salaries, recruiting, tooling and management |
| Product depth | Builds over time through your runbooks and training | Deeper, as the same people only see your product | Deepest, as staff sit near your engineers |
| False-positive handling | Good with strong intake templates and clear escalation | Good, with more room for judgement calls | Best, with direct access to rule owners |
| Incident-time surge | Flexible if surge terms are agreed in advance | Limited to the team size unless extra cover is added | Hardest to scale quickly |
| Staff vetting and access control | Must be verified, since the pool serves several clients | Easier to tailor to your policy | Fully under your control |
| Coverage across time zones | Strong, thanks to a larger pool | Depends on the contract | Requires hiring for every shift |
| Flexibility to scale down | High | Moderate, depending on minimum terms | Low |
| Confidentiality risk | Needs strict data separation between clients | Moderate, depending on contract | Lowest |
No column wins on every row. Shared support suits vendors that want flexible coverage and predictable spend, provided access control and vetting are proven. Dedicated or in-house teams make sense when product depth and confidentiality outweigh flexibility.
What drives cost
We will not print prices here, because they depend on your scope. These are the factors that move a shared support quote:
- Coverage hours and whether weekends and nights are included.
- Expected ticket volume and the share of technical tickets.
- Languages supported.
- Onboarding effort, including runbook writing and training on your product.
- Surge arrangements for incident periods.
- Reporting and review cadence.
Ask for these as separate lines in an itemised quote so you can compare providers fairly and spot anything bundled in.
Red flags to watch for
- Vague answers about who sees customer data and how access is removed.
- Agents advising customers to turn protection off as a first step.
- No written escalation path to your engineers.
- Long minimum terms with no trial or exit clause.
- Quotes that bundle everything into one number.
How to run a sensible pilot
Start with a limited ticket category, such as onboarding and general product questions, then add false-positive triage once the team has shown it follows your intake template. Review a sample of closed tickets every week for the first month, check that escalations arrived with complete information, and update the runbooks as gaps appear. This approach lets you test vetting, access and responsiveness before anything sensitive is handed over. For a closer look at how a staged start works, see our shared support plans for security and hosting teams.
Why Companies Choose CloudHouse for Shared team support for web hosting companies
Clients come to CloudHouse because we plan delivery in stages, stay available for support after launch and provide transparent, itemised quotes so you can see what each part of the service costs. We work within your access and escalation policies instead of asking you to adopt ours.
Conclusion
Choosing a shared support team for a WAF or website security provider comes down to whether the team can handle false positives with discipline, absorb incident surges, and operate inside tight vetting and access controls. Define your ticket types, test the vendor against the checklist above, read the service levels closely and compare itemised quotes. To discuss your requirements and receive a proposal, visit our shared team support service page and request a quote.

