Skip to main content
These scenarios show Studio in real operating conditions. Each one starts where work actually starts — a ticket, an alarm, a customer call, a sales handoff — and walks the full path through diagnosis, action, vendor coordination, and customer communication until the loop is closed. Studio is not the only system in any of these flows. Tickets still live in Kayako, ConnectWise, or Freshservice. Alarms still come from Zabbix, PRTG, or LibreNMS. Hardware still talks IPMI, iDRAC, and iLO. The point is that Studio sits in the middle of the working day and stitches those systems together with the terminal, the diagram, the runbook, and the AI that has the context.

​
What these scenarios cover

MSP scenarios

Customer-facing helpdesk and field work — ticket triage, server hardware faults, security incidents, fleet upgrades, customer onboarding, executive reporting.

ISP and WISP

Subscriber networks at scale — upstream outages, DDoS, PON and fiber deployment, CGNAT, capacity planning, RADIUS disputes, CPE firmware.

VoIP and telco

Voice carriers and PBX operators — SIP and RTP issues, PSTN provisioning, E911 validation, STIR/SHAKEN, Teams Direct Routing, DR drills.

​
How each scenario is structured

Every scenario uses the same shape so you can scan and compare:
SectionWhat it covers
OpenerThe trigger and who’s running it.
Systems involvedEvery external platform, vendor system, or comms channel touched.
WalkthroughStep-by-step from trigger to closed loop.
Where Studio earns its keepThe handful of moments Studio collapses what would otherwise be five tabs and three apps.

​
How Studio shows up across these flows

The same Studio surfaces appear across most scenarios:
  • Hosts and protocols — SSH, Telnet, HTTPS, RDP, VNC, video stream, serial. One inventory, many ways in.
  • Copilot with connectors and MCP — pull a Kayako ticket, query Zabbix, post in Slack, draft a Gmail reply, file a vendor RMA, book a Google Calendar slot.
  • Procedures — promote a successful path into a parameterized runbook so the next person doesn’t have to rediscover it.
  • Memories — durable facts about a customer, site, or device so the next conversation starts informed.
  • Shared sessions and calls — bring a teammate, a vendor, or a field tech into the same terminal and escalate to voice or video without leaving Studio.
  • Diagrams — autogenerate site or topology diagrams from inventory and discovery so customer reports look professional with no extra effort.
  • Files and artifacts — drop the post-mortem, the report, the config diff, the recording, the customer email back into the workspace where the work happened.

​
A note on connectors

Most of the third-party systems referenced — Kayako, Zabbix, PRTG, LibreNMS, Freshservice, ConnectWise, ServiceNow, Slack, Microsoft Teams, Gmail, Outlook, Google Calendar, Twilio, Stripe, Splynx, Sonar, NetBox, FreePBX, 3CX, Bandwidth, Telnyx, iDRAC, iLO, Cloudflare, Datto, and so on — are reachable from Studio via connectors or MCP servers. You configure the integration once with your own credentials and Copilot calls it with approval. None of these are bundled vendor relationships; they are how Studio fits into the toolchain you already have.

​
Where to start

If you only read three, read these:
  1. Dell R720 disk failure — the canonical MSP loop: ticket → monitoring → iDRAC → vendor RMA → datacenter access → customer.
  2. Upstream provider outage — the canonical ISP loop: many alarms → looking glass → carrier ticket → bulk customer comms → status page.
  3. One-way audio complaint — the canonical VoIP loop: ticket → call recording → SIP trace → SBC → firewall → validation → customer reply.