Bring an Excel repair list into a safer customer-update workflow.

Use one header row and one repair per row

Put field names in the first row and keep the repair records directly below them. Remove merged cells, subtotals, decorative headings and blank separator rows from the data range. Each reference must identify one job consistently; changing it later can make the same work look like a different record.

BenchPing needs a reference, customer name, customer email and item to create a useful record. Other columns can carry the phone number, notification preference, SMS consent, status, customer-facing note, internal note, estimate and expected completion.

• Reference: a stable job or ticket ID.
• Customer name and email: checked for the correct person.
• Item: the bike, device, instrument or other product being serviced.
• Status and customer note: plain-language progress the customer may see.
• Internal note: private operational context, not customer communication.
• Estimated completion: include date, time and UTC offset when time matters.

Clean the data before uploading it

Check email addresses and normalize phone numbers before import. Use a small, controlled list of status values instead of spelling the same stage several ways. Separate the customer-facing update from internal comments so staff-only information does not appear on a tracking page.

Do not place passwords, device unlock codes, payment-card data or other unnecessary sensitive information in the workbook. An import tool cannot make an unsafe source file safe.

Example, not a customer result

Example row: BP-2041 | Jamie Lee | jamie@example.com | Trek FX 3 | Diagnosing | We are checking the brake system | Priority customer | 2026-09-18T15:30:00-06:00

Map and preview before committing the import

Upload the CSV or XLSX file, select the worksheet when needed and map each spreadsheet column to the matching BenchPing field. A preview confirms how the rows were read; it is not proof that every contact detail or business rule is correct.

Start with a small file using contact details you control. Confirm row counts, dates, estimates, status names and the distinction between public and internal notes. Only then import the operational list.

• Keep an untouched backup of the original workbook.
• Test dates that Excel may have reformatted.
• Confirm the currency used for estimate amounts.
• Spot-check the first, middle and last imported records.

Know when imported records notify customers

A confirmed initial file import creates the records without sending a separate item-added email for every imported row. This prevents a historical workbook from unexpectedly producing a burst of customer messages. A repair added manually can follow the shop's normal notification workflow.

A CSV or XLSX upload is a one-time import, not a live connection to the local file. For ongoing synchronization, BenchPing can read an eligible public Google Sheet on the configured schedule. When a genuinely new row appears during a later synchronization, it can be treated as a new repair and notify according to the configured customer channels.

Verify the queue before relying on automation

Compare the imported count with the source, open several repairs and check the customer tracking view using records you control. Completed or removed work should not appear as active merely because it existed in the workbook.

Finally, make one deliberate manual status change and inspect the tracking page and delivery history. This verifies the complete path without notifying an entire imported customer list.

• Confirm the active queue count.
• Check customer-visible and internal notes separately.
• Verify estimate, currency and expected completion.
• Test one email or SMS destination you control.
• Keep the source workbook until the result is reconciled.