A technical support case at Varjo rarely looks like a consumer one. The headset in question is usually installed in a certified simulator, on an air base or at a training center, with a syllabus running around it. There may be three organizations involved before you even reach us: a prime contractor, a system integrator, and the unit that actually trains on the thing. The device may not be allowed to leave the building it is in. The deadline is often a course starting on Monday.
My job is to make sure that complexity lands on us instead of on you. This post covers the part of that you can use: which team to contact for what, and what makes an urgent case move fast.
Customers often assume Varjo has one technical group. There are two, and knowing which one you need can save a lot of time.
Tech Support is the team I work on. It comes with every purchase, and it handles cases: something is behaving unexpectedly, a license needs sorting out, a new workstation is not cooperating, a question came up that nobody on your side can answer. We work by case and by device, which is why serial numbers matter so much to us. There is no such thing as a question too small to send us. If you bought through a reseller or integrator, your case may route through them, and that is normal rather than a delay.
Varjo Alpha is our professional services team of solutions engineers. They are not a help desk. They come in on a scope, work on your system, and often work on site. There are three levels of engagement:
The rule of thumb: if your question is about the system you already have, send it to tech support. If the work is about designing, integrating, or scaling a system, ask your Varjo contact about the Varjo Alpha team. Simulator manufacturer Entrol did the latter, and the case study from their Madrid workshop is a fair picture of what that engagement looks like.
Some of this is obvious once you see it written down, and almost nobody does all of it.
Two bookmarks also save everyone time: the Help Center Downloads section, which holds user guides, compliance documents, and calibration sheets that procurement and accreditation teams ask for, and the Security FAQ, which is the page to forward to your own IT and security people.
The reason support can absorb a case with three organizations and a Monday deadline is structural, and it is the part I spent much of this year rebuilding.
When I mapped how cases moved through Varjo, I did not find chaos. I found three teams, each doing their work well without a shared view of the others. Context was being reassembled at every handoff. So we rebuilt the flow in Jira around how those teams actually work, rather than around an ideal version of it, and we kept five distinct case scenarios separate instead of flattening them into one queue that would have been easier to explain and much harder to work in.
A case now has one record, one named owner at every stage, and visibility for every team that touches it. One colleague told me her team was finally in the loop and could comment on cases directly, which was the feedback I valued most.
None of that is visible from the outside. What it produces is: your case does not restart when it crosses a team boundary, and you get told where things stand instead of an estimate. That is what makes enterprise support workable at the scale and urgency our government and commercial customers operate at, and it is the kind of groundwork we will keep doing as the customer base grows.
If you have a question, the Help Center is the fastest way to reach my team. If you are planning a deployment, talk to your Varjo contact about Varjo Alpha before the room is built rather than after.
-Gabriela
Helpful links: