Where you will run into Zendesk (5)
- Sales Cloud customer whose support team runs Zendesk Suite, where account teams cannot see open tickets without switching tools or trusting the sync
- Support leader with 20 to 200 agents planning AI agents for chat and email who is comparing automated resolution pricing with Agentforce
- Company adding field service, returns or entitlements and finding that the help desk does not hold assets, contracts or service history
- Customer experience program led by a COO or CIO who wants one view of the customer across sales, service and success
- Zendesk renewal where the buyer is weighing an upgrade to Suite Professional or Enterprise against consolidating on Service Cloud
Competitor snapshot (10) Verified facts
| Zendesk list prices (as of October 2026) | Support Team $19, Suite Team $55 and Suite Professional $115 per agent per month paid yearly; $25, $69 and $149 billed monthly. Suite Enterprise is quoted by sales. The page advertises 20% off for annual billing. Source |
|---|---|
| Plan boundaries | Suite Team adds AI agents, an AI knowledge base, AI Action Builder, omnichannel routing, messaging, live chat and telephony. Suite Professional adds skills-based routing, an IVR phone tree and AI App Builder. Suite Enterprise adds approval workflows, a sandbox environment and custom agent roles. Source |
| AI agents and automated resolutions (as of October 2026) | Zendesk says AI agents are included in every Suite and Support plan and billed per automated resolution: a request resolved without escalation to a human. Plans include 5 (Team tiers) or 10 (Suite Professional) resolutions per agent per month. More cost $1.50 each committed or $2.00 pay-as-you-go. Source |
| Copilot add-on (as of October 2026) | $50 per agent per month paid yearly, available on Professional and higher plans. Suite Professional also lists a pooled allowance of 5 Copilot uses per agent per month, capped at 500 uses per instance. Source |
| Action credits (as of October 2026) | Action Builder usage draws on credits: up to 40K actions per month on Support Team and Suite Team, 100K on Suite Professional, and 2.7M per year on annual Suite Enterprise. Additional credits cost $200 per 100K actions per subscription term. Source |
| Other add-ons and seats (as of October 2026) | Workforce Engagement Bundle $50 and Contact Center $83 per agent per month paid yearly. Suite Professional includes up to 100 light agents, who can read tickets and add private comments without a full seat. Source |
| Contract and trial terms | Subscriptions are month to month, annual or multi-year. The 14-day trial runs on Suite Professional features with Copilot included by default. Source |
| Zendesk-Salesforce integration | Works with Salesforce Performance, Unlimited, Enterprise or Developer Edition, or other editions with API access. It updates Zendesk organizations and users from Salesforce accounts and contacts, and syncs Zendesk ticket data to Salesforce case fields. Multiple Salesforce orgs can be connected. Source |
| Service Cloud comparison prices (as of October 2026) | Service Cloud lists Starter Suite at $25 and Pro Suite at $100 per user per month, with the Core, Advanced and Max editions at $195, $395 and $550 per user per month on annual billing. Max includes Agentforce for Service, contact center digital channels and 2.75M Flex Credits per org per year. Enhanced Messaging is $75 per user per month on Core and Advanced. Source |
| Agentforce buying models (as of October 2026) | Flex Credits at $500 per 100K credits, Conversations at $2 per conversation for customer-facing agents, or a $125 per user per month Agentforce add-on (Sales, Service or Field Service) for unmetered employee use. Source |
As of October 27, 2026. Vendors change packaging and prices often; confirm before quoting a number to a customer.
Who decides, and how to talk to them (5) Approach
VP of Support / Head of CX
Cares about: Agent productivity, resolution times, and not disrupting a team that is hitting its targets today.
Your angle: Respect the operation they built. Ask which metrics they report every week and where agents leave the help desk to find answers, such as order status, contract terms or the account owner. Then show those answers on the case.
CIO / IT
Cares about: How many systems hold customer data, identity and security reviews, and the cost of keeping two customer databases aligned.
Your angle: Map every integration that touches support today. Show where one platform removes a connection, and be honest about the integrations that will remain.
Sales leadership (CRO or VP Sales)
Cares about: Seeing open issues before a renewal or expansion call, and no surprises from support escalations.
Your angle: Ask about the last renewal that went badly because of a support problem the account team did not know about. That story often moves the deal.
CFO
Cares about: Per-agent cost, AI spend that grows with volume, and add-ons that raise the bill after signature.
Your angle: Model both AI pricing units with real volumes: Zendesk resolutions and Copilot seats against Agentforce Flex Credits, conversations or per-user add-ons. Add light agents, contact center add-ons and admin time on both sides.
Support Operations / Zendesk admin
Cares about: Triggers, macros, views and routing rules tuned over years, and how much of that work must be rebuilt.
Your angle: Treat this person as the expert they are. Ask for an export of triggers and macros, sort them into keep, rebuild or retire.
Where Salesforce wins (6) Approach
Cases sit next to the revenue record
In a Salesforce org, a case belongs to the same account that holds opportunities, contracts, orders and assets, so a support agent and an account executive look at one record. Zendesk's Salesforce integration copies account and contact data into Zendesk and pushes ticket data into Salesforce case fields. That works, but two systems still hold the customer. Ask the support lead what an agent looks up elsewhere during a typical ticket, then show that context on the case page. The cybersecurity case study replaced a separate ticketing tool with Service Cloud beside Sales Cloud.
See the proof →Agentforce works with the customer's real data and permissions
Agentforce for Service runs through Salesforce Flows, objects and user permissions, so an agent that checks an order, updates an entitlement or drafts a reply follows the same rules as a person. Start with one high-volume case type and keep a human reviewing drafts until the knowledge base is strong. The biotech case study took that phased path and produced send-ready drafts for 30% of question-type cases.
See the proof →More than one way to pay for AI
Salesforce lists three Agentforce buying models: Flex Credits at $500 per 100K credits, $2 per conversation for customer-facing agents, and $125 per user per month add-ons for unmetered employee use. Max includes the Agentforce for Service add-on and 2.75M Flex Credits per org per year. Zendesk bills AI agents per automated resolution beyond a monthly allowance per agent. Neither unit wins in every case, so run both with the buyer's ticket volume and expected resolution rate.
Entitlements, assets and field work on one platform
Contracts and entitlements are available from Pro Suite, while assets and work orders come with Core and higher editions. When support depends on what the customer bought, what is under warranty and whether a technician must visit, those records belong next to the case. The packaging manufacturer case study moved field scheduling out of Outlook calendars onto Salesforce Field Service.
See the proof →Portals for customers, partners and independent agents
Experience Cloud builds authenticated portals on the same data as Service Cloud, so a partner or customer can open a case, check status or search knowledge without a second user store. The payments ISO case study gave 60+ independent agents a self-service portal, plus Service Cloud case routing with SLA escalations.
See the proof →Back-office integration for service that touches money
Refunds, credits, warranty claims and shipment changes all need billing or ERP data. MuleSoft and Salesforce APIs connect those systems at volume, with errors an admin can see and fix. Ask which support requests today require someone to log in to another system, and count them. That list becomes the integration roadmap.
Where Zendesk is strong, and how to respond (4)
Acknowledging these builds credibility. Buyers already know them.
Quick to launch and easy for agents
Zendesk sells on a clean agent workspace and guided setup. Its trial runs on Suite Professional with Copilot included, so a support leader can test the full product before buying.
How to respond: Do not argue about the interface. Ask what agents need to see that is not in the help desk today, and keep the discussion on customer context and process rather than screens.
Published entry pricing and flexible terms
Support Team lists at $19 and Suite Team at $55 per agent per month on annual billing, and Zendesk offers month-to-month subscriptions. A small team can buy online and move up one tier at a time.
How to respond: Price the tier they will really need, with Copilot at $50 per agent, Contact Center at $83, extra resolutions and action credits. Compare that with the Service Cloud edition that fits, using three years of growth.
Outcome-based AI pricing
Zendesk charges for AI agents per automated resolution, defined as a request resolved without escalation to a human, and includes a monthly allowance with each plan. Finance teams often like paying only when the AI finishes the job.
How to respond: Grant that the model is easy to explain. Ask how they will forecast resolutions as AI coverage grows, then lay the Agentforce options beside it with the same volume assumptions.
Broad channel coverage and prebuilt apps
Suite plans bring email, messaging, live chat and telephony into one workspace, and the Zendesk Marketplace offers prebuilt apps and integrations for common support tools. Teams with a standard stack find much of what they need ready to install.
How to respond: Narrow the list to integrations that carry customer or financial data, such as ERP, billing and order management, and compare how each platform handles those at volume.
Discovery questions that change the deal (11) Approach
Business
- How does a support problem reach the account team today, and how often do they hear about it too late?
- What does leadership want to know about customers that takes both sales and service data to answer?
- Are you planning to add field service, partner support, a customer portal or new regions in the next two years?
Service operations
- Which tickets need information from outside Zendesk, and where does the agent go to find it?
- How do you handle contracts, warranties or service levels that differ by customer?
- Which triggers, macros and routing rules are critical, and which does nobody remember the reason for?
AI and automation
- Which request types could an AI agent close on its own this year without a person reviewing it?
- How many automated resolutions do you expect per month at full rollout, and what would that cost on your current plan?
- What actions must an AI agent take in other systems, such as issuing a credit or checking a shipment?
Cost and ownership
- What do you spend today on Zendesk add-ons, extra resolutions and the integration with Salesforce?
- Who maintains the sync between the two systems, and how much time does it take each month?
Objections, and what to say (6) Approach
"Our agents love Zendesk. We are not changing."
Ask whether the problem is the agent tool or the customer record, because those can be solved separately. If the buyer has Sales Cloud, the first step can be better context through the integration while you build the case for consolidation at the next renewal. If agent productivity is the worry, offer a pilot on one queue in the Service Console with their real case types.
"Zendesk is far cheaper than Service Cloud."
Line up quotes for the same scope. Suite Professional lists at $115 per agent on annual billing, and Copilot adds $50 per agent. Contact Center adds $83, and resolutions beyond the allowance cost $1.50 to $2.00 each. Then add the cost of running the Salesforce integration. Service Cloud Core lists at $195 per user per month. When the scope is pure ticketing, Zendesk may well cost less, and you should say so.
"Zendesk's AI agents are included. Agentforce costs extra."
Zendesk includes an allowance of automated resolutions per agent each month, 5 on Team plans and 10 on Suite Professional, and charges for each one after that. At volume, both platforms charge for AI work. Ask for monthly contact volume and the share they expect AI to resolve. Price that on Zendesk resolutions and on Agentforce Flex Credits or conversations. Then compare what each agent can actually do in their systems.
"The Zendesk integration already gives us one view of the customer."
It gives a useful view, and Zendesk supports it on Salesforce editions with API access. Ask how it behaves day to day: which fields sync, in which direction, how often, and who fixes errors. Account and contact data flows into Zendesk and ticket data flows into Salesforce case fields, so each team still works in its own tool. Coexistence may be enough. If they want routing, entitlements and AI acting on one record, consolidation is the real conversation.
"Migrating years of tickets is too risky."
Ask how far back agents actually look. Many teams need recent tickets in full and older history only for reference or compliance. Propose moving open and recent tickets as cases with comments and attachments, archiving the rest where it stays searchable, and keeping Zendesk read-only for a period. The cybersecurity company consolidated a homegrown ticketing tool into Service Cloud and went live in roughly 6 to 8 weeks.
Proof to send →"Service Cloud needs consultants and an admin. Zendesk does not."
A lean support org may run Zendesk without outside help, and that matters. Ask who maintains triggers, macros and the Salesforce sync today, because that person is already an admin in practice. Show Omni-Channel routing and case assignment configured in Setup without code. Then be clear about ownership after go-live: an internal admin, a partner, or both.
Traps that lose these deals (5)
- Treating the support leader as a blocker. They own the metrics and will veto any plan that puts those metrics at risk.
- Pitching Service Cloud to a small team whose only need is email ticketing with no link to a CRM.
- Quoting Max against Suite Team without matching channels, AI volume and scope on both sides.
- Promising an AI resolution rate. Scope a pilot on one case type and let their data set the number.
- Ignoring years of triggers and macros. Plan the admin's review before the first design workshop.
Qualify honestly
Strong fit for Salesforce
- Sales Cloud already in place, with leadership frustrated that support data sits in another system
- Service that depends on contracts, entitlements, assets, orders or warranty status
- Plans for field service, a customer or partner portal, or service-led renewals and expansion
- AI agent goals that need actions in CRM, billing or ERP, not only answers from a knowledge base
- A CIO or COO sponsoring fewer systems and a single customer record
Risky fit
- Small support team running email-only ticketing with no CRM and no plan to add one
- Support org that just renewed a multi-year Zendesk contract and faces no executive pressure to change
- Budget set at Support Team or Suite Team pricing with no room for implementation
- No owner for Salesforce administration and no appetite for a partner
Salesforce products to lead with (6)
Moving the customer off Zendesk
Plan a Zendesk move in three parts: data, logic and channels. Organizations map to accounts, end users become contacts, and tickets become cases, with public and private comments carried into the case feed and attachments into Files. Agree on a cut-off for full ticket history and archive the rest. Export triggers, automations, macros and SLA policies, then rebuild what still matters as assignment rules, Omni-Channel routing, Flow, and entitlements with milestones. Help Center articles move into Salesforce Knowledge and need review before an AI agent relies on them. Re-point email addresses, chat widgets and phone numbers last, one channel at a time, and keep Zendesk read-only briefly.
Questions AEs and buyers ask (5)
How much does Zendesk cost compared with Service Cloud?
As of October 2026, Zendesk lists Suite Team at $55 and Suite Professional at $115 per agent per month on annual billing, with Suite Enterprise quoted by sales. Salesforce lists Service Cloud Pro Suite at $100 and Core at $195 per user per month, billed annually. Add AI, contact center and integration costs before comparing.
How does Zendesk charge for AI agents?
Per automated resolution, meaning a request the AI agent resolves without escalation to a human. Plans include 5 or 10 resolutions per agent per month, and more cost $1.50 each committed or $2.00 pay-as-you-go. Copilot for human agents is a separate add-on at $50 per agent per month.
Can Zendesk and Salesforce run side by side?
Yes. Zendesk's Salesforce integration brings account and contact data into Zendesk and ticket data into Salesforce cases, on Salesforce editions with API access. The push to consolidate usually comes from wanting service processes and AI to work on one record.
How is Agentforce priced for service teams?
As of October 2026, Salesforce lists Flex Credits at $500 per 100K credits, $2 per conversation for customer-facing agents, and a $125 per user per month Agentforce add-on for unmetered employee use. Max edition includes the add-on and 2.75M Flex Credits per org per year.
When should a buyer stay on Zendesk?
When support is a self-contained ticketing operation, the team is satisfied, and service has no need to share records, processes or AI actions with sales, billing or field teams.