Support routing

Support for the moments operators cannot leave unresolved.

Alerts, Square permissions, voice calls, billing, location routing — whatever's stuck, start here. 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.

Pick the lane that matches your issue. The right context up front means a faster, sharper reply.

iOS app

Alerts, dashboard, customers, and transactions

Push alerts, top customers, transaction detail, dashboard metrics, low-stock views, manager PIN, or anything else inside the app.

ios.support

Square link

OAuth, scopes, and location routing

Square login, permission refreshes, 403s, selected locations, or webhook routing — anything where Sidekick and Square aren't talking.

square.scope

Voice AI

Agent calls, menu sync, and payment handoff

Voice ordering, transcripts, menu behavior, payment links, escalation paths, and anything else in the phone workflow.

voice.agent

Billing

Subscription, access, and account status

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

billing.route

Reliability

Sync health, API behavior, and incidents

Background sync, Square API behavior, webhooks, or report freshness drifting from 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.

Tell us which lane is affected and what you were doing when it broke. We respond in business hours, usually within a day.

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