Connect Collect! (Comtronic)

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

Short answer: This connects your own Comtronic Systems 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 Comtronic Systems. Only the status word and.

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 Comtronic Systems 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 Comtronic Systems. 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 Comtronic Systems 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 Comtronic Systems's public developer documentation (a few details could not be confirmed) and has not been tried yet on a live Comtronic Systems 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: lending collections. How Comtronic Systems gives access: The vendor charges extra for API access or a higher plan. Check your plan before you start. What it costs you: The REST API is a separate install on your own Collect! server. Licensing cost for it is not stated in the public help; ask Comtronic.

Part 1. Get your key from Comtronic Systems

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

  1. Confirm with your Collect! administrator that the Collect! REST API is installed (the Help topic is API Installation - How To).
  2. Ask them to confirm the API is reachable over HTTPS at an address such as api.your-agency.example (set up with Apache).
  3. In Collect!, create a dedicated operator for Speakvora with the lowest user level the Authorization Server accepts and read-only rights to account records.
  4. Contact Comtronic support or your Collect! reseller and ask for read-only API access to debtor account status, and whether a long-lived access token can be issued.
  5. Paste the API address and the access token they give you into the two fields here.
  6. Tell us the Collect! version so we can confirm the account lookup call.

WARNING: If Comtronic Systems asks which permissions to give, tick only the read-only ones: Read access to debtor/account records only. 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 Comtronic Systems 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 Collect! (Comtronic). 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

2 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 Collect! API address. The domain your IT person set up for the Collect! REST API (the address in front of /api/v1).
  2. API access token (secret: it stays on this computer and is never shown again, only the last few characters). A token issued by your Collect! Authorization Server for a dedicated read-only operator. Ask your Collect! administrator.
  3. 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. Comtronic Systems 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 Comtronic Systems), or *I could not find that order. A team member will check and reply.*
  • Each person can ask five times an hour. If Comtronic Systems is down, the conversation carries on and the problem is written to Activity.
  • Mode: the agent asks Comtronic Systems when a customer asks.

If something is wrong

  • It says the key was refused (401 or 403): copy the key again from Comtronic Systems. 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 Comtronic Systems, or Comtronic Systems 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.
  • Comtronic Systems says you need a plan or approval: Collect! is installed on the customer's own server. Its REST API signs in with an operator ID and password (POST /api/v1/auth/login) and returns a Bearer token that expires after about 1 hour by default, so a long-lived key is not available from public docs. The debtor read path exists (GET /api/v1/collect/data/debtor with a filter) but a lookup by account number and the status field name were not documented, so no test or order call is configured.
  • Still stuck? Press Connect, then Download report, and email it to support. It never contains keys or customer messages.

If your plan has no API

  • Ask Comtronic whether a long-lived token or integration key can be issued for a read-only operator.
  • Use the Collect! portal or reports export until the API is confirmed.

Comtronic Systems's own instructions: https://www.collect.org/cv13/Help/howtousetherestapi.html

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

Collect! is installed on the customer's own server. Its REST API signs in with an operator ID and password (POST /api/v1/auth/login) and returns a Bearer token that expires after about 1 hour by default, so a long-lived key is not available from public docs. The debtor read path exists (GET /api/v1/collect/data/debtor with a filter) but a lookup by account number and the status field name were not documented, so no test or order call is configured.

What if this happens: Still stuck??

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