This article contains a breakdown of the key concepts that are good to know when working with Implio.
A piece of content that enters Implio is called an item, and items are sent to the tool in batches via the API. Each item gets assigned an individual task ID, which will follow it through the entire process, all the way back to you.
When an item has gone through the automation part of Implio it will return with one of the following decisions: Approved, Refused or Requires Manual Moderation.
An item can never be edited, so if you want to make changes you need to send it in as a new item.
Ex. user sends in a piece of content. It becomes an item when it enters Implio. If the user now edits his content on the site/app, the content needs to be entered as a new item into Implio.
|Task ID||The unique ID that Implio assigns each item. This will follow the item through the moderation process all the way back to you.|
|Remote ID||The unique ID that a piece of content has been assigned by the customer, before entering Implio.|
The item will keep it’s remote ID so that it can be tracked all the way through the moderation process.
|Content||This refers to the content of the item, for example the text or an image.|
|User||This is the end-user who published the piece of content on your site.|
|Location||The location from where the content was published.|
|New||The item has reached Implio but not yet been processed.|
|Automation||The item is going through the automation process.|
|Manual Review||The item is waiting for someone to manually review it.|
|Finished||The item is finished and a decision will be sent to your system.|
|Approved||The item is approved for publishing.|
|Refused||The item is refused. A refused item contains a refusal reason.|
Automation allows you to leverage the full power of Implio. You can automatically approve, refuse and send items to manual review, as well as highlight certain words and add notes to the manual review panel.
Automation in Implio builds on rules. Implio tests incoming items against all active rules in order to find a match and make a decision.
A Rule consists of an expression and an action.
An Expression decides whether an item matches a rule or not.
An Action is a suggested action that a particular rule gives to an item. Since an item can be matched to multiple rules, this might not always be the final decision. You can choose from four types of actions: Refuse, Approve, Manual or Nothing, where “nothing” is most often used for analytics purposes. Read more about decisions under orchestration.
Lists can be used to facilitate rules that include multiple keywords. These keywords could either be exact or regular expressions.
Based on the action/s of the rule/s that match an item, the orchestration function will make a final decision to Approve, Refuse or Require Manual Moderation. If an item matches multiple rules, the orchestration flow will decide the final decision.
Items that require manual review are sent to the manual moderation panel.
Items that are sent to manual moderation enters the default inbox for first line moderation. Items in this inbox can be manually either approved, refused or escalated. You can also choose select to send improvement suggestions to the end user.
Items that have been escalated from the default inbox enters the escalated inbox. These items could for example need extra work or an expert review.
An item that enters the manual review panel gets locked to the first user loading it for 10 minutes. It will not be possible to open this item in another tab or for other users to load it. This is to avoid that two moderators work on the same item at the same time.
We are here to support you.