Connect Help Scout

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

Short answer: This connects your own Help Scout 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 Help Scout. Only the status word and the order number.

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 Help Scout 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 Help Scout. 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 Help Scout 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 Help Scout's public developer documentation (a few details could not be confirmed) and has not been tried yet on a live Help Scout 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 Help Scout 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: Plan requirements for API access are not stated in the public docs.

Part 1. Get your key from Help Scout

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

  1. Sign in to Help Scout as the account owner or an invited user with access to the mailbox.
  2. Click [[your profile picture > Your Profile]].
  3. Open My apps and click Create My App.
  4. Name it Speakvora and enter a placeholder redirect URL such as https://www.google.com (only needed to save the app).
  5. Copy the App ID and App Secret shown for the app.
  6. Request a token with the client credentials flow at https://api.helpscout.net/v2/oauth2/token and paste the access token here; it expires after 2 days.

WARNING: If Help Scout asks which permissions to give, tick only the read-only ones: conversations: read (the app acts as the invited user who owns it). 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 Help Scout 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 Help Scout. 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

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

  1. Access token (secret: it stays on this computer and is never shown again, only the last few characters). A bearer token minted from your own Help Scout app (client credentials). It is valid for 2 days only.
  2. 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. Help Scout has no safe read-only check we can run, so nothing is called. The connection is used for real the first time a customer asks about an order, and any problem shows in Activity.
  3. Part 4: the green message under the buttons means it worked (1)

YOU SHOULD SEE: green words starting with Connected. (here: *Saved* and the sentence about the first customer)

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 Help Scout), or *I could not find that order. A team member will check and reply.*
  • Each person can ask five times an hour. If Help Scout is down, the conversation carries on and the problem is written to Activity.
  • Mode: the agent asks Help Scout when a customer asks.

If something is wrong

  • It says the key was refused (401 or 403): copy the key again from Help Scout. 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 Help Scout, or Help Scout 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.
  • Help Scout says you need a plan or approval: Help Scout documents only OAuth2 tokens that expire after 2 days (client credentials flow, token endpoint https://api.helpscout.net/v2/oauth2/token); no long-lived personal token is documented. A connector that stores a fixed token will stop working after 2 days unless it re-mints from the app id and secret. No cheapest key-check call was confirmed in the docs, so test is omitted. The conversation path uses the internal id; the customer-facing number may need a search by number.
  • Still stuck? Press Connect, then Download report, and email it to support. It never contains keys or customer messages.

Help Scout's own instructions: https://developer.helpscout.com/mailbox-api/overview/authentication/

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 Help Scout. 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 Help Scout, or Help Scout 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: Help Scout says you need a plan or approval?

Help Scout documents only OAuth2 tokens that expire after 2 days (client credentials flow, token endpoint https://api.helpscout.net/v2/oauth2/token); no long-lived personal token is documented. A connector that stores a fixed token will stop working after 2 days unless it re-mints from the app id and secret. No cheapest key-check call was confirmed in the docs, so test is omitted. The conversation path uses the internal id; the customer-facing number may need a search by number.

What if this happens: Still stuck??

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