> ## 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.

# Overview

> What Click to Call is, when to use it, and how it fits into your product

**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.

## 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.

Either way, the widget:

* 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

<Note>
  ApifyCloud hosts the runtime, signalling, and media infrastructure. You keep
  full control of where calls route to and what data leaves the widget.
</Note>

## 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:

<CardGroup cols={2}>
  <Card title="Post-purchase support" icon="headset">
    Reduce refund rates by letting a customer talk to an agent the moment
    something is wrong — without them leaving the order page.
  </Card>

  <Card title="Lead qualification" icon="user-check">
    High-intent prospects (pricing page, enterprise form) get a one-tap path to
    sales instead of a contact form queue.
  </Card>

  <Card title="Concierge commerce" icon="sparkles">
    High-AOV categories (travel, jewelry, automotive) convert dramatically
    better when the buyer can ask a human before committing.
  </Card>

  <Card title="Onboarding & activation" icon="rocket">
    New users stuck on a step can reach a human in under three seconds,
    keeping them in the product.
  </Card>

  <Card title="Cart recovery" icon="cart-shopping">
    Hesitant checkout sessions see a "Talk to us" affordance instead of
    abandoning.
  </Card>

  <Card title="Urgency / help desks" icon="phone">
    Emergency flows (health, travel, financial) where typing is slower or
    the user is stressed.
  </Card>

  <Card title="QR codes & offline-to-online" icon="qrcode">
    Restaurants, events, retail, ticketing, printed materials. Scanning
    the QR opens a direct call — no app install, no phone number to dial.
  </Card>

  <Card title="SMS, email & ad callbacks" icon="message">
    Marketing campaigns, abandoned-cart flows, appointment reminders.
    The call-to-action is a one-tap voice link instead of a form.
  </Card>

  <Card title="No website required" icon="link">
    Consultants, coaches, agents, small teams. Share the widget URL in
    your link-in-bio, business card, or WhatsApp and let clients call you
    directly.
  </Card>
</CardGroup>

## How it works

At a high level, three layers are involved when a visitor clicks the call
button:

<Steps>
  <Step title="Browser captures audio">
    The widget requests microphone permission and opens a WebRTC session over
    encrypted transport (DTLS-SRTP for media, WSS for signalling).
  </Step>

  <Step title="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.
  </Step>

  <Step title="Call reaches your agents">
    The SIP leg connects to the destination you configured — your contact
    center, IVR, queue, or a direct SIP URI.
  </Step>
</Steps>

In parallel, the widget emits **lifecycle events** (`call_started`,
`call_ended`, `survey_submitted`, and more). These events power your
analytics, dispatch to webhooks, and drive any custom scripts you've
attached.

<Info>
  The visitor never dials a number and never sees one. The entire experience is
  in-page.
</Info>

## 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

<CardGroup cols={2}>
  <Card title="Browser & device support" href="/guides/click-to-call/browser-support">
    Confirm which browsers and OS versions your users are on.
  </Card>

  <Card title="Network requirements" href="/guides/click-to-call/network-requirements">
    What visitors' and agents' networks need for reliable calls.
  </Card>

  <Card title="Embedding" href="/guides/click-to-call/embedding">
    Drop the widget into your site with a single iframe.
  </Card>

  <Card title="Events" href="/guides/click-to-call/events">
    Catalogue of lifecycle events and what they mean.
  </Card>
</CardGroup>