Data ImportAI-Powered

Klau Command

Klau Command is your AI-powered data import assistant. Upload CSV files, and Klau intelligently maps columns, detects conflicts, resolves cross-entity references, and loads your operational data — all through a conversational interface.

How It Works: Upload → Preview → Resolve → Load

Klau Command turns messy spreadsheets into clean operational data in four steps. Here is what makes it different from a typical CSV importer:

Conversational Import — Drag and drop a CSV into the chat. Klau identifies the entity type, maps columns, and walks you through the import.

Smart Column Mapping — Klau understands that “Phone #” means phone number and “Sched Date” means requested date. No rigid column naming required.

Conflict Detection — If a driver named “John Smith” already exists, Klau asks what you want to do — update the existing record, keep it unchanged, or skip the import row.

Cross-Entity References — Jobs reference customers, sites reference customers, trucks reference yards. Klau validates these links before importing.

Step by Step

The Import Flow

1

Upload Your CSV

Drag a CSV file into the Klau Command chat or use the upload button. Klau detects the entity type from the filename and column headers.

2

Preview

Klau shows how many records were found, which columns were mapped, and a sample of the first few rows. Review the mapping before proceeding.

3

Resolve Issues

If there are conflicts (duplicates, missing references, invalid data), Klau presents each issue with clear options: Update existing, Keep existing, or Skip.

4

Import

Confirmed records are created in your account. Klau shows a summary: X created, Y updated, Z skipped.

Import Multiple Entity Types in Sequence

You can import multiple entity types in sequence. Start with yards and dump sites, then drivers and trucks, then customers and sites, then jobs. Each import can reference entities from previous imports.

9 Entity Types

Supported Entity Types

Klau Command supports all 9 operational entity types. Import them in the recommended order so that cross-entity references resolve automatically.

1

Yard

2

Dump Sites

3

Materials

4

Drivers

5

Trucks

6

Customers

7

Sites

8

Jobs

9

Assets

Yard

Name, address, city, state, ZIP, default yard flag, service radius.

Dump Sites

Name, address, open/close times, average wait time, accepted container sizes.

Materials

Name, code, display name, economic direction, default price, description.

Drivers

Name, phone, email, driver type (Full-Time or Flex).

Trucks

Number, license plate, VIN, compatible container sizes, home yard.

Customers

Name, contact name, contact phone, contact email, billing address, notes.

Sites

Customer name (required reference), site name, full address, on-site contact, access notes.

Jobs

Customer name (required), site name, job type (Delivery/Pickup/Dump Return/Swap), container size, requested date, time window, priority, notes.

Assets

Serial number, display name, asset type, container size, home yard (required), condition, maintenance interval.

Data Protection

Conflict Resolution

When Klau encounters data that overlaps with existing records, it flags the conflict and asks you how to proceed. Here is what triggers a conflict and how to resolve it.

What Triggers a Conflict

Duplicate

A record with the same name or number already exists. For example, a driver named “John Smith” or a truck with the same number.

Missing Reference

A site references a customer that does not exist yet, or a job references a site that has not been imported.

Invalid Format

A date, price, or phone number could not be parsed. Klau shows the original value and explains what it expected.

Missing Required Field

A required field (like name) is blank. Klau identifies the row and tells you which field is missing.

Resolution Options

Update Existing

Merge the imported data into the existing record, updating only the fields provided in the CSV.

Keep Existing

Leave the existing record unchanged and discard the import row.

Skip

Do not import this record at all. Useful when you are unsure and want to handle it manually later.

Conflicts Are Normal

Conflicts mean Klau is protecting your data. A duplicate flag on 3 out of 50 drivers just means those 3 already exist. Resolve them and the other 47 import cleanly.

Dependencies

Import Order Matters

Entities reference each other. Sites belong to customers. Jobs belong to customers and sites. Trucks and assets belong to yards. Importing in the right order means Klau can automatically resolve these references without manual intervention.

1

Yard

2

Dump Sites

3

Materials

4

Drivers

5

Trucks

6

Customers

7

Sites

8

Jobs

9

Assets

Sites need their Customer to exist first. Jobs need their Customer and Site. Trucks and Assets need their Yard. Import in this order and references resolve automatically.

If you import out of order, Klau flags the missing references and tells you what to import first. You will not lose data — just import the missing dependency and re-run.

Best Practices

Tips for Clean Imports

Follow these guidelines to get the smoothest import experience and the fewest conflicts.

  • One entity type per CSV

    Do not mix drivers and customers in the same file. Each CSV should contain a single entity type.

  • Headers matter

    Include column headers in the first row. Klau uses them for mapping.

  • Consistent naming

    Use the same customer name in your Sites CSV as in your Customers CSV. “Acme Inc” and “ACME Inc.” will match, but “Acme” and “Acme Corporation” may not.

  • Dates are flexible

    Klau parses common formats — MM/DD/YYYY, YYYY-MM-DD, “Jan 15, 2026” all work.

  • Prices are flexible

    “$25.50”, “2550”, and “25.50” are all understood. Klau normalizes to cents internally.

What's Next?

You now know how to use Klau Command to import your operational data. Here are some recommended next steps to continue setting up your operation.

Import Support

Need Help With Your Import?

If your CSV has unusual formatting or you are importing thousands of records, our team can help. We have imported data from Routeware, custom ERPs, and spreadsheets of every shape.