Base Importer (CSV)

The Base Importer feature allows you to upload CSV files directly through the SoluCX platform to trigger satisfaction surveys in bulk. The entire process is self-service — you have full autonomy to configure, validate, and submit your data files without relying on intermediaries.

How It Works

The import flow follows four simple steps:

  1. Upload — Submit the CSV file through the platform
  2. Validation — The system automatically checks the file structure and data
  3. Adjustments — Review and fix any inconsistencies flagged during validation
  4. Dispatch — Confirm the submission and surveys will be triggered automatically

Preparing the CSV File

The file must be in CSV format (values separated by semicolon ;) with UTF-8 encoding. Each row represents a transaction (a customer interaction with your company) that may trigger a survey.

In general, the CSV needs to contain information about:

  • Transaction — Unique identifier and date of the experience
  • Unit — Identification of the business unit (store, clinic, agency, branch) where the experience occurred
  • Employee — Identification of the professional linked to the service (when applicable)
  • Customer — Name, identifier, and contact channel (email, phone) of the customer
  • Journey — Journey slug configured in the platform, which directs to the correct survey model
  • Extra columns — Custom fields (e.g., param_orderNumber, param_serviceChannel) available in the data extract and can appear in email templates

Step by Step: Importing a Data File

1. Access the Base Importer

In the SoluCX platform, navigate to the Base Importer section in the side menu.

2. Upload the File

Drag the CSV file or click to select the file from your computer. The system accepts files in .csv format.

3. Wait for Validation

After upload, the system will automatically check:

  • Whether the file structure is correct
  • Whether required fields are filled in
  • Whether data formats are valid (email, phone, dates)
  • Whether there are duplicate records

4. Review and Adjust (Base Cleanup)

If validation flags inconsistencies, the system will display alerts per record. For each alert, you can choose one of three cleanup actions:

  • Ignore Row — Keeps the row exactly as it is, ignoring the alert. The row will be dispatched normally.
  • Remove Row — Removes the entire row from the base. This row will not be dispatched.
  • Remove Information — Keeps the row in the base, but removes only the field that triggered the alert. The row will be dispatched without that information.

5. Confirm Dispatch

After successful validation, confirm the submission. Surveys will be scheduled according to the journey rules configured (immediately, after X days, etc.).


Best Practices

  • Check the platform before preparing your file — The Base Importer screen is the most up-to-date reference for fields, formats, and requirements.
  • Verify data before uploading — Ensure emails and phone numbers are in the correct format to avoid validation errors.
  • Use unique identifiers — Transaction identifiers prevent the same experience from generating duplicate surveys.
  • Maintain consistency — Use the same unit and employee identifiers across all files to ensure consistent reporting.
  • Leverage custom fields — The more data you send in extra columns, the richer your analysis in the platform will be.
  • UTF-8 encoding — Save the file with UTF-8 encoding to avoid issues with special characters and accents.

Frequently Asked Questions

Can I import files on a daily basis? Yes! You can import files as often as needed. For recurring and automated submissions, consider the SFTP or Bucket integration options.

What happens if a record has an error? The system identifies records with issues and offers three cleanup options: Ignore Row (keep and dispatch as is), Remove Row (do not dispatch) or Remove Information (dispatch without the problematic field). See the "Review and Adjust" section above for details.