Skip to content
OffsightAI
Sign In

Support

Something not right?
Tell us what happened.

A line stops for a lot of reasons, and software should never be one of them.

  • Emailed to support@offsight.com
  • Ticket numbers and threaded history in-product
  • Console, iOS and Android
Drywall tables running on a prefabrication floor

Send a message

Write to support.

Give us the plant, the screen and roughly when it happened, and the first reply can be a useful one instead of a request for more information.

Emailed to support@offsight.comWe will not add you to a drip campaign.

Your message is emailed to support@offsight.comPlease don’t include passwords, API keys or any other credential in it.

Already have a tenant?

The Support dashboard in the console is faster.

For anything account-specific, a product that will not close out, a checklist behaving oddly in one zone, a purchase order that did not sync, a user who cannot see a module.

Use this page instead when you cannot get into the console at all, when you do not have an account yet, or when you are reviewing Offsight on someone else’s behalf.

  • Every Offsight tenant has a Support mailbox It is not a separate portal with its own password.
  • Every request gets a ticket number, so nothing turns into “that email from Tuesday” halfway through a build week.
  • The history stays threaded to the ticket, which means whoever picks it up next.
  • You are already signed in, so the ticket arrives attached to your account and your user instead of opening with three questions about who you are.
An operator working through a checklist on a shop-floor tablet

Help us move fast

Make the first reply the useful one.

It is simply what turns a two-day thread into a same-thread answer.

  • Where it happened. The plant or account, the dashboard you were on, and the product, work order or paperwork packet in front of you.
  • When it happened. A date and a rough time with your time zone, so we can line the report up against the record.
  • Who hit it. The user or the user group.
  • Which surface. The console, the iPhone app or the Android app, and the app version if you can see it.
  • What you expected instead. The gap between what the screen did and what the floor needed it to do is often the whole ticket.
  • A screenshot. One picture of the actual screen beats a paragraph describing it, every time.

Evaluating Offsight rather than running it?

If you are here because you are still deciding, a demo answers more in half an hour than a support thread will.