Outbound sales for pharma exporters
The enquiry that gets answered first is usually the one that turns into an order.
Outbound OS pulls your IndiaMART enquiries, WhatsApp messages and email into one queue, drafts the reply in your own language and terms, and keeps the follow-up going until the buyer answers or the lead is closed.
Built for export teams selling into the US, UK and Australia.
The problem
Enquiries do not arrive politely.
They land in four places at once
An IndiaMART enquiry, a WhatsApp message from a buyer who found you on a directory, an email to the sales alias, a form on your site. Nobody owns the whole list, so the same buyer gets two replies or none.
They land at three in the morning
A distributor in Chicago sends an enquiry at the end of their working day. Your team reads it eleven hours later. By then they have written to four other suppliers.
The follow-up is where they die
The first reply goes out. The buyer asks for a quotation. The quotation goes out. Then nothing — and nothing is where most pipelines quietly end, because chasing is the work nobody has time to do consistently.
How it works
One pass, from enquiry to answer.
Each step is visible and reversible. Nothing sends without a rule you set, and every message is attributable to a person or a campaign.
- 01
Intake
IndiaMART enquiries are pulled through their API. WhatsApp and email threads land in the same queue. Duplicates against an existing buyer are merged rather than opened twice.
- 02
Scoring
Leads are ranked on how recently they arrived, what they asked for, and how they have behaved before. Recent, specific, responsive enquiries surface first.
- 03
Drafting
A reply is generated against the buyer’s actual enquiry — the product, the quantity, the market — using your templates and your commercial terms. A person approves it before it leaves.
- 04
Sending
WhatsApp through the official Cloud API, email through your own mailboxes. Sending respects business hours and per-account limits so a number does not get itself blocked.
- 05
Follow-up
Sequences continue on a schedule until the buyer replies. A reply stops the sequence immediately — nobody receives a chase for a message they already answered.
- 06
Pipeline
Every lead sits in a stage a manager can see, with the full message history attached. Stalled deals are visible as stalled, not merely absent.
The workspace
One queue, not six tabs.
Reps work a single inbox across every channel. Managers see the same pipeline the reps do, without asking for a status update.
Capabilities
What the system actually does.
Lead sourcing
IndiaMART enquiries over their API, CSV import, and inbound WhatsApp and email captured as leads.
Lead scoring
Recency, enquiry specificity and past engagement decide the order of the queue, so the day starts with the leads worth working.
Message generation
Drafts written against the buyer’s enquiry and your terms, in your templates, for a person to approve.
Campaigns
Sequenced outreach to a filtered set of leads across WhatsApp and email, with replies pulling a lead out automatically.
Shared inbox
Every channel in one thread per buyer, with the full history and who said what.
Pipeline and reporting
Stages, ownership, reply rates and stalled-deal visibility for whoever runs the number.
It does not send without you
Generated messages are drafts. Approval is a person’s job, and the audit trail records who approved what.
WhatsApp has rules we do not set
Business messaging runs on Meta’s official API. Template messages need approval, and there are limits on what an unsolicited first message can say. We work inside that.
It is not a replacement for knowing your buyer
The system gets the reply out fast and keeps the thread alive. The commercial judgement — pricing, terms, whether a buyer is real — stays with your team.
Where the line is
What this does not do.
Worth knowing before a demo rather than after one.
See it against your own enquiries.
A working session, not a slide deck. Bring a week of real enquiries and we will show you what the queue looks like.