Objective

Measure and improve RingCentral-in-Teams adoption so staff can use the Teams placement instead of relying on non-clickable or context-poor notifications.

What changed

• Audited the initial state and confirmed 0 enabled member users and 0 teams had the RingCentral Teams app installed.
• Ran the user install pass for licensed accounts.
• Installed RingCentral for 49 licensed users with 0 install failures.
• Skipped two unlicensed users: HR@kylawoffice.com and Hatfield.global@kylawoffice.com.
• Captured the install outputs and counts in local CSV/JSON logs.

Commands or live systems touched

• Microsoft Teams / Graph app catalog with RingCentral Teams app catalog id 2f285d77-896a-4c5f-901e-0902316003b5.
• Local evidence folder: /Users/samaguiar/Documents/Projects/admin/session_logs/ringcentral-teams-adoption-2026-05-27/.
• Source summaries: summary.json and install-summary.json in that folder.

Rollback state

• Roll back by removing the RingCentral Teams app assignment from the affected users if adoption needs to be reversed.
• No rollback command file was captured in the session log.

Open follow-up

• Team-level installs were still 0 at the audit point.
• User testing still needs to confirm the Teams placement actually improves adoption and notification usability.

Pickup prompt

Verify the RingCentral Teams app is visible for a few installed pilot users, then decide whether to add team-level rollout or keep the rollout user-scoped only.