Recommendation

The next move should be A first, but expanded into a trust gate, not just a visual QA pass. Staff confidence depends on the panel proving that every communication shown or started from a Matter is related to that Matter and will be logged. After that gate passes, build C and B together as a Matter communications command surface.

Recommended Sequence

1. Matter Communications Trust Gate: verify normal-user access, multi-phone Matters, related contact roles, persistent RingCentral login behavior, call placement, SMS compose, inbound SMS visibility, voicemail visibility, call log creation, RingSense summary logging, transcript availability, and Matter note linkage.
2. Matter-scoped Timeline and Notifications: make the default view a useful Matter communication history with SMS chat bubbles, call summaries, voicemail items, dates, times, direction, sender/recipient, and conspicuous unread badges.
3. Actionable Contact Cards: show the client and other matter-linked people, such as insurance adjusters, as compact cards with Call and SMS actions. Clicking a number should not make the user think about the phone system, it should launch the correct RingCentral action and preserve logging.
4. RingCentral Global Activity Boundary: use the floating RingCentral button for non-Matter RingCentral activity. The Matter tab should stay Matter-specific.

Why This Order

If we make the phone number clickable before proving logging and Matter matching, the UI may look easy but still feel risky. If we add notifications before proving the inbound source and unread state, staff may mistrust the badge. The better path is to prove the data/logging truth first, then make the actions and notifications obvious.

Design Direction

The Matter tab should feel like a communication cockpit for that Matter. The top shows the active contact context. The default view shows recent Matter communications and summaries. Call, SMS, History, and Templates become task modes. Templates should live under SMS, not as a free-floating unrelated button. Related people should be selectable from the same area so staff can call or text the client, adjuster, or other linked people without hunting through the page.

Handoff

Continue from the deployed contact-header cleanup. Preserve SMS Magic history and rollback safety. Do not delete SMS Magic records, uninstall the package, or disable automation. Treat RingCentral as the live action surface and Litify Notes/history as the durable record trail. The next agent should start with read-only live validation where possible, then implement the Matter-scoped communication surface only after the trust gate confirms the fields, objects, and logging behavior.