Business support · Planned service

Contact Data Enrichment & Refresh

Planned service: discuss updating selected fields in a contact file, with matching rules, source permissions and availability reviewed first.

Contact index cards and a laptop spreadsheet at a research desk.
Service formatBatch file or refresh plan

Planning an update to your contact list?

This planned service would update selected contact fields across a supplied file. A marketing list and an administrative or account portfolio can have different source permissions and matching needs. Tell us the intended use, record count and fields you want refreshed so we can review feasibility.

Production availability and source permissions still need confirmation. A proposal would explain returned fields, matching rules, ambiguous or unmatched records and the delivery format. An added phone number or email address does not establish consent to contact someone or guarantee that the message will reach them.

Is this the service you need?

When this fits

  • You want to plan a file-level refresh with defined identifiers and returned fields.
  • You can explain the intended use, record volume and handling of ambiguous matches.

Other services that may help

This service is planned. Production availability and source arrangements must be confirmed; an appended field does not establish permission to contact someone.

What’s included.

Explain how the data will be used

Select the use case first: managed marketing contact appending or portfolio and administrative refresh. Do not reuse a dataset for a purpose its source terms do not support.

Check the input record quality

Define qualifying input records and the fields required to attempt a match. Poor or ambiguous inputs should be flagged rather than converted into false certainty.

Agree on output and matching

Before any production work, agree on the fields to return, source permissions and how uncertain or unmatched records will be shown.

Choose batch or recurring refresh

Choose a one-time update or recurring refresh. Individual records needing manual research require a separate case and price.

Confirm availability before processing

The service is planned. A sample-file review can inform the proposed scope, but no match rate, deliverability rate, or recurring processing capability is promised.

What you’ll receive

  • A proposed input and output field specification.
  • An availability and permitted-use review for the requested fields.
  • The accepted match rules and update or non-match labels.
  • An agreed format for duplicates, missing inputs and other exceptions.
  • A written production order if the requested service is available and accepted.

How it works.

  1. Describe the update you want

    Describe the record count, identifiers, fields to update and intended business use. A column list can start the discussion.

  2. Check feasibility and matching

    Check current source permissions, required inputs and how original values, updates, uncertain matches and non-matches would be handled.

  3. Confirm availability before processing

    Proceed only when production availability and an order are confirmed. Agree on returned fields, price, delivery format and how unmatched records will be reviewed.

Know what to expect.

We’ll confirm the work, the updates you’ll receive and who to contact along the way.

  • The accepted source file, record count, input identifiers and permitted use.
  • The matching rules, fields allowed to change and labels for proposed updates or non-matches.
  • The output format, exception review and any sample evaluation agreed before a production order is accepted.

What helps us help you.

  • The business purpose, record population and approximate file size.
  • A non-sensitive example of the input field layout and file format.
  • The fields you want added or refreshed and how your team intends to use them.
  • The desired matching rules, output labels and person who will review exceptions.

What shapes your quote.

  • Record count and qualifying-input criteria.
  • Requested fields and permitted-source costs.
  • One-time batch versus recurring refresh.
  • Exception handling and any separately approved manual research.

Tell us what you need help with. We’ll explain which records are needed and how to provide them. Personal reports, ID images and account files can wait until then.

Frequently asked questions

Questions about this service?

A few details to help you decide.

Ask another question
Is this service available to order now?

It is a planned service. A scope discussion can establish the use case and required file format, but production availability and source arrangements must be confirmed before an order is accepted.

Does an appended phone number mean we can text it?

No consent or outreach permission is established by appending a field. Your contact strategy must be reviewed separately from the data-matching work.

What counts as a successful match?

That must be defined in the scope. Agree on the required identifiers, returned fields, quality description, and handling of ambiguous or unmatched records instead of relying on an undefined match-rate claim.

Can each unmatched record receive a manual investigation?

Only as a separately agreed exception scope. Batch matching and individual locate research have different inputs, effort, and pricing structures.

Can marketing and administrative files use the same arrangement?

Do not assume they can. Their purpose, source permissions, matching fields, and delivery requirements need separate review.

Let’s talk

What would you like to update?

Tell us the file format, approximate record count, fields and update frequency you have in mind. A column list is enough to begin; we’ll explain whether the planned service can support your request.

Build your request

Scope, availability and price confirmed before work begins.

What can we help you find?

Navigation menu