DEV Community: Ebrahim Manj

Building CallRing AI: From Call Tracking to Lead Intelligence

Ebrahim Manj — Wed, 16 Sep 2026 08:06:42 +0000

Building a SaaS product from scratch is very different from building a normal web application.

You don't just need to make the features work.

You need to think about architecture, integrations, data isolation, permissions, scalability, tracking, billing, and — most importantly — how all of those pieces work together.

That's what we've been working on with CallRing AI.

What is CallRing AI?

CallRing AI is a call tracking and lead intelligence platform designed to help businesses understand where their calls are coming from and what happens after the call.

The basic idea is simple:

Don't just track the call. Understand the lead behind it.

A business may receive calls from:

Google Ads
Facebook Ads
Landing pages
Organic traffic
Referrals
Offline campaigns
Direct traffic

Instead of treating every call as an isolated event, CallRing AI connects the call with its source and other lead information.

The Stack

The application is built around the Laravel ecosystem and the TALL Stack:

Laravel
PHP
Livewire
Tailwind CSS
Alpine.js
MySQL

We also use external services and APIs for things such as telephony, payments, analytics, and AI-powered conversation processing.

One of the reasons I enjoy Laravel for SaaS development is how quickly you can move from an idea to a structured application without sacrificing the ability to build more advanced architecture later.

The Interesting Part: Attribution

One of the biggest challenges is connecting a phone call back to its marketing source.

Imagine someone clicks a Google Ad, visits a landing page, and later calls a business.

The useful question isn't only:

"Did we receive a call?"

It's:

"Which campaign generated this call, and what happened to the lead afterward?"

That means the system needs to connect multiple pieces of data.

Marketing Source
       ↓
Website Visit
       ↓
Tracking Number
       ↓
Incoming Call
       ↓
Contact / Lead
       ↓
Deal
       ↓
Revenue

This creates a much more useful picture of marketing performance.

Workspaces

Another part of the architecture is the workspace system.

Businesses can have multiple teams, branches, locations, or clients.

For example:

Workspace
├── Location A
│   ├── Phone Numbers
│   ├── Campaigns
│   └── Calls
│
├── Location B
│   ├── Phone Numbers
│   ├── Campaigns
│   └── Calls
│
└── Location C
    ├── Phone Numbers
    ├── Campaigns
    └── Calls

Each workspace can have its own configuration, users, numbers, campaigns, and reporting.

This also makes the platform useful for marketing agencies managing multiple clients.

Role-Based Access

SaaS applications quickly become complicated when multiple people need different levels of access.

CallRing AI uses workspace-based permissions so different users can have different responsibilities.

For example:

Owner
Manager
Member
Client

The important part is making sure users only access the data they're supposed to see.

This sounds simple, but it becomes an important architectural concern once an application has multiple workspaces and thousands of records.

AI-Powered Conversation Intelligence

Call tracking tells you that a conversation happened.

But the conversation itself contains valuable information.

That's where AI processing comes in.

A call can be transformed into structured information such as:

Transcript
Summary
Sentiment
Speaker identification
Lead score
Important conversation details

Instead of manually listening to hundreds of recordings, a sales or marketing team can quickly understand what happened.

The goal isn't simply to add "AI" to the product.

The goal is to turn unstructured conversations into useful business data.

What I've Learned Building It

One of the biggest lessons I've learned while building CallRing AI is that SaaS development is mostly about connections.

A single feature can touch several parts of the system.

For example:

Call
 ↓
Recording
 ↓
Transcript
 ↓
AI Analysis
 ↓
Lead
 ↓
Campaign
 ↓
Deal
 ↓
Revenue
 ↓
ROI

Each step needs reliable data.

If one part of the chain is poorly designed, the final reporting becomes unreliable.

That's why I'm spending a lot of time thinking about the data model and relationships instead of only focusing on the UI.

What's Next?

We're continuing to work on CallRing AI with a focus on:

Better call attribution
AI conversation intelligence
Marketing integrations
CRM integrations
Analytics
Multi-workspace reporting
Lead intelligence
Developer-friendly APIs

The product is still evolving, and that's one of the most interesting parts of building a SaaS product.

You start with an idea.

Then real users, real data, and real problems force the architecture to evolve.

That's the journey we're currently on with CallRing AI.

Track. Analyse. Grow.

Learn more about CallRing AI and follow the journey as we continue building the platform.

What are you building right now?

I'd love to hear about the architecture, stack, or problem you're working on.

Building CallRing AI: Turning Business Calls Into Actionable Data 📞🤖

Ebrahim Manj — Mon, 07 Sep 2026 14:14:03 +0000

As a developer, I’ve always been interested in how we can turn raw data into something businesses can actually use.

One area that still has a huge amount of untapped data is phone calls.

Businesses receive hundreds or thousands of calls, but simply storing call logs and recordings isn't enough. The real value is understanding what happened during those conversations.

That’s why I started building CallRing AI.

