Consistent Conversation Identification Between Historical Exports and New Reporting
Expected Outcome / Requested Evolution
Provide a solution that enables reliable conversation matching between historical exports and the new reporting, for example by:
exposing a stable and persistent conversation/thread identifier shared across legacy exports and the new reporting module, or
providing a mapping mechanism between historical contentthreadid values and the new conversation identifiers (UID / UUID), or
adding a field in the new reporting that explicitly references the historical conversation identifier.
Business Impact
Without this evolution:
historical vs. current conversation analyses cannot be reconciled,
longitudinal KPIs and trend analysis are not reliable,
manual and error-prone reconciliation is required.
1
vote
Henry
shared this idea