Sapa
Join with a code Sign in Get Sapa

Sapa support

Answered within one business day

Your account is managed by your organisation

For recording retention, who can host, being removed from a meeting, or anything set by policy, your own IT can act and we cannot. Everything else is ours.

Ask your own IT or carry on below

Write to us

You do not need to be signed in. If signing in is the problem, this form is the way round it.

What went wrong

What you expected, and what happened instead

An example that saves a round trip

Tried to join the 09:00 standup with my company sign-in three times and was sent back to the sign-in page each time. Joined as a guest in the end, which worked, but the host had to admit me and I lost my name badge.

One reply by email, no ticket portal to log into.

Attach diagnostics from this device

It saves a round trip. Here is all of it.

An attachment you cannot enumerate is not consent, so it is itemised both ways.

What is sent

See all of it

  • Your device and browser, and their versions
  • The names of your camera, microphone and speaker
  • Connection quality, error codes and timestamps
  • Which meetings you joined in the last hour

Not included, and not askable

  • Anything your camera or microphone saw or heard
  • Chat, shared files or your screen
  • Recordings, transcripts or captions

Let us open one recording

Manage what Support can open

Turning this on lets us open the one recording you name, for seven days, and writes a line in your organisation’s audit log. It expires by itself and you can revoke it from the email we send. We do not read recordings otherwise — not to improve anything, and not to train anything.

Everything above is kept for 30 days with the request, then dropped. It is listed as a category in the Privacy notice.

Outage? Check status first — it is hosted apart from Sapa and will be up when we are not.

Follow it on the status page once a request is in — the status page carries the incident, and a reply carries yours.