LAUNCHING SOON · THE SIGNAL 50

Same customer. Are these the same job?

A familiar name doesn’t always mean the same job. Confirm the customer and work first. A clearer match helps your team interpret the questions Signal raises across available records.

The first 50 customers receive a free initial Signal scan after launch.

Check the customer and job Explore Signal

Leads · Estimates · Billing · Payments · Business changes · Marketing. NORI helps explain the records and patterns behind the day.

We’ll follow up to confirm fit and explain next steps before launch.

THE WORKING DAY BEHIND THE PROBLEM

Does this sound like your week?

The quote and invoice screens show two versions of a customer name. The owner remembers them, but they have two properties and several visits. The records might belong together, or the invoice might cover other work. A familiar name starts the check.

An uncertain match can lead to the wrong invoice review, a repeated call or an overlooked job. Keep the evidence visible for the next person.

Check the customer and job

Two identities. Three possible decisions.

First review the customer, then the job. Keep the evidence beside the decision.

Customer identity

Evidence to inspect: Shared references and supporting contact details
Question to answer: Do these records describe the same customer?
Next check: Confirm changed details or shared contact channels.

Job identity

Evidence to inspect: Site, scope, dates and linked work references
Question to answer: Do they describe the same work?
Next check: Separate repeat visits, properties and billing stages.

Supported match

Evidence to inspect: Consistent references and context
Question to answer: What lets another person understand this match?
Next check: Keep the evidence with the next review.

Conflicting or insufficient

Evidence to inspect: The disagreement or missing record
Question to answer: What still needs confirmation, and by whom?
Next check: Leave the match unresolved until that check is made.

A matching rule is a starting point, not permission to merge records. Product-specific rules and authorized changes belong in the original system.

Start with the right records.

If you are checking possible duplicate customer records across systems, confirm the customer and the work separately first. This is a manual evidence review. It does not merge, delete or repair records. Confirm the relationship before an authorized person changes anything in the original tool.

Customer references and available contact details from each source, including existing cross-system links.
Site, job reference, dates, scope or quote version, and related invoice references.
The source of each record and any conflicting, changed or unavailable information.

What should I know before checking?

Check customer identity and job identity separately. Shared references and supporting contact details can help identify a customer; site, scope and linked quote or job references help identify the work. Similar names, amounts or dates alone are not enough. Record a supported match, conflicting evidence or insufficient evidence.

Make the handoff visible.

Check who the records describe
Use shared references and supporting contact details. Households or businesses may share an email or phone. Confirm changed details. Local IDs from different tools are not necessarily shared identifiers.
Check which work they describe
Compare property, scope, dates and linked work references. One customer can have several jobs; deposits and stage invoices can belong to one job. Confirm the billed work matches the work under review.
Write the decision and what supports it
Mark the relationship supported, conflicting or insufficient. Preserve the source reference and reason. Ask the person who knows the customer or owns the record to resolve uncertainty before a billing or contact action.

FICTIONAL EXAMPLE · A HANDOFF TO CHECK

Read the story across the records.

Quote: Customer C-18 · work at the Oak Street property
Invoice: Customer C-18 · work at the Pine Street property
Work references: Different job references and scopes

What it establishes. The customer reference agrees, but these records describe separate jobs. The invoice does not answer the Oak Street billing question.

What to check next. The office keeps the jobs separate and looks for the invoice or documented hold for the Oak Street work.

A gap needs context.

Check these legitimate explanations before deciding the handoff was missed.

Several customers share a household or business contact channel.
A customer changed their details, or sources use different local identifiers.
One customer has several properties, repeat jobs or multiple invoices for a billing stage.

The questions your office will ask.

Is a matching name enough?

Use supporting references and context. People can share names or contact details, and one customer can have several jobs. Check the work separately from the customer.

Should the office merge two similar contacts?

This guide does not decide or perform a merge. The authorized record owner should confirm identity and follow the installed tool’s rules before changing records.

What if we cannot confirm the match?

Record the missing or conflicting evidence and the person who can check it. Leave the relationship unresolved rather than using a guess to justify another call or invoice.

More help for your team

Bring these questions to your team.

What supports the customer match?
What supports the exact job match?
Who can confirm conflicting or unavailable evidence?

Choose a printable review worksheet Check other reasons your tools disagree Review billing for the confirmed job

Try a sample Signal scan

Use the weekly operations checklist

Why gaps appear between business tools

Further reading: HubSpot explains shared identifiers and product-specific record matching. Vendor guidance does not establish a supported Signal connection.

THE BROADER SIGNAL PICTURE

See today’s priorities. Understand what changed.

Signal is launching soon. It is designed to compare available records across your existing tools, show what needs attention and help your team understand the changes behind the working day.

What changed since the last review?

Response speed, bookings, job values and invoice age can shift while everyone is busy.

Signal compares available records over comparable periods and keeps open gaps in view. NORI helps explain what changed and what still needs checking; your team reviews the context.

Continue to the Signal story

Understand the story behind the records.

Signal compares available records read-only and shows which handoffs need your attention. Your team confirms the customer and job before acting in its original tools. We confirm fit and record coverage before starting. Missing or outdated evidence stays unknown.

The first 50 customers receive a free initial Signal scan after launch.

We’ll follow up to confirm fit and explain next steps before launch.

Continue to the Signal story SAVE MY SPOT

Prefer a written overview?

Read how Signal works

More guides for your team

01 · COMPLETED WORK → BILLING