Once a reviewer clicks the Verify Identity button in Decision Console, the Decision Overview displays the verification results. It consolidates every identity signal into one workspace, including an actionable Identity Score, an AI-powered Decision Summary, individual Attribute Cards for each core identity signal, and a Relative Distances and Map view for geographic context.
This article walks through each section of the Decision Overview and how to interpret what you see.
What is the Identity Score? #
The Identity Score is a single 0-100 score that provides an aggregated assessment of the identity associated with a signup or transaction. A score of 100 indicates the highest trust and lowest risk; a score of 0 indicates the highest risk of potential fraud or abuse.
| Score | Interpretation |
| 70+ | Lower risk. The signup or transaction has enough positive signals that the associated identity is high trust and can generally be approved. |
| 31-69 | Medium risk or incomplete assessment. May result from inconsistent matches, certain risk signals, or insufficient inputs to perform all available checks. |
| <30 | High risk. The signup or transaction should be reviewed further and potentially rejected. |
The Identity Score is derived from the comprehensive validations, identity checks, and cross-checks within Trestle’s internal database, calibrated against the customer feedback loop across millions of monthly signups and transactions.
What is the Decision Summary? #
The Decision Summary is an AI-powered recommendation synopsis that identifies the key positive and negative signals of the identity to help reviewers quickly decide whether to approve, reject, or further verify an identity. It sits between the contact’s name and the Identity Score. Clicking the “Decision Summary” button opens a pop-up with a recommendation, the signals supporting it, and a short written explanation.
Every Decision Summary returns one of three recommendations:
| Recommendation | What it Means |
| Approve | The identity holds up under cross-examination. Positive signals outweigh any potential concerns, and the signup or transaction should generally move forward. |
| Investigate | The identity is mixed or incomplete. Positive signals are worth weighing against specific concerns, and the case warrants a closer look before a decision is made. |
| Reject | The identity shows significant risk. Negative signals point to a likely synthetic, mismatched, or fraudulent identity. |
Below the recommendation, the Decision Summary lists the positive and negative signals that drove it, drawn from the same Attribute Cards shown in the Decision Overview.
An Approve recommendation might surface positive signals such as:
- Email first seen more than 5 years ago
- Phone subscriber match, high confidence
- Phone line type is mobile
A Reject recommendation might surface negative signals such as:
- Email first seen within the last 30 days
- Phone is low activity or disconnected
- Primary address is invalid
The summary then synthesizes those signals into a plain-language explanation of the recommendation, including the Identity Score. Reviewers can copy the full Decision Summary to their clipboard, formatted for case notes, escalation tickets, or audit trails.
What Are Attribute Cards? #
Decision Console organizes identity data into Attribute Cards, with one card per core identity signal. Depending on the inputs provided, the Decision Overview will return Attribute Cards for Primary Phone, Primary Address, Secondary Address, Email, and IP Address.
Each card displays a set of Attribute Details. These are the individual data points that make up the signal. Attribute Details are intuitively color coded: green if the data is verifiable and consistent, red if it’s invalid or potentially risky. Any card can be expanded into the Details Panel for deeper investigation.
For a full breakdown of every Attribute Card and the details they return, see What is an Attribute Card and How Do I Read It.
What is the Relative Distances and Map view? #
The Relative Distances and Map view plots the phone subscriber billing address, primary address, secondary address, and IP geolocation onto a map and calculates the distance between each. The reviewer can select an anchor point, and all relative distances are calculated from that anchor.
The map includes overlay zones for quick interpretation:
- Green zone (within 50 miles): Lower risk. Geographic consistency between identity attributes.
- Neutral zone (50-200 miles): Worth checking. Some legitimate variation, but worth a closer look.
- Outside 200 miles: Higher risk. Geographic inconsistency that typically warrants closer investigation.
For example, an IP in Los Angeles and a shipping address in New York would appear well outside the green zone, prompting the reviewer to drill into the data and look for a legitimate connection (a known second resident, a verified business address, etc.).
What is the Details Panel? #
The Details Panel is a slide-out drawer that lets reviewers drill into the underlying data behind any Phone, Address, or Email Attribute Card. Each Details Panel provides a reverse lookup view, with underlying identity associations and associated social profiles.
Within any Details Panel, each address, alternate phone, and email is clickable, triggering a reverse lookup on that entity. This allows reviewers to chain investigations and uncover identity connections. For example, confirming that a primary and secondary party in an e-commerce transaction historically shared the same address.
Phone and Email Detail Panels may also list associated social profiles of the identity. When a contact links to more than one person, profiles are grouped by individuals. Agents can click these profiles to investigate further. If a profile lists the same city as the address on file, that’s another point of corroboration. Social Profiles don’t factor into the Identity Score, but instead act as a supplemental signal.
For a deeper walkthrough of the Phone, Address, and Email Details Panels, see What is an Attribute Card and How Do I Read It?
For more information on Decision Console, check out the articles below: