Review proposals

The Twin builds your map of the business from your connected systems. Along the way it proposes things it cannot settle on its own, and those arrive in your Inbox. This page is for the person deciding them.

What the Twin proposes

Every proposal is one of three kinds. They look the same in the Inbox and take the same decisions.

• A link says two records in two systems are the same thing: a supplier in a spreadsheet and a contact in Xero, say. It carries a confidence from 0 to 100% and a signal strip: one chip per compared field showing whether the two sides agreed (✓), disagreed (✕) or had no data (–).
• A definition is a governed product the Twin authored from your data: a named, described, tested view of one thing in your business. Accepting it puts it in front of the assistant; until then it stays dark.
• An action is something the Twin wants to do for you, written as a prompt with the evidence it noticed. Accepting it runs the prompt as you, with your permissions.

Proposals arrive in batches: a matcher run, an authoring release, or a review of your recent activity. The Inbox shows one row per batch; opening it shows the proposals inside.

The three decisions

1. Accept. A link records the relation between the two records. A definition is installed and activated, replacing the version that was serving. An action runs.
2. Decline. The proposal is recorded as declined and is not offered again.
3. Later. The proposal steps out of the queue without a decision. Bring it back with Reopen.

Add a note when your reason is not obvious from the data. The note is kept with the decision.

Taking it back

Open a decided proposal and press Undo. The decision stays as history marked reversed, whatever it did is put back, and the proposal returns to the queue. A link is unlinked, a definition is deactivated and the version it replaced comes back. Automatic decisions undo the same way, which is how you correct a matcher that is too sure of itself.

An accepted action cannot be undone: it has already run. The record shows it as done.

Working faster

• Tick several proposals and apply one decision to all of them. Select … % and above ticks every link at or above a confidence.
• Accept all on a batch accepts everything still open in it. For links you can set a minimum confidence first.
• Filter links to With a contradiction first. A contradiction is a field the matcher treats as decisive disagreeing, so the pair can never be applied automatically. Those need thought; clean pairs with high confidence usually go through in bulk.

Who decides, and what happens on its own

An organisation admin sets a policy per kind under the Twin's settings.

• Ask or auto: whether the engine's automatic band may decide by itself. Links default to auto, so a matcher's confident pairs are applied without you; definitions and actions always require a person to decide.
• Accept automatically at or above a confidence: for links, a threshold that overrides the matcher's own band. A pair at or above it counts as automatic, unless it carries a contradiction, which always asks.
• Who may accept: everyone, or admins only. Definitions default to admins, because a definition changes what every answer is built on.
• Default daily cap: how many action reviews a person may request in a rolling 24 hours before they choose a personal cap. Background and manual reviews share that cap.

Everything decided automatically appears in Changes with Undo, so nothing happens silently.

Changes

The Twin page has a Changes view: every decision, newest first, who made it or that the Twin made it, what it did, and Undo where it can still be put back. It is the audit trail of your map.

Staying on top of it

When a batch leaves proposals for you, you receive a Proposals to review notification in the app, and in Slack when it is connected. Notification settings let you turn it off or move it into a daily digest.