Connect Square Appointments
A step-by-step guide with pictures, from the Speakvora agent's own Connect tab.
Short answer: This connects your own Square 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 Square. 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 Square 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 Square. 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 Square 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 Square's public developer documentation (the addresses and sign-in style were read there) and has not been tried yet on a live Square 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: appointments scheduling. How Square gives access: You create the key yourself in your own account; no approval is needed. What it costs you: Creating a Square developer application and a personal access token is not stated to carry a charge in Square's docs. A Square Appointments plan is needed for bookings to exist.
Part 1. Get your key from Square
Do this on your computer, in a new browser tab, signed in to Square.
- Sign in to the Square Developer Console at developer.squareup.com/apps with the owner account.
- Open your application, or press the plus button to create one named Speakvora.
- In the left pane choose Credentials.
- At the top of the page switch from Sandbox to Production.
- In the Production Access token box press Show and copy the token.
- Paste the token into the Square production access token box in Speakvora.
- Use the booking ID from the Square booking as the reference number when testing a lookup.
WARNING: If Square asks which permissions to give, tick only the read-only ones: MERCHANT_PROFILE_READ (locations test call), APPOINTMENTS_READ and APPOINTMENTS_ALL_READ (read bookings). 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 Square in the box that says Find an app (1), or scroll down the list.
- Press Square Appointments. 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:
- Square production access token (secret: it stays on this computer and is never shown again, only the last few characters). Square Developer Console > your application > Credentials > Production > Production Access token > Show.

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.
- Square is asked for one harmless record, just to prove the key works. Nothing is changed in Square.

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 Square), or *I could not find that order. A team member will check and reply.*
- Each person can ask five times an hour. If Square is down, the conversation carries on and the problem is written to Activity.
- Mode: the agent asks Square when a customer asks.
If something is wrong
- It says the key was refused (401 or 403): copy the key again from Square. 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 Square, or Square 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.
- Square says you need a plan or approval: A personal access token is suitable for production only for your own Square account; Square's docs say this suits integrations that touch only your own account. The token grants full account access, so keep it private. Square's docs say seller-level booking access needs the APPOINTMENTS_ALL_READ and APPOINTMENTS_READ permissions.
- Still stuck? Press Connect, then Download report, and email it to support. It never contains keys or customer messages.
Square's own instructions: https://developer.squareup.com/docs/bookings-api/what-it-is
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 Square. 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 Square, or Square 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: Square says you need a plan or approval?
A personal access token is suitable for production only for your own Square account; Square's docs say this suits integrations that touch only your own account. The token grants full account access, so keep it private. Square's docs say seller-level booking access needs the APPOINTMENTS_ALL_READ and APPOINTMENTS_READ permissions.
What if this happens: Still stuck??
Press Connect, then Download report, and email it to support. It never contains keys or customer messages.