A client leaves if they can't quickly get in touch. Manager busy, order form fails — leads vanish. Callback powered by CoMagic solves the problem: automatic callback in 30 seconds and transparent analytics for every call — source, UTM tags, how many times reached. We implement CoMagic turnkey: from widget installation to deep CRM and BI integration. Below, we dive into technical details and compare with a custom PBX. Our CoMagic integration service includes callback widget installation, call tracking setup, CRM integration, and custom webhooks—all for improved call analytics and telephony savings of $2,000–$5,000 per month.
CoMagic is more effective than a custom PBX
A custom PBX requires weeks of development and maintenance, while CoMagic goes live in a day. Conversion to callback using the widget grows by an average of 25% compared to a regular form. CoMagic launches a callback 5 times faster than typical custom PBX: the client receives the call in 30 seconds. Analytics of UTM tags and call recording come out of the box — no coding needed. For a custom solution, you'd have to implement everything from scratch and ensure 99.9% SLA, which requires significant investment. According to CoMagic documentation, the average connection time does not exceed 30 seconds.
Increasing call conversion with CoMagic
The callback widget detects when a visitor is ready to call and prompts them to enter their number. Within 30 seconds, the system connects the client to the manager. This increases inquiries by 20–40% compared to a regular order form. Additionally, CoMagic records conversations and detects emotional tone — data can be used for sales training. In one project (an electronics online store), call conversion increased by 87% after implementation, and missed calls dropped from 35% to 8%. The average savings on missed calls are substantial, often over $2,000 per month for mid-sized businesses.
CRM integration requirements
For standard CRMs (amoCRM, Bitrix24), just add an API key in CoMagic settings. Call data (number, duration, UTM) immediately appears in the deal card. If the CRM is custom, we implement webhooks; on call completion, CoMagic sends a POST request with JSON to your endpoint. We also configure two-way synchronization: a call from CRM initiates a callback via CoMagic.
Technical details: from widget to API
Installing the widget on the site is straightforward. Add the script to <head>:
Widget installation code
<script type="text/javascript">
var _comagic_data = { id: 'YOUR_COMAGIC_ID' };
(function(a,b,c,d){a[b]=a[b]||function(){(a[b].q=a[b].q||[]).push(arguments)};
var e=c.createElement(d);e.async=1;e.src='//cdn.comagic.ru/modules/app/v2/app.js';
c.getElementsByTagName('head')[0].appendChild(e)})(window,'comagic',document,'script');
</script>
For customization, use the API — hide the widget on certain pages, pass user data:
// Hide/show widget
comagic('widget', 'hide');
comagic('widget', 'show');
// Pass visitor data
comagic('visitor', {
name: user.name,
email: user.email,
phone: user.phone
});
CoMagic provides a REST API for report export and webhooks. Example request for calls in the last hour:
API call example
$response = Http::withToken(env('COMAGIC_API_TOKEN'))
->post('https://dataapi.comagic.ru/v2.0/', [
'method' => 'get.calls_report',
'params' => [
'user_id' => env('COMAGIC_USER_ID'),
'date_from' => now()->subHour()->format('Y-m-d H:i:s'),
'date_till' => now()->format('Y-m-d H:i:s'),
'fields' => ['id', 'start_time', 'caller_number', 'utm_source', 'duration']
]
]);
Configuring CoMagic webhooks
When a call ends, CoMagic sends a POST request to your specified endpoint. Example PHP handler:
Webhook handler code
// Get data from CoMagic
$payload = json_decode(file_get_contents('php://input'), true);
if ($payload['event'] === 'call_ended') {
// Save call in your CRM
$callData = [
'phone' => $payload['caller_number'],
'duration' => $payload['duration'],
'utm_source' => $payload['utm_source'] ?? '',
'record_url' => $payload['record_url'] ?? '',
];
// Send to CRM
$crm->createCall($callData);
}
Which is better: CoMagic or custom PBX?
| Criterion |
CoMagic (ready service) |
Custom PBX |
| Time to launch |
1 day (5x faster) |
2–4 weeks |
| Call analytics |
Built-in, UTM, recording |
Must be written from scratch |
| CRM integration |
Ready (amoCRM, Bitrix24) |
Via API |
| Total cost of ownership |
Fixed tariff from $99/month |
Development + maintenance |
| Reliability |
99.9% SLA |
Depends on infrastructure |
| Telephony savings |
Up to $5,000/month |
None |
What are the key metrics improvements?
| Metric |
Before integration |
After integration |
| Call conversion |
1.5% |
2.8% (+87%) |
| Time to first call |
2 minutes |
30 seconds (4x faster) |
| Missed call rate |
35% |
8% (77% reduction) |
| Source attribution accuracy |
no data |
100% (UTM + call tracking) |
Data based on 50+ projects by our engineers.
Process: from audit to deployment
- Audit current telephony — check which numbers are used, how routing is configured.
- Design integration — choose scenario: simple widget, callback with dynamic number, CRM integration.
- Implementation — install script, configure API, write webhooks if needed.
- Testing — verify call routing, recording, data transfer to CRM.
- Deployment — go live, set up monitoring.
Timeline and cost
Basic integration (widget + call tracking) — from 1 day. Extended (with CRM and webhooks) — from 3 days. CoMagic tariff starts at $99/month. Cost is calculated individually: depends on number of phone numbers, CRM complexity, and need for custom reports. Contact us for a free consultation.
Checklist: what's included
- [ ] Install callback widget on all pages
- [ ] Configure dynamic number for different traffic sources
- [ ] Integrate with CRM (amoCRM/Bitrix24/custom)
- [ ] Set up webhooks for call data to external systems
- [ ] Train managers on CoMagic dashboard
- [ ] Testing and operational guarantee (7 days support)
Our engineers have 5+ years of CoMagic implementation experience, with 50+ projects completed. We provide a warranty on all work and documentation. For more on call tracking, see Wikipedia article on Call tracking. Detailed API documentation is available at CoMagic developer docs.
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.
| Provider |
Type |
Transactional Emails |
Marketing |
Notes |
| Unisender |
email+SMS |
Unisender Go (separate) |
Yes |
Popular in Russia, simple REST |
| SendPulse |
email+SMS+web push+Viber |
Yes |
Yes |
Unified API, omnichannel |
| Mailchimp |
email |
Mandrill |
Yes |
Analytics, international |
| Twilio |
SMS+email |
Yes |
No |
Global, expensive in Russia |
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:
- Generate a key pair (e.g.,
openssl genrsa -out private.key 2048).
- Publish the public key in DNS as a TXT record for the selector (e.g.,
mail._domainkey.tx.example.com).
- Provide the selector to the provider (SendGrid, Mailgun, Unisender).
- 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
| Scenario |
Timeline (business days) |
Notes |
| Basic transactional emails (one provider) |
5–7 days |
Price is calculated individually after audit |
| Trigger sequences + SMS + web push |
10–20 days |
Price is calculated individually after audit |
| Full omnichannel automation |
20–40 days |
Price is calculated individually after audit |
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.
