Turnkey Zadarma IP Telephony Integration for Websites

Every fifth call to a high-volume online store never reaches a manager — the customer hangs up after 20 seconds of waiting. Without telephony integration, data about the caller is lost, no task is automatically created in the CRM, and the percentage of converted leads cannot be measured. We integrate Zadarma with your site in 2–5 business days: configure webhooks, callback, WebRTC calls, call recording, and data transfer to AmoCRM, Bitrix24, or any other system. Our years of turnkey telephony integration experience help reduce missed calls by 40% and increase call-to-lead conversion by 15%.

Technical Implementation of Integration

Webhook Notifications

Route::post('/webhooks/zadarma', function (Request $request) {
    $data  = $request->except('sign');
    ksort($data);
    $sign  = md5(http_build_query($data) . env('ZADARMA_SECRET'));
    if ($request->sign !== $sign) return response('Invalid sign', 403);

    $event = $data['event'];

    switch ($event) {
        case 'NOTIFY_START':
            $caller = $data['caller_id'];
            $this->handleIncomingCall($caller);
            break;

        case 'NOTIFY_END':
            CallLog::create([
                'zadarma_callid'  => $data['call_id_with_rec'],
                'caller'          => $data['caller_id'],
                'duration'        => $data['duration'],
                'disposition'     => $data['disposition']
            ]);
            break;

        case 'NOTIFY_RECORD':
            $recordingUrl = $data['link'];
            CallLog::where('zadarma_callid', $data['call_id_with_rec'])
                   ->update(['recording_url' => $recordingUrl]);
            break;
    }
});

API for Callback

$params = [
    'from'      => $agentPhone,
    'to'        => $customerPhone,
    'sip_id'    => env('ZADARMA_SIP_ID')
];
ksort($params);
$sign = base64_encode(hash_hmac(
    'sha1',
    env('ZADARMA_KEY') . urldecode(http_build_query($params)) . md5(serialize($params)),
    env('ZADARMA_SECRET')
));

Http::withHeaders([
    'Authorization' => env('ZADARMA_KEY') . ':' . $sign
])->get('https://api.zadarma.com/v1/request/callback/', $params);

WebRTC — Call from Browser

<script src="https://my.zadarma.com/webphoneApi/v3/js/zadarmawebrtc.js"></script>
<script>
var webrtcPhone = new ZadarmaWebRTC({
    sipId:    '{{ $sipId }}',
    sipPass:  '{{ $sipPassword }}',
    onCallStateChange: function(state, data) {
        console.log('Call state:', state);
    }
});
webrtcPhone.dial('79001234567');
</script>

Fetching and Storing Recordings

$response = Http::get('https://api.zadarma.com/v1/pbx/record/request/', [
    'call_id'    => $zadarmaCallId,
    'pbx_call_id'=> $pbxCallId
]);
$downloadUrl = $response->json()['link'];

What Problems Does Zadarma Integration Solve?

Missed calls are the biggest loss for an online store. Without a callback widget, customers wait and hang up. We set up callback: the system automatically calls the customer back after 30 seconds, reducing churn by 40%. Lack of analytics is the second problem. Without call recording and logs, you can't measure channel effectiveness. After integration, the CallLog database stores caller_id, duration, disposition, and a link to the recording. Manual transfer of leads to CRM slows processing and risks errors — we automate deal creation on every call. In one project (an electronics e‑commerce store), missed calls dropped from 25% to 8%, and phone orders increased by 18% in a month.

Why Choose Zadarma?

Zadarma is an international provider with numbers in 100+ countries and a flexible virtual PBX. The API enables any scenario — from a widget to a contact center. Call costs start at €0.005/min, and integration is 2–3 times faster than manual setup. The main advantage is low price and easy webhook/REST integration. Compared to wired telephony, Zadarma saves up to 60% on subscription fees and long-distance calls. With over 5 years of experience and 50+ successful telephony integrations, we ensure reliable setup.

Comparison: Our Integration vs Manual Setup

Zadarma Business Plan Comparison

Typical Mistakes in Self-Integration

• Incorrect webhook signature. Without ksort and MD5 with the secret key, Zadarma returns 403. Check sorting and http_build_query.
• Missing NOTIFY_END handler. Without this event, the call log stays empty — you won't get caller_id, duration, or status.
• Encoding issues. For REST API, use urlencode with PHP_QUERY_RFC3986, otherwise the signature won't match.
• Ignoring API errors. Always check $response->json()['status'] — not all requests return success.

Integration Work Stages

1. Analysis — review current telephony setup, load, and CRM needs.
2. Design — choose scenarios: callback, WebRTC, recording, integration.
3. Implementation — write code, configure webhooks and API, integrate with CRM.
4. Testing — test all scenarios: inbound, outbound, recording, CRM transfer.
5. Deployment — deploy to production, train staff.

What You Get as a Result

• Integration documentation with endpoint descriptions.
• Access to the control panel and logs.
• Staff training on the system.
• 2 months of post-launch support.
• Guarantee of correct operation for all scenarios.

We'll evaluate your project. Contact us and we'll write an integration plan. We work turnkey in 2–5 days. Request a consultation and get an analysis of your current telephony setup.

According to Zadarma documentation, the service uptime is 99.9%. WebRTC requires a modern browser (source: Wikipedia). We also provide IP telephony for your website and call automation features to streamline operations.

Email Campaign Integration: Why Does It Often Break?

