Help centre / Guide 07

Recover the flow without creating a second problem.

Most blocks come from account access, venue selection, an interrupted first-run step, plan access, or the shared balance. Start with what the screen shows, retry once, and preserve the work SANDR already confirmed.

6 minute guideAccounts · onboarding · AI · voice · filesUpdated 19 August 2026

01 / Guide 07

Check what the screen shows first.

Confirm you are signed into the intended account and workspace, then check the active venue and your connection. If you belong to more than one workspace, switch to the one that owns the venue, report, or invitation you need.

Retry the specific action once. If the screen looks stale, refresh it once and let SANDR reload the last confirmed information. Avoid creating replacement workspaces, venues, purchases, or submissions while an earlier request may still be resolving.

Capture before you retry

Note the date, workspace, venue, screen, action, and the exact message shown. A screenshot helps when it does not expose private information.

02 / Guide 07

Sign-in, code, and invitation problems.

Verification and password recovery use a six-digit code. Check the address you entered and the spam folder. If SANDR says the code is invalid or expired, request a fresh one and use the newest code.

  • Use Forgot password to request recovery and set a new password.
  • Never share a password or verification code with support.
  • If an invitation expired or was already used, ask the workspace owner for a fresh one.
  • If your account is inactive or a venue is missing from your access, the owner must restore or correct it.

03 / Guide 07

Onboarding stopped after the venue was created.

Return with the same email and select the same workspace. When the first-venue screen lists the venue you already started, choose Continue with [venue name]. That reconnects the flow without consuming another venue slot.

If setup was interrupted while SANDR was reading the first observation, the page returns to the check-in step rather than leaving an endless loading screen. Submit the observation again. If the first check-in already completed, SANDR reloads the saved result.

Do not create a duplicate venue to work around the block. If the existing venue is not offered, send feedback with the workspace and venue name.

04 / Guide 07

A check-in will not complete.

Confirm an active venue is selected, the observation contains real text, and the proposed patterns and venue have been reviewed. Remove anything that does not belong to the incident before saving, check the connection, and retry once.

Wrong venue

If a note about North Café opens under South Café, stop before committing and select the correct place. If SANDR keeps showing material from the wrong venue, treat it as a privacy issue and report it immediately.

If a request may have completed despite a lost response, refresh before submitting it again. SANDR’s confirmation and receipt are the reliable record.

05 / Guide 07

AI, plan, credit, and payment blocks.

If AI work is paused, the workspace may have no available credits. Existing reports, tasks, proof, and history stay accessible. An owner can review Settings → Plan & usage, buy a pack, change plan, or configure capped auto-reload where available.

  • If an action opens Plan & usage, the capability may not be included or a venue or member limit may have been reached.
  • Extra credits do not unlock features from a higher plan.
  • Self-serve usage does not create an automatic excess bill.
  • Credits are added after payment confirmation; keep the purchase reference if a paid pack is missing.
  • A failed auto-reload adds no credits and needs deliberate owner review.

Never send full card details. Use the secure billing portal for payment-method changes.

06 / Guide 07

Voice, files, privacy, and support.

If voice is included but will not start, allow microphone access, end another call or recording using the microphone, check the audio output, and reconnect once. Typed chat stays available. Realtime voice is metered by time, so end a session that is no longer active.

A successfully uploaded file remains available even when optional AI processing is waiting on credits. Do not upload passwords, card details, private keys, medical information, or unnecessary personal details.

For a persistent issue use Settings → Help → Send feedback and choose the closest category: problem, billing, privacy, or safety. Include the safe reproduction details.

Urgent access or security issue

Stop the affected work and email gm@sandr-ai.com. Describe what appeared, where, and when, with the minimum sensitive detail needed. For a suspected compromise, change the password and do not continue using the exposed session.

Keep going

Follow the next thread.

Each guide starts from a real part of the work and keeps the next move clear.