Click to Call is an embeddable voice widget. Visitors on your website or app tap a button and a voice call is established from their browser to your agents — no phone dialer, no installed app, no native client on either side.Documentation Index
Fetch the complete documentation index at: https://docs.apifycloud.io/llms.txt
Use this file to discover all available pages before exploring further.
What it is
A hosted voice widget you can use in two ways:- Embed it on any website or app with a single
<script>tag or an<iframe> - Share it as a direct link — paste the URL in SMS, email, QR codes, ads, or a link-in-bio. No website of your own required.
- Handles microphone permissions and user consent
- Establishes a WebRTC audio session from the browser to your contact endpoint
- Routes the call to the agent, queue, or IVR you configured
- Renders the entire call UI (pre-call form, in-call timer, mute, hang-up, post-call survey) — fully styleable in Call Studio
- Emits lifecycle events you can forward to analytics, CRMs, and webhooks
ApifyCloud hosts the runtime, signalling, and media infrastructure. You keep
full control of where calls route to and what data leaves the widget.
When to use it
Click to Call is a fit whenever a phone call is the highest-conversion path for a specific moment in the user journey:Post-purchase support
Reduce refund rates by letting a customer talk to an agent the moment
something is wrong — without them leaving the order page.
Lead qualification
High-intent prospects (pricing page, enterprise form) get a one-tap path to
sales instead of a contact form queue.
Concierge commerce
High-AOV categories (travel, jewelry, automotive) convert dramatically
better when the buyer can ask a human before committing.
Onboarding & activation
New users stuck on a step can reach a human in under three seconds,
keeping them in the product.
Cart recovery
Hesitant checkout sessions see a “Talk to us” affordance instead of
abandoning.
Urgency / help desks
Emergency flows (health, travel, financial) where typing is slower or
the user is stressed.
QR codes & offline-to-online
Restaurants, events, retail, ticketing, printed materials. Scanning
the QR opens a direct call — no app install, no phone number to dial.
SMS, email & ad callbacks
Marketing campaigns, abandoned-cart flows, appointment reminders.
The call-to-action is a one-tap voice link instead of a form.
No website required
Consultants, coaches, agents, small teams. Share the widget URL in
your link-in-bio, business card, or WhatsApp and let clients call you
directly.
How it works
At a high level, three layers are involved when a visitor clicks the call button:Browser captures audio
The widget requests microphone permission and opens a WebRTC session over
encrypted transport (DTLS-SRTP for media, WSS for signalling).
Signalling & media transit our network
Voice infrastructure terminates the WebRTC session and bridges it to
a SIP endpoint. STUN/TURN is used to traverse the visitor’s NAT or
corporate firewall when needed.
call_started,
call_ended, survey_submitted, and more). These events power your
analytics, dispatch to webhooks, and drive any custom scripts you’ve
attached.
The visitor never dials a number and never sees one. The entire experience is
in-page.
What you bring vs. what ApifyCloud brings
| Responsibility | You | ApifyCloud |
|---|---|---|
| Distribution surface (website, app, URL, QR, link-in-bio) | ✅ | |
| Destination (SIP URI / contact centre) | ✅ | |
| Business rules (hours, routing, surveys) | ✅ (configured in console) | |
| Widget runtime & CDN | ✅ | |
| WebRTC ↔ SIP media bridge | ✅ | |
| Signalling & media infrastructure | ✅ | |
| Event delivery, retries, circuit breaker | ✅ | |
| Call Studio visual editor | ✅ | |
| Security (sandbox, encryption, audit) | ✅ |
Key differences from traditional phone support
| Traditional phone number | Click to Call | |
|---|---|---|
| User must dial | Yes | No |
| User leaves the page | Usually | No |
| Works without cell signal | No | Yes (Wi-Fi) |
| Cross-border cost to visitor | Yes | No |
| Attribution to page / session | Difficult | Native |
| Pre-fill form data into call | Manual / verbal | Automatic via URL context |
| Mobile app required | Sometimes (for VoIP) | No |
| Works on desktop | Via softphone | Native |
What’s next
Browser & device support
Confirm which browsers and OS versions your users are on.
Network requirements
What visitors’ and agents’ networks need for reliable calls.
Embedding
Drop the widget into your site with a single iframe.
Events
Catalogue of lifecycle events and what they mean.