Appearance
Zendesk
Overdesk connects to Zendesk with an API token from your Admin Center. It reads your tickets, learns from your resolved tickets, macros and Help Center articles, and posts each draft on the ticket as an internal note for your agents to review. For the overview of Overdesk with Zendesk, see the Zendesk page on overdesk.io.
Connect Zendesk
You need to be an owner or admin in Overdesk, and an admin in Zendesk to create the token.
- In Zendesk, open Admin Center, then Apps and integrations, then APIs, then API tokens, and create a token.
- In Overdesk, open Integrations and choose Zendesk.
- Enter your Subdomain: the part before .zendesk.com, such as
acme. - Enter the Admin email of the Zendesk account you created the token on.
- Paste the API token and choose Connect.
Zendesk pairs the token with that email address, so a token typed against a different email fails as if the token itself were wrong. Once connected, the Zendesk page on Integrations shows your Zendesk address.
What joins your knowledge base
- Resolved tickets, through Sync past conversations, every night at 03:00.
- Macros, imported as saved replies alongside your tickets.
- Help Center articles, through Sync help desk docs, every night at 04:30. Only published articles are imported, and the sync uses the same credentials, so there is nothing more to set up. If your account has no Help Center, the Knowledge base page says so, and articles start syncing once you enable one.
Drafting also needs a docs site address. Your knowledge base lives in Zendesk Guide: activate Guide, make your Help Center public, and paste its address into Docs site URL(s) in Settings → Knowledge base. See Point Overdesk at your docs.
Where drafts appear
Every draft arrives on the ticket as an internal note, visible to your agents and never to the requester. Zendesk has no API for filling in an agent's reply box, so the unsent draft reply option in Where drafts go stays with Help Scout, and your team keeps receiving notes.
If you edit or discard a draft from its page in Overdesk, Overdesk adds a note to the ticket saying what changed.
Sending replies
Once your workspace turns sending on, Overdesk sends the replies your guardrails approve as a public reply on the ticket, as the agent whose email you entered when you connected. It sends on tickets that came in by email and on tickets created through the API. A ticket from a web form, chat, messaging, SMS, voice or a social channel waits for your team.
After a reply the ticket is set to Pending, so it waits for the customer. Under After Overdesk sends a reply you can choose Open or Leave as is instead. Solved and On-hold are not offered: Solved would assign the ticket to the agent Overdesk replies as, and a Zendesk account can switch On-hold off. A reply that hands the ticket to a teammate leaves it Open, in your team's queue, whatever you chose.
Overdesk cannot see a teammate who is part-way through a reply, so if a teammate answers at the same moment as an automatic reply, your customer can get both.
Zendesk wraps what Overdesk sends. The email your customer receives carries Zendesk's own footer, "This email is a service from" your company's name and "Delivered by Zendesk", the quoted original message and feedback buttons. Anyone copied on the ticket gets the reply too. Before Overdesk sends a reply on its own, it checks everyone copied against Excluded senders, your rules' customer lists and the people you erased, and a reply that would reach one of them waits for your team (see Sending replies).
Inboxes, views and escalation
- In Allowed inboxes, enter
allto draft every group; with a second help desk connected, writeZendesk:all. A group number, such asZendesk:82640, limits Overdesk's scheduled drafting runs to that group, but real-time updates from Zendesk carry no group number, so enterallif you want a new ticket drafted the moment it arrives. A group number also limits where@Overdeskanswers a note, and which tickets that answer can open. - To scope reports and analyses to one saved view, set Default view ID (Zendesk only) in Settings → General. The number is in the address bar when you open the view.
- Escalation rules can assign a ticket to an agent or to a group, picked from a list Overdesk reads from your Zendesk account. See Escalation.
- When you turn on closing stale conversations, Overdesk sets those tickets to Solved.
Real-time updates
Zendesk generates the webhook signing secret and shows it on the webhook's own page in Admin Center, behind "Reveal secret". The steps are in Real-time updates with webhooks.
If the connection is refused
The form shows the reason next to the fields. A message starting "credentials rejected by Zendesk" is followed by Zendesk's own words; check the token and that the email is the one it was created on. A subdomain can hold only letters, digits and hyphens. A message saying the Zendesk subscription on this account is inactive means Zendesk accepted the credentials but refuses every conversation read until the subscription is renewed, so renew it with Zendesk and then connect again. A message starting "Overdesk could not read conversations with this token" means the credentials opened the account but Zendesk then refused to list conversations; Zendesk's own words follow it, so check the credentials' permissions.
Disconnecting Zendesk deletes its credentials and everything it put into your knowledge base.