Session objective

Evaluate whether birthday text messages to clients can be set up nicely through Litify and RingCentral, using live state rather than guessing.

Work completed

• Loaded Litify and Salesforce workup instructions.
• Checked existing memory and Notion handoffs for the June 3 RingCentral direct-send work.
• Verified LITIFY_ORG is connected as sam@kylawoffice.com.
• Verified live RingCentral SMS broker health with npm run health; result was ok: true and no SMS was sent.
• Confirmed Salesforce Named Credential RingCentral_SMS points to https://sail-ringcentral-sms-broker.onrender.com with principal type NamedUser.
• Confirmed Apex classes LitifyRingCentralSmsSender, LitifyRingCentralContextController, AttorneyHubNickController, and AttorneyHubPaytonClientServiceController are active.
• Confirmed relevant Account fields exist: litify_pm__Date_of_birth__c, Next_Birthday__c, litify_pm__Phone_Mobile__c, Receive_Birthday_Emails__c, and SMS_STOP__c.
• Confirmed Matter has client lookup, status, phone, and formula SMS_STOP__c sourced from the client account.
• Confirmed Attorney Hub birthday prompts already exist for Nick and Payton, using a window of today minus 2 days through today plus 5 days.
• Confirmed current birthday prompt links open the Matter record for RingCentral context; they do not yet prefill or direct-send a birthday template.

Live count snapshot

As of June 4, 2026:

• Birthday today among open matters: 0 matters, 0 distinct clients.
• Birthdays in the next 7 days among open matters: 18 matters, 17 distinct clients.
• Next 7 days with mobile present and SMS_STOP__c = false: 17 matters, 16 distinct clients.
• Next 7 days with SMS_STOP__c = true: 0 matters, 0 distinct clients.

Recommended architecture