OPERATIONSPRO
Accountability. Clarity. Results.
Early access You were invited. Thank you.
You are testing something unfinished.
That is the point. The app working is not news; the app annoying you is. Everything on this page exists to get you in with as little frustration as possible, so that the frustration you do hit is the app's fault and worth telling us about.
Getting onto an iPhone app that is not in the App Store yet takes a few steps, and Apple owns most of them. Start below.
Step one
Which setup guide do you need?
There are two, and the answer depends on how Apple invited you. If you are not sure, look at the first email you got from Apple — it decides.
If Apple's email said
“Join our developer account”
You are on the internal test team. Before the app can reach your phone you have to accept an Apple invitation, sign in with the right Apple Account, and have two-factor turned on. That is what this guide walks through.
Then read Start here below.
If Apple's email said
“You're invited to test Vector Operations Pro”
You are an external tester, and you have the easier path. No developer account, no Apple team to join — just TestFlight and the app. This is also the guide everyone reads eventually.
This is the only one you need.
The one thing that catches nearly everybody: two invitations arrive, from two different senders, usually days apart — one from Apple, which puts the app on your phone, and one from Vector, which lets you sign into it. Installing the app does not sign you in. On a modern iPhone neither email lands in your inbox; they get filed under Transactions, Updates or Promotions. The guides tell you exactly where to look.
Documents
Everything we have written down
All of them are short, and none of them assume you have seen Vector before.
Joining the test team
Getting through Apple's side of it: which of your Apple Accounts we actually need, turning on two-factor, accepting the invitation without it looping, and why TestFlight says “no builds available” when everything looks right.
9 pages · PDF
Start here
Installing TestFlight, finding Apple's email in whichever category it was filed under, accepting the build, then the second invitation from us and the six-digit code that gets you into the app. Ends with a tour of the five tabs.
9 pages · PDF
The floor card
A folded card for your pocket. One side is raising something you have found, the other is getting it closed. Print it double-sided and fold it — it is the fastest answer to “what do I tap now” when you are standing in front of a problem.
4 pages, folded · PDF · ready-to-print version, 2 per sheet
The Operator's Manual
How you would actually run a site on Vector: setting up areas and maps, writing programs, inviting people and what each role may do, walking the floor, and producing the evidence pack at the end. Written from an administrator's point of view.
30 pages · PDF · you do not need this to start
While you are using it
The help is inside the app, and it is searchable
You should not have to come back to a PDF to find out what a button does.
Settings → Help Center
Every screen in Vector is explained there, in the app, with a search box. It is the fastest answer to “what does this do” and it works with no signal.
The same articles, on the web
Identical content, easier to read on a big screen, and you can send someone a link to a single article. Good for reading ahead before you start.
If the Help Center and the app ever disagree with each other, the app is right and the article is wrong — tell us, because that is a real bug and an easy one to fix.
There is a website too
You do not have to do everything on a phone
The same sign-in works at vectorxpro.com/team. Reading through what has been recorded, and inviting people if that turns out to be your job, are simply easier on a laptop. Walking the floor is not — that is what the phone is for.
Open the web appWhat we need from you
Telling us what is wrong
In rough order of how useful it is to us:
- Anything you could not work out. If you stared at a screen and did not know what to do next, that is the single most valuable thing you can report. It is not you being slow; it is us being unclear.
- Anything that took more taps than it should have.
- Wording that does not match how you actually talk on the floor.
- Anything that broke — obviously. What you tapped, and what happened.
- Anything missing that you would need before you would use this for real.
Screenshot, then Send Beta Feedback
Take a screenshot, then in TestFlight tap Send Beta Feedback — or just share the screenshot to TestFlight. It attaches what the app was doing at the time, which saves us guessing. Best when something looks wrong on screen.
support@vectorxpro.com
Plain words are fine. If it is about one item or one walk, quote its number — something like VX-0012 or AU-0008 — and we can find exactly what you saw.
Please do not put real, sensitive information in it yet. This is a test build. Use real-looking work if you like — that is the most useful kind of feedback — but nothing confidential, and no photographs of people who have not agreed to be in them.
Stuck for more than five minutes?
Stop and email us. There is no such thing as a question too small here — if you had to ask it, the next person would have too, and we would rather fix that than have you work around it politely.
Email supportTell us which email address you were invited at — nine times out of ten that is the answer.