SRMB Steel: Building India's Infrastructure, One TMT Bar at a Time
SRMB Steel is one of India's most recognized names in TMT rebars and structural steel, with a legacy built on serving the country's construction and infrastructure sectors. Their customer base is genuinely diverse, spanning large enterprise buyers placing bulk procurement orders, distributors and dealers managing regional supply chains, contractors and project managers sourcing steel for active sites, and individual buyers purchasing retail quantities.
This diversity is a strength, but it also demands a level of operational sophistication that a single, one-size-fits-all communication approach simply can't deliver. Each customer segment has different information needs, different buying signals, and different expectations from every interaction.
Steel Manufacturing & Distribution
Enterprise Buyers, Distributors, Contractors, Retail Individuals
Clicky (In-House) + Order and Dispatch (Separate)
10 callers, ~80 calls/day, Tata Dialer with 10 channels, 6 days/week
A Sales Operation Built to Grow, Ready for the Next Level
SRMB's inside sales team was doing solid work. Ten callers running approximately 80 calls a day, six days a week, across a Tata dialer with ten active channels. For a company managing multiple distinct buyer profiles simultaneously, this was a team that clearly knew what it was doing.
But certain realities were becoming harder to ignore. The sheer breadth of the customer base, each segment with its own conversation flow, qualification criteria, and CRM classification, meant the cognitive load on callers was significant. There was also a genuine opportunity to handle inbound queries, order status checks, invoice questions, and dealer communications at far greater volume and consistency than a ten-person team could realistically sustain. The question wasn't whether the team was good enough. The question was how far automation could carry the routine work, so the human callers could focus where it genuinely matters.
Scaling Call Volume Beyond 10 Channels
With a fixed dialer infrastructure and fixed headcount, outreach volume had a natural ceiling. Rootle's own infrastructure removed that ceiling entirely by deploying multiple numbers to handle scale without adding a single agent.
One Workflow for Five Different Caller Profiles
Enterprise buyers, distributors, contractors, retailers, and individuals each needed a distinct conversation path, qualification logic, and CRM entry. Standardizing this manually across callers was inconsistent by nature.
CRM Data Quality and Classification
Every call outcome needed to land in Clicky with the right classification, correctly tagged by segment and intent. Manual logging introduced variance that was hard to correct downstream.
Inbound Call Handling at Scale
Order status inquiries, invoice queries, and dealer support were coming in regularly. Having the sales team absorb inbound volume was an opportunity cost, not a sustainable model for growth.
Three Use Cases. One Intelligent Voice Layer.
Rootle designed and deployed a multilingual Voice AI system for SRMB built around three distinct use cases, each with its own conversation logic, qualification flow, and CRM sync behavior. All three ran on Rootle's own infrastructure, with multiple numbers assigned to handle volume without the constraints of a third-party dialer.
Lead Prequalification Across Five Buyer Types
SRMB's incoming leads aren't homogeneous. A distributor asking about bulk pricing and an individual buyer asking about retail quantities need conversations that feel entirely different, because they are. Rootle built a dynamic qualification flow that identifies the prospect's segment early in the conversation and then branches into the appropriate script, tone, and question set automatically.
Every qualified lead is logged in Clicky with the correct segment classification, buying intent, and conversation summary. No manual tagging. No post-call data entry delays. The CRM record is clean from the moment the call ends.
Segment detection in the first 30 seconds of conversation
Separate qualification criteria per buyer type
Auto CRM entry with classification and outcome tagging in Clicky
Consistent call quality regardless of time of day or caller load
Segment-Specific Call Workflows for Every Prospect Type
Beyond prequalification, SRMB needed fully differentiated outreach workflows for each of its five customer segments. An enterprise procurement conversation follows a very different cadence than a contractor inquiry or a retail buyer asking about local availability. Rootle built each workflow separately, not as variations of a single template, but as distinct conversation designs shaped around what each buyer actually cares about.
Dealer communication for gifts, loyalty programs, and events got its own flow too, keeping SRMB's channel relationships warm without pulling the sales team away from active lead work. Each interaction is still logged to Clicky with the right flags, so the sales team knows exactly where every contact stands without reading call notes.
Distinct workflows for B2B enterprise, distributors, contractors, retail, and individuals
Dealer communication flow for events, gifts, and channel engagement
CRM entries classified correctly at segment level, no manual review required
Sales team receives warm, pre-context handoffs for every follow-up
Inbound Call Handling for Order Status and Support Queries
Inbound call volume at SRMB covers a lot of ground. Customers and dealers call to check order status, ask about invoices, follow up on pending deliveries, and seek general support. These are legitimate, important calls, and handling them well builds trust. But routing every inbound query through the same sales team handling active outreach wasn't an efficient use of anyone's time.
Rootle's inbound layer handles these calls end to end. The Voice AI answers, identifies the caller's intent, pulls relevant details from the Order and Dispatch system where needed, and responds accurately. For anything requiring human judgment, it routes to the right person with context already in hand. The Clicky CRM is updated on inbound interactions as well, keeping the full customer communication record in one place.
24x7 inbound handling for order status and invoice queries
Integration with Order and Dispatch for real-time query resolution
Smart escalation with full context to the right team member
Inbound interactions logged to Clicky automatically alongside outbound records
Hindi, English, and Bengali. In One Deployment.
Steel is sold across geographies and communities that don't share a single language preference. SRMB's customer base spans Hindi-speaking markets, English-comfortable corporate buyers, and Bengali-speaking regions where natural, local-language conversation isn't a nice-to-have but a commercial necessity.
Rootle's Voice AI handles all three natively, not through literal translation, but through conversations built to feel right in each language. A contractor in Bengal gets a conversation that sounds like a local call. An enterprise procurement head gets the tone and vocabulary they'd expect in a professional B2B exchange. The language adapts. The quality of the interaction doesn't change.
Built on Rootle's Own Infrastructure, Not a Dialer Dependency
One of the important decisions in this deployment was stepping away from a third-party dialer as the primary calling infrastructure. SRMB's earlier setup ran on a Tata dialer with ten channels, which created a hard ceiling on concurrent call capacity. Rootle replaced this with its own calling infrastructure, assigning multiple numbers to handle the volume SRMB actually needed to reach.
This shift also removed the per-channel constraint on outbound scale. When campaign volume increases or new use cases get added, SRMB isn't waiting on a dialer configuration change or license expansion. The infrastructure grows with the requirement.
The SRMB Voice AI Call Flow
Every call, whether it arrives inbound or goes out as part of a campaign, follows a structured path. The AI detects who it's speaking with, switches to the right language, follows the appropriate conversation flow for that buyer type, and closes the loop with an automated CRM entry. Here's what that looks like end to end.
Call Connected. Conversation Begins.
Bulk procurement, pricing, supply terms
Regional supply, channel programs, events
Project needs, delivery timelines, site specs
Stock availability, local pricing, smaller orders
Retail quantities, basic product guidance
Lead Prequalification
- Qualify purchase intent and timeline
- Capture volume requirements
- Assess buying authority
- Score and tag lead in Clicky
- Route hot leads to sales team
Segment-Specific Outreach
- Follow segment conversation script
- Dealer gift and event communication
- Contractor site delivery discussion
- Retail pricing and availability
- CRM entry with segment classification
Inbound Support
- Greet and identify caller intent
- Query Order & Dispatch system
- Resolve order and invoice queries
- Escalate complex cases with context
- Log full interaction to Clicky
Handed to sales with full conversation context
Auto-classified, zero manual entry required
For cases that need human follow-up
Inbound queries closed without human agent
What Changed After Rootle Went Live
The changes SRMB experienced weren't incremental adjustments to an existing operation. Deploying Rootle across three use cases simultaneously, with multilingual support and two-system CRM integration, restructured how the sales and support function actually works.
Call Volume Capacity
Without adding a single agent or dialer channel
CRM Entry Accuracy
Every call logged and classified automatically in Clicky
Languages Live on Day One
Hindi, English, and Bengali from a single deployment
Buyer Segments, One System
Enterprise to retail, each with its own conversation flow
Inbound Coverage
Order and invoice queries handled round the clock
Manual Post-Call Logging
Sales team time redirected to conversations that need them
"What made the Rootle deployment genuinely different was that it didn't ask us to simplify our customer operation to fit the technology. It handled the complexity we actually have: different buyers, different languages, two systems, and both inbound and outbound in the same platform."
Sales Leadership, SRMB Steel
Complexity Handled, Not Avoided
Most Voice AI deployments struggle when the customer base isn't uniform. SRMB's diversity, five buyer profiles across B2B and B2C, three languages, two backend systems, and both inbound and outbound requirements, is exactly the kind of scenario that exposes the limits of a plug-and-play solution.
Rootle's approach was to design workflows that match how SRMB actually operates rather than ask SRMB to operate the way a generic system expects. Each buyer segment got its own conversation logic. Each language got its own natural speech design. The CRM integration was built to classify correctly from the start, not to push raw data and let someone sort it out later.
The result is a Voice AI layer that the sales team actually relies on, because it reflects their business accurately, speaks to their customers naturally, and keeps their data clean without any extra effort on their end.



