Integrating SMS Notifications via SMS.ru on Laravel

When a user doesn't receive an SMS with a code during registration, it's not just an error—it's a lost customer. According to SMS.RU data, 30% of users abandon the form if the OTP doesn't arrive within 30 seconds. Another 15% of orders are canceled without SMS confirmation. Integrating with a reliable provider like SMS.ru solves these problems and reduces churn. We connect SMS.ru to your website built on Laravel, Django, Rails, or any other framework. Our stack includes PHP 8.3+, Node.js, Go—we adapt to any architecture. Let's dive into the technical details.

How to Integrate SMS.ru in 1 Day?

We use a single service class with explicit error handling. Example for Laravel:

class SmsRuService
{
    public function send(string $phone, string $message): bool
    {
        $phone = preg_replace('/[^0-9]/', '', $phone);
        if (str_starts_with($phone, '8')) {
            $phone = '7' . substr($phone, 1);
        }

        $response = Http::get('https://sms.ru/sms/send', [
            'api_id' => config('services.smsru.api_key'),
            'to'     => $phone,
            'msg'    => $message,
            'json'   => 1
        ]);

        return $response->json("sms.{$phone}.status") === 'OK';
    }

    public function getBalance(): float
    {
        return Http::get('https://sms.ru/my/balance', [
            'api_id' => config('services.smsru.api_key'),
            'json'   => 1
        ])->json('balance');
    }
}

The class normalizes the number (8 → 7), sends the request, and checks the status. For asynchronous sending, we wrap the call in Laravel Queue or Redis Pub/Sub. The documentation for SMS.ru recommends using JSON response format for quick validation. Thanks to the provider contract, switching services (e.g., to SMSC.RU) is as simple as replacing one class.

Synchronous vs Asynchronous Sending

For high-load projects, asynchronous sending is mandatory—it is 2x faster for the user compared to synchronous.

class SendSmsJob implements ShouldQueue
{
    use Dispatchable, InteractsWithQueue, Queueable, SerializesModels;

    public function handle(SmsRuService $service)
    {
        $service->send($this->phone, $this->message);
    }
}

Why Is Asynchronous Sending Critical?

With synchronous calls, each API request adds ~500ms to the server response time. If you have 1000 registrations per hour, that's 8 minutes of CPU time just waiting for SMS. Queues solve this: we enqueue a job in 10ms, and a background worker processes them in batches. Plus, retries on temporary API errors—synchronous code would simply fail, asynchronous will retry.

Balance Monitoring and Alerts

Zero balance means messages don't go out, and users don't receive OTPs. We set up a check every hour with notification via Telegram. The threshold is 100 RUB. Example code for a console command:

$balance = app(SmsRuService::class)->getBalance();
if ($balance < 100) {
    Notification::route('telegram', config('services.telegram.chat_id'))
        ->notify(new BalanceLowNotification($balance));
}

Additionally, we log all API responses for quick diagnostics. If the balance is zero, sending doesn't happen—this directly impacts conversion. We also add overspend protection: a daily sending limit in code. Savings from timely top-ups can be up to 25,000 RUB per month by preventing downtime.

What to Do If SMS Are Not Delivered?

Check four points:

• Balance—most common cause.
• Number format: 7XXXXXXXXXX (no 8 or +).
• Sender name—must be registered with SMS.ru.
• API response status: code 100 means success, others indicate errors.

We log all requests with response codes so you can spot a problem in a minute. One-time password (OTP) is the standard for verification, but without reliable delivery it's useless.

Scope of Work

• Code: service class with error handling, number normalization, and queue support.
• Tests: unit tests for SmsRuService and functional tests for sending scenarios.
• Monitoring: script to check balance with Telegram or Slack notifications.
• Documentation: description of configuration, environment variables, and integration points.
• Training: one-hour demonstration for your team.
• Support: two weeks after deployment to fix any issues.

Process and Timeline

1. Analysis — review existing code, choose integration points (1-2 hours).
2. Design — create service contract, provider factory.
3. Implementation — write wrapper class, tests (Unit + Feature) — 4-6 hours.
4. Testing — verify in SMS.ru sandbox (valid key + test number) — 2-4 hours.
5. Deployment — roll out to staging, monitor logs — 1-2 hours.

Timeline: from 1 to 3 days depending on complexity. Contact us for an assessment of your project.

Why Order Integration from Us?

You get stable sending and experience from over 100 successful SMS gateway integrations. The investment in integration pays off through reduced customer churn. Request an integration — we'll evaluate your project in 1 hour. Get a consultation to discuss details.

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.