Zendesk vs HubSpot: Which Platform Is Better for Your Business?

Zendesk vs HubSpot is a choice between two platforms that solve customer support from opposite directions. Zendesk is a dedicated support platform built around agent workflows, ticket management, and omnichannel service operations. HubSpot is a CRM platform that added its Service Hub to connect support with sales, marketing, and revenue data on the same system. So when buyers weigh HubSpot vs Zendesk, the right choice depends on whether your team needs deep support specialization or unified customer data across departments. If your primary challenge is handling a high volume of complex requests with intricate routing and escalations, Zendesk is typically stronger. If your priority is giving sales and support teams a shared view of the entire customer journey, HubSpot Service Hub usually fits better.

Here is the short version before the detail:

• Choose Zendesk when support operations are your system of record and specialized customer service tools matter most.
• Choose HubSpot Service Hub when CRM context and sales-service alignment matter more than dedicated support depth.
• Use both when sales and marketing live in HubSpot but support needs Zendesk depth. The two integrate directly (see our HubSpot Zendesk integration guide).
• Add an AI layer (like Pluno) only when tickets regularly require context from past cases, internal tools, or engineering systems.

Below is a practical comparison of both platforms across core features, pricing, ease of use, and scalability. Prices checked on 20 October 2026 against Zendesk's and HubSpot's public pricing pages.

Zendesk vs HubSpot at a glance

This Zendesk vs HubSpot summary covers the twelve points buyers ask about most. The sections below explain each one.

Zendesk vs HubSpot: Key Platform Differences

The core difference between Zendesk and HubSpot comes down to platform DNA: what each product was originally built to do.

• Zendesk is a support-first platform. Every capability, from its ticketing system to its AI-powered tools, was designed around the daily work of support agents and service teams.

• HubSpot is a CRM-first ecosystem. Its Service Hub is one piece of a broader CRM platform that connects marketing, sales, and service interactions on the same customer record.

Both platforms can handle customer requests, live chat, and knowledge bases. But the trade-offs show up quickly: Zendesk offers deeper escalation flows, more advanced routing logic, and stronger omnichannel support. HubSpot offers stronger cross-department visibility, native CRM functionality, and a unified interface for teams that need to track the customer journey from first touch to retention.

Understanding these key differences helps you evaluate which platform matches your team's actual workflows, not just a feature checklist.

Quick Decision Path: HubSpot vs Zendesk

Before comparing feature by feature, map yourself to one of four buyer paths. Most teams fit cleanly into one:

Use this as a filter. If two paths feel equally true, the feature, pricing, and scalability sections below will break the tie.

Core Platform Focus and Strengths

How a platform was built affects everything: the initial setup experience, what is easy to configure, what requires workarounds, and where you hit limits as your team grows. A concrete example: standing up conditional SLAs and multi-brand help centers is native to Zendesk but requires more assembly in HubSpot, while surfacing a contact's marketing history next to a ticket is native to HubSpot but requires an integration in Zendesk.

Zendesk: Support-First Platform

Zendesk was founded in 2007 as a customer support tool and has spent nearly two decades refining its approach to service delivery. It is widely regarded as one of the strongest dedicated help desk platforms available, and Zendesk is designed for high-volume customer support.

Key features include:

• Omnichannel support: Native handling of email, chat, voice (with IVR phone trees), social media, and SMS, all within a unified Zendesk Agent Workspace.

• Advanced ticket management: Custom fields, dynamic ticket layouts, macros, triggers, and side conversations give agents granular control.

• Automation and SLAs: Skill-based routing, conditional SLAs (first reply time, time to close), escalation flows, and triggers for complex service processes.

• Knowledge base and community: Hierarchical article structures (up to six levels), multilingual support, community forums for peer self-service, and AI-driven content gap detection to help teams create searchable articles efficiently.

• AI add-ons: Copilot, AI Agents, auto-assist, and intelligent triage, though many are paid extras on top of base pricing.

Zendesk shines when customer support is a primary operational focus. Teams dealing with a high volume of requests, multi-brand operations, or complex escalation paths tend to get the most from its depth.

Zendesk pros and cons

Pros

• Deep omnichannel support, including voice with IVR and SMS
• Advanced routing, conditional SLAs and multi-brand help centers
• A marketplace of 1,800+ apps, partners and integrations
• Workforce management and QA available as add-ons