The idea is simple:

📞 Track calls from different marketing sources
🎙️ Record conversations
📝 Transcribe calls with AI
🤖 Analyze conversations and extract useful insights
📊 Connect calls with leads, deals, and revenue
🏢 Manage multiple workspaces and teams
🔗 Integrate with tools businesses already use

From the development side, building this has been an interesting combination of:

Laravel & PHP
Livewire
MySQL
JavaScript
REST APIs
VoIP integrations
AI transcription
Stripe
Google APIs
Webhooks & automation

One of the biggest challenges is making all these systems work together reliably — especially when dealing with real-time calls, recordings, webhooks, transcription, and analytics.

The goal isn't just to build another call-tracking dashboard.

The goal is to turn every business conversation into useful data.

I'm continuing to build and improve CallRing AI, and I'll be sharing more of the technical challenges, architecture, integrations, and lessons learned along the way.

What are some interesting problems you've been solving lately?

DevCommunity #Laravel #PHP #AI #SaaS #CallTracking #VoIP #SoftwareDevelopment #WebDevelopment #CallRingAI

Building an AI-Powered Call Tracking Platform: Turning Phone Conversations Into Data

Ebrahim Manj — Wed, 02 Sep 2026 16:57:11 +0000

Phone calls are still an important source of leads for many businesses, but tracking what happens during those calls can be surprisingly difficult.

Forms and website events are easy to measure. Phone conversations are different.

A business may know that someone called, but often doesn't know:

Which marketing campaign generated the call?
Was the caller a qualified lead?
What was discussed?
Was the call converted into a customer?
What was the outcome of the conversation?

This is the problem I wanted to solve with CallRing AI.

What is CallRing AI?

CallRing AI is an AI-powered call tracking and analytics platform designed to help businesses understand the value behind their inbound phone calls.

The basic flow looks like this:

Website / Marketing Campaign
            ↓
      Dynamic Number
            ↓
       Inbound Call
            ↓
      Call Tracking
            ↓
    Recording / Metadata
            ↓
      AI Transcription
            ↓
    Conversation Analysis
            ↓
      Business Insights

Instead of treating a phone call as simply "someone called," the goal is to turn the conversation into structured business data.

The technical challenge

Building a call tracking platform involves much more than receiving a phone call.

The system needs to connect several pieces:

Phone infrastructure
Call tracking
Dynamic number insertion
Call recording
Speech-to-text transcription
AI analysis
Marketing attribution
Analytics
Integrations

For example, when a visitor lands on a website, a dynamic phone number can be displayed based on the visitor's marketing source.

When the visitor calls that number, the platform can associate the call with information such as:

Source: Google Ads
Campaign: Emergency Plumbing
Keyword: emergency plumber
Caller: +1XXXXXXXXXX
Duration: 04:32
Status: Qualified Lead

The conversation can then be transcribed and analyzed using AI.

Why AI makes call tracking more useful

Traditional call tracking tells you things like:

Caller number
Call duration
Time of call
Tracking number
Campaign/source

AI can go further.

A conversation can potentially be analyzed for:

Intent
Lead quality
Topics discussed
Customer questions
Buying signals
Call outcome
Sentiment
Potential revenue

This transforms raw call logs into information that sales and marketing teams can actually use.

Building the platform

For the backend, I'm using technologies from the Laravel ecosystem, with APIs connecting the application to telephony and AI services.

A simplified architecture looks like:

              ┌─────────────────┐
              │     Website     │
              └────────┬────────┘
                       │
                       ▼
              ┌─────────────────┐
              │  DNI / Tracking │
              └────────┬────────┘
                       │
                       ▼
              ┌─────────────────┐
              │ Telephony Layer │
              └────────┬────────┘
                       │
              ┌────────▼────────┐
              │   Call Events   │
              └────────┬────────┘
                       │
          ┌────────────┴────────────┐
          ▼                         ▼
   ┌─────────────┐           ┌─────────────┐
   │ Call Storage│           │ Transcription│
   └─────────────┘           └──────┬──────┘
                                    │
                                    ▼
                             ┌─────────────┐
                             │ AI Analysis │
                             └──────┬──────┘
                                    │
                                    ▼
                             ┌─────────────┐
                             │   Analytics │
                             └─────────────┘

One of the interesting parts of this project is making sure all these asynchronous events remain connected to the same call and customer journey.

The bigger idea

The goal isn't simply to build another call log dashboard.

The bigger idea is:

Every phone conversation contains business data.

If that data can be captured, transcribed, analyzed and connected to marketing attribution, businesses can make much better decisions about where their leads and revenue are coming from.

I'm continuing to build CallRing AI around this idea and exploring how AI can make traditional call tracking significantly more useful.

If you're building something around Laravel, AI, telephony, call analytics, or SaaS, I'd love to hear how you're approaching similar problems.

laravel #php #ai #saas #calltracking #conversationintelligence #webdevelopment #softwaredevelopment