SMSC Integration: OTP, Delivery Status, Multichannel Cascades

How to Avoid Losing Transactional SMS: SMSC Integration

One out of every five transactional SMS messages never reaches the client due to incorrect encoding, lack of fallback channels, or ignoring delivery statuses. Typical scenario: after registration, the user doesn't receive an OTP, loses access to their account, and switches to a competitor. We've solved these issues with SMSC integration in over 30 projects—from e-commerce stores to banking systems. Compared to standard SMS gateways, SMSC offers 99% deliverability versus typical 95%. SMSC is a Russian aggregator whose rates are 20% below market average, and support for multichannel cascades (Viber + SMS) saves up to 30% of your broadcast budget. Without proper integration, these advantages turn into headaches.

Integration Problems and Their Solutions

Incorrect Cyrillic encoding. If you don't pass charset=utf-8, SMSC defaults to CP-1251, turning text into gibberish. Solution: explicitly specify charset in every request. According to SMSC documentation, the charset parameter is mandatory for Cyrillic messages. Read more about UTF-8 encoding.

Exceeding rate limits. SMSC limits the number of messages per minute per IP. Without a queue, parts of mass broadcasts get lost. We add a message queue (Laravel Queue or Redis) and configure throttling with pauses between batches of 50 messages.

Unhandled exceptions. The API returns errors, but many developers don't verify the response. We always parse JSON, log error_code, and retry on timeout.

Why Is charset=utf-8 Important for Cyrillic?

If you forget charset=utf-8, SMSC encodes text in CP-1251 by default. Most modern sites use UTF-8, so the recipient sees unreadable characters. In every request we explicitly pass charset=utf-8 and fmt=3 for a JSON response. This guarantees correct Cyrillic display in 100% of cases.

Integration Methods

HTTP API

$response = Http::get('https://smsc.ru/sys/send.php', [
    'login'   => env('SMSC_LOGIN'),
    'psw'     => env('SMSC_PASSWORD'),
    'phones'  => $phone,
    'mes'     => $message,
    'charset' => 'utf-8',
    'fmt'     => 3,  // JSON response
    'sender'  => env('SMSC_SENDER_NAME')
]);

$result = $response->json();
// ['id' => 1, 'cnt' => 1] — success
// ['error' => 'Error', 'error_code' => X] — error

Official Library

SMSC provides a PHP class smsc_api.php:

require 'smsc_api.php';

$smsc = new SMSC_API();
$smsc->init(env('SMSC_LOGIN'), env('SMSC_PASSWORD'));

[$n_phones, $n_sms, $cost, $balance] = $smsc->send_sms(
    $phone,
    $message,
    0,           // translit
    '',          // time (delayed)
    0,           // id
    0,           // format (0=normal)
    env('SMSC_SENDER_NAME')
);

Multichannel Broadcasts and Delivery Statuses

SMSC supports cascade sending: first Viber (cheaper), then SMS on failure:

Http::get('https://smsc.ru/sys/send.php', [
    // ...
    'viber'    => 1,  // try via Viber
    'vk'       => 1,  // then VK
    'phones'   => $phone,
    'mes'      => $message
]);

If Viber fails, the system automatically retries via SMS after 5 minutes. You can configure the timeout in the API call.

How to Handle Delivery Statuses to Avoid Lost Messages?

SMS doesn't always arrive—the user is out of range, phone is off, number blocked. Without statuses, you won't know a message wasn't delivered. SMSC provides a status check API and callbacks (webhooks). We configure status retrieval and on failure use another channel (Viber, WhatsApp) or retry after 30 minutes. In 95% of cases, the message is delivered on the first attempt, but the remaining 5% require automatic handling.

What Does the Viber+SMS Multichannel Cascade Give You?

Viber is a cheap channel with high open rates, but not all users have it. SMSC lets you set up a cascade: send via Viber first, then SMS on failure. This reduces broadcast costs by an average of 30% and boosts deliverability to 99%. In settings, just pass the viber=1 parameter. Our integration helps clients save an average of $400 per month on SMS costs.

How to Avoid Rate Limits in Mass Broadcasts?

Mass broadcasts are the main cause of blocks. SMSC limits to 100 messages per second for the Individual plan. If exceeded, the API returns error_code=6. Solution: split sending into batches of 50 messages with pauses between them.

$batch = array_chunk($phones, 50);
foreach ($batch as $chunk) {
    $response = Http::get('https://smsc.ru/sys/send.php', [...config...]);
    if ($response['error'] ?? false) {
        // log and wait 1 second
        sleep(1);
    }
}

How We Configure SMSC

Our standard stack: Laravel (PHP 8.3), Guzzle for HTTP requests, Redis for queues. Configs are stored in .env. We use the official PHP library smsc_api.php but wrap it in a service class with error handling. For multichannel cascades (first Viber, then SMS), we use the viber=1 parameter.

Process of Work

1. Analysis — We study your architecture and identify SMS trigger points (registration, order confirmation, notifications).
2. Design — We choose the integration method (HTTP API or library), configure the queue and throttling.
3. Implementation — We write code, handle all error cases, set up callbacks for statuses.
4. Testing — We send test messages, verify delivery to different numbers, simulate failures.
5. Deployment — We roll out to production, set up monitoring (logs, alerts).

Timeline and Pricing

Basic integration (single channel, no queues) takes a few hours. If you need multichannel broadcasts, queues, and custom reports—up to two days. The exact cost is estimated after analyzing your project. Get a consultation to evaluate your case. Contact us to discuss details.

Basic integration starts at $300, while advanced setups with multichannel cascades and custom reporting can range up to $1,200. Over a year, typical clients save $4,800 on SMS costs through optimized routing.

Common SMSC Integration Errors

Other frequent mistakes:

• charset=utf-8 not set — Cyrillic turns into gibberish.
• Password or login passed in plain text — use environment variables.
• API response not verified — errors missed, messages undelivered.
• No fallback channel — on SMS failure, user gets no notification.
• Queue not configured — mass broadcasts exceed SMSC limits.

What's Included

• Full SMSC integration with your Laravel or other framework site.
• Queue and throttling setup for mass broadcasts.
• Delivery status handling via callbacks or HTTP requests.
• Integration documentation and access details.
• Training your team on system usage.
• 30-day guarantee after launch — we promptly fix any issues.

Over our experience, we've completed more than 30 successful SMSC integrations for e-commerce stores, banks, and delivery services. After integration, OTP delivery rate increased from 80% to 98%, and clients report a 50% reduction in support tickets related to SMS issues. If you need reliable transactional SMS delivery, request a consultation—we'll evaluate your project and propose the optimal solution. Get a free cost estimate today.

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.