Outcome
The approach is proven. Calls, call controls and video all work from a web page on Teams Phone.
The problem
The customer’s staff work all day in their own web application, but their phone calls lived somewhere else. The customer wanted calling inside their app: click to call, answer incoming calls, hold and transfer, step up to video. It had to run on Teams Phone, so numbers, call queues and compliance recording stay in one place.
What I did
- Built a working browser phone that signs in as the user’s own Teams account and makes and takes calls on their Teams number.
- Tested every control staff would use: inbound and outbound calls, mute, hold, transfer to phones and Teams users, keypad tones into an auto attendant, 1:1 video and joining Teams meetings with guests.
- Tested a requirement the documentation appeared to rule out before designing around it, and avoided an unnecessary workaround.
- Built a demo softphone that sits over any web page, keeps the call going while you move around, and can float above other apps.
- Packaged it as reusable code with setup, deployment notes and a list of developer gotchas for the customer’s own developers.
Result
The customer’s developers have a proven pattern and working reference code to build calling into their app, on Teams Phone rather than a second phone system. The remaining checks are answering from a call queue, long sessions, and end-to-end recording of browser calls.