Issues and workload
Issue trends, cases open too long, open workload, resolution stats, repeat issues, per-location rankings and inspection status.
AI assistant integration
CineScope exposes a Model Context Protocol (MCP) server. A circuit connects it once via OAuth and can then ask questions of its own operational data in natural language from an AI assistant such as Claude — no exports, no BI tool, no SQL. Read-only, and scoped to what the connected account is already allowed to see.
We'll walk the circuit view, your POS sync and showtime setup on a live screen. Backed by our 30-day guarantee.
The answer comes back as a sentence with the numbers in it, drawn from the same data your case monitor and cinema operations dashboards already show.
Example answer
“How can I improve the schedule at Union North?”
Union North has a clear problem next week, and it’s the same one it had this week.
The core issue: the weakest title is gaining screens, the strongest are losing them.
Last seven days at Union North:
| Title | Shows | Tickets | Per show | Booked next week |
|---|---|---|---|---|
| REDLINE XII | 35 | 960 | 27.4 | 30 ↓ |
| DINO SQUAD RESCUE | 16 | 411 | 25.7 | 13 ↓ |
| WINTERING | 28 | 345 | 12.3 | 29 ↑ |
Wintering is running at 9% occupancy — 28 showings in a 59-seat room to sell 345 tickets total. Next week it’s keyed for one more show than this week, while both underbooked titles get thinned. CineScope’s programming analysis flags all three as “repeats.”
The swap to make
Drop the 21:35 Wintering in Auditorium 1 and give the screening to Redline XII. Auditorium 4 already carries five Redline shows on Saturday, so the pattern exists — extend it to the weeknights. That’s one pair, once a day, and it moves roughly 15 tickets a show to a title doing 27.
Dino Squad Rescue is in the wrong slots
On Saturday, Auditorium 3 gives Nightrunner the 11:40 and puts Dino Squad Rescue at 14:00 and 18:30. Your Saturday 11:00 hour averages 39 tickets a show and Sunday 11:00 averages 33 — that’s the family window, and a 103-minute kids title is what belongs in it. An 18:30 start for Dino Squad Rescue is close to dead weight. Swap the two titles within Auditorium 3 on Saturday and Sunday: no extra screenings, no room changes, just reordering.
Trim the midweek matinees
Wednesday 9/16 as keyed has six showings starting between 13:50 and 14:05, and four more between 16:10 and 16:35. Over the last 90 days, Wednesday 13:00 shows average 3 tickets, 14:00 average 6, and 16:00 average 3. Thursday is barely better at 6–9. Cutting the first show of the day Monday through Thursday costs almost nothing in admissions and buys back staffing and lamp hours — and it frees the slot you need for the Redline and Dino Squad adds.
One smaller timing fix
Your peak hour is 18:00 every single day (Saturday 87 a show, Sunday 63, Tuesday 57). The 19:00 hour drops off sharply. Right now The Hollow Door starts at 19:00 and Wintering at 19:05, both just past the peak. Pulling The Hollow Door to around 18:15 in Auditorium 5 puts it in the better band without disturbing Auditorium 6’s Skyline Guardian 18:00.
A real response — only the location names, film names and ticket numbers have been changed for example purposes. It surfaces and ranks; a human still books.
Issue trends, cases open too long, open workload, resolution stats, repeat issues, per-location rankings and inspection status.
Sellout stats, schedule utilization, room capacity, a title's performance against its usual draw, the week ahead, programming moves and the cost of downtime.
Nothing the assistant can do changes anything. It answers questions about your data; it does not create, edit, close or dispatch anything, and it does not act on its own.
The assistant sees exactly what that person could already see by signing in — never more. A general manager's connector answers about their own sites.
CineScope implements MCP as specified, so it works with any MCP-capable assistant rather than being locked to one vendor's chat window.
Off until your account admin switches it on and chooses which roles may connect; each person then authorizes their own assistant with OAuth, the same way they would any other app. No exports, no BI tool, no SQL — though answers do stay in that person's own AI assistant history.
Each person can end their own connections in Settings. The account admin sees every connection across the circuit and can end them all with one press, after which each assistant has to be connected and approved again.
How CineScope handles hosting, encryption and access control is written up on the security page.
No, the two are separate. The AI Assistant is a chat on every staff page inside CineScope, and besides answering it can draft a note on a case, a new case or a closure, each of which waits as a card until the person presses Confirm. Its questions come out of your included AI tokens.
The connector is for the assistant a person already uses elsewhere. It answers the same questions read-only — it cannot draft or change anything — and what it is asked is paid for on that person's own AI plan. What each of CineScope's own AI agents may do is set out separately.
An MCP server is a service that implements the Model Context Protocol, an open standard for giving an AI assistant structured access to a specific system's data and tools. CineScope runs an MCP server for a circuit's own operational data, so an assistant can answer questions about it directly instead of relying on exports or a BI dashboard.
Any assistant that supports the Model Context Protocol, including Claude. Because CineScope implements the standard rather than a proprietary plugin, a circuit is not tied to a single vendor's chat window.
No. The CineScope MCP integration is read-only. The assistant can retrieve and summarize data through purpose-built tools, and it cannot create, edit, close, dispatch or delete anything in the platform.
Exactly what the connected account could see by signing in to CineScope, and nothing beyond it. Permissions are enforced on the CineScope side, so a general manager's connector answers about their own sites while a circuit owner's connector covers the estate.
The account admin switches the connector on — it is off by default — and chooses which roles may connect. Each person then authorizes it once via OAuth from their AI assistant, and the assistant queries CineScope directly. There is no export step, no separate BI tool and no SQL to write.
It covers 61 purpose-built tools across the estate: issue trends, cases open too long, open workload, resolution statistics, repeat issues, per-location rankings and inspection status, plus the programming side — sellout stats, schedule utilization, room capacity, title performance against a title's usual draw, the week ahead, programming moves and the cost of downtime.
No. The MCP server reads the operational data CineScope already holds for your circuit, so questions are answered in a sentence without a warehouse, an export pipeline or a report builder in between.
See also guest sentiment and NPS, programming and film booking analytics — reachable through the same MCP server — and what a circuit pays on the pricing page.
We'll walk the circuit view, your POS sync and showtime setup on a live screen. Backed by our 30-day guarantee.