Key takeaways
- One workspace covers users, roles, branding, and billing.
- Support sessions can be promoted to verified inspections.
- A single audit log spans both products.
- Roles keep separate departments cleanly scoped.
One account, both products
Users, roles, branding, retention policy, integrations, and billing are shared. There is no second tenant to administer and no duplicate user directory to keep in sync.
Sessions convert
A support call that turns out to matter — visible damage, a warranty dispute, a claim — can be promoted into a verified inspection so the frames already captured carry the full evidence chain.
The reverse also works: an inspector reviewing a self-serve submission can open a live session with the customer to fill a gap.
Permissions keep teams separate
Where inspections and support are run by different departments, role-based access keeps each team scoped to its own queues while leaving administrators a single view.
Keep reading
People also ask
- Do we pay twice if we use both?
- No. Volume-based pricing covers the workspace; see the pricing page for how tiers count sessions.
- Can we start with one and add the other later?
- Yes, enabling the second product is a workspace setting.
- Do integrations cover both?
- Yes — webhooks and the API expose inspections and support sessions alike.
Need a hand with something more specific?
help@virtualinspection.ai