Importance: Medium. Status: Complete, done. No follow-up sync required. One verification question is open (see Recommended next actions).
Weekly backup sync: RingSense call Tasks to Litify Notes. It exists to catch any calls the primary automation (Nathaniel's flow) failed to turn into a Litify Note. Scheduled for Sundays 9 AM ET; this run executed Friday May 22, off-cadence, likely a manual or drifted trigger.
Records synced this run: 0. Confirmed missed calls: 0. No writes were made to the live org, which is the correct outcome here.
Dedup key (confirmed live). Nathaniel's flow links each Note to its source call by session ID:
CallObject = RS~<sessionId>~<callId>External_Id__c = rc_call_<sessionId>litify_pm__lit_Note__c: body field litify_pm__lit_Note__c (textarea), title Name ([RingSense] Inbound/Outbound call with ...), topic litify_pm__lit_Topic__c = Call, links via litify_pm__lit_Matter__c or litify_pm__lit_Intake__c.8-day volume (May 14 to 22): 1288 RingSense Tasks, 718 linked Notes. Raw unmatched = 570.
Day-by-day, the decisive test:
| Day | Tasks | Notes | Match |
|---|---|---|---|
| 05-14 | 217 | 126 | 58% |
| 05-15 | 161 | 87 | 54% |
| 05-16 | 3 | 3 | 100% |
| 05-17 | 1 | 1 | 100% |
| 05-18 | 217 | 124 | 57% |
| 05-19 | 224 | 114 | 51% |
| 05-20 | 201 | 106 | 53% |
| 05-21 | 186 | 114 | 61% |
| 05-22 | 78 | 43 | 55% |
The match ratio holds at 51 to 61 percent every single day with no cliff. An outage or systematic miss shows up as a day where Notes crash toward zero while Tasks stay high. That never happens. The weekend (05-16, 05-17) had near-zero call volume and matched 100 percent. The flow created Notes as recently as 15:58 today, so it is live and current.
The 570 are not missed syncs. Nathaniel's flow only creates a Note when a call resolves to a Matter or Intake. Of 1288 Tasks, 1192 (92.5 percent) carry a Contact, but only 718 became Notes, so the flow's real filter is whether the Contact resolves to an active Matter or Intake. Calls from insurance adjusters, vendors, opposing parties, wrong numbers, and closed-matter contacts are excluded by design. A steady ~55 percent resolution rate across 8 days is consistent with that.
Writes were held deliberately. Creating a faithful backup Note requires replicating the flow's Contact-to-Matter/Intake resolution, which lives in the sail-litify repo and was not reachable from this environment. Blind-creating Notes for unmatched Tasks would have produced misfiled or wrong-Matter notes in a live legal system. With no outage detected, there was nothing to safely create. This stays within the 85 percent confidence rule.