Jev CRM account relationship

Compare CRM accounts for duplication or a company relationship

Provide identity records for two accounts. Distinguish one company listed twice from separate parent or subsidiary entities, unrelated companies and unresolved names.

CRM account relationshipLive API
Try an example

The input explicitly establishes a rename of one entity.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This original text demonstration adapts a decision in a repository linked by the cited X post. The examples and explicit uncertainty outcomes are ours. The post is a directory reference, not proof that its author built every linked project. No third-party benchmark, business outcome or external action is reproduced.

Compare the accounts: Same for one company represented twice, including a documented rename; Related for separate entities in a documented parent, subsidiary or group relationship; Unrelated when evidence establishes separate unconnected companies; Unclear when names alone, missing evidence or contradictions prevent a conclusion.

Decision rules and labels
SameRelatedUnrelatedUnclear
A real response from the Jev API

Edit any input to explore a different decision. No request is sent until you run it.

Your next decision

Not run yet

Choose an example or write your own input, then run it to see the ranked choices.

Results are not stored by this site. Your submitted text is processed by the API provider.

The decision

What the decision checks

Account matching needs a relationship distinction, not just a similarity score. A documented rename can create two records for one company, while a parent and subsidiary should remain separate entities even if their names resemble each other.

The page reasons over evidence you provide. It does not query a business registry, confirm legal status or merge a CRM record. Retain the provenance and inspect both records before any destructive action.

This original text demonstration adapts a decision in a repository linked by the cited X post. The examples and explicit uncertainty outcomes are ours. The post is a directory reference, not proof that its author built every linked project. No third-party benchmark, business outcome or external action is reproduced.

Illustration of one spreadsheet row producing two separate classification results
Illustration of the decision flow.
How it works

Try the example in four steps

Use the sample to understand the rule, then test your own input for crm account relationships.

  1. Illustration of adding the text or evidence for a decision

    Add the information to check

    Provide identity records for two accounts.

  2. Illustration of defining a question and its allowed choices

    Confirm the question and labels

    Open the decision rules and keep the intended distinction between Same, Related, Unrelated, Unclear. Edit the choices only when testing your own rule.

  3. Illustration of sending one input and comparing the returned choices

    Run the decision

    Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

  4. Illustration of reviewing a result and an uncertain item before using it

    Review the next step

    Review Unclear before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
Documented renameSame100%
Parent and subsidiaryRelated100%
Unconnected namesUnrelated100%
Name similarity onlyUnclear95.0%
Same entity IDSame100%
Conflicting identifiersUnclear99.0%

These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 6 of 6 results matched the authored fixture expectations.Verified

Understand the results

CRM account relationships: six recorded examples

The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.

Using the result in your application

The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.

Replay options

Inspect saved outputs or request a new decision

View the code example
Two independent commands
# Offline: inspect the downloaded saved observations. No API key is needed.
python preview_choice_workflow.py samples.json saved-api-results.json

# Optional live request: install the SDK and set TYPESAFE_API_KEY privately.
npm install @typesafe-ai/sdk@0.6.0
node run-choice-sample.mjs samples.json case-1
# The live response prints to the terminal; it does not update saved-api-results.json.
Scope of this demo

Where this decision fits

Useful scope

  • Preparing a CRM data-review queue
  • Separating duplicates from parent-child relations
  • Highlighting missing identity evidence

Outside this demonstration

  • External company-identity verification
  • Automatic record merging
  • Ownership conclusions based only on names
Example FAQ

Using this example

The input contract and these limits define what the result means.

Can a shared domain prove Same?

Not by itself. Several entities may share a domain. Provide explicit entity evidence and any parent-subsidiary relationship.

Does Related permit merging?

No. In this contract Related explicitly means separate entities. A CRM may record their relationship, but this demo does not change either record.

Does the leading probability measure accuracy?

It describes the distribution over the supplied choices for this request. These six synthetic examples are functional tests with authored expectations, not a production accuracy benchmark.

Will a result change an external system?

No. The demo displays a label and distribution. The downloadable consumer produces a pending preview packet. Application code and a separate authorization policy would control any real action.

Test a different input

Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.