Refractory and insulation suppliers in India use the WhatsApp Business API for three jobs that email keeps losing: confirming a plant's shutdown window, turning a BOQ into a priced quote inside a day, and handling lining-life complaints with photos attached to the right heat number. The setup is a verified business number, six to eight approved templates and a shared inbox for your sales and service team — no per-seat licence and no minimum spend.
This is a working guide, not a pitch. If you sell castables, bricks, ceramic fibre, calcium silicate, mineral wool or pre-cast shapes to steel plants, cement lines, glass tanks, boiler houses or foundries, the sales cycle already lives on WhatsApp. What is usually missing is the discipline: a business number instead of the area sales manager's personal SIM, templates that survive a staff change, and a record you can pull up eight months later when a customer says the lining failed early.
Why refractory selling already runs on WhatsApp
Refractory demand is event-driven. A cement kiln takes an annual shutdown, a steel ladle gets relined on a cycle, a reheating furnace gets patched between campaigns. The buying decision is made by a maintenance head or a plant engineer who is standing on site, often in a helmet, often with poor desk time. They are not going to open an ERP portal to raise an enquiry. They will send a photo of a spalled wall and ask for a rate.
The problem is what happens next. On a personal number the enquiry sits with one salesperson. If that person is on leave, travelling, or resigns, the thread and the relationship go with them. On a WhatsApp Business API number, the same conversation lands in a shared inbox that your commercial head, your technical service engineer and your dispatch clerk can all see — and it stays in your account when the salesperson leaves.
That is the honest reason most suppliers move. It is not automation for the sake of it; it is getting the customer relationship off a private phone. The same logic drove industrial valve manufacturers and brick kiln operators onto the API.
The five conversations that decide a refractory order
Map your automation to these five and you cover most of the volume. Anything beyond this is decoration.
| Conversation | Who starts it | What must go back | Automatable? |
|---|---|---|---|
| Shutdown window confirmation | You, ahead of the plant's planned outage | Dated reminder, site engineer's name, material readiness status | Yes — scheduled utility template |
| BOQ or drawing to quote | Customer, usually with a photo or PDF | Acknowledgement in minutes, priced quote in hours | Partly — auto-acknowledge, human prices |
| Despatch and lorry receipt | You, at despatch | Invoice, LR number, expected arrival, driver contact | Yes — fully automated from ERP |
| Installation and supervision booking | Customer, close to shutdown | Engineer allocation, arrival date, scope confirmation | Partly — slot options automated, allocation human |
| Lining-life complaint or warranty claim | Customer, months later | Structured intake: photos, batch, install date, operating data | Yes — guided intake flow, human verdict |
Notice that only two of the five are things you send cold. The rest are replies. That matters for cost, and we will come back to it.
Shutdown scheduling: the window nobody can miss
A cement plant that told you in March that its kiln stops in November expects you to remember in September. Most suppliers rely on a salesperson's diary. That is how orders leak to a competitor who called first.
The fix is dull and effective. Keep a field on each plant record for the expected shutdown month, and fire a utility template at a fixed lead time — typically eight weeks out for imported or long-lead items and four weeks for stock castables. The message should carry the plant name, the expected window, and one question that is easy to answer on a phone: is the window still holding?
Two useful habits:
- Send to two people, not one. The maintenance head approves, the purchase officer executes. If only one is on the thread, the other will call you anyway.
- Log the reply as data, not chat. A reply saying the outage shifted to December should update the record, not just sit in a message. Otherwise you are back to relying on memory.
Suppliers who have sequenced this properly describe the same result: fewer scrambles in the last fortnight, and a materially better chance of being asked to quote before the enquiry goes out to three vendors.
BOQ to quote without the email chain
A BOQ arrives as a PDF, a photograph of a typed sheet, or a WhatsApp voice note listing shapes and quantities. The failure mode is not pricing — it is the twelve hours before anyone acknowledges receipt.
Build the flow in three steps:
- Auto-acknowledge inside the 24-hour service window. A free-form reply confirming receipt, naming the engineer who will price it, and stating when the quote will land. This costs nothing extra because the customer opened the conversation.
- Route by product family. Castables and gunning mixes to one desk, bricks and pre-cast shapes to another, insulation and fibre to a third. Routing in the inbox beats forwarding screenshots.
- Send the quote back on the same thread as a PDF. Not as an email the plant engineer will read three days later on a desktop.
If your enquiries are structured enough, a guided form can collect furnace type, operating temperature, atmosphere, existing lining and area before a human sees it. That is the same pattern used for B2B RFQ automation, and it removes most of the back-and-forth that makes a two-day quote out of a two-hour one.
Technical documents: what you can and cannot send
Refractory sales are document-heavy — data sheets, installation procedures, safety sheets, test certificates, drawings. WhatsApp handles documents well, with some real limits worth planning around.
| Document | Practical approach | Watch out for |
|---|---|---|
| Product data sheet | PDF attached to the reply, or a template with a document header | Keep file size modest; site connectivity is often poor |
| Safety data sheet | Same, but send proactively with the first despatch | Do not treat a WhatsApp send as your only compliance record |
| Test or batch certificate | Attach against the specific despatch, name the file with the batch | Unnamed scan files are unfindable six months later |
| Installation drawing | PDF; for large drawings send a link to your own portal | Photos of drawings lose dimensions — send the file |
| Voice notes from site | Accept them, transcribe into the record | A voice note is not an order confirmation |
One caution on standards and specifications: quote the exact IS, ASTM or customer specification your product is actually tested against, taken from your own certificate. Do not let a chatbot generate a specification claim. A wrong standard reference in writing is a commercial liability, and it is the easiest way to lose an argument during a claim.
Get a 1-minute BSP audit on WhatsApp
Drop your WhatsApp number — we line-item your current invoice against Meta India rates in under 60 seconds. India-hosted, DPDP-compliant.
Lining-life claims: structure the intake, not the verdict
This is where WhatsApp earns its keep. A claim usually arrives as an angry message with two blurry photos and no context. Eight weeks of email follow, establishing what should have been captured on day one.
Use a guided intake that asks, in order, for: the plant and furnace, the material and batch or heat number, the installation date, the observed hours or campaigns achieved, operating temperature and atmosphere if known, the failure mode in the customer's words, and finally three photos — overall, close-up, and the adjacent sound area for comparison.
The automation stops there. A technical service engineer decides whether it is a product issue, an installation issue, a dry-out issue, or an operating excursion. Never let a bot express a view on liability. What the bot does is guarantee the engineer is never missing the basics, and that everything is timestamped in one place.
Two side benefits fall out of this. You accumulate a comparable dataset on real lining life by furnace type, which is genuinely useful for the next tender. And when a claim is unreasonable, you have a dated record rather than a recollection.
What it actually costs in 2026
Indian refractory suppliers are usually surprised by how small the messaging bill is, because the traffic is low-volume and high-value. A supplier with 400 active plant contacts might send a few thousand messages a month, not a few hundred thousand.
Cost has two layers: what Meta charges per conversation, and what the platform charges you to sit on top of it. On RichAutomate there is no setup fee and no monthly subscription — you pay only for usage, on one of two models.
| Model | Setup | Monthly | Per message | Suits |
|---|---|---|---|---|
| Client Pay | ₹0 | ₹0 | ₹0.10 platform fee; Meta bills you directly | Suppliers who already have a Meta billing account and want the lowest all-in cost |
| SaaS Pay | ₹0 | ₹0 | ₹1.20 marketing · ₹0.30 utility | Suppliers who want one consolidated Indian invoice and no Meta billing setup |
The commercially important point for this sector is the split between categories. Shutdown reminders, despatch notifications, claim acknowledgements and document sends are utility conversations — the cheap kind. Genuine promotion, such as announcing a new low-cement castable to plants that have not enquired, is marketing. Most refractory suppliers find their traffic is overwhelmingly utility and service, which keeps the monthly bill in the low hundreds or low thousands of rupees.
Free-form replies inside the 24-hour service window after a customer messages you carry no conversation charge from Meta. Since most refractory traffic is a reply to a plant engineer who messaged first, a large share of your real conversations cost nothing beyond the platform fee.
Templates that get approved
Template rejection wastes days. The pattern that passes is specific, transactional and free of sales language. Below are shapes that work for this sector — write your own copy, but keep the structure.
| Purpose | Category | Shape that passes |
|---|---|---|
| Shutdown reminder | Utility | Names the plant, the recorded window, asks for confirmation. No offer, no discount. |
| Quote sent | Utility | References the enquiry, states quote number and validity, attaches the PDF. |
| Despatch notification | Utility | Invoice number, LR number, quantity, expected arrival. |
| Supervision engineer allocated | Utility | Engineer name, reporting date, scope line. |
| Claim acknowledged | Utility | Reference number, engineer assigned, next step and date. |
| New product announcement | Marketing | Short, one product, clear opt-out. Send only to plants that have transacted. |
Two rules prevent most rejections: never put a price or a discount inside a utility template, and never write a template that could be sent to someone who has no relationship with you. If you would not be comfortable explaining the message to the recipient's manager, it will probably be rejected — and if it is not, it will be reported.
A 30-day rollout that does not stall
Suppliers who try to automate everything at once usually ship nothing. The sequence that works is narrow first.
- Week 1 — number and inbox. Get the business number verified, migrate the sales team into a shared inbox, stop new enquiries going to personal SIMs. Nothing else.
- Week 2 — despatch notifications. The easiest win: it is fully structured, it comes from data you already have, and customers immediately notice.
- Week 3 — enquiry acknowledgement and routing. Auto-acknowledge, route by product family, measure how long quotes actually take.
- Week 4 — shutdown reminders and claim intake. These need clean plant records, which is why they come last.
Insulation-only suppliers — mineral wool, calcium silicate, ceramic fibre, LRB mattresses — can compress this, because the despatch and enquiry patterns are simpler and the claim volume is lower. The same staged approach works across adjacent industrial trades, from job-shop metal finishing to broader manufacturing supply chains.
What to measure after 90 days
Four numbers tell you whether this worked. Everything else is vanity.
- Enquiry-to-quote time. Measured in hours, not days. This is the number that wins shutdown orders.
- Percentage of shutdown windows confirmed in advance. If it is not rising, your plant records are stale, not your messaging.
- Claims with complete intake on day one. A claim that needs three rounds of questions costs you an engineer-week.
- Enquiries arriving on the business number versus personal numbers. If personal numbers are still dominant, the rollout has not actually happened.
None of this requires a large team. A refractory supplier with two commercial people and three service engineers can run the whole thing, because the automation handles the repetitive sends and the humans keep the technical judgement where it belongs.