Cons

• Advanced configuration needs a support operations admin
• Copilot, workforce engagement and AI resolutions add cost on top of seats
• CRM data needs an integration, since Zendesk Sell is being retired

HubSpot: CRM-First Ecosystem

HubSpot provides a comprehensive all-in-one CRM ecosystem. Its Service Hub is built into a platform that already includes Marketing Hub, HubSpot Sales Hub, and Operations Hub. HubSpot emphasizes a unified platform for CRM, marketing, and service.

Key features of HubSpot Service Hub include:

• Unified customer data: Every support ticket, marketing email, sales call, and deal lives on the same customer record. This gives service teams instant context on the entire customer journey.

• Customer success tools: Health scores, proactive alerts, NPS, CSAT, and CES surveys for feedback collection, all built natively into the platform.

• Cross-department workflows: Automation that connects marketing, sales pipelines, and support interactions. HubSpot connects service directly into marketing and sales.

• Breeze AI: AI features including a Customer Agent for automated resolution and a Knowledge Base Agent for identifying documentation gaps, though these consume credits tied to your plan tier. My HubSpot Breeze AI pricing breakdown shows what Customer Agent costs at real volume.

HubSpot is suitable for small teams needing a CRM alongside customer service, and for organizations where pipeline tracking, marketing automation, and customer engagement need to live on the same platform as support.

HubSpot Service Hub pros and cons

Pros

• Native CRM, so every ticket sits on the shared customer record
• Free tier for up to 2 users and an interface teams learn quickly
• Customer success tools: health scores, NPS, CSAT and CES surveys
• A lower per-resolution AI price (50 credits, or $0.50, per resolved conversation)

Cons

• Required onboarding fees: $1,500 on Professional and $3,500 on Enterprise
• Skill-based routing is Enterprise-only
• Less depth in voice, workforce management and QA
• The Customer Agent needs a Professional or Enterprise plan

Customer Support Capabilities

Feature lists look similar on paper. The real differences show up when you look at what each platform can actually do when service work gets complex: multi-step escalations, product bugs that need engineering context, or billing disputes that require account history.

Zendesk Support Features

Zendesk's ticketing system categorizes requests automatically and offers deep customization for how support tickets flow through your team:

• Advanced ticketing: Custom fields, dynamic layouts, custom forms, internal comments, and side conversations. Agents can handle context switching between cases without losing track.

• Unified agent workspace: A single pane where agents manage customer conversations across email, chat, voice, and social media. Zendesk provides pre-built dashboards integrating data from all channels.

• AI-powered routing and suggestions: Intelligent triage can classify tickets by intent, language, and sentiment. Auto-assist suggests responses. Zendesk's AI tools include Copilot for agent assistance, offered as a paid add-on.

• Knowledge base with analytics: Multi-language help centers, hierarchical article organization, and AI tools that detect content gaps and auto-suggest improvements.

• Workforce management: Add-ons for agent scheduling, quality assurance, and performance optimization, available through the Workforce Engagement Bundle.

For genuinely complex service work (say, a bug report that needs context from Zendesk cases, Jira issues, and product logs), an AI layer like Pluno pulls internal documentation, customer history, and escalation paths into one view inside Zendesk.

HubSpot Service Hub Features

HubSpot Service Hub includes a knowledge base for customer self-service and integrates ticketing directly with CRM customer data. HubSpot Service Hub allows for shared customer timelines across teams, so any agent can see prior marketing touches, sales conversations, and support history.

Core capabilities of HubSpot Service Hub include:

• Ticketing with CRM context: Support tickets automatically link to the customer's full timeline: deals, emails, form submissions, and prior conversations.

• Multichannel help desk: HubSpot's help desk workspace supports chat, email, forms, calling, custom channels, WhatsApp, and Facebook Messenger on Professional and Enterprise tiers.

• Feedback and surveys: Built-in NPS, CSAT, and CES surveys. HubSpot includes customer success features like health scores and surveys for proactive retention.

• Automation: Workflows and routing exist at the Professional tier and above, with some advanced capabilities such as skill-based routing available at Enterprise.

