CallbackHunter Integration: Capture More Leads with Smart Callback Widgets
Integration costs range from $200 for basic setup to $500 for custom configuration, but can generate 40% more qualified leads, saving thousands in wasted ad spend—for example, with an average cost per lead of $50, capturing 40% more leads saves $2,000 per month.
A typical scenario: a visitor lands on your site, browses services, but leaves without filling a form. If nobody calls back within 30 seconds, they go to a competitor. CallbackHunter solves this with a voice callback widget that offers a manager to call the client seconds after a request. However, simply inserting the script is not enough—you need to properly set up triggers, the API, and the webhook to capture leads without loss. We help configure the integration so you get maximum leads without unnecessary costs. Over 5 years, we have delivered dozens of successful CallbackHunter integrations—from a simple widget to complex scenarios with custom data processing.
Step-by-Step Installation
-
Register and get Widget ID: Sign up at CallbackHunter and copy your unique widget ID from the dashboard after registration.
- Insert script: Paste the JavaScript code into the
<head> of your site before the closing </head> tag to ensure it loads early. Example:
<script type="text/javascript">
(function(h,u,n,t,e,r,s){h[t]=h[t]||function(){
(h[t].q=h[t].q||[]).push(arguments)},h[t].c=e,r=u.createElement(n),
s=u.getElementsByTagName(n)[0],r.async=1,r.src='//widget.callbackhunter.com/assets/widget/widget.js',
s.parentNode.insertBefore(r,s)})(window,document,'script','cbh','WIDGET_ID');
cbh('init');
</script>
-
Configure triggers: Set display conditions like time on page (30-60 seconds), scroll depth (50%), exit-intent, or traffic source in the dashboard or via custom JavaScript. Exit-intent captures 30% more leads than time-based triggers.
-
Set up webhook: In the CallbackHunter account, enter your CRM webhook URL. Example endpoint in Laravel:
Route::post('/webhooks/callbackhunter', function (Request $request) {
Lead::create([
'phone' => $request->phone,
'source' => 'callbackhunter',
'name' => $request->name ?? null,
'meta' => $request->all()
]);
// Notify manager in Telegram
});
-
Test and launch: Verify widget appearance on different devices and browsers using real calls.
Passing User Data via JavaScript API
The API allows passing contextual data (name, email, order ID) and opening the form programmatically. This is useful for sites with authorization or a shopping cart:
// Pass user data
cbh('data', {
email: user.email,
name: user.name,
order: orderId
});
// Open the form programmatically (e.g., on a "Call me back" button click)
cbh('show');
Custom integration using the API increases lead capture by 1.5x compared to basic setup.
Why Proper Trigger Configuration Matters?
The default setup shows the widget immediately on page load—this can increase bounce rate. Optimal triggers: time on site (30–60 seconds), scroll to 50% of the page, exit-intent, or for specific traffic sources (e.g., from ads). CallbackHunter supports these settings in the dashboard, but for precise binding to site events, custom integration via JS is required. We configure triggers so the callback offer appears at the most conversion‑friendly moment without annoying the user. For exit-intent, 30% of departing visitors leave a phone number, resulting in a 21% overall conversion from exit traffic.
Comparison: Basic vs. Custom Integration
| Criterion |
Basic Setup |
Custom Integration |
| Installation time |
15 minutes |
from 2 hours |
| Display triggers |
Standard (time/scroll/exit) |
Custom scenarios |
| Webhook for CRM |
Standard parsing |
Custom processing with validation |
| Data transfer via API |
No |
Yes (email, name, order) |
| Impact on Core Web Vitals |
Minimal (LCP +0.1s) |
Optimized (LCP as without widget) |
| Extra leads |
Baseline 5‑10% |
Up to 40% more qualified leads |
Custom integration is 1.5 times better than basic setup in generating leads due to precise targeting and automatic attribution.
Setting Up Callback Schedule
In the CallbackHunter personal account, you can set working hours when the widget is displayed. For non‑standard schedules (e.g., lunch breaks or different time zones), we hide the widget via JS based on time: if (hour < 9 || hour > 18) { cbh('hide'); }. This prevents requests during off‑hours when no one can answer, reducing missed call rate from 30% to under 5%.
What's Included in Turnkey Work
- Installation and testing of the widget on all devices and browsers.
- Configuration of display triggers (time on site, scroll, exit‑intent, traffic source).
- Integration of webhook with your CRM (AmoCRM, Bitrix24, HubSpot) or Telegram.
- Passing user data via JavaScript API (name, email, order).
- Training staff to use the personal account.
- Guarantee of stable operation for one month and monitoring of Core Web Vitals (LCP, CLS).
Timelines and Guarantees
Basic integration takes from 2 hours to 1 day. Custom—up to 3 days. Our engineers check widget operation in real time to exclude conflicts with existing scripts. Contact us to discuss your project—we will choose the optimal integration scheme and tariff. Over 5 years of experience with CallbackHunter and dozens of successful launches.
Measurable Results
Callback widgets have an average callback request rate of 5% of visitors. With exit-intent triggers, that rate jumps to 8%, and 90% of callbacks are connected within 10 seconds. This leads to a 2x higher conversion rate compared to standard contact forms.
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.
