Sales & service toolkit

Everything you need for the next conversation

Talk tracks for demos, a one-page cheat sheet, who uses what, the questions you'll get, and the jargon decoded.

Demo scripts

Talk tracks

Run these against the live portal or the demo on the For clients page.

5 minFirst meeting · any stakeholder

The 5-minute demo

Hotlist (1 min). “Here’s every room across the estate. These three need attention right now, and we knew before anyone called.”
One device (1 min). Open an offline room and show the connected equipment, the system monitor chart and recent logs. “The display dropped off the network at 07:42.”
Fix it (1 min). Show remote actions: schedule a reboot for tonight. “No site visit.”
Insights (1 min). Room usage and ratings. “This room is booked 30 hours a week, but it’s empty for 12 of them.”
Ask the assistant (1 min). Press ⌘K and type /offline. “Anyone on your team can ask questions like this.”

Close: “Every room we build runs on this, and it gets better every month.”

15 minIT / facilities / technical buyer

The 15-minute deep dive

Architecture (2 min). Use the Platform page diagram: processor → cloud → portal / panels / AI. Stress outbound-only connections and tenant isolation.
Monitoring (3 min). Hotlist, a device overview, the system monitor trend, logs, and network tools run from the room.
Management (3 min). Config history and diffs, property-list backup, a package deploy with its compatibility check, and a scheduled action.
Insight (2 min). Room usage, ghost bookings, energy, ratings, all per location.
Security (2 min). SSO by domain, custom roles, scoped API keys, API-only data access.
AI (2 min). The assistant pulse, then a triage question. Show a proposed action waiting for confirmation, and mention MCP for their own AI tools.
How we build (1 min). Shared framework, AI-first engineering, the tested pipeline and the approval gate.

Close: the roadmap. Be clear about what’s live today and what’s vision.

Who uses what

Know your audience

● main user · ○ uses it sometimes

Capability	Sales	Service desk	Engineers	Client facilities	Client IT
Hotlist & live status	○	●	●	○	●
Logs, console & network tools	not used	●	●	not used	○
Remote & scheduled actions	not used	●	●	not used	○
Room usage, energy & ratings	●	○	not used	●	○
Packages & firmware	not used	○	●	not used	○
Config history & backups	not used	●	●	not used	not used
SSO, roles & API keys	○	not used	○	not used	●
Assistant & MCP	●	●	●	○	○
This showcase site	●	●	○	not used	not used

FAQ

Questions you'll be asked

Who pays for the AI assistant?

The assistant is switched on per tenant using that tenant's own Anthropic API key, and the portal shows 30 days of usage. It's off until a tenant admin enables it.

Can the AI break something?

No action happens without a person confirming it, and that person's permissions are re-checked at the moment they confirm. The MCP interface for external AI tools is read-only and fully audited.

Does it send email or Teams alerts?

Not yet. Today alerts appear in the portal's hotlist and live notifications, and the assistant's pulse highlights what needs attention. Proactive channels (Teams, email, webhooks) are on the roadmap — please don't promise them as available.

Does the client get access to the dashboard?

Yes. Each client is its own tenant, signs in with their own identity provider if they want, and sees only their estate. Roles decide who can only view and who can act.

Where is the data held?

In Google Cloud (Firebase / Firestore, Cloud Run, Cloud Storage). The portal and panels never read the database directly; client data goes through permission-checked APIs. Refer detailed InfoSec questionnaires to engineering.

Can we add it to a client's existing rooms?

Rooms built on proAV.Net get everything. For older programs, talk to engineering — the framework is designed to be adopted, but the effort depends on the existing code.

What happens if the internet drops?

The room keeps working — control runs locally on the processor, which also hosts its own on-device dashboard. Cloud monitoring catches up when the connection returns, and offline detection flags it after five minutes.

How do I know what a room is running?

The device page shows the program package version (dated, with git commit and branch) and firmware against the newest in the library. The package library shows where each version is deployed.

What hardware does it run on?

Crestron 4-series control processors and Crestron Virtual Control (VC-4). Touch panels can be Crestron CH5 panels or iPads using our panel app. The processor talks to the room's other equipment — displays, codecs, DSPs, cameras, PDUs, sensors.

In one sentence, what is proAV.Net?

Our platform for building, monitoring and supporting AV systems. Software on every control processor connects each room to a secure cloud portal where we — and the client — can see, manage and improve the estate.

Glossary

Jargon, decoded

Assistant: The AI chat built into the portal. Answers from live data; proposes actions that a person confirms.
Beta / test environment: test.proav.cloud — where new features land first from the develop branch.
CH5: Crestron's HTML5 touch-panel technology. Our UI library builds modern CH5 panel interfaces.
Check-in: The regular heartbeat each processor sends to the cloud with its status. Miss them for 5 minutes and it shows as offline.
Config drift: When one room's configuration quietly differs from its siblings. The platform can detect it.
CPZ / program package: A compiled Crestron program. Stored in the package library with release notes and version history.
Hotlist: The ranked list of current issues across a tenant's estate.
Linked / connected device: Equipment the processor controls — displays, codecs, DSPs, cameras, PDUs, sensors.
MCP: Model Context Protocol — an open standard that lets AI tools (Claude and others) safely query a system. Our cloud is an MCP server.
PDU: Power distribution unit — switched / metered power strip. Lets us power-cycle equipment and measure energy.
proAV.Net.Core: Our framework that runs on every processor. Provides the web server, cloud connection, monitoring, config and touch-panel plumbing.
Processor: The Crestron control system in a room or rack (4-series hardware or VC-4 virtual). Runs the room and proAV.Net.Core.
Release approval: The human sign-off required before anything ships to production.
Tenant (namespace): One client's isolated area of the portal — their devices, locations, users and settings. Engineers call it a "namespace".
VC-4: Crestron Virtual Control — control-system programs running on a server instead of dedicated hardware.