Where HubSpot's service tooling is less specialized than Zendesk: voice and telephony are newer and less deep, and the granularity of routing logic for high-complexity contact-center scenarios does not yet match a platform built purely for support. The fair takeaway is not that HubSpot Service Hub cannot run support (it clearly can) but that Zendesk goes deeper for specialized service operations such as advanced contact-center setup, WFM, QA, and multi-step escalation flows.

CRM and Sales Integration

How well your support platform connects to CRM data affects how much context agents have when they pick up a case. A billing escalation is easier to resolve when the agent can see the customer's subscription tier, recent invoices, and past conversations without switching between multiple tools.

Zendesk CRM Integration

Zendesk Sell is a separate CRM product with native integration to Zendesk Support, and Zendesk will retire it on 31 August 2027, recommending Pipedrive as the replacement. Sell handles contact management, deal tracking, and pipeline management, but its CRM features are basic compared to Zendesk's support tools, and it does not include marketing tools the way an all-in-one CRM platform does.

Where Zendesk compensates is through its marketplace. Zendesk lists more than 1,800 apps, partners and integrations, and Zendesk integrates with popular tools like Salesforce and MailChimp. Zendesk's integrations enhance service delivery significantly, letting teams connect their help desk to whatever CRM system they already use, such as Salesforce through the Zendesk Salesforce integration. The trade-off: you will need to combine tools to get full CRM functionality, especially with Sell on its way out.

HubSpot CRM Integration

This is where HubSpot has a clear advantage. HubSpot's CRM integrates sales, marketing, and service tools on a single platform. HubSpot's CRM provides a centralized view of the customer record. Every interaction, deal, campaign, and ticket lives in one place.

Key benefits:

• Native CRM with full pipeline tracking: HubSpot offers a comprehensive CRM with lead tracking and marketing automation. Sales pipelines, deal stages, and revenue data are visible alongside support cases.

• Native shared platform: When a ticket is created, the customer's marketing engagement, sales conversations, and lifecycle stage are already on the same record. No integration setup required.

• Revenue reporting: HubSpot's reporting tools cover pipelines and campaign performance, and teams can see how service interactions affect retention and revenue. HubSpot allows customization of dashboards for specific metrics.

HubSpot's CRM tool is free, enhancing its pricing appeal for teams that want customer relationship management alongside service without paying for a separate CRM platform.

Connecting Zendesk and HubSpot

You do not have to pick one CRM layer. Two free official apps connect Zendesk Support to HubSpot CRM: one adds Zendesk ticket activity to the HubSpot contact timeline, and HubSpot's Data Sync app keeps Zendesk users and organizations aligned with HubSpot contacts and companies (with ticket sync running one way into HubSpot). For setup steps, sync limits, and field mapping, see our HubSpot Zendesk integration guide.

Ease of Use and Setup

A platform that requires extensive configuration and a dedicated admin is a different investment than one your team can start using quickly. Both Zendesk and HubSpot have trade-offs here.

Zendesk User Experience

Zendesk's agent-focused interface is designed for support workflow efficiency. The unified agent workspace is well organized for handling customer inquiries across channels, and experienced reps tend to feel at home quickly.

The complexity shows up on the admin side. Configuring sophisticated routing, conditional SLAs, multi-brand help centers, and AI-powered tools takes technical expertise. Teams without a dedicated support operations person may find friction in:

• Configuring advanced automation rules, triggers, and routing logic

• Managing integrations across external platforms

• Fine-tuning AI features like intelligent triage and Copilot

• Building custom dashboards and reports. Zendesk offers custom reporting options for deeper insights, but getting there takes work.

For larger teams, this investment pays off. For smaller teams, the initial setup can feel like overkill.

HubSpot User Experience

HubSpot is frequently cited for its intuitive, user-friendly interface. If your sales teams or marketing teams already use HubSpot, adding HubSpot Service Hub feels natural, since the navigation, workflows, and data model are consistent.

Getting basic support running tends to be quick: shared inboxes, live chat, simple ticketing, and a knowledge base can be configured without a long implementation project. Unified training across marketing, sales, and support teams is easier because everyone uses the same platform.

The costs appear at higher tiers: required onboarding fees on Professional and Enterprise, and skill-based routing only on Enterprise. HubSpot also lacks the dedicated QA and workforce-management depth of Zendesk's Workforce Engagement add-ons. For teams that need AI-powered support QA on either platform, a QA layer fills that gap.

Pricing and Total Cost of Ownership

