OpSage Release 0.9.5: Capture the Why Behind the Numbers

Every day, your managers walk the floor and know things your data doesn't. They know tomato prices jumped. They know the dishwasher went down at 6 and came back at 9. They know four burger patties got thrown out before service. That context has always existed, but it just lived in someone's head, a group chat, or a text thread that disappeared by Monday.

OpSage 0.9.5 changes that. This release introduces Operational Observations  and it's one of the most meaningful updates we've shipped.

Headline Feature: Operational Observations

Operational Observations gives managers a way to capture what's happening at the restaurant (in plain language, as it happens) directly through AI Chat. No separate app. No form to fill out. Just describe the event, and OpSage takes it from there.

Behind the scenes, OpSage automatically classifies the observation by domain (food cost, labor, equipment, waste, staffing, reviews, customer), extracts relevant entities like vendors, items, and prices, and stores it in structured form so it flows into your weekly reports and anomaly explanations. The manager's original words are preserved verbatim — the AI classification is additive, not a replacement.

A few examples of what that looks like in practice:

• “Tomato prices jumped to $95 a case on Tuesday’s order.”

• “Threw out four burger patties, shelf life.”

• “Dishwasher broke at 6pm, back up by 9.”

OpSage classifies each one, links it to the right section of your weekly report, and — when an observation is submitted in response to an anomaly alert — ties it directly to that alert so the “why” lives with the data permanently.

If the AI classifies something incorrectly, managers stay in control: tap the domain tag to reassign it, or just tell OpSage in chat (“actually that was a labor issue, not food cost”) and it updates. No friction, no dead ends.

This is the kind of capability no single-source tool can replicate. Sales systems know sales. Labor systems know labor. OpSage knows what your managers know — and now it can capture, structure, and surface that knowledge across the entire platform.

Anomaly Alerts: Now You Can Answer “What Happened?”

When an anomaly alert fires — a food cost spike, a labor overrun, a traffic drop — you can now reply directly in AI Chat. Your explanation is captured as an observation and linked to that specific alert, so the context doesn't get lost in email or buried in a Slack thread. Over time, this builds a searchable, per-location history of operational context that makes future analysis meaningfully richer.

Hands-Free Capture: Voice Input in AI Chat

AI Chat now accepts speech input. Managers can talk through what they saw on a line walk, flag a prep issue, or note a receiving variance — OpSage transcribes and classifies it exactly like typed input. Observations don't have to wait until someone gets back to a screen. Capture happens in the moment, which is when it's most accurate.

Included in Your Subscription: No Per-User Fees

Operational Observations, voice input, scheduled report distribution, and the full reports framework are all included in the OpSage subscription — no per-user fees. Every manager at every location can capture context, receive reports, and use the platform without that decision turning into a licensing conversation. Deploy broadly and get the full value of the platform.

Reliability: Reports Module Stability

Three crash fixes were included in this release, all targeting custom report templates:

• Fixed: Crash when opening reports built on custom templates
• Fixed: White screen when selecting a “(custom)” template during report creation
• Fixed: Crash when deleting a report

If you tried custom templates previously and hit an error, it's worth trying again.

Security: Proactive Controls

Security updates included in 0.9.5:

• Input sanitization against SQL injection in search and observation text
• Role-based access control for the Reports module

Polish & Updates

• Inventory updates — Inventory management flow aligned with the per-restaurant MarketMan configuration introduced in an earlier release.
• UI polish — Interactive text now darkens on hover; close icons standardized across the app.

The gap between what your data shows and what your managers know has always been one of the hardest problems in restaurant operations. Release 0.9.5 closes that gap in a meaningful way — connecting the operational context that already exists in your locations to the analytics platform that needs it to be fully useful.

To learn more about what OpSage can do for your operation, visit F.A.Q. or request a demo.