Import customer visits without a direct integration

CSV and XLSX provide a fallback when your booking or POS system is not directly connected. Export visit history, map the source columns to RetentionTek fields, validate the file, and explicitly confirm the active dataset.

Which fields are required?

Customer ID, customer name, first-visit proof, appointment ID, visit date, attendance status, location ID and service category. Download the template in the workspace. Map renamed columns explicitly. Supported service categories are intro, core and personal; do not guess a category if your data cannot support it.

What file limits apply?

Files must be CSV or XLSX, at most 2 MiB, with up to 5,000 data rows and 80 source columns. XLSX must contain exactly one worksheet. Paste values only: formulas and rich cells are rejected. Dates use YYYY-MM-DD in the business reporting calendar.

What happens after validation?

Validation checks required values, dates, IDs, duplicate appointments and reporting coverage. Review the counts before confirming. Only then does the dataset become active and persist in your workspace. Re-importing identical normalized data does not create a duplicate dataset.

What remains unavailable?

Uploading a file does not connect your provider, verify contact consent or authorize external messages. The current import calculates visit-based retention, not LTV or revenue. Delete an import from its history to remove its stored dataset and related internal review tasks.