DanJMillsContact
Back to projects

SMSBridge

Project year 2026

A controlled SMS communications bridge for campaigns, devices and delivery visibility.

60 second pitch

What SMSBridge does.

SMSBridge helps sales and operations teams manage outbound SMS campaigns through a controlled pool of Android devices. Users can create campaigns, upload recipient files, choose active devices, pace message sending and see what happened after each message leaves the web platform.

The important part is visibility. Messages, devices, replies, failed sends, missed calls, health checks and webhook events are brought into one system, so the team has a clearer operational record instead of scattered phone activity.

Role

Product planning, Laravel architecture, campaign workflow design and hands-on delivery

Sector

Sales operations, campaign communications, device management and delivery tracking

Stack

Laravel, Inertia, Vue, MySQL, Sanctum, queues, Firebase Cloud Messaging, webhooks and Android device reporting

Product shape

SMSBridge makes a messy device-based process behave like an accountable platform.

The platform connects campaign planning, active devices, message records, delivery outcomes, inbound replies, missed calls and webhook notifications. Every part of the flow is built around a simple idea: the team should be able to see what was sent, where it was sent from and what happened next.

The messages view gives the team one place to review inbound and outbound SMS activity, unread replies, sender devices, dates and quick follow-up actions.

Campaign detail screens show progress, selected devices, pacing, sent times and per-recipient outcomes so campaign activity is visible after launch.

The device view tracks the Android pool behind the platform, including online status, battery, signal, owner, network provider and message symmetry.

SMSBridge messages screen showing received SMS messages, unread counts, filters and actions
SMSBridge campaign detail screen showing campaign status, sent messages, devices and campaign records
SMSBridge device management screen showing Android device health and owner details
01

The problem

SMS campaigns become hard to control when sending is spread across devices and people.

Sales teams sometimes need to manage outbound SMS at volume, but the process quickly becomes messy if every device, reply, delivery state and failed send is handled separately. Without a central system, it is hard to know what has been queued, which phone sent it, whether it failed, whether a reply came back or whether a device has quietly gone offline.

The operational problem was not just sending messages. It was giving the team one place to manage campaigns, monitor devices, understand message outcomes and keep a clearer record of the communication flow.

02

Why it was built

SMSBridge gives campaign teams a controlled way to manage device-based sending.

The platform was built for teams that need campaign control, not a loose collection of handsets. Users can send individual messages, upload campaign files, choose which active devices should be used, schedule sending and apply a delay between messages so the campaign runs in a more deliberate way.

Behind the scenes, the system keeps every message and device event traceable. A message moves through a clear lifecycle: queued, dispatched to phone, sent, delivered or failed. That gives the team a much better view of what actually happened.

03

How it works

The web platform coordinates the work while Android devices report back the outcome.

When a message is created, Laravel records it, queues the work and sends a Firebase instruction to the selected Android device. The phone then sends the SMS and reports the result back to the API as a single event or as part of a periodic batch sync.

The same system also captures inbound SMS, missed calls, device health, battery and signal information, phone event logs and webhook notifications, so operational teams can see more than just a list of sent messages.

04

Why it matters

The value is control, visibility and fewer blind spots around campaign communication.

SMSBridge turns a device-based sending process into something measurable. Teams can see campaign progress, message status, device availability, inbound replies, failed sends and webhook delivery from one platform.

That makes the operation easier to manage and easier to improve. Instead of guessing what happened across several phones, the business has a clearer system of record for campaign activity and device performance.

Platform capability

Features

SMSBridge covered the practical tools needed to run campaign communications through managed devices: sending, scheduling, delivery status, inbound activity, health monitoring, webhooks and API access.

  • Managed Android devices

    Register, monitor and manage the devices used for sending.

  • Device health monitoring

    Track online status, last seen time, battery, signal and app version.

  • One-to-one SMS sending

    Send individual messages from the web UI or REST API.

  • Campaign CSV uploads

    Create campaign batches from phone number and message files.

  • Campaign scheduling

    Start campaigns immediately or schedule them for later.

  • Message pacing

    Control the wait time between campaign messages.

  • Device pool allocation

    Distribute campaign messages across selected active devices.

  • Delivery status lifecycle

    Track queued, dispatched, sent, delivered and failed states.

  • Phone event reporting

    Devices report sent, delivered and failed events back to the platform.

  • Batch sync support

    Phones can submit grouped status updates on a regular sync.

  • Inbound SMS capture

    Received messages are stored and matched to contacts where possible.

  • Missed call logging

    Incoming missed calls can be recorded against the right device.

  • Conversation views

    Messages can be grouped by device and phone number.

  • Signed webhooks

    Notify external systems about SMS, device and call events.

  • API access

    Documented endpoints for sending, devices, events and statistics.

  • Operational dashboard

    Surface totals for sent, received, queued, delivered, failed and active devices.

The results

A clearer operating layer for SMS campaign activity.

The result was a platform that moved campaign sending away from disconnected phone activity and into a controlled workflow with message status, device health and event visibility.

5

message states

Queued, dispatched to phone, sent, delivered and failed outcomes tracked clearly.

7

event types

SMS, device and missed-call events can trigger secure webhook notifications.

16

feature areas

Campaigns, devices, delivery states, inbound messages, calls, webhooks and API access.

Next Case Study

WorkCRM installer vetting and accreditation platform

View project

Need this kind of control?

Let us turn a fragile operational process into a platform your team can actually manage.

Discuss a project