Connect ServiceM8

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

Short answer: This connects your own ServiceM8 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 ServiceM8. 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 ServiceM8 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 ServiceM8. 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 ServiceM8 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 ServiceM8's public developer documentation (the addresses and sign-in style were read there) and has not been tried yet on a live ServiceM8 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: home services. How ServiceM8 gives access: You create the key yourself in your own account; no approval is needed. What it costs you: No developer account is needed for API keys; the vendor documents no plan requirement.

Part 1. Get your key from ServiceM8

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

  1. Sign in to ServiceM8 as the Business Owner (only the owner can create API keys).
  2. Open [[Settings > API Keys]].
  3. Create a new API key, name it Speakvora, and choose Read Only access if the option is shown.
  4. Copy the key right away; it may not be shown again.
  5. Paste it into the API key box in Speakvora and press Test.
  6. If the test is refused, contact ServiceM8 support and ask for a REST API key with read-only access to jobs.

WARNING: If ServiceM8 asks which permissions to give, tick only the read-only ones: Read Only API key (jobs). 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 ServiceM8 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 ServiceM8. 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. ServiceM8 API key (secret: it stays on this computer and is never shown again, only the last few characters). Settings > API Keys in ServiceM8, created by the Business Owner. Choose Read Only access if offered.
  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. ServiceM8 is asked for one harmless record, just to prove the key works. Nothing is changed in ServiceM8.
  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 ServiceM8), or *I could not find that order. A team member will check and reply.*
  • Each person can ask five times an hour. If ServiceM8 is down, the conversation carries on and the problem is written to Activity.
  • Mode: the agent asks ServiceM8 when a customer asks.

If something is wrong

  • It says the key was refused (401 or 403): copy the key again from ServiceM8. 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 ServiceM8, or ServiceM8 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.
  • ServiceM8 says you need a plan or approval: Some accounts only offer plugin keys (starting smk-) that may not work with the REST API; if the test fails, ask ServiceM8 support to enable a full API key. Job lookup uses the documented job list with a $filter on the job number (generated_job_id), which returns a list; the first match is used.
  • Still stuck? Press Connect, then Download report, and email it to support. It never contains keys or customer messages.

ServiceM8's own instructions: https://developer.servicem8.com/docs/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 ServiceM8. 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 ServiceM8, or ServiceM8 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: ServiceM8 says you need a plan or approval?

Some accounts only offer plugin keys (starting smk-) that may not work with the REST API; if the test fails, ask ServiceM8 support to enable a full API key. Job lookup uses the documented job list with a $filter on the job number (generated_job_id), which returns a list; the first match is used.

What if this happens: Still stuck??

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