Lesson 7 of 7 · 6 min

Data hygiene: audit logs, consent and duplicates

Keep the data clean with audit logs, consent checks and duplicate checks.

Read the lesson

Goal: Keep the CRM clean with a 15-minute weekly check that catches duplicates, consent gaps and stale records.

You need: A live client with real data. Contacts, Deals and Settings access. Lessons 1 to 6.

Why this matters

A CRM gets dirty a little every day. A caller gives a new number, and the AI creates a second contact. A tech types a gate code into the wrong field. A lead from last spring sits in New forever.

Each small mess has a cost. A duplicate contact gets every reminder twice. A customer who opted out on one record may still look textable on the other. A stale deal makes the forecast look bigger than it is. After a few months, the office stops trusting the CRM, and goes back to paper.

Cleaning once a year does not work, however big the cleanup day. By then the mess is too big, and the bad data has already sent wrong messages. A short weekly check works.

The 15-minute weekly check

Do it on the same day each week. Monday morning works for most offices. Use a timer. Write the counts in a small log each week: duplicates found, blank consent, stale deals. The log shows the owner the CRM is getting cleaner, and it shows you where the office needs more training.

The timeline shows the five checks in order, with where to look for each one.

Fig 1

The 15-minute weekly check

  1. 0 to 4 minNew duplicates: search new contacts by phone
  2. 4 to 7 minSmart Merge review tasks in the task list
  3. 7 to 10 minConsent on contacts created in the last 7 days
  4. 10 to 13 minStale deals in Deals, oldest first
  5. 13 to 15 minTag drift in the Tag library
Same day, same order, every week.

Keep the check even in busy weeks. Busy weeks make the most duplicates. A storm week for a roofer or a heat wave for an HVAC shop doubles new contacts. Skip the check then, and you clean for a month.

Duplicates: prevent first, fix second

There is no contact merge on the contact menu. Duplicates are handled at import, with Smart Merge. So prevention matters most.

Prevent:

  • Teach the office to search by phone before creating a contact.
  • Use Smart Merge for every import into an account that already has contacts. It merges obvious duplicates and creates review tasks for unclear ones.
  • Keep phone numbers in one format.
  • Keep import files inside the limits: up to 10MB and 10,000 rows, as CSV, TSV or TXT.
Fig 2

Choosing how an import handles duplicates

How should we handle duplicates?

Simple ImportOnly create new contacts; skip rows that match
Smart MergeMerge obvious duplicates; review tasks for unclear ones
Files can be up to 10MB and 10,000 rows. There is no merge on the contact menu, so Smart Merge at import is the main tool.

Fix, when one gets through:

  1. Open both records. Compare their Activity tabs.
  2. Keep the record with more history.
  3. Copy any missing facts to it: phone, email, custom fields, tags.
  4. Check consent on both. If either opted out, the kept record must respect it.
  5. Delete the extra record.
Fig 3

Fixing one duplicate by hand

  1. Two records for one customer
  2. Compare both Activity tabs
  3. Keep the record with more historyCopy missing phone, email, fields and tags
  4. Did either record opt out?YesThe kept record keeps the opt-outNoKeep the consent source and date
  5. Delete the extra record
Keep the history, and never lose an opt-out.

Deleting removes that record's own history. That is why you keep the one with more activity.

Consent: what the app does, and what you track

Opt-out is always enforced. A contact who replies STOP cannot get texts. That cannot be switched off.

What you set is the yes. Each contact has its own SMS consent value in the app. Turn it on only when the person agreed. When it is off, a review invite by text will not send: "SMS consent is required before sending". SMS Campaigns also send only to contacts with SMS consent.

Also record how and when each person agreed. For example, add a Dropdown sms_consent_source. Its answers are Booking page, Phone script, In person and Web form. Add a Date field sms_consent_date beside it.

Contacts imported with no consent record keep the imported-no-consent tag until they agree. Each week, check that new contacts have SMS consent set and the source filled. A blank means nobody asked.

Fig 4

Consent: what the app does, what you track

The app enforces
  • No texts after a STOP reply
  • Opt-out cannot be switched off
  • SMS Campaigns and review texts need SMS consent
