Live status refresh

• Active Flow: RingCentral_Process_RingSense_Calls version 52, id 301UV00000m3OdHYAU.
• Flow version count: 50, meaning future Flow edits will hit the cap unless obsolete versions are cleaned first.
• Latest 10 post-fix RingSense Notes: all have Summary, Call Details, Transcript, no raw delimiter leakage, and 0 Staff Unknown.
• Newest sampled note: a0xUV000004evRuYAI, created 2026-05-14T13:17:56Z, Staff Timmera House.
• Last 7 days RingSense Tasks: 967.
• Last 7 days RingSense Tasks with no WhatId: 192.
• Last 7 days RingSense Litify Notes with rc_call_% external ids: 527.
• Last 7 days structured SMS rows: 337.
• Last 7 days SMS Litify Notes with rc_msg_% external ids: 337.

What remains pending

1. No pending fix for the formatter or Staff row. This is live and QA-clean.
2. Flow version hygiene remains pending because the Flow is back at 50 versions.
3. Unlinked RingSense task cleanup remains pending. 192 unlinked tasks in the last 7 days is enough to justify a focused linking/matching audit.
4. RingSense Action Queue v1 remains recommended. Use summaries and transcripts to create reviewable follow-up suggestions, not automatic case-changing actions.
5. Communications QA dashboard remains recommended. It should track RingSense, RingCentral task linking, Notes, structured SMS, CallRail/Dialpad if relevant, and exception queues.
6. Historical backfill/reformat is optional. It is lower priority than making current and future records clean unless staff specifically needs older notes converted.

Recommendation order

Recommended sequence: Flow version hygiene, unlinked RingSense task audit, RingSense Action Queue v1, communications QA dashboard, then optional historical reformat/backfill.