Customer Support and Voice AI
AI receptionist for small business: calls, bookings and handoffs
What an AI receptionist does on a real call, the rules that apply, a sample greeting and a pass/fail checklist to launch one safely.
Support Operations
AI Support Knowledge Agent for Zendesk
Solved Zendesk tickets point to the help center articles you are missing, and drafts appear in Zendesk Guide for review.
If your Zendesk agents keep pasting the same macro, that answer belongs in your help center. This agent reads solved tickets and your most-used macros, compares them with your existing articles, and drafts articles for the questions that have no answer yet. Drafts are saved unpublished in your Zendesk help center, so an editor reviews every word before customers see it.
- Solved tickets and overused macros reveal missing articles
- Drafts saved unpublished in your Zendesk help center
- An editor approves every article before it goes live
$4,400
20–30 working days
Optional maintenance $249/mo
What it is
AI Support Knowledge Agent for Zendesk reads your solved Zendesk tickets and the macros agents keep pasting, compares them with your help center, and drafts articles for the questions that have no answer yet. Drafts are saved unpublished in your Zendesk help center for an editor to approve.
Why businesses buy it
Every repeated macro in Zendesk is a small cost: an agent's time on a question a customer could have answered alone. Over months, those costs add up while the help center stays the same size. After launch, you see which topics lack articles and get drafts waiting in Guide for review. The Scope Card lists the Zendesk fields, destination and review rules before you order, so your content owners know exactly what will appear and that nothing publishes itself.
Problems this solves
Agents keep pasting the same Zendesk macro because no article exists
The agent reads your solved Zendesk tickets and the macros agents keep using. It compares them with your help center to find questions that have no article yet.
Help center gaps are guessed at rather than measured
Gaps are drawn from real solved tickets, not opinion. Your team sees which questions keep coming back without a public answer in your Zendesk help center.
Drafting help center articles keeps slipping down the list
Draft articles are written in your brand voice and saved unpublished in your Zendesk help center. An editor approves each one before customers can see it.
A good fit if
Your Zendesk agents paste the same macro dozens of times a week because no help center article covers that question.
Your help center runs on Zendesk Guide, and you want new drafts to appear there rather than in a separate document.
Ticket tags or forms in Zendesk already show roughly what each ticket was about, which helps group similar questions.
A Zendesk admin can issue an API token with an agent or admin role and spend 30 minutes on the field mapping.
Not the right fit if
Your help desk is Intercom. See AI Support Knowledge Agent for Intercom.
Your help desk is Freshdesk. See AI Support Knowledge Agent for Freshdesk.
You want suggested replies inside open Zendesk tickets, not new articles. See AI Support Copilot for Zendesk.
You want incoming Zendesk tickets sorted and assigned automatically. See AI Ticket Routing for Zendesk.
How it works
- Your Zendesk admin issues an API token with an agent or admin role, and a 30-minute call settles which ticket fields, tags and help center sections are in the mapping.
- The agent reads a batch of solved tickets and groups them by the question being asked, using tags and ticket forms where they help.
- Each group is checked against your published Zendesk help center articles and against your macros, so an answer that only lives in a macro is marked as a gap.
- For each gap it drafts an article in your brand voice, following up to twenty reference articles you picked, with the macro wording as a starting point.
- The draft is saved unpublished in the help center section you chose, ready for your editor to change, publish or reject in Zendesk.
- Before launch, twenty-five sample drafts are reviewed with you, so tone and structure are settled before the pipeline runs on its own.
What you provide within 72 hours
Your portal lists these the moment you order. Delivery starts the working day after everything is in and your access is checked.
- A Zendesk API token with an agent or admin role, shared securely in the way we agree, never by email.
- Your Zendesk admin for a 30-minute call on fields, tags and help center sections.
- Brand and tone guidelines, plus ten to twenty existing articles you consider good examples.
- The help center section where drafts should be saved, and the person who approves them.
- Any topics to start with, such as a product area that generates many tickets.
- Your escalation rules and support hours, and one decision-maker for sign-off.
- An API key for your own AI model account (for example OpenAI or Google Gemini), created for this build with a spending limit.
The 72-hour rule. Send everything on your checklist, including access, within 72 hours of ordering so your build starts on time.
Timeline
Start
Intake verified, Zendesk token working, mapping call booked.
Weeks 1–2
Ticket grouping and gap check against articles and macros built.
Week 3
Draft writing and unpublished saving to Zendesk Guide connected.
Weeks 3–4
Twenty-five sample drafts produced and reviewed with you.
Week 4
Two rounds of changes to tone, structure and topics.
Go-live
Pipeline live, handoff recorded, support begins.
| Option | Delivery time | Price |
|---|---|---|
| Standard | 20–30 working days | $4,400 |
| Express | 15–25 working days | $5,150 |
| Rush | 10–20 working days | $5,950 |
What you receive at handover
- The knowledge agent connected to your Zendesk account, saving drafts unpublished to your help center
- Two-way Zendesk connection with documented field mapping, plus up to one more system
- Brand profile and up to 20 reference examples, with up to three output formats
- Test report with 25 sample drafts reviewed and approved by you
- Admin guide, recorded 45-minute handoff session and 30 days of post-launch support
Expected benefits and how to measure them
- Your Zendesk help center can cover the questions agents answer most.
- Agents can rely less on pasting macros for common questions.
- Editors can review ready drafts instead of writing from scratch.
- Help center articles added
- Count new articles published from the agent's drafts each month in Zendesk Guide.
- Macro use on covered topics
- Use Zendesk Explore to compare macro usage on each new article's topic for four weeks before and after publishing.
- Tickets on covered topics
- Track ticket counts on topics with a new article, before and after it goes live.
Before you start: Export macro usage and ticket counts by topic from Zendesk Explore for the month before setup.
These are things to track, not promised results. Outcomes depend on your data, your team and your market.
Running costs
You pay for the build once. Running it costs roughly $20 to $150 a month in AI model usage, depending on how many tickets are read and drafts written, billed to your own accounts. Your Zendesk plan stays as it is.
Usage while we build and review samples is billed the same way, so the API token and provider accounts stay yours.
Ask about running costsCustom requirements
Writing drafts into more than one Zendesk brand or help center, translating articles, or mapping custom Zendesk objects needs a written Change Quote. Note it at checkout and the quote follows.
Request a custom versionKeep it running
Monthly maintenance covers monitoring, fixes and change hours for work such as pointing drafts to a new help center section or adding reference articles. It starts after the post-launch support period, bills monthly and can be cancelled any month.
$249/mo (the minimum fee, includes 2 change hours)
Optional. Starts after the post-launch support period. Cancel any month.
How maintenance worksHow this compares
| Do it yourself with a SaaS tool | Hire a custom agency | Upmark Labs | |
|---|---|---|---|
| Price | A help center AI add-on usually raises your per-agent subscription | A content writer bills per article | Ours is one fixed price, shown on this page before you buy |
| Finding gaps | Often searches articles, not solved tickets | Relies on a manual ticket review | Ours compares solved tickets with articles and macros |
| Where drafts go | Varies | A shared document you copy across | Ours saves unpublished drafts in your Zendesk help center |
| Delivery | Switch on fast, tune for weeks | Booked per batch | Ours has a fixed delivery time shown before you buy, with faster options |
Questions about this product
Why does the Zendesk knowledge agent look at macros?
Because a macro that agents paste often usually marks a question your help center should answer. The agent compares solved tickets with both published articles and macros, and flags answers that only exist in a macro as gaps. The macro text can then seed the first draft of the article.
Does it publish to our Zendesk help center on its own?
No. Drafts are saved unpublished in the help center section you choose, and an editor on your team publishes, edits or deletes them in Zendesk as usual. The agent never changes a published article, and nothing goes live to customers without a person approving it first.
Which Zendesk role does the knowledge agent's token need?
An API token tied to a user with an agent or admin role, created by your Zendesk admin. It is shared securely in the way agreed at intake, never by email. The connection reads tickets and macros and writes draft articles only within the documented field mapping.
Can the Zendesk edition skip tickets with personal or sensitive details?
Yes. Ticket forms, tags or groups can be excluded in the mapping, for example billing disputes or account security tickets. Drafts are written about the question, not the customer, and the twenty-five reviewed samples let you confirm no personal details carry through into article text.
What are express and rush prices for the Zendesk knowledge edition?
One fixed price covers the whole build and is shown on this page before you buy, with express and rush delivery listed beside it at a set extra cost. Each includes the Zendesk mapping, twenty-five reviewed sample drafts, two rounds of changes and a recorded forty-five-minute handoff.
How often does the agent look for new help center gaps in Zendesk?
On a schedule you set at intake, such as weekly or monthly. Each run reads tickets solved since the last one, so drafts track what customers are asking now. A short gap list is delivered alongside the drafts so your editor can see what was found and why.
Guides on this topic
All guides Turn repeated Zendesk answers into help center articles.
Order the Zendesk edition and solved tickets and overused macros become unpublished help center drafts, waiting in Zendesk for your editor.
Works well with
Employee Lifecycle
AI Helpdesk Agent
Resolves employee IT and internal service requests and routes the rest to the right team.
Support Operations
AI Support Copilot
Drafts replies and surfaces relevant articles for human agents inside the helpdesk.
Support Operations
AI Support QA
Scores conversations against your quality rubric and highlights coaching points.