Twilio Integration: SMS, OTP, Voice Notifications

We often take projects where clients complain about undelivered SMS to the US or Europe. Built-in CMS SMTP servers are not suitable, and building your own SMS gateway is expensive and unreliable. According to Twilio statistics, up to 15% of messages are blocked by carriers due to incorrect sender configuration. Using a correctly configured API increases deliverability to 99%. A single API for SMS, voice calls, WhatsApp, and OTP codes solves these problems. Below is real-world experience configuring on a Laravel + PHP 8.3 stack. We have over 5 years of experience with Twilio, more than 50 integrations for clients in Europe and the US. In 9 out of 10 cases, integration takes no more than 3 days. We guarantee stable delivery and compliance with privacy laws (GDPR, CCPA).

What problems does Twilio solve?

Problems with international SMS delivery, OTP code security, complexity of supporting multiple communication channels (SMS, voice, WhatsApp) — all solved via a single API. Twilio provides ready SDKs for PHP, Python, Node.js, and other languages. For example, for OTP codes there is Twilio Verify, which is 5 times more secure than a custom solution thanks to automatic code expiration and built-in attempt limits. Development time savings up to 40 hours on implementing a code system yourself.

How to set up Twilio for sending SMS?

To send SMS via Twilio you need:

1. Register a Twilio account, get Account SID and Auth Token.
2. Buy or rent a phone number in the required country (Twilio provides numbers in 100+ countries).
3. Install SDK: composer require twilio/sdk.
4. Create a service for sending:

$twilio = new \Twilio\Rest\Client(
    env('TWILIO_ACCOUNT_SID'),
    env('TWILIO_AUTH_TOKEN')
);
$message = $twilio->messages->create(
    $to,
    [
        'from' => env('TWILIO_PHONE_NUMBER'),
        'body' => "Your code: {$code}"
    ]
);

5. Configure a webhook for status tracking (see below).

Important: before going to production, test delivery on real numbers — some carriers block traffic from unverified senders. Ensure A2P 10DLC settings are correct for the US. Average delivery speed for transactional SMS is 2-5 seconds.

Why use Twilio Verify instead of a custom OTP?

Twilio Verify is two-factor authentication as a service that is on average 5 times more secure than a custom solution due to automatic code expiration and built-in attempt limits. The cost of one OTP check via Twilio is comparable to the cost of developing and supporting your own solution, but saves development time and reduces error risks. Key differences:

Example integration of Twilio Verify in Laravel:

// Send OTP
$verification = $twilio->verify->v2
    ->services(env('TWILIO_VERIFY_SERVICE_SID'))
    ->verifications->create($phone, 'sms');

// Check
$check = $twilio->verify->v2
    ->services(env('TWILIO_VERIFY_SERVICE_SID'))
    ->verificationChecks->create(['to' => $phone, 'code' => $userCode]);

if ($check->status === 'approved') {
    // success
}

In the Twilio panel, create a Verify Service and copy its SID. Configure attempt limit (e.g., 5) and code lifetime (usually 10 minutes). For production, be sure to enable signature validation on webhooks.

How to handle SMS delivery statuses?

Twilio sends POST requests to the specified URL when message status changes (sent, delivered, undelivered). This allows logging and reacting, for example, retrying on error:

Route::post('/webhooks/twilio/sms', function (Request $request) {
    $validator = new \Twilio\Security\RequestValidator(env('TWILIO_AUTH_TOKEN'));
    if (!$validator->validate($request->header('X-Twilio-Signature'), $url, $request->all())) {
        return response('Unauthorized', 403);
    }
    SmsDelivery::updateOrCreate(
        ['message_sid' => $request->MessageSid],
        ['status' => $request->MessageStatus]
    );
});

Always check the signature (X-Twilio-Signature) — this is a mandatory security requirement. Without it, you could accept a fake call and record an incorrect status.

How to integrate Twilio into Laravel with minimal effort?

Use a service provider to register the Twilio client. Move configuration to config/twilio.php and use a facade for convenience. Example:

// config/twilio.php
return [
    'account_sid' => env('TWILIO_ACCOUNT_SID'),
    'auth_token' => env('TWILIO_AUTH_TOKEN'),
    'phone_number' => env('TWILIO_PHONE_NUMBER'),
];

Create a Twilio facade and use it throughout the application. This simplifies provider replacement and testing.

What's included in the work?

Turnkey integration includes: Twilio account registration, number setup and sender verification, SDK integration into the project (Laravel, Symfony, any PHP framework), Twilio Verify implementation for two-factor authentication, webhook setup with signature validation, plus documentation and team training (1 hour online). After deployment, we hand over credentials and configurations.

Timeframes and guarantees

Basic SMS integration — from 1 business day. If Verify, webhooks, and voice calls are needed — up to 3 days. We provide a guarantee on correct API operation and timely notification delivery (within Twilio SLA). We assess your project free of charge — send us your technical specifications. Contact us for a consultation or to order an integration.

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.