Reports and Intelligence:

Reports and Video Analytics

Video Analytics provides Envysion Reports with another layer of depth by which to surface transactions based on whether or not a customer or employee was present for that transaction.

Refunds with Customer Counts

Refunds equate to money lost from your bottom line, whether due to a guest’s dissatisfaction, or dishonest behavior by employees. While refunds should be a rare occurrence, the time to review refunds across your organization can become time consuming. Video Analytics can help reduce the number of refunds to review by analyzing the number of guests present during a refund transaction and inform you whether a guest was present or not without you having to open the video player.

Setting up the AI

In order to begin configuring the video analytics for a site:

  1. Click the Gear Menu and select the Intelligence Configuration option from the menu
  2. On the Intelligence Configuration page, select the third option from the left sidebar to launch the mask screen configuration, then click the “Add Mask” button in the top right corner of the page. The table will show sites and registers that are already configured.
  3. Select the desired Site, Register, and Camera, then click on the grid boxes that you expect a customer to be in at the end of a refund transaction.
  4. Click the “Save” button to create the mask and enable analytics for refund transactions conducted at that location on that register.
  5. Repeat steps 1 – 4 for other registers at that location.


The mask configuration tool does not automatically choose a camera based on it being mapped to the register for traditional video playback because we understand that sometimes constraints around camera positions means that the camera normally used to review the employee actions for transactions may not be the best view for analyzing the customer side of the counter. This allows the user the flexibility to select the best camera for the customer side of the counter if analyzing refund transactions at the front counter.

When setting up a mask, the tool only allows for one camera to be masked per register to prevent any potential conflicts in results. Each new register mask will trigger a seven day lookback at refund transactions on that register for video analysis to provide users immediate feedback when running the report (see below) on the results of that mask.

Run the Refunds Report

  1. From the Intelligence page, select the Report Templates and choose the Refunds report.
  2. Click the “Customize” button and add the new  “Person Count” filter to the report.
  3. Set the logic operator to your desired comparison and add a value for how many persons you are interested in knowing about, for example setting the logic operator to “EQUALS” and the value to “0”.
    1. Optional: add other filters to continue to refine the query parameters, such as the tender filter to look for refunds being issued to credit cards when no one is on the customer side of the register.
  4. Run the report.

Users will now see a reduced number of refund transactions based on the supplied filters. Drilling down to the receipt level of any group will display a new field that will display the count of people counted in that masked area for the refund transaction. Clicking on the row will open the video player and receipt view as normal for review. Existing user reports saved from the Refunds report can also take advantage of this new filter. Simply add the filter to your existing filters, run the report, and save the new configuration.

Editing the Mask

In order to make changes to existing mask configuration, from the setup screen, find the site in the configured sites table, and drill down to the specific register and the mask will be displayed. Click the edit button to make any changes and then click save to update the mask configuration. There are options to revert and cancel changes as well once editing is enabled. If you want to change the camera the mask is associated with, you must click the trash-can icon and delete the mask, then create a new mask using the setup steps above.

Was this post helpful?