Summary: Allow macros to set Date & Time conversation data attributes (CvDAs), with the ability to insert the current date/time at the moment the macro is applied.
Current behavior: When adding a "Set conversation data attribute" action to a macro, Date & Time attributes appear in red and cannot be saved. This is a known product limitation that also affects workflow steps.
Desired behavior: Macros should support setting Date & Time attributes, with at minimum one dynamic value option: "Current date/time" — automatically populated with the timestamp at the moment the macro is run by a teammate.
Use case: We use a "QA Resolved" macro to mark conversations as resolved via the ai_event_resolution_status attribute. We also want to automatically record when that resolution occurred using an ai_event_resolution_date attribute, without requiring teammates to manually enter a date or rely on an external API/webhook setup.
This pattern — stamping a date when a specific status is set — is a common support operations need for QA tracking, SLA measurement, and reporting.
Why this matters :Without this capability, teams must either:
- Build and maintain an external API/Data Connector integration just to capture a timestamp, or
- Forgo date-based reporting on key operational events entirely
Native support for "current date/time" as a macro action value would unlock meaningful reporting with no additional infrastructure.
Workaround currently in use: None — the attribute type is blocked at the macro editor level. We manually set the date.