Shopify
Stripe
Slack
Notion
Google Workspace
Confluence
How to Choose a Zendesk Implementation Partner (2026): A 6-Step Process, Scorecard and SOW Checklist
To choose a Zendesk implementation partner, decide the scope first (an AI agent on the Zendesk you already have, or a full Zendesk build or migration), then shortlist three to five partners, send them all the same written brief, score the proposals on weighted criteria, call two references about AI work specifically, and sign a statement of work that names who fixes the AI after go-live. When we read public prices on October 14, 2026, one UK government framework supplier's Zendesk rate card ran £800 to £1,600 a day, and published Zendesk build packages ran from $3,750 (Smart Instinct) to £20,000 (Capventis). If the only new thing is the AI agent, you may not need a partner at all.
Key takeaways
- Choosing a Zendesk implementation partner takes six steps: define the scope, shortlist three to five partners, request proposals from one brief, score them, check references and negotiate the statement of work.
- Capventis lists a Zendesk Suite Core Launch at £10,000 to £20,000 and day rates of £800 to £1,600 by role on the UK's G-Cloud 15 framework, read October 14, 2026.
- Smart Instinct's Zendesk builds cost $3,750, $10,500 and $17,500 for up to 33, 90 and 150 hours, which works out to about $114 to $117 an hour.
- Zendesk's own Professional Services sells Launch, Assist and Premier plans but publishes no prices, saying pricing is scoped to the plan, environment size and requirements.
- A Zendesk statement of work for AI should name who owns the agent's configuration and prompts, the post-launch support hours, and how wrong answers get fixed after go-live.
This page is the buying process: the steps, what an engagement costs, a scorecard and the contract. It doesn't repeat our other two Zendesk pages. For partner tiers, the AI Agents certification, how to filter the directory, the 10 questions to ask and red flags, read our ranked list of Zendesk implementation partners. For the three routes to AI on Zendesk and the phases with days, read our Zendesk AI implementation guide.
Disclosure: Macha publishes this blog. Macha isn't a Zendesk partner. It sells an AI agent that runs inside Zendesk with setup included, and it appears once, in the section on when you don't need a partner.
What are the six steps to choosing a Zendesk partner?
| Step | What you produce | Typical time |
|---|---|---|
| 1. Define the scope | A one-page brief: AI layer only, or a Zendesk build or migration | 1 to 2 days |
| 2. Shortlist | Three to five partners with a reason each | 2 to 3 days |
| 3. Request proposals | The same brief, the same questions, the same deadline for all | 1 to 2 weeks |
| 4. Score | A weighted scorecard per proposal | 1 day |
| 5. Check references | Two calls per finalist, about AI work | 3 to 5 days |
| 6. Contract | A statement of work you'd be happy to enforce | 1 to 2 weeks |
The times are our estimate for a mid-sized team, not a published benchmark. Most of the calendar goes to waiting on proposals and legal review, so start step 6's security and DPA paperwork while proposals are out.
Step 1: Decide whether you need a Zendesk build or only an AI layer
This decision changes who you should talk to. A partner's core work is Zendesk itself: groups, routing, SLAs, forms, views, Explore reporting, migrations and custom apps. Capventis's published Core Launch package on G-Cloud is a good picture of that work. It lists a workshop, solution design, users and roles, channels, triggers and automations, groups and views, fields and forms, macros, testing, UAT, admin training and go-live support. There's no AI line in it.
| Your situation | Scope to put in the brief | Who to ask |
|---|---|---|
| Moving to Zendesk from another desk | Migration, build, then AI | Partners only |
| Zendesk works but routing, SLAs or reporting don't | Redesign, then AI | Partners only |
| Zendesk works and you want an AI agent on top | AI agent only | Partners with AI work, and AI vendors with setup included |
| On Zendesk's Essential AI agents or legacy bots | Rebuild on current agents or a third-party agent | Both |
If the AI agent is the whole project, include at least one vendor that sets its agent up for you in the comparison. It changes the price you'll accept from everyone else.
Step 2: Shortlist three to five partners
Start in Zendesk's partner directory; our partners list shows how to filter it for AI work. Two other places are worth a look. UK public-sector buyers can buy Zendesk services through the government's G-Cloud 15 framework, where suppliers publish pricing documents. And Zendesk sells its own Professional Services in three forms: Launch (standard and custom implementation), Assist (a designated consultant for configuration and optimization) and Premier plans (technical support with response-time guarantees). None of the three has a published price.
Write down why each name is on the list. Three is enough to compare prices. More than five, and nobody on your side reads every proposal properly.
Step 3: Send every partner the same brief
Proposals are only comparable if every partner answers the same brief. Put these in it:
- Monthly ticket volume by channel, your Zendesk plan, and agent count.
- The ticket categories you want the AI to handle first, with 30 to 50 sample tickets per category (redacted).
- Systems the AI needs to read from or write to, such as Shopify, Stripe or an internal API.
- What "done" means: the acceptance criteria from the SOW section below.
- Who on your side has admin rights and how many hours a week they can give.
- A budget range. Partners who know it scope to it instead of guessing high.
- A required price format: a fixed price per phase, the day rate behind it, and a separate monthly price for support after go-live.
The price format matters most. Without it, one partner quotes a project, another quotes days, and a third bundles a license, and you can't compare any of them.
Step 4: Score proposals on a weighted scorecard
The scorecard is in the next section. Score every proposal alone before the team discusses them, then average. Discussing first means the loudest person's favorite wins.
Step 5: Call references about AI work, not Zendesk work
Directory reviews often describe Zendesk setup work from before AI agents. Ask each finalist for two clients whose AI agent has been live for at least three months, and ask those clients:
- What share of tickets the AI handles today, and how that compares with what the partner forecast.
- Who reads AI conversations each week now, and whether that was the plan at signing.
- How many hours of post-launch support were in the contract, and when they ran out.
- What the first change request after launch cost and how long it took.
- Whether they could make changes to the AI agent themselves after handover.
- Whether they'd hire the same people again for the next category.
Question 3 tells you more than any proposal. A partner that sold a 30-day hypercare and then a retainer will have clients who can tell you exactly when the hours ran out.
Step 6: Negotiate the statement of work
Use the checklist further down. Most of the money you'll spend after the project gets decided in this document, so give it as much time as the scoring.
How should you score Zendesk partner proposals?
Copy this table into a spreadsheet. Score each criterion 1 to 5, multiply by the weight, and add up. The maximum is 500. The weights are ours, set for a team adding AI to Zendesk; move weight from row 2 to row 1 if the project is mainly a migration.
| Criterion | Weight | A 5 looks like | A 1 looks like |
|---|---|---|---|
| 1. Understood your scope | 20 | Restates your categories, volumes and systems correctly; flags risks you missed | Generic deck, your company name pasted in |
| 2. Evidence of Zendesk AI delivery | 20 | Named AI agent projects in the last 12 months, two live references | AI mentioned only in a services list |
| 3. Help after go-live | 15 | Named hours or a monthly tuning service, with a price | "Hypercare" with no hours or end date |
| 4. Price clarity and first-year total | 15 | Fixed price per phase, day rate, monthly support price, Zendesk AI fees shown separately | One lump sum, or "to be scoped" |
| 5. The people who'll do the work | 10 | Named consultant, certified on AI Agents, on your project | Senior people in the pitch, unnamed team on delivery |
| 6. Ownership and exit terms | 10 | You own config, prompts and docs; handover included | Configuration lives in the partner's accounts |
| 7. Timeline realism | 10 | Phases with weeks and what they need from you | A date with no dependencies |
For example, Partner A scores 4, 5, 2, 3, 4, 4, 4 and totals 80 + 100 + 30 + 45 + 40 + 40 + 40 = 375. Partner B scores 4, 3, 5, 4, 3, 5, 4 and totals 80 + 60 + 75 + 60 + 30 + 50 + 40 = 395. B wins with less AI experience because it priced and named the work after go-live. We weighted it that way because a partner that prices month-three fixes up front is rarer than one that can configure an AI agent.
What does a Zendesk partner engagement include and cost?
Most partners don't publish prices. These are the public figures we found on October 14, 2026, each from the provider's own page or its government framework pricing document. The G-Cloud figures are what those suppliers offer UK public-sector buyers, in pounds; a commercial quote may differ.
| Provider (source) | What it sells | Published price |
|---|---|---|
| Capventis (G-Cloud 15 pricing document, January 2026) | Zendesk Suite Core Launch: workshop, design, build, testing, training, go-live | £10,000 to £20,000 |
| Capventis (same) | Ad-hoc drawdown; data migration; training; extra channels | From £1,200 a day; £1,250 a day; £1,250 a session; £3,300 a channel |
| Capventis (same) | Role rate card, time and materials | £800 to £1,600 a day; 5% off at 50 days, 10% at 100, 15% at 500 |
| The SaaSy People (G-Cloud 15 pricing document, January 2026) | Expert services, scoped per project | £157 to £360 an hour |
| The SaaSy People (same) | Managed services, by term length | From £89 an hour (3 months) down to £49 an hour (24 months) |
| Netpremacy (G-Cloud 15 pricing document, January 2026) | Zendesk Suite deployment, configuration and training, on a company-wide rate card | £1,095 a day for project manager, analyst, trainer and developer roles; £1,595 for its Google Cloud architect roles; a 7.5-hour day |
| Smart Instinct | Audit; three build tiers; retainer | $750; $3,750, $10,500, $17,500; from $1,000 a month |
| Zendesk Professional Services | Launch, Assist, Premier | Not published |
| Marketplace freelancers (PeoplePerHour and Freelancer.com Zendesk pages) | Hourly Zendesk work | $10 to $92 an hour (PeoplePerHour); $19 to $50 an hour (Freelancer.com featured profiles) |
Three numbers are worth doing the arithmetic on. Smart Instinct's tiers include up to 33, 90 and 150 hours, valid for 90 days, which works out to about $114 to $117 an hour if you use every hour, and more per hour if you don't. Past a tier's limits it charges $1,500 per extra integration and $3,000 per extra brand. Its first tier with "AI agents and Copilot configured" is the $10,500 Professional build; its Zendesk page lists core ticketing for the $3,750 tier, though its general pricing page says that tier's AI "answers the easy questions and escalates the rest". On time and materials, a 15-day project at Capventis's £1,200 drawdown rate is £18,000, inside its Core Launch range. And a retainer from $1,000 a month is $12,000 a year, which is more than the Professional build itself.
Then there's the meter. A partner usually configures Zendesk's own AI agents, so Zendesk's per-resolution charge runs on top of every figure above. Our Zendesk AI pricing breakdown covers that meter. For comparison at the low end, the two 2026 PeoplePerHour posts we found for "turn our Zendesk history into a help center and put an AI agent on top" offered $537 and $671.
Which commercial model should you sign?
The model decides who carries the risk of the project running long, and who gets paid when the AI needs fixing.
| Model | How it bills | Pros | Cons | Fits |
|---|---|---|---|---|
| Fixed fee | One price per phase or project (Capventis Core Launch, Smart Instinct tiers) | You know the cost; overruns are the partner's problem | Scope gets defined narrowly; every addition is a change request; hours often expire (Smart Instinct's after 90 days) | A build with a clear scope |
| Time and materials | Day or hourly rate (Capventis £800 to £1,600 a day) | Flexible; you pay for what's used | No ceiling unless you write one; the partner earns more the longer it runs | Discovery, or work you can't scope yet |
| Retainer | A monthly block of hours (Smart Instinct from $1,000 a month) | Someone is on call for changes | Unused hours are usually lost; it pays for availability, not results | Teams changing Zendesk every month |
| Managed service | A monthly fee for running the instance (The SaaSy People from £49 to £89 an hour by term) | Ongoing admin and tuning are someone's job | Longer terms buy the lower rate; harder to leave | Teams with no Zendesk admin |
Name the incentive in each before you sign. A time-and-materials partner earns more from a longer project. A fixed-fee partner earns more from a narrower definition of "done". A retainer earns the same whether the AI improves or not. Managed services tie the rate to the term, so the cheapest hour comes with the longest commitment. Each incentive points to a clause to negotiate: a not-to-exceed cap on time and materials, written acceptance criteria on a fixed fee, a rollover on retainer hours, and an exit clause on a managed service.
What should a Zendesk AI statement of work include?
Use this as a checklist when the first SOW draft arrives. Each line is something we'd want in writing before signing.
| Clause | What to write | Why it matters |
|---|---|---|
| Deliverables | Every configured object by name: AI agent use cases, knowledge articles, triggers, integrations, reports | "Configure AI agents" can mean one use case |
| Acceptance criteria | A test set of real past tickets per category (normal cases, escalations, edge cases, tone) and the pass mark for each | Without it, "done" is the partner's call |
| Knowledge base ownership | Articles written for the AI live in your Zendesk help center, in your name | Content is the expensive part to rebuild |
| AI agent configuration and prompts | Instructions, use cases, actions and API credentials live in your Zendesk and accounts; the partner documents them | You can change or move partners without starting over |
| Post-launch support hours | A number of hours, the period they cover, who reads AI conversations, and the price after they run out | Most packages stop at go-live or after 30 days |
| Change requests | How a change is requested, the rate, and a turnaround time | Policy changes break AI answers fastest |
| Data access and security | Least-privilege admin roles, named people with access, a DPA, where ticket data is processed, and deletion at the end | Partners see every ticket you have |
| Third-party fees | Zendesk AI resolution fees and other vendor costs listed separately from services | Stops a license or meter hiding inside the services fee |
| Exit and handover | A handover session, admin credentials returned, documentation delivered, and a notice period | Decides what leaving costs |
| Payment milestones | Payment tied to accepted phases, not dates | Keeps the incentive on finishing |
For the test set in the acceptance criteria, our pre-launch test guide shows how to build one from real tickets. For what happens when a launch goes wrong anyway, see why AI pilots get switched off.
Partner, freelancer or vendor-led: which fits you?
| You are | Pick | Why |
|---|---|---|
| Moving to Zendesk from another help desk | A Zendesk partner | Migration is core partner work; Smart Instinct publishes migrations from $3,500 |
| A UK public-sector team | A G-Cloud 15 Zendesk supplier | Published prices and a framework contract |
| Enterprise, several Zendesk products, strict procurement | A Premier-level partner or Zendesk Professional Services | Certifications, contract terms, and response-time guarantees on Zendesk's Premier support plans |
| Zendesk works and you want one AI agent, no admin to spare | A vendor that sets its agent up and tunes it | Setup and tuning in one monthly price |
| Zendesk works and you have an admin with time | Zendesk's own AI agents, maybe a freelancer for a few days | Lowest cash cost; the tuning is your admin's job |
| A small team on a tight budget, one clear task | A marketplace freelancer | $10 to $92 an hour on PeoplePerHour; agree a fixed scope and a handover |
| You need custom Zendesk apps or Salesforce or HubSpot sync | A Zendesk partner | Development work, out of scope for AI vendors |
What if you only need the AI agent?
Run the same process, but put an AI vendor that sets its own agent up on the shortlist next to the partners, and score it with the same seven rows. Two rows change most. On row 3, a vendor that includes tuning in its monthly price scores high, where a partner's 30-day hypercare scores low. On row 6, the question shifts from "who owns the configuration" to "what happens to the agent and its knowledge if we cancel", and the vendor should answer it in writing just as a partner would.
Macha is our product and one of those vendors, not a Zendesk partner; it doesn't sell Zendesk licenses, builds or migrations. Against the SOW checklist above, here's what the done-for-you offer covers. Deliverables: our team analyzes about a month of your past tickets, then builds the knowledge base and the agent for the first category. Acceptance: the agent runs in safe mode, drafting internal notes in your Zendesk, and a category only goes to public replies when your team says the drafts are right. Timeline: "live in safe mode within 7 days, or your first month is free", after about 15 minutes of connecting. Post-launch support and change requests: a dedicated success manager handles new categories, instruction changes and new tools. Price: about $0.40 per ticket, from $299/month for 750 tickets, with setup included and no setup fee. The trial includes the same setup: $50 of free usage (about 125 tickets), no credit card, no time limit. Data: our DPA is public.
It suits teams on Zendesk whose Zendesk already works and who want an agent someone else builds and tunes. It's the wrong fit for a migration or a Zendesk redesign; hire a partner for that, and the two can work side by side. To see which of your categories an agent could take first, request a free support audit.
Common questions
How do I choose a Zendesk implementation partner?
Decide the scope first, then shortlist three to five partners, send them one written brief with a required price format, score the proposals on weighted criteria, call two references whose AI agent has been live for three months or more, and negotiate a statement of work that covers post-launch support and ownership of the configuration.
How much does a Zendesk consultant cost?
On the UK's G-Cloud 15 framework, read October 14, 2026, Zendesk suppliers published £800 to £1,600 a day by role (Capventis), £1,095 a day for Netpremacy's project and delivery roles, and £157 to £360 an hour for expert services (The SaaSy People). Smart Instinct's published builds work out to about $114 to $117 an hour if every included hour is used. Freelancers on PeoplePerHour's Zendesk page listed $10 to $92 an hour on the same day.
What does Zendesk Professional Services include, and what does it cost?
Zendesk's own Professional Services sells Launch (standard and custom implementation), Assist (a designated consultant) and Premier plans (technical support with response guarantees). It publishes no prices. Its page says pricing is scoped to your plan, the size of your environment and the complexity of your requirements.
Should I pay a Zendesk partner a fixed fee or by the day?
Pay a fixed fee per phase when the scope is clear, and add written acceptance criteria so "done" isn't the partner's call. Pay by the day for discovery or work you can't scope yet, with a not-to-exceed cap. Price support after go-live separately in either case.
Who should own the AI agent configuration after a Zendesk project?
You should. Write into the statement of work that the AI agent's instructions, use cases, actions, knowledge articles and credentials live in your own Zendesk and accounts, and that the partner documents them and runs a handover session. Smart Instinct's answer to this question on its own page is "You do, documented."
How many Zendesk partners should I shortlist?
Three to five. Three gives you a price comparison, and more than five means nobody on your side reads every proposal properly. If the AI agent is the whole project, make one of the names a vendor that sets up its own agent, so you can compare a project fee with a monthly price.
How we researched this
On October 14, 2026 we searched the UK government's Digital Marketplace (G-Cloud 15, Cloud Support) for Zendesk services and read the pricing documents published by Capventis (dated January 26, 2026), The SaaSy People (January 4, 2026) and Netpremacy (January 27, 2026). We checked the unit in each document and only quote rates where it's stated (per day, per hour, per session). We read Smart Instinct's Zendesk page and Zendesk's Professional Services page the same day. We read the PeoplePerHour and Freelancer.com Zendesk pages for hourly rates the same day. The two PeoplePerHour job budgets come from our who-can-set-up page, read October 13, 2026. The six steps, the scorecard weights, the worked scoring example and the SOW checklist are ours, built from the gaps we saw in published packages: post-launch hours, change requests and ownership are the clauses most often missing. We didn't contact or hire any partner, and none paid for a mention. Prices change, so confirm before you sign. For every route to AI support across help desks, see our AI customer support implementation guide.
