A customer browsing a marketplace app finds a product they want but needs a quick answer.
The old way: copy the seller’s phone number, switch to the dialer, wait through voicemail, and hope for a callback.
The new way: tap a call button inside the app. Both parties connect instantly, the listing stays on screen, and the conversation resolves in under two minutes. For the product team that built that marketplace, in-app calling is the difference between a support model that keeps context and one that loses it the moment the call connects.
That contrast explains why in-app calling is growing fast. The global WebRTC market behind this technology reached US$9.56 billion in 2025 and is projected to hit US$122 billion by 2034. Businesses across ride-hailing, healthcare, e-commerce, and financial services are embedding voice directly into their platforms – because keeping the customer inside the app means keeping the context alive.
The Problem with App-to-Phone Handoffs
Every time a customer leaves an app to make a phone call, the experience breaks. They lose sight of the screen showing their order, account, or booking details.
Then they dial a support number, sit through an IVR menu, and explain their issue from scratch. The agent has no idea what the customer was looking at seconds earlier.
This handoff costs time for both sides – and increases abandonment. Customers who face friction during support interactions are more likely to give up and less likely to return.
In-app calling eliminates this loop entirely. The voice connection happens inside the same interface, so agents can see the customer’s session data alongside the conversation.
How In-App Calling Works
In-app calling relies on WebRTC, a protocol that enables real-time voice and video communication directly through web browsers and mobile apps. No plugins or separate downloads are required.
Businesses add voice through SDKs from CPaaS providers – the SDK sets up the connection, secures it, and keeps call quality steady in the background, so your team ships a call button, not a telephony stack.
From the developer’s perspective, adding a call button to an app takes days rather than months. From the customer’s perspective, voice support feels native to the platform.
70% of companies already use WebRTC for real-time communication, and 52% integrate it specifically for customer support. Cloud-based deployments account for 73% of the market, making voice SDKs accessible without on-premises infrastructure.
Read more: App-to-App Calling in Last-Mile Delivery
In-App Calling for E-Commerce and Marketplaces

Online marketplaces need buyers and sellers to communicate quickly. Product questions, delivery timing, and customization requests all benefit from a live voice conversation.
In-app calling lets buyers tap a button on a product listing to reach the seller directly. Both parties see the listing during the call, removing the need to describe items verbally.
The payoff is concrete. A quick call clears up sizing, delivery, or a customization request before it becomes a cancelled order or dispute. That means fewer abandoned carts, fewer “where is my item” tickets, and sellers who spend less time chasing clarification.
Privacy matters here, too. Marketplace platforms can pair in-app calling with number masking so neither buyer nor seller ever sees the other’s personal phone number – the platform retains control of the interaction.
In-App Calling for Healthcare and Telehealth
Telehealth has moved from novelty to norm. As of 2024, 87% of U.S. hospitals let patients connect with care teams virtually.
In-app calling gives healthcare providers a way to conduct consultations directly within their patient portal. The doctor sees the patient’s medical history, appointment notes, and lab results on the same screen – reducing consultation time and improving diagnostic accuracy.
Patients don’t need to download a separate video app or share a meeting link. They tap a button inside the platform they already trust.
For healthcare buyers, compliance is the first question. 8×8 supports HIPAA-compliant communication across its platform, with call recording and the controls regulated teams need.
In-App Calling for Financial Services
Banks and fintechs run on trust, and voice is where trust gets tested.
In-app calling lets a customer reach their bank from inside the app they already logged into, with the account and transaction in view. That fits account verification, lending and mortgage conversations, wealth advisory, and fraud-alert callbacks.
It also closes a security gap. A masked, in-app call can’t be spoofed the way a “your bank is calling” scam can, because the customer starts it inside the authenticated app.
In-App Calling for Ride-Hailing and Logistics

Ride-hailing and delivery apps face a specific challenge: connecting two strangers for a short interaction without sharing personal phone numbers.
In-app calling solves it cleanly, and it’s already the norm across Southeast Asia. Super-apps like Grab and Gojek connect riders and drivers through a masked in-app call, so neither party ever sees the other’s real number.
Logistics companies use the same approach for last-mile delivery. When a courier can’t find the drop-off location, they call the recipient through the app. The conversation is recorded for dispute resolution, and neither party’s number is exposed.
Read More: The Communication Gap Costing Last-Mile Logistics Millions
What to Look for in a Voice SDK
Not all voice SDKs are built the same. Judge them by the problems they solve, not the length of the feature list.
- Keep context in the app: The SDK should run natively on iOS, Android, and web, so customers never leave the screen they are on.
- Protect personal numbers: Built-in number masking should come standard, not as a custom build, for marketplaces and ride-hailing.
- Hold call quality on any network: Adaptive bitrate, noise suppression, and echo cancellation should keep audio clear across WiFi, 4G, and 5G.
- Stay secure and compliant: Look for encryption in transit, call recording, and the controls healthcare and financial teams need.
- Reach any phone when needed: PSTN bridging should connect in-app calls to landlines and mobiles, so no one is left unreachable.
- Prove the value: Real-time analytics on call quality, duration, and resolution should show what the voice channel returns.
These are the same requirements 8×8’s App-to-App Calling is built around: native in-app voice, privacy controls, PSTN fallback, and global routing in one SDK.
How 8×8 Powers In-App Calling

8×8’s App-to-App Calling provides voice SDKs for embedding calling functionality directly into mobile and web applications.
Ship Voice Without the Telephony Build
8×8 runs the carrier relationships, the media servers, and the routing behind the call. Your developers integrate an SDK; nobody on your team becomes a telephony engineer.
Keep Support Context Inside the App
An in-app voice call can route to a support agent in 8×8 Converse, escalate to video, or bridge to a phone number when the situation calls for it. Because the call starts inside your app, the agent already has the session: the order, the account, the screen the customer is looking at.
Connect Both Parties Without Exposing Numbers
Combined with the Number Masking API, App-to-App Calling creates private voice connections between both parties without revealing either personal number. For marketplaces, ride-hailing, and logistics operations across APAC, that privacy layer is what separates a call feature from a safe one.
Hold Call Quality Across Every Market
8×8’s network connects through 130+ direct mobile network operators worldwide, with strong coverage spanning 190 countries. When someone can’t be reached in the app, PSTN fallback bridges the call to a landline or mobile, so the conversation still happens.
Bring Voice Inside Your App
In-app calling isn’t about adding a call button. It’s about keeping the customer, the context, and their privacy in one place at the moment they need help – producing faster resolutions, fewer drop-offs, and conversations that never expose a personal number.
8×8’s App-to-App Calling SDKs put voice inside your mobile and web apps, with number masking, PSTN fallback, and global carrier reach already handled.
Talk to 8×8 about turning your app into the fastest support channel you have.
FAQ – In-App Calling
- What is in-app calling? In-app calling lets users make and receive voice calls directly in a mobile app or on a website, without switching to a phone dialer or a separate communication tool.
- What technology powers in-app calling? Most in-app calling solutions use WebRTC, a protocol that enables real-time voice and video in browsers and apps without plugins, combined with voice SDKs from CPaaS providers.
- Which industries benefit most from in-app calling? E-commerce marketplaces, healthcare and telehealth, ride-hailing, logistics, and financial services see the strongest benefits from embedded voice capabilities.
- Does in-app calling protect user privacy? Yes, when paired with number masking. The platform routes calls between users without revealing personal phone numbers, which is critical for marketplaces and ride-hailing apps.
- Can in-app calls connect to regular phone numbers? Yes. PSTN bridging allows in-app voice calls to connect to traditional landlines and mobile numbers when needed.
