Reviews

A review runs one or more prisms on one screen of a site. When an operator checks their work on that screen, the extension captures the screen's elements and runs every prism of the review on them. The review decides which element each prism field reads and what each answer means: information only, a warning before sending, or a held send.

You manage reviews under Browser, Reviews in the app. The list shows each review's site and screen, how many prisms it runs and its status. Under the name, Checks before send marks a review that guards the Send button, and Shows answers one that only shows answers in the panel. Search reviews filters by name, site, screen or prism.

Create a review

Add the site first. Then choose New review.

1. Enter a Review name, such as Reply review. Operators see it in the panel when more than one review applies.
2. Pick the Site and the Screen the review reads.
3. Under Prisms, choose Add prism for each prism to run, up to 20.
4. For each prism, pick the Prism, map its fields to elements, and set its outcomes.
5. Choose Save review.

Every review on a screen applies at once. One capture of the screen feeds all of them.

Suggested prisms

Built-in sites suggest library recipes for each screen. Prisms you made from those recipes with Use this prism are listed first in the Prism menu, under Made for and the screen's name. When you pick one, its field mappings and outcomes are filled in from the recipe. Check them before you save. Your other prisms are listed under Other prisms. Archived prisms are not offered.

Map fields to elements

Each field of the prism gets a menu, such as Reply reads. Pick the screen element that field reads. The menu lists the elements as site, screen and element label, such as Talkt › Reply composer › Draft reply. Every field must read exactly one element, and several fields can read the same element. An image field must read an element set to Image (img element).

When a field's key matches an element's key, the editor picks that element for you.

Prism key

Prism key names the prism inside this review, such as prism_1. It starts with a letter and holds letters, numbers and underscores. Each prism in a review needs its own key. The key shows on every result the review saves.

Outcomes

An outcome says what one answer means for the operator. Open Outcomes under a prism to set them. Each question lists its possible answers, and each answer gets No outcome, Info, Warn or Block.

• A Choice question lists its options, plus Other and Not enough information.
• A Scale question lists its levels.
• A Yes / No question lists Yes and No.

Outcome	In the panel	When the operator presses Send
No outcome	Folded into the fine answers, unless Unsure	Nothing happens
Info	Listed above Unsure and fine answers	Nothing happens
Warn	Listed under Confirm before sending	The operator must confirm before the text is sent
Block	Listed under Holds the send, at the top	The send is held until the text changes

Warn and Block act on Send only when the screen has a Send button and the operator has turned on the Check button for the site. The send guard covers the details. On a screen with no Send button, outcomes only order the answers in the panel, and the editor says so.

The summary line shows the count of each outcome, such as Outcomes: 1 block, 2 warn. A prism with none reads Outcomes: none, every answer only shows.

Unsure answers

An answer can be Unsure. A Choice or Scale answer is Unsure when its top probability is under the prism's Unsure under threshold. Set it in the prism's Display settings, from its More menu, or for the whole account in Defaults. It is 60% unless you change it. A Yes / No answer is Unsure when its probability falls between the prism's Yes / No cutoffs. The extension uses the prism's current threshold and cutoffs, not ones saved with the pinned version.

You cannot give Unsure an outcome of its own. An Unsure answer to a question that has a Warn or Block outcome on any of its answers counts as a warning. The operator then confirms before sending, as for Warn. An Unsure answer to any other question is listed under Unsure in the panel and does not stop a send.

Policy context

Extra context or approved policy (optional) adds background for one prism in this review, such as your refund policy. The model reads it on every check after the prism's own context. It holds up to 20,000 characters. Operators cannot edit it.

Use it when the same prism runs in several reviews that need different policy, such as one per brand.

Who runs which prisms

An admin runs every prism of a review. An operator runs only the prisms an admin allowed them, set in Users under Prisms they can run: All prisms or Only these.

• A review shows for an operator when it has at least one prism they may run, and it runs only those.
• A review with none of their prisms does not show for them.
• The send guard counts only the prisms the operator runs. A Block outcome on a prism they may not run does not hold their send.

A change to an operator's prisms applies on their next check, with no new sign-in.

Pinned versions

Each prism in a review runs one saved version, shown under Pinned version. When you add a prism, the review pins its published version. The menu marks that one (published), and a note shows the published version when the review pins another.

Saving or publishing a new version of the prism does not change the review. Its operators keep running the pinned version, with the fields, questions and answers you set outcomes for. When you publish, the publish dialog lists the reviews that use another version, with a link to each.

Move to a new version

1. Open the review and pick the new version under Pinned version.
2. Check the field mappings. Fields the new version shares with the old one keep their element. Pick an element for each new field.
3. Check the outcomes. Outcomes for answers the new version does not offer are removed, and the editor lists them.
4. Choose Save review.

Test the new version on the prism's Test tab before you move a review that blocks sends.

Saving a review

Saving a review, or the site it runs on, changes it for every operator at once. The extension fetches reviews before every check, so a capture taken before the save cannot run, and the operator captures again.

Disable a review

Disable in the reviews list stops a review. The extension stops showing and running it, and a screen guarded only by that review no longer checks Send. Enable turns it back on. Reviews cannot be deleted, so disable one you no longer need. A disabled review still keeps its site from being deleted.

Where results show up

Every prism a review runs saves a result, as a call to that prism would. You find them on the prism's Results tab, where they count under the Browser extension source. A result from a review also shows:

• Checked by, the operator who ran the check.
• Review, the review's name and revision.
• Session, the extension sign-in that ran it.
• Prism key, with the prism version that answered.
• Sent anyway, when the operator confirmed a warning and sent. See Send anyway.

Operators see their own checks on the prism's Results tab. For a prism with no results yet, the Results tab lists the reviews that run it.