Objective

Create a plain-English runbook for the incoming IT/developer company so they can maintain and enhance the Litify direct-SMS integration without relying on chat history.

What Was Created

• Repo runbook: docs/ringcentral-litify-sms-runbook-2026-06-04.md.
• Docs index update: docs/README.md now links to the runbook.
• Git commit: 24b52f9 Add RingCentral Litify SMS runbook.
• Branch: codex/ringcentral-sms-broker-2026-06-03.

What The Runbook Covers

• Executive explanation of Litify, Salesforce, Render, and RingCentral roles.
• Current live configuration for LITIFY_ORG, RingCentral_SMS, Render service sail-ringcentral-sms-broker, RingCentral sender number, and daily monitor.
• Key source files for Apex, LWC, broker service, tests, monitor, and permission set.
• Credential and secret locations, including why secrets should live in controlled credential/config surfaces rather than Apex source code.
• End-to-end send flow from staff click to SAIL_SMS_Message__c log row.
• Proven live test evidence from 2026-06-04.
• No-send health monitor behavior and expected checks.
• Common failure modes: broker outage, Basic auth mismatch, invalid RingCentral from number, and Litify logging failure.
• Useful commands for Salesforce and broker health checks.
• Broker deploy, Salesforce deploy, credential rotation, rollback, and IT pickup steps.

Live Validation Used

• sf org list --all confirmed LITIFY_ORG connected as sam@kylawoffice.com.