Support routing

Support for the moments operators cannot leave unresolved.

Use this page when alerts, Square permissions, voice calls, billing, or location routing need attention. The goal is to move from issue to next step quickly, with the right context attached.

support console

from operator issue to clear next step

routed
issue.reportedoauth scope / alert / voice
route.ownersupport lane selected
context.checklocation + screenshot
response.statequeued for reply

target

one business day

privacy

no passwords

We do not need your Square password, and you should not send API tokens. Square authorization remains on Square hosted screens.

support lanes

Start with the workflow that is blocked.

Square Sidekick support is easier when the request starts with the affected operating lane instead of a generic message.

iOS app

Alerts, dashboard, customers, and transactions

Use this lane for push alerts, top customers, transaction detail, dashboard metrics, low-stock views, manager PIN, or navigation issues.

ios.support

Square link

OAuth, scopes, and location routing

Use this when Square login, permission refresh, 403 responses, selected locations, or webhook routing need attention.

square.scope

Voice AI

Agent calls, menu sync, and payment handoff

Use this for voice ordering, transcripts, menu behavior, payment links, escalation paths, and phone workflow questions.

voice.agent

Billing

Subscription, access, and account status

Use this for App Store subscriptions, plan access, TestFlight questions, account state, or owner access changes.

billing.route

Reliability

Sync health, API behavior, and incidents

Use this when background sync, Square API behavior, webhooks, or report freshness do not match what you expect.

system.trace

before you write

Send the details that let support act quickly.

The most useful support note tells us what screen or workflow failed, which Square location was involved, and whether the issue is stopping live operations.

Square location or locations affected
Screenshot or exact screen name
What you expected to happen
Approximate time the issue happened
Whether this blocks business operations

Intake

Your message gets routed by product area so alerts, Square access, voice, billing, and reporting do not land in the same generic bucket.

Context check

We look for the account, location scope, recent app state, and affected workflow before asking for anything sensitive.

Operator action

The response should tell you what to do next: relink Square, refresh locations, verify a threshold, or wait on a fix.

contact

Send the case to the Sidekick team.

The same contact flow stays in place. The redesign adds better context around what to send and which operating lane is affected.

We typically reply within one business day. Feel free to email alerts@squaresidekick.com as well.