Job crm-missing-fields-proposed-from-your-own-records · revised 12 October 2026
Fill your blank industry, country and lead-source fields, but only the changes you approve
For up to three blank fields you name, you get a change file with a proposed value and source per row. Only the rows or bands you tick are applied, with a rollback file.
You might be seeing
- Reports show a large "unknown" group
- Leads without a country fall out of the routing rule
No passwords, keys, card details or admin invites needed to start.
What usually happened
Blank fields stop records matching a routing rule or a report filter. Filling them by hand is slow, and a bulk fill from a guess puts wrong values into reports and routing. The risk is a wrong fill that nobody can tell from a right one.
Who it’s for: Operations lead whose reports and lead routing break on blank industry, country or source fields.
Usually starts when: A routing rule or report skips records because a field is empty, and nobody has time to fill thousands of rows.
The result: You receive a change file that proposes a value for each blank field with its source and a confidence band. Only rows or bands you tick go into the import file, and a rollback file restores the old values.
Check whether this job fits
Answer these without sending files or logins. Nothing is submitted unless you choose to contact us.
What you get
- The change file with source and band
- The import file for ticked rows
- The rollback file
- A before and after difference report
Included
- One object (contacts or companies) and up to three blank fields you name
- Up to 5,000 rows from an export
- A proposed value per row from your own other fields, the email domain or text on the company's own public site
- A source and a high, medium or low band per row
- An import file for ticked rows only and a rollback file
Not included
- Applying any change in your CRM
- Buying or scraping person-level data
- Overwriting a value that is already filled
- Keeping the fields correct afterwards
- Rows in the low band (never applied), and any testing of medium-band rows: tick medium-band rows only after your own check
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
In a sample of 50 proposals from the high band drawn after the rules are frozen, your named person marks at least 45 right, which shows a true rate of at least 80% with 95% confidence, and any proposal that overwrites a filled value fails the whole test.
Evidence: The marked sample and the written pass mark.
No row in the low band appears in the import file.
Evidence: The import file and the band counts.
A before and after export on a test copy differ in exactly the ticked rows and in no others.
Evidence: The difference report.
The rollback file restores the before-values on the test copy.
Evidence: The restore check.
Sign-off. You re-run the test yourself, check the list of severe errors and sign off in writing. Payment follows sign-off.
If it fails. If the agreed pass mark is not met, we say so, hand over the results and the failures, and do not call the output working. You do not pay for this scope; we agree whether to stop or re-quote.
When it fits, and when we stop
It fits when
- Values can be worked out from your own data or the company's own public pages
- An admin imports the file and tests it on a copy first
- Real records are read only after a written agreement that covers how your records are processed and a separate access step you control; until then we test on invented or redacted data.
We stop and tell you if
- You want person-level enrichment from a third party
- Another sync will overwrite the fields after import
- Nobody can tick rows
What could go wrong
The rollback file restores every before-value on a test copy. We change nothing in your live CRM.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| A wrong fill pollutes routing and reports | Only ticked rows are imported, the low band is never applied and the rollback file is tested on a copy. |
| Old values are overwritten | Rows that already hold a value are excluded and the difference report proves it. |
| Import limits slow the job | Import size is planned against the platform's published limits. |
A separate automated reviewer checks the proposals, the import file and the difference report before hand-over, and no person on our side reviews unless your agreement names one. Your named person ticks every row that is applied. At launch the work is largely automated, and we say so.
How we deliver
We arrange the work and independent review, then show you the result against the agreed checks. You keep authority over your systems.
- Agree the fields, the allowed values, the sources and the pass mark
- Receive the export by the agreed route
- Propose a value and source per blank row and assign a band
- Check a sample of the high band with your named person
- Independent automated review of the proposals, the files and the difference report
- Hand over the files; your admin tests on a copy and imports
This is a one-off job, not a subscription or emergency cover. We confirm eligibility, price, a start window and a delivery date before you accept, and work starts only after agreed inputs and access are in place. Nothing is sent, merged, posted or changed in your live systems by us, and an enquiry creates no charge or booking.
Need to keep it working?
Discuss a monthly list of blank-field proposals waiting for approval.
Ongoing work is separately scoped and quoted: no monitoring, response-time guarantee or automatic subscription is included in this job.
Explore an ongoing managed lane, or mention the responsibility you need in your enquiry.
What you can check
This is a new service. We have not delivered this job for a client yet.
Other ways to get this done
- Your CRM may offer a built-in way to fill fields one record at a time. For a small number of rows that may be enough.
Questions
Does a language model write the values?
Rules read your own fields first. A model may help only with free text on the company's own site, and each value shows its source.
Will you change my live CRM?
No. We send files, and your admin imports the rows you ticked.
What if a value is wrong after import?
The rollback file restores the old values you exported.
How is this different from adding company details to new leads?
This job proposes values for blanks already in your records, for you to tick. The new-leads job fills each new lead as it arrives and writes a source on every value.
Send an enquiry
Send us
- The object, the field names and what a correct value looks like
- Roughly how many rows are blank
- Whether any sync writes to those fields
Later, once you agree
- A read-only export with agreed columns
- A sandbox or test copy for the import check
- A secure handoff route agreed before any record is shared
You keep the CRM. We read an agreed export and return files; your admin imports them. Which service reads your records is agreed in writing before any real record is shared; the entry test uses invented or redacted data, or your own provider account.
Email fallback: open your mail app
If website submission is unavailable, review and send the fallback email yourself. An email fallback is not a website receipt. Or write to hello@syntheticindustry.ai with “crm-missing-fields-proposed-from-your-own-records” as the subject.