Connect Ticket Tailor
A step-by-step guide with pictures, from the Speakvora agent's own Connect tab.
Short answer: This connects your own Ticket Tailor 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 Ticket Tailor. Only the status word and the order.
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 Ticket Tailor 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 Ticket Tailor. 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 Ticket Tailor 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 Ticket Tailor's public developer documentation (the addresses and sign-in style were read there) and has not been tried yet on a live Ticket Tailor 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: events ticketing cinema, library museum tourism. How Ticket Tailor gives access: You create the key yourself in your own account; no approval is needed. What it costs you: Ticket Tailor does not state a separate API fee in its developer docs; limit is 5000 requests per 30 minutes.
Part 1. Get your key from Ticket Tailor
Do this on your computer, in a new browser tab, signed in to Ticket Tailor.
- Sign in to Ticket Tailor as the box office owner or an admin.
- Open the box office you sell tickets from.
- Go to Box office settings and open the API section (app.tickettailor.com/box-office/api).
- Create a new API key and name it Speakvora.
- Copy the key and paste it into the API key box here.
- Use the Speakvora test button; it reads one recent order to confirm the key works.
- If you run several box offices, repeat with the key for each one.
WARNING: If Ticket Tailor asks which permissions to give, tick only the read-only ones: Read access to orders (the key can only see the box office that issued 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
- Open your agent's dashboard (the page you open from the Start Speakvora Agent file).
- 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.
- Under Your apps type Ticket Tailor in the box that says Find an app (1), or scroll down the list.
- Press Ticket Tailor. 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.)



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:
- Box office API key (secret: it stays on this computer and is never shown again, only the last few characters). Box office settings > API. The key belongs to one box office.

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
- Press the orange Save and test button.
- Ticket Tailor is asked for one harmless record, just to prove the key works. Nothing is changed in Ticket Tailor.

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 Ticket Tailor), or *I could not find that order. A team member will check and reply.*
- Each person can ask five times an hour. If Ticket Tailor is down, the conversation carries on and the problem is written to Activity.
- Mode: the agent asks Ticket Tailor when a customer asks.
If something is wrong
- It says the key was refused (401 or 403): copy the key again from Ticket Tailor. 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 Ticket Tailor, or Ticket Tailor 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.
- Ticket Tailor says you need a plan or approval: The official docs name GET /v1/orders/:order_id but do not show the order response fields, so the status field name is not confirmed. A real account test is needed.
- Still stuck? Press Connect, then Download report, and email it to support. It never contains keys or customer messages.
Ticket Tailor's own instructions: https://developers.tickettailor.com/docs/intro
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 Ticket Tailor. 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 Ticket Tailor, or Ticket Tailor 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: Ticket Tailor says you need a plan or approval?
The official docs name GET /v1/orders/:order_id but do not show the order response fields, so the status field name is not confirmed. A real account test is needed.
What if this happens: Still stuck??
Press Connect, then Download report, and email it to support. It never contains keys or customer messages.