Microsoft Teams Rooms and Phone Journey at Toyota Financial Services

JT Elliott, Unified Communications and Collaboration Manager at Toyota Financial Services, describes a career that began with courtroom AV and 15 years at 7-Eleven before landing in a Microsoft-centric collaboration role. He walks through refreshing over 300 Microsoft Teams Rooms on Logitech hardwar

Microsoft Teams Rooms and Phone Journey at Toyota Financial Services

Prefer audio?

Who should listen: Microsoft 365 service owners, UC managers and AV professionals planning large-scale Teams Rooms refreshes, weighing Android versus Windows MTR, or migrating Teams Phone from Direct Routing to Operator Connect.

Guest: JT Elliott — Unified Communications and Collaboration Manager, Toyota Financial Services

JT Elliott, Unified Communications and Collaboration Manager at Toyota Financial Services, describes a career that began with courtroom AV and 15 years at 7-Eleven before landing in a Microsoft-centric collaboration role. He walks through refreshing over 300 Microsoft Teams Rooms on Logitech hardware, deploying 125 Rally Board 65s in six weeks with AVI-SPL, and moving Teams Phone from Direct Routing to Operator Connect.

Many thanks to Logitech, sponsor of this episode.

Key insights

  • Toyota Financial Services supports just under 9,000 users with roughly 300 rooms at HQ, another 125 across regional offices and a further 150 being added over the coming months as the business returns to office and expands into new buildings. ▶ 4:40
  • Toyota went global-standard on Teams for meetings in 2020, but the HQ campus had opened in 2017 with expensive cameras, mic systems and AV switchers mid-lifecycle — the retrofit period of converters and part-certified kit was an operational headache, masked only because most staff were still hybrid. ▶ 9:49
  • User research showed people were phoning AV support just to start a call — the same behaviour seen years earlier with 'star phone' conference units — which set reliability and a native, familiar interface as the primary design requirement rather than any specific feature. ▶ 11:21
  • Subjective feedback on soundbar tone, mic pickup and camera framing split evenly between users and never produced a clear winner, so the team stopped treating it as a differentiator and made the decision on standardisation, room-size coverage and fleet observability instead — landing on Logitech Rally Bars with mic pod extensions plus Tap. ▶ 13:28
  • Android was chosen over Windows for MTR, partly because Logitech devices also support USB mode so a single room could be converted with an added Windows compute if a feature gap ever forced it; two years on they have not flipped a single room and say they have missed nothing beyond early speaker recognition. ▶ 15:34
  • Surface Hub v1 rooms were replaced by wall-mounted Rally Board 65s used primarily as meeting devices — whiteboarding turned out to be used by only a very small percentage of staff — with 125 units decommissioned and deployed in six weeks, three rooms a day, pace limited only by how many rooms the business could spare. ▶ 20:13
  • Systems were specified so the operations team could hot-swap a bar within an hour without reprogramming or elevated skill sets; every in-room device is monitored, failures beyond a set number of minutes trigger alerts to both an inbox and a Teams channel, and firmware is managed globally through Teams Pro Management Portal and Logitech Sync side by side. ▶ 24:49
  • The move from Direct Routing to Operator Connect was triggered by ageing SBCs reaching end of life plus an exit from the hosting data centre; with no complex routing requirements, Operator Connect met the need, and a phased POC-then-small-group porting approach saw carriers switched with no user noticing. Next on the list is automated phone number provisioning by role or department. ▶ 28:23

Insights summarised by AI from the episode transcript, reviewed by the Empowering.Cloud team.

Listen: Apple Podcasts · Spotify · Other platforms