In a Zendesk vs HubSpot cost comparison, the number on the pricing page is rarely the whole story. Add-ons, onboarding fees, AI usage costs, and feature locks behind higher tiers all affect the real cost.

Zendesk Pricing Structure

Zendesk offers modular pricing with add-ons for advanced capabilities. Per Zendesk pricing, checked 20 October 2026:

On top of base plans, add-ons include Copilot at $50/agent/month, the Workforce Engagement Bundle at $50/agent/month, and Contact Center at $83/agent/month, all billed annually. AI agents are billed per automated resolution (see AI agent pricing compared below). Self-serve plans are paid, with a 14-day trial of Suite Professional.

For a team of 5 agents on Suite Professional at listed annual prices: $115 × 5 = $575/month, or $6,900/year before add-ons.

HubSpot Service Hub Pricing Structure

HubSpot Service Hub pricing includes Free, Starter, Professional, and Enterprise tiers. The free tier is free for up to 2 users with basic ticketing, shared inbox, and live chat. Per HubSpot's pricing page, checked 20 October 2026:

The Starter discount is a limited-time offer for new customers, so budget on the $20 list price for renewals. HubSpot's integrations focus on CRM and marketing automation, and teams that expand beyond service may need to purchase additional Hubs.

For a team of 5 seats on Professional at listed annual prices: $90 × 5 = $450/month + $1,500 onboarding = $6,900 first year. After year one, the annual cost drops to $5,400 since onboarding is a one-time fee. These figures exclude taxes, discounts, plan minimums, and AI usage.

The practical takeaway: First-year costs are roughly comparable at the Professional tier. After year one, HubSpot typically costs less per seat. But Zendesk's add-on model means you can start leaner and add capabilities selectively, while HubSpot's mandatory onboarding and credit-based AI usage can create less predictable costs.

Zendesk vs HubSpot AI agent pricing compared

Both vendors now bill their AI agents per resolution, as of 20 October 2026:

Sources: Zendesk pricing and automated resolution tiers; HubSpot's credits rate sheet and Customer Agent guide. HubSpot's own comparison page quotes the same $0.50 against $1.50 to $2.00, as of April 2026.

For comparison, Pluno's Deflection AI is €0.90 per resolution on top of the monthly platform fee, runs inside both Zendesk and HubSpot, and never bills an escalated ticket.

Scalability and Advanced Automation

How a platform handles growth (in request volume, team size, geographic reach, and workflow complexity) determines whether you will outgrow it or grow with it.

Zendesk Scalability

Zendesk excels in high-volume ticketing and complex workflows. It was built for enterprise-scale support teams and handles growth through:

• Advanced routing: Skill-based assignment, round-robin, load balancing, and conditional routing based on ticket attributes.

• Multi-brand and multilingual support: Separate help centers, custom branding, and content in multiple languages, critical for global operations.

• Enterprise governance: Sandbox environments, custom agent roles, audit trails, and data residency controls.

• Scalable automation: Complex trigger chains, scheduled automations, and API-driven processes for teams handling thousands of requests daily.

When ticket complexity (not just volume) is the challenge, AI agents like Pluno handle the context-gathering that simple triggers cannot, so the next person in the chain gets full context rather than a bare ticket number. For straightforward work (password resets, order status checks), Zendesk's native AI agents are typically sufficient.

HubSpot Scalability

HubSpot scales well for unified customer operations across departments. Its strength is keeping marketing, sales, and service aligned as organizations grow:

• Cross-department workflows: A single automation can trigger actions across marketing, sales pipelines, and service based on any customer interaction.

• Customer success workspace: Health scores, alerts, and proactive retention workflows help success teams identify at-risk accounts.

• Revenue operations alignment: Service data feeds into pipeline management, revenue attribution, and customer lifetime value calculations.

Where HubSpot is less specialized than Zendesk at scale: deep IVR configurations, complex incident escalation, granular agent-performance analytics, and very high-volume triage lean more on third-party tools. Teams that need specialized service operations at enterprise scale (multi-brand help centers, advanced SLA configurations, dedicated WFM and QA) may find themselves extending HubSpot rather than relying on native capabilities.

Integration Ecosystem

No support platform works in isolation. The real question is how well it connects to the tools your team already uses, and whether you need external platforms to fill gaps. These are the core features buyers usually compare:

