AI inspections for Opsyte

Overview

An Opsyte ticket is a very good record of a problem someone already noticed. The maintenance section holds defects as tickets with a submitter, an assignee, a priority, attached images and the time since they were logged; incidents, lost property and the shift handover sit alongside them, and the night is closed off with an online cash up. What no part of that describes is the condition of a venue nobody filed a ticket about. RapidEye reads your venue list and trading dates from Opsyte and the photos your team takes, and returns a finding for every issue it can see, including the ones nobody raised.

How it works with Opsyte

Opsyte's operational tools each capture one slice of a night, so the checks attach to those slices rather than adding a new one.

• Maintenance tickets. The images already attached to an open ticket get read: how far the split in the banquette actually runs, whether the leak has stained the ceiling, whether the thing marked completed looks completed. RapidEye also raises what no ticket covers, because the loose handrail was in the background of a photo taken for something else.
• Incidents. An incident report is written in a form, in the moment, by someone dealing with the incident. The photos from that night sit under the report, so the condition of the floor or the glass or the step is on the record rather than in a description typed afterwards.
• Lost property. Opsyte lets a ticket carry photos of the item. The same photos let RapidEye tell you what else was in the frame: the table left uncleared, the missing chair, the stack that never went back to the store.
• Handover and close. The handover passes the night to the next shift in words. Findings for the same venue and date arrive with it, so the opening manager reads what happened and sees what was left.
• Across the group. Opsyte benchmarks venues on their numbers. Findings tagged by venue benchmark them on condition, which is the half that shows up in a review long before it shows up in a P and L.

Each finding names the venue and area, where it is in the frame, the kind of problem, how bad it looks, the photos behind it, and a suggested next step. It lands in the RapidEye dashboard and, if you want, a Slack channel or an area manager's inbox, and you decide whether it becomes an Opsyte maintenance ticket. What is listed here are examples rather than limits: video walkthroughs, a cellar or kitchen format of your own, or a brand standard specific to your group is something we set up with you.

How to connect Opsyte to RapidEye

1. Your venues on Opsyte. The sites you want checked need to be trading on the account. A venue you would rather not have looked at simply stays off the list.
2. A source for the photos. If your managers already attach images to maintenance or incident tickets, RapidEye reads those. If nobody photographs the venue today, RapidEye sends a capture link that opens on any phone with nothing to install, walked at close before the cash up is locked.
3. RapidEye added as an External User. Opsyte has a documented path for exactly this kind of account, the one built for off-site accountants and area management. Read Only is enough.

How an Opsyte maintenance ticket works, and where it stops

Checked against Opsyte's help centre, September 2026.

Opsyte is hospitality management software for restaurants, pubs, bars and quick service groups: scheduling, time tracking, payroll, right to work checks, online cashing up and head office reporting, with a set of operational tools that includes maintenance, incidents, lost property, the handover and a bulletin board. According to Opsyte's help centre documentation (opsyte.com), the maintenance section lets you log any defect as a ticket assigned to another employee or to management, and every ticket lives in one of three places.

The three sections as Opsyte documents them; a ticket moves between them from the Status dropdown after clicking Manage. The bottom line of each is what RapidEye does there.

Tickets are created from the Create New button, and Opsyte will email a contractor the whole ticket from the Details view, recipient, message and all. That is a genuinely well-shaped loop for a known defect: seen, logged, priced, assigned, sent, closed. It runs on a defect being seen and typed up first.

Where photos already exist in Opsyte

In more places than people expect, which is why this integration usually needs so little from a team.

• Maintenance ticketOpen tickets display any images that have been attached, alongside the submitter, assignee, priority and age.
• Lost property ticketAdd photos is an explicit step when creating one, with an image preview from the thumbnail.
• Incident reportFiled from a form with dropdown answers and a confirmation toggle, then editable and viewable in greater detail.
• HandoverFree text under Financial, for staff on duty, sickness, covers, sales and anything else relevant to the next shift.
• Cash upLocked and unlocked at the end of the night, with an email alert to management on both.

What no Opsyte documentation describes is anything that looks at a stored image and tells you what is in it. That is not a shortcoming of a back office system, it is simply not what a back office system is for. The gap belongs to the workflow: photos exist, and at eleven at night with the till to count there is nobody free to open them. RapidEye is the pair of eyes on the other end, so the images your team already attaches become a short list an area manager can work down before service.

Who sees the findings

Opsyte's own access model makes this easy to scope. External Users are documented as people who need access to your information but are not on the rota or payroll, off-site management and off-site accountants being the examples, and they are invited from Manage Staff with permissions set module by module and department restrictions set to No Access, Read Only or Read and Write. Restriction sets can be saved as presets and reused. Reporting from RapidEye follows whatever shape you have already drawn there: a general manager sees their venue, an area manager sees their patch, the head office sees everything.

Opsyte integration FAQ