We’ve observed that a trigger email sent 10 minutes after registration converts 4–5 times better than the same email sent after 24 hours. This isn’t a marketing myth—it’s mechanics: while the user is still warm, while they remember the context. But most integrations with email services are built like this: form submits → synchronous HTTP request to API → if the API is slow, the user waits 3 seconds → the email either goes out or doesn’t, nobody knows. In one project, we saw a 30% drop in conversion simply because the email service responded with 504 and Laravel’s queue driver wasn’t configured. Lost emails often hit customers silently – no log, no alert, just a missing order confirmation.

If you’re facing lost emails or spam folder issues, order an audit of your current integration – we’ll find bottlenecks within 2 days.

Providers and Their APIs

Unisender — a Russian provider popular in the SMB segment. REST API, simple. Adding a contact: importContacts, sending a transactional email: sendEmail. Important: for transactional emails (order confirmations, password resets), Unisender Go is a separate service with a different API and separate pricing. Mixing bulk and transactional mailings in one stream is bad for domain reputation. Unisender Go handles up to 1000 requests per second.

SendPulse — provides email, SMS, web push, Viber, and Telegram bots through a unified API. Convenient for projects requiring an omnichannel approach. Automation 360 is a visual chain builder; you can trigger automation via API events. The PHP SDK (sendpulse/rest-api-php-sdk) is maintained but updated irregularly – better to use Guzzle directly.

Mailchimp — a choice for international audiences and marketing teams accustomed to the Mailchimp ecosystem. Transactional email via Mandrill (a subsidiary service). Marketing API v3 for list, tag, and campaign management. Webhooks for opens, clicks, unsubscribes, bounces.

SMS. For Russia: SMSCenter, MTS Exolve, Devino Telecom, SMS Aero. Their APIs are similar: a send method with phone, message, sender parameters (sender name must be registered separately with the operator). One nuance: the sender name must be registered through the aggregator with a contract – otherwise SMS won’t be sent on MTS/MegaFon/Beeline networks.

How to Build an Integration That Doesn’t Lose Emails?

Separate Transactional and Marketing Streams

Transactional emails (order confirmations, password resets, delivery status) go through a dedicated sender domain or subdomain tx.example.com. Marketing campaigns go through mail.example.com or news.example.com. If a marketing campaign receives many spam complaints, it should not affect the reputation of the transactional stream. According to SendGrid documentation, transactional messages should be sent through a dedicated IP pool to prevent cross-contamination.

Queue and Retry

Any call to the email API goes through a queue (Laravel Queue, Bull, Celery). If Unisender returns a 503, the job retries after 5 minutes, then 15, then 60. After 5 failed attempts, it goes to a dead letter queue with an alert. The user already received their 200 OK and knows nothing about the issue. This approach reduces bounce rate on projects to 0.5%.

Example Laravel job:

public function handle(): void
{
    try {
        $response = Http::post(config('services.unisender.email_url'), $this->params);
        if ($response->failed()) {
            $this->release(300); // retry after 5 min
        }
    } catch (\Throwable $e) {
        $this->release(300);
    }
}

Templates

We store templates in code (Blade, Twig, React Email), not in the provider’s interface. Reasons: versioning via Git, browser preview without sending, testability. For complex templates with dynamic content — react-email with export to HTML via @react-email/render.

Validation and Consent

Before adding a contact to a list — double opt-in (confirmation email). Store the confirmation timestamp in your own database. Upon unsubscription — synchronously unsubscribe both at the provider and in your database. Ignoring webhook unsubscriptions is a direct path to account suspension at the provider. All processes comply with Федеральный закон № 152-ФЗ «О персональных данных».

Deliverability Monitoring and DKIM Setup

Connect provider webhooks for events: bounce (hard and soft), spam_complaint, unsubscribe. Hard bounce — immediately mark the email as invalid in your database, stop sending. Soft bounce 3 times in a row — same. Metrics: open rate, click rate, bounce rate, unsubscribe rate — review at least once a week. Our certified engineers configure alerts in Grafana/Prometheus.

DKIM configuration steps:

1. Generate a key pair (e.g., openssl genrsa -out private.key 2048).
2. Publish the public key in DNS as a TXT record for the selector (e.g., mail._domainkey.tx.example.com).
3. Provide the selector to the provider (SendGrid, Mailgun, Unisender).
4. Verify with dig TXT mail._domainkey.tx.example.com.

SPF, DKIM, DMARC must be configured separately for each stream. We use subdomains with different DNS records.

Why Is It Important to Separate Streams?

If you send a marketing campaign from the same domain as transactional emails and receive spam complaints, you risk getting the domain blocked — and users will stop receiving even order confirmations. SPF, DKIM, DMARC (Sender Policy Framework, DomainKeys Identified Mail, Domain‑based Message Authentication, Reporting and Conformance) must be configured separately for each stream. In one project, a marketing blast with 12% spam complaints blocked the transactional domain for 48 hours — we had to re‑authenticate with Google and Yandex.

What Does the Integration Scope Include?

• Audit of current communication streams and domain reputation (SPF, DKIM, DMARC)
• Provider and schema selection: transactional vs marketing traffic
• Configuration of SPF, DKIM, DMARC DNS records
• Development of email templates (HTML + dynamic content)
• Backend integration via queues and API
• Webhook setup for deliverability and complaints
• Operations documentation and team training
• Deliverability guarantee and post‑launch support

We deliver production‑ready documentation, access to monitoring dashboards, and a handover session with your engineers. Our certified engineers provide a 30‑day post‑launch health check guarantee.

Timelines and Cost

Cost is calculated individually after audit. We provide turnkey service: from analysis to production monitoring. Contact us for a free engineer consultation — we’ll evaluate your project and give accurate timelines. Over 7 years of experience in email service integration, 50+ projects implemented. Order a free audit of your current integration and receive a report with recommendations and estimated savings.