Thanks for following up. Here are the answers:

Which feed: the nightly DriveCentric CRM export you deliver to our SFTP server. It's one CSV per entity per store, for example 1643_v2_textmessage_<dates>_<timestamp>.csv. The files we need content in are:

Today these rows come through with timestamps, direction and who handled them, but not the message or note text.

Who consumes it: our own internal reporting dashboard. Our team loads the files into our database each night. The data stays internal and is access-controlled by store and role.

Scope: everything tied to each deal or lead, delivered the same way as now, as the daily incremental files. This is for leads we're currently working, so a short one-time backfill is enough: activity from April 1, 2026 forward. We don't need anything outside of deals and leads.

Main goal: analytics and manager review. We match lost leads against Ford's defection data, meaning customers who bought from another dealer. Managers need to see what was actually said in the texts, emails and calls, so they can review follow-up quality and coach the team. The timestamps tell us that contact happened, but not what was said.

Thanks for posting this, Patrick McLemore — totally hear you on wanting the SFTP feed to include the actual note/email content, not just timestamps. To make sure we’re looking at the right export and scoping it correctly: which SFTP feed are you referring to (leads/customers/activities, etc.), and what system or team on your side is consuming it? Also, when you say “full customer notes” and “email conversations,” are you looking for the complete history for each customer, or only notes/emails tied to specific objects/events (like a lead/deal) or within a date range? Lastly, what’s the main goal for having the full content in the feed (compliance archiving, analytics/reporting, syncing into another CRM, support visibility, etc.)?