Marketplace counts are each vendor's own figures and shift constantly. HubSpot's marketplace leans toward CRM and marketing automation connections.

The key difference: HubSpot's integration capabilities shine when you want everything on the same platform, with your CRM, marketing hub, and service tools sharing data without middleware. Zendesk's integration ecosystem is stronger when you need specialized support tools connected to engineering, product, and operations systems.

For teams running complex workflows across help desk, CRM, product, and engineering tools, the question is not just which platform has more integrations. It is whether the integrations provide the context needed for ticket resolution. An AI layer that can pull data from multiple connected systems and present it inside the agent workspace can reduce the need to combine several tools during complex customer interactions.

Zendesk to HubSpot Migration (and Vice Versa)

Most teams run both tools side by side, but some consolidate onto one platform. Whichever direction you move, plan the migration as a project, not an export.

What moves. Customer records (users and organizations in Zendesk, contacts and companies in HubSpot), ticket history with comments and attachments, knowledge base articles, and custom fields. Workflows do not transfer: triggers, automations, macros, SLA policies, routing rules, and HubSpot workflows have to be rebuilt by hand on the new platform.

Your options.

• Native import tools. Both platforms accept CSV imports for customer records. Moving from Zendesk to HubSpot, the Data Sync app can also bring Zendesk users, organizations, and tickets into HubSpot, which covers a lot of the record work.
• APIs. Both platforms have extensive REST APIs for tickets, contacts, and help center content. A custom script gives you full control over field mapping, timestamps, and comment order, at the cost of engineering time.
• Migration service. Third-party migration services handle mapping, test runs, and delta syncs for a fee. This is usually the safest path when you have years of ticket history.

Gotchas to plan for.

• Archived tickets. Zendesk archives older closed tickets, and HubSpot Data Sync does not sync archived tickets, so a sync alone will not carry your full history.
• Field and status mapping. Custom fields, ticket statuses, priorities, and pipeline stages rarely map one to one. Define the mapping before moving any data.
• Duplicates. Match records on a stable key such as email, and clean duplicates before import rather than after.
• Help center links. Article URLs change, so set up redirects for any knowledge base content that ranks or is linked from your product.
• Cutover. Run both systems in parallel for a short period, move active tickets first, and freeze configuration changes until the switch is done.

Zendesk vs HubSpot: Which Should You Choose?

Choose Zendesk if:

• Customer support is your primary operational focus and you need a dedicated support platform

• You handle high ticket volumes with complex routing, escalation, and SLA requirements

• Your team needs deep omnichannel support: voice with IVR, social messaging, SMS, and chat in one workspace

• Multilingual help centers and multi-brand operations are requirements

• You have (or plan to hire) dedicated support operations staff to configure and maintain the system

Choose HubSpot Service Hub if:

• You want unified customer data across sales, marketing, and support teams on the same platform

• Cross-department visibility matters more than specialized support depth

• Your team is small to mid-size and values fast initial setup over deep customization

• Revenue attribution, pipeline tracking, and customer journey mapping are core priorities

• You already use HubSpot for marketing or sales and want to avoid adding external platforms

Consider a hybrid approach when your organization needs both: many teams run Zendesk for service delivery while using HubSpot CRM for sales and marketing. The two integrate directly. This lets support teams use Zendesk's ticketing system and advanced features while giving sales teams a consistent customer experience view in HubSpot.

When AI support agents add value: For teams where tickets regularly require pulling context from multiple sources (ticket history, product logs, internal documentation, customer account data), tools like Pluno can improve resolution quality and reduce unnecessary escalations on either platform. In our experience working with B2B SaaS support teams, the honest fit boundary is this: Pluno is not needed for simple FAQ deflection, transactional chat, or very small teams with basic workflows. It is most useful for teams using Zendesk where complex tickets require investigation across past cases, Jira, Slack, internal docs, logs, APIs, or account data before an answer is safe. For straightforward, repetitive inquiries, native automation in both Zendesk and HubSpot is typically sufficient.

Evaluation checklist before deciding:

1. Count your daily request volume and map your channels. Does the platform handle them natively?

2. Identify your most complex ticket type. Walk through how each platform would handle it end to end.

3. Calculate total cost for year one and year two, including onboarding, add-ons, and AI usage.

4. Test the admin experience. Can your team configure workflows without outside help?

