Connect Zendesk Support

A step-by-step guide with pictures, from the Speakvora agent's own Connect tab.

Short answer: This connects your own Zendesk account to your Speakvora agent. Then a customer can text where is order 1234 and get the answer in seconds, and the agent can send status and tracking texts. The agent only reads. It can never create, change or delete anything in Zendesk. Only the status word and the order number are.

Every key, number and name in the pictures is a made-up example. Nothing here asks you to share a real key with anyone but the app on your own computer.

This connects your own Zendesk account to your Speakvora agent. Then a customer can text *where is order 1234* and get the answer in seconds, and the agent can send status and tracking texts. The agent only reads. It can never create, change or delete anything in Zendesk. Only the status word and the order number are ever texted back, never names, prices, items or addresses.

TIP: You need about 15 minutes, a computer, and the sign-in for your Zendesk account (the owner or a manager). You can't break anything: if a step does not work, nothing has changed and you can just try again. The keys and screens below are made-up examples.

NOTE: This guide was written from Zendesk's public developer documentation (the addresses and sign-in style were read there) and has not been tried yet on a live Zendesk account. If a screen looks different from what is described, press Connect, then Download report, and send it to support. We fix it for everyone.

Who this is for: customer service. How Zendesk gives access: The vendor connects through an authorised app. Follow the steps below to create or authorise it in your own account. What it costs you: Zendesk's authentication page states no plan restriction for API access; rate limits per minute are 200 on Team, 400 on Professional and 700 on Enterprise.

Part 1. Get your key from Zendesk

Do this on your computer, in a new browser tab, signed in to Zendesk.

  1. Sign in to Zendesk as an administrator.
  2. Create or pick an agent just for Speakvora with read access to tickets, and note its email address.
  3. Open [[Admin Center > Apps and integrations > APIs > Zendesk API]].
  4. On the Settings tab make sure Token access is enabled.
  5. Press Add API token, name it Speakvora, then press Save and copy the token straight away because it is shown only once.
  6. In Speakvora enter your Zendesk address, the agent email followed by /token, and the token.
  7. Press Test to confirm the connection.

WARNING: If Zendesk asks which permissions to give, tick only the read-only ones: Use a dedicated agent with read access to tickets; the token acts as that agent. Never give write or admin access.

TIP: To copy the key, click inside the box that shows it, press Command + C on a Mac or Ctrl + C on Windows (or right-click and choose Copy). Nothing will look different. It is now in your clipboard, ready to paste. Keep it private: anyone who has it can read your orders.

Part 2. Open the Connect tab in your agent

  1. Open your agent's dashboard (the page you open from the Start Speakvora Agent file).
  2. Press Connect in the menu. On a phone the menu is the bar along the top; slide it sideways if you do not see Connect.
  3. Step 1: press Connect (1)

  4. Under Your apps type Zendesk in the box that says Find an app (1), or scroll down the list.
  5. Step 2: the Find an app box (1)

  6. Press Zendesk Support. A card slides up. (If you only see apps for your own kind of business, that is on purpose: your agent only shows the systems that make sense for it.)
  7. Step 3: an app's card. The Full Guide button (1) opens this page.

Part 3. Paste it in

3 boxes to fill in. Click inside a box, press Command + V on a Mac or Ctrl + V on Windows, then move to the next:

  1. Your Zendesk address. The first part of the web address you sign in to, for example your-company in your-company.zendesk.com.
  2. Agent email followed by /token. Type the email of the agent who owns the token, then /token with no spaces, for example agent@example.com/token.
  3. Zendesk API token (secret: it stays on this computer and is never shown again, only the last few characters). Admin Center > Apps and integrations > APIs > Zendesk API > Add API token. Zendesk shows it only once.
  4. Part 3: each numbered box is one thing to paste. These are made-up examples.

TIP: Pasted by mistake into the wrong box? Click the box, press Command + A (Ctrl + A on Windows) to select all, then paste again.

Part 4. Test it

  1. Press the orange Save and test button.
  2. Zendesk is asked for one harmless record, just to prove the key works. Nothing is changed in Zendesk.
  3. Part 4: the green message under the buttons means it worked (1)

YOU SHOULD SEE: green words starting with Connected.

WARNING: Red words mean it did not work yet. Read them, then see If something is wrong below. Nothing bad happened.

What happens next

  • A customer texts something like where is order 1234. The agent answers *Your order 1234 is preparing.* (the status word from Zendesk), or *I could not find that order. A team member will check and reply.*
  • Each person can ask five times an hour. If Zendesk is down, the conversation carries on and the problem is written to Activity.
  • Mode: the agent asks Zendesk when a customer asks.

If something is wrong

  • It says the key was refused (401 or 403): copy the key again from Zendesk. Make sure there is no space before or after it, and that it is a live key for the right shop or location.
  • It cannot find an order (404): the number is not in Zendesk, or Zendesk uses a longer number than the one on the receipt.
  • It says too many requests (429): wait a minute and press Save and test again.
  • Zendesk says you need a plan or approval: Zendesk labels the API token method deprecated and recommends OAuth access tokens, which need an OAuth client created by an admin. Tokens act as the agent who created them, so use a dedicated agent with limited access. The lookup reads one ticket by its numeric ticket number.
  • Still stuck? Press Connect, then Download report, and email it to support. It never contains keys or customer messages.

Zendesk's own instructions: https://developer.zendesk.com/api-reference/introduction/security-and-auth/

All help guides · Every agent feature · AI receptionist by industry

Questions

What if this happens: It says the key was refused (401 or 403)?

copy the key again from Zendesk. Make sure there is no space before or after it, and that it is a live key for the right shop or location.

What if this happens: It cannot find an order (404)?

the number is not in Zendesk, or Zendesk uses a longer number than the one on the receipt.

What if this happens: It says too many requests (429)?

wait a minute and press Save and test again.

What if this happens: Zendesk says you need a plan or approval?

Zendesk labels the API token method deprecated and recommends OAuth access tokens, which need an OAuth client created by an admin. Tokens act as the agent who created them, so use a dedicated agent with limited access. The lookup reads one ticket by its numeric ticket number.

What if this happens: Still stuck??

Press Connect, then Download report, and email it to support. It never contains keys or customer messages.