The setting
Asking a family member at a distance to install an app is a bigger barrier than it sounds. The moment an install is required, most of these calls simply never start.
Removing that barrier is the whole of this scenario. On the receiving side, opening a link is the entire job.
What gets assembled
The browser connects to the voice engine over WebRTC. Neither an install nor an account is a precondition for starting the call.
When the mobile app is used instead, the stack it reaches is identical — the iOS and Android apps are covered on web and mobile apps.
Transcription accumulates during the call, and a record survives it.
Where it stands
Running today
Browser WebRTC calling and the mobile call path both run today.
Still in development
Some of the family-facing surfaces are UI-complete with backend integration in progress.
Scoped during the deployment
How the link is delivered, and who can see a call record afterwards, is scoped with you deployment by deployment.
A WebRTC call starts in the browser with nothing to install, and when the mobile app is used instead the voice engine it reaches is the same one.
This page is not a customer story. No organization is named or implied, and nothing here carries a customer quote or an outcome figure.
No install
to start from the browser
Web + mobile
on one shared stack
Work out whether this shape fits
Contact sales