5. Check whether your existing tools (CRM, engineering, product) integrate cleanly.

The best Zendesk vs HubSpot test is simple: run your hardest real ticket through each platform, and choose the stack that gives agents the best context with the least operational overhead.

What people actually say about Zendesk vs HubSpot

Reviewers who weighed both platforms tend to split along the same line this guide draws: HubSpot for simpler ticketing on a shared CRM, Zendesk for flexibility and complex flows. On TrustRadius, checked 20 October 2026, Zendesk Suite scores 8.5 out of 10 from 1,096 reviews and ratings and HubSpot Service Hub 8.0 from 60.

The pattern holds: the more brands, flows and channels you run, the more reviewers lean toward Zendesk, while SMBs already on HubSpot rarely see a reason to leave it.

Zendesk vs HubSpot FAQ

Can you integrate Zendesk with HubSpot CRM?

Yes, Zendesk and HubSpot can integrate, but the exact sync behavior depends on which integration you use. HubSpot's Zendesk app can add Zendesk ticket activity to HubSpot timelines, while Data Sync by HubSpot supports bidirectional sync for certain records. Ticket sync is not always fully bidirectional, so teams should verify contact, company, ticket, conversation, and field-mapping requirements before choosing a hybrid setup. Many organizations still run Zendesk for support and HubSpot for CRM so each platform does what it does best.

Zendesk vs HubSpot: which is better for small support teams?

HubSpot's free plan is typically more practical for small teams. It includes basic ticketing, shared inbox, live chat, and free tools for up to 2 users at no cost. Zendesk's lowest tier, the Support Team plan, starts at $19/agent/month, which is affordable but adds up with necessary features. Note that Zendesk also offers free trials and startup programs. The trade-off: HubSpot is easier to launch but offers less customer support depth, while Zendesk gives more advanced features out of the box but demands more configuration time.

Is Zendesk also a CRM?

Not at its core. Zendesk is a customer service platform, and its CRM, Zendesk Sell, is a separate product. HubSpot is the opposite: a CRM first, with Service Hub on the same record. Most Zendesk teams connect a CRM such as HubSpot or Salesforce through the official apps.

Is Zendesk Sell shutting down?

Yes. Zendesk announced on 9 September 2025 that it will retire Zendesk Sell on 31 August 2027. It recommends Pipedrive, which has built migration tools. Teams on Sell that want marketing and service on one record often evaluate HubSpot instead; see our Zendesk Sell alternatives.

What is Zendesk's biggest competitor?

There is no single answer, but Zendesk publishes head-to-head pages against the rivals it meets most, including HubSpot, ServiceNow and Intercom. Our Zendesk competitors guide covers the wider field.

What is HubSpot's biggest competitor?

Salesforce. The most popular head-to-heads in HubSpot's own comparisons library are against Salesforce Sales Cloud and Marketing Cloud, and on the service side Zendesk vs HubSpot is listed among them.

HubSpot vs Zendesk: how do pricing models compare as teams grow?

Zendesk's per-agent pricing with optional add-ons scales linearly. Each new agent adds a predictable seat cost, but capabilities like Copilot or workforce management add incremental costs. HubSpot's onboarding fees are one-time, so the per-seat cost becomes more favorable after year one. HubSpot's AI credits (50 per resolved conversation) and Zendesk's per-resolution fees both add usage-based costs that grow with volume. For a 10-agent team, running the numbers for both year-one and year-two costs at current listed pricing is essential before committing.

What are the migration considerations when switching platforms?

Migrating between Zendesk and HubSpot involves moving ticket history, knowledge base content, automation workflows, and customer data. Key risks include losing ticket context during migration, breaking existing automations, and retraining agents on new workflows. Plan for a parallel-run period where both systems operate simultaneously, and prioritize migrating active support tickets and high-traffic knowledge base articles first. The Zendesk to HubSpot migration section above covers options and gotchas in more detail.

Which platform offers better reporting and analytics?

It depends on what you are measuring. Zendesk is stronger for pure service analytics: agent performance, SLA compliance, resolution times and pre-built dashboards across channels. HubSpot is stronger for lifecycle visibility, with dashboards that span marketing, sales, and service data. For agent quality and workforce management, HubSpot lacks Zendesk's dedicated QA and WFM depth, so support-focused teams often supplement it.