Check AI file review results on a project's Files & Links and Responses tabs
Updated
Who can do this: Internal users who can open the project
When a file request has a description of a good file, Aero checks each customer upload against it. You can see the result for every file on the project's Files & Links tab and open the same review the customer saw.
This feature is available when it's turned on for your organization. If you don't see it, contact your OnRamp team.
Before you begin
This feature is available when it's turned on for your organization. If you don't see it, contact your OnRamp team.
Uploads are checked when the file upload in the task has a description under What does a good file look like?, a file under Example of a good file, or both. If both are empty, uploads aren't checked. After a file upload has had 25 review attempts in a day, more uploads to it aren't checked and get a Couldn't check chip. Only the first two example files are used. Customers see an example only when Let customers download the example is on.
Aero can read PDFs, Word (.docx), PowerPoint (.pptx), Excel (.xlsx and .xlsm), CSV and text files (.txt and .md). For images, it reads .png, .jpg, .jpeg, .gif and .webp files. Files of any other type, such as .heic, .tiff or .svg images, and files over 20 MB, aren't checked. They get a Couldn't review chip instead.
Optional: To test your description before customers use it, go to Try it with a file in the task builder, select Try with a file, and upload a sample. This section appears only on a saved step of a playbook task, not on a project's task. The button is available once you've entered a description or attached an example of a good file. The sample is checked against whichever of the two exists, and it isn't saved.
Check file review results
Open the project.
Select the Files & Links tab.
In the Files table, find the File review column.
To see the details for a file, select its chip.
The File review column shows only when the project has at least one file uploaded to a request that asks for a review. Files on other requests have an empty cell.
What the chips mean
Chip | What it means |
|---|---|
Looks good | The file meets the description and the example of a good file, whichever the request has. |
Missing 1 thing or Missing N things | The file is partly right. |
Not what was asked | The file doesn't look like the requested file. |
Couldn't review | Aero couldn't read the file, the file type isn't supported, or the file is over 20 MB. |
Couldn't check | The review couldn't run, for example after an error or when the daily limit was reached. |
Not reviewed | The file has no review. For example, it was uploaded before the request had a description or an example of a good file, or before file review was turned on. |
Each request reviews at most 25 uploads a day. Uploads past that limit are stored but not checked.
If a customer uploads the same file again to the same request, and neither the description nor the example files have changed, Aero reuses the earlier review instead of checking it again. Changing either one gets a fresh review.
Read the review card
The card opens with What the customer was told and the review date. Below that you'll see:
A title that matches the result, such as This looks like what we need, Almost there. 2 things are missing or This doesn't look like the file we asked for, with the file name.
A short summary.
Lists under What's missing, What looks good and Worth adding. Only lists with items appear.
Customers see the review labeled as OnRamp AI. Except for Couldn't review and Couldn't check results, they're told the review is a guide: they can continue, or upload a corrected file to check it again. This note doesn't appear on your team's card. For a file that couldn't be checked, they're told nothing is needed from them and your team will review it. When the portal agent is available in the customer portal, a customer's card for a file that's missing something or isn't what was asked also shows an Ask OnRamp AI about this button. It asks OnRamp AI what's missing from the file and how to fix it. Your team's card doesn't show this button.
The review results on these tabs are for your team. Customer users can't load the project's list of reviews. The portal agent can read the reviews on the task a customer is working on, so it can answer their questions about them. It sees only what the customer was shown, not your description of a good file.
Check results on the Responses tab
If your organization has the updated Responses tab, the same chips appear next to uploaded files there.
Open the project.
Select the Responses tab.
To open the review card, select the chip next to a file.