You track
  • SMS consent on each contact who agreed
  • How they agreed: sms_consent_source
  • When: sms_consent_date
  • imported-no-consent until they agree
The app enforces the no and checks the consent value. You set the yes and record how and when.

Who changed what

When a record changes and nobody knows why, check Audit logs in Settings → Connections & developer tools. It only helps if every person has their own login.

Data retention is set in Settings → Data protection → Retention & holds. Policies stay off until someone turns them on. So no data is deleted on a schedule unless the client chooses a rule. Ask the client's advisor whether a rule is needed.

Build it in ServiceAgent

  1. Agree the weekly check day and owner with the client.
  2. Build a saved view: Contacts, Created From 7 days ago. Name it "New this week".
  3. Add the consent source and date fields if they do not exist yet.
  4. Write the 5-step check on the office card.
  5. Run the first check with the office lead watching.
  6. Note how many duplicates, blanks and stale deals you found.
  7. Check it works. Run the check again next week. The counts should be lower.

Size changes the check

An owner-operator can do the check in 5 minutes. Few new contacts, few deals.

A fleet needs the full 15 minutes and a named office lead. The Operator spot-checks once a month.

A multi-location business needs one check per location, or one central person who checks all locations by tag.

Worked example: Summit Roofing after a hail storm

In a normal week, Summit Roofing gets about 60 new contacts. Say 4% are duplicates. That is 60 x 4% = 2.4, or about 2 a week.

In the storm week, Summit gets 300 new contacts. At the same rate, 300 x 4% = 12 duplicates.

Each duplicate gets the appointment reminder twice. Say each reminder is 1 SMS segment, sent at 24 hours and 1 hour before. The Appointment Reminder template is 1 run per appointment with 2 texts. So the duplicate adds 1 + 2 + 2 = 5 credits each visit. Twelve duplicates cost 12 x 5 = 60 extra credits.

Fig 5Example numbers

Duplicates at Summit, normal week vs storm week

Normal week: 60 new contactsabout 2
Storm week: 300 new contacts12
At 4%, a storm week makes 12 duplicates. Each costs 5 extra credits a visit: 60 in all.

The credits are small. The real cost is 12 customers who get every text twice and think the business is sloppy. And if one of them opted out on one record, the other record could look textable.

The office manager wants to skip the weekly check until fall. You keep it, and add 15 minutes in storm weeks.

Common mistakes

  • A once-a-year cleanup. Fix: 15 minutes, every week.
  • Skipping the check in busy weeks. Fix: busy weeks need it most.
  • Deleting the record with more history. Fix: compare Activity tabs first.
  • Tracking only opt-outs. Fix: record how and when each person said yes.
  • Shared logins. Audit logs cannot help. Fix: one login per person.

Do this now

Write the 5-step weekly check on a one-page card for a real or practice client. Create 3 deliberate duplicates in your practice account. Find them with the search, and fix each one with the 5-step method.

Practice the conversation

  1. Operator I'd like 15 minutes of your office manager's time each Monday for a data check.
  2. Owner We're slammed after this storm. Can it wait till fall?
  3. Operator Storm weeks make the most duplicates. That's when it matters most.
  4. Owner What happens if we skip it?
  5. Operator Customers get every text twice. Some might get texts they opted out of.
  6. Owner That last part sounds bad.
  7. Operator It is. Fifteen minutes a week keeps it from happening.
  8. Owner Fine. Mondays at nine.
  9. Operator I'll join the first one and show them the steps.

Quick check

  1. After a hail storm, a roofer's office manager wants to skip the weekly data check until fall. What do you advise?
    • Skip it and clean up at the end of the season
    • Keep the weekly check, because busy weeks make the most duplicates
    • Skip it, because `Smart Merge` cleans nightly
    • Let the techs fix records from the field
  2. You find two records for one customer. One opted out of texts. Which consent applies to the record you keep?
    • The opt-out
    • Whichever is newer
    • The opt-in, because the business needs it
    • Neither; consent resets on a merge
  3. A client adds 200 new contacts in a week. 5% are duplicates. How many duplicates is that?
    • 5
    • 20
    • 10
    • 40

ServiceAgent UniversityLearn to run a service business on autopilot. Free courses, Blueprints and certification for Service Operators.

Learn

Get certified

Community