Book a Demo

Bring the failed spreadsheet import, not just the clean example

Format: Company perspective.

A clean spreadsheet can hide the problem you need the software to solve. Bring the failed import too, with private details removed and the failure still intact.

For a hypothetical account list, prepare three small copies of the same sample:

  • Leave one required account ID blank. Ask whether the tool holds the row and says why. It should not guess which account the row belongs to.
  • Change the header from “Account ID” to “Account reference.” Ask whether the import stops or uses an approved rule that links the new column name to the right field.
  • Mix a date written as “April 5, 2026” with “04/05/2026.” Ask who decides whether the second date means April 5 or May 4. The tool should not guess without telling you.

Keep a clean copy beside the failed ones. Write what should happen to each row before the demo. Then check what the tool does against that note. Do not rely on the presenter's explanation after the test.

RFC 4180 describes quoting CSV fields that contain commas, quotes or line breaks.[2] That file rule does not settle business meanings such as your date convention or account identity.

Use this card: sample name; what is wrong; private fields removed; expected hold or import; person who may fix it. Replace each real name and ID with the same made-up value wherever it appears. This keeps links between rows intact. Do not send passwords, tokens or unapproved customer files.

Ask to see the rejected-row report and the accepted result separately. “Import finished” should not conceal skipped records.

Core Agentic scopes custom software around the work your team actually faces. Book a Demo and bring a permitted failed sample, not just the version somebody cleaned up afterward.

Sources

These sources describe the named provider or framework. They do not establish a Core Agentic integration, customer result or certification.