Sixlinked

Demos / Customer records

One customer record across three systems.

A test of spotting the same customer in a web form, a CRM and an accounts export, even when the name is typed differently. Doubtful matches go to a person. Updates that fail are held and sent again.

Data
Made-up customer records with known duplicates, built for this test
Model
None. Python and SQLite.
Recorded
19 November 2026

Recorded test on made-up records, not client work. There is no staff app or film for this one yet; the viewer below was drawn for this page from the recorded run.

The result

It found 94 in every 100 duplicates.

3,809 of 4,050duplicate customer pairs found
3,809 of 3,814automatic merges were right
0 lostand 0 doubled, after 396 failed updates were held and sent again

Matching exact names and postcodes found 203 of the same 4,050 pairs. 6,000 records across three stand-in systems; 2,016 incoming events handled at 137.5 a second on one desktop machine, after matching.

Where it falls short

  • 5 of 3,814 automatic merges were wrong. The end-state check also found a parent and child with the same name and address merged as one person.
  • 254 of 6,000 records were sent to review. Nobody reviewed them in this demo.
  • The records are made up (synthetic), we wrote the test set ourselves, and the three systems are local stand-ins, not live CRM or accounting software.

The end-state check counted 102 customer entries left separate that should have been joined, and 3 entries missing after different people were joined, across the three systems.

One customer from the run

Three versions in, one record out.

Recorded run, 19 November 2026. Viewer drawn for this page.

Web form

name
Barbara, Beebe
street_number
247
street
Station Drive
town
Cairns
zip
8999
region
NT

CRM

first_name
Barbara
last_name
Beebe
number
247
address
Station Drive
suburb
Cairns
postcode
2749
state
NT

Accounts

FIRST
Barbara
LAST
Beebe
ADDRESS
247 Station Drive
TOWN
Cairns
POSTCODE
2749
STATE
NT

Customer record

address
Station Drive
given
Barbara
number
247
postcode
2749
state
NT
suburb
Cairns
surname
Beebe

The web form's postcode differs from the other two, so this match was sent to a person to decide.

The recorded event log for this customer (18 entries)
SequenceStatusEventSystem
385Received32-1
386Delivered32-1Web form
387Delivered32-1CRM
388Held: system was down32-1Accounts
389Received32-2
390Delivered32-2Web form
391Delivered32-2CRM
392Held: system was down32-2Accounts
393Received32-3
394Delivered32-3Web form
395Delivered32-3CRM
396Held: system was down32-3Accounts
7735Delivered32-1Accounts
7736Sent again32-1Accounts
7737Delivered32-2Accounts
7738Sent again32-2Accounts
7739Delivered32-3Accounts
7740Sent again32-3Accounts

Nothing hidden

The 5 wrong merges, and everything sent to a person.

All 5 wrong automatic pairs and all 149 pairs sent for a person to decide. Nobody decided them in this test.

The wrong pairs are listed first.

For the engineer

Why the matcher is written as code.

Each decision can be explained and traced. No AI model decides who a customer is. Every incoming event gets an identity, so a repeat delivery is recognised and not applied twice. If a system is down, the update is held, not lost, and the end state is checked after it is sent again.

What this test does not show

  • A live CRM or accounting system. The three systems are local stand-ins.
  • Follow-up messages. It matches and routes records only.
  • A person working the queue of doubtful matches.

Let's talk

The same customer in three places?

Tell us which systems hold your customers and enquiries, and what goes wrong between them.

You will get a reply by email from Matthew, the engineer who would do the work.

Your enquiry goes straight to our inbox. We use your details only to reply to you. Privacy

Send an enquiry

Sending an enquiry needs JavaScript. You can also email hello@sixlinked.com.