Quotes and estimates on WhatsApp: qualified first, priced from your list
"What are your rates?" is not a question a price can answer. Linkubit asks what the price depends on — route, quantity, specification, timeline — before it lets a quote through, prices what it can from your list, hands the rest to your pricing desk as a complete brief, and follows the quote up until it books or says no.
Linkubit answers a quote request within a minute, captures the fields a price depends on, refuses to quote until it has them, prices from your catalogue where a price is listed and hands a complete brief to a person where it is not, sends the quote with the number in the text and a validity date, and follows up until it books.
What it asks for
- What exactly — item, service, specification
- How much — quantity, volume, area, duration
- Where — origin, destination, site, delivery
- When — needed by, and one-off or recurring
- Any constraint that changes the price
- Who else is quoting
None of this is hardcoded. It is a schema you edit, which is why a completely different business runs on the same system.
Qualified before it reaches pricing
The assistant never quotes before it knows what it is quoting
Origin, destination, volume for freight; dimensions and finish for interiors; roof size and monthly bill for solar. The missing field is named and asked for. Pricing gets a real enquiry rather than a one-line question.
- The block is a rule in code, not a hope in a prompt
- Captured fields fill in as the conversation goes
quote_rates blocked — volume not captured yet
Sales Agent
A number is a claim
Prices come from your catalogue, or from a person
A price the assistant states is one you listed. Where the price is a calculation nobody has written down, the enquiry goes to your desk with every field captured, and the assistant sends the quote the desk writes.
- A quoted price is checked against the catalogue before it sends
- The deal opens at the catalogue price, never a number from the chat
Closed won · ₹2.4L
Attribution frozen at closeOpportunity
Mumbai–Jebel Ali lane, weeklyConversation
WAWhatsAppTouchpoint
Click-to-WhatsApp ad, signed tokenCampaign
Meta · Exporters – Gujarat
The rule that holds
The quote tool is blocked until the required fields exist
You mark which fields a price depends on. Until every one is on the record the model cannot reach the quoting tool — it is a rule in code, not a line in a prompt — so a customer who says "just give me a ballpark" gets the next question, politely, not a number that is wrong.
Anything else goes to a person
A topic you named, a value above a threshold, a customer who asks for a human, or a question the assistant cannot answer from what you gave it — the conversation is handed over before a reply is written, with the whole thread and every field captured so far.
From rate request to a booking
What a quote looks like when the qualifying, the chasing of missing details and the follow-up are handled, and a person handles the price.
The request is acknowledged with a reference
"We have your request for X. Reference Q-2214. You will have a quote by 4 pm." The reference is what the customer says on the phone and what your desk searches for.
The fields a price depends on are asked for, once
Everything missing is asked in one message, not three. Quantity, specification, timeline, delivery — the assistant knows which ones your price needs because you marked them.
Listed prices are quoted; the rest goes to a person
A product on your list with a price is quoted at that price. A brief that needs working out lands on your desk as a complete enquiry with a deadline.
The quote goes out with the number in the text
Rate, validity date, what it includes, and 'reply YES to book'. A customer comparing three quotes on a phone reads the message and skips the PDF.
The follow-up until it books
One nudge before the validity date, one after, then a stop. A reply — a question, a counter, a yes — ends the sequence and reopens the conversation; a rate change on the same lane goes only to people who asked about it.
The templates it sends
6 WhatsApp message templates from the industry packs that carry this use case, each written the way Meta's review reads it. Open one for its variables, a filled example and what gets it rejected.
| Template | Category | When it goes out |
|---|---|---|
| Quote request received | Utility | The moment an enquiry arrives, before anyone has priced it. |
| Quote ready | Utility | When pricing has a number and the customer's window has closed. |
| Missing details to quote | Utility | The enquiry cannot be priced — no volume, no commodity, no Incoterm. |
| Itinerary and quote | Utility | Dates, pax and budget are known and the itinerary is priced. |
| On-road price | Utility | Variant and city are known. |
| Estimate | Utility | After a consultation, when the patient asked for the cost. |
Each template opens on its own page with the variables, a filled example and what Meta’s review objects to. Utility and authentication templates cost ₹0.115 a message in India, marketing ₹0.8631 — the pricing guide has the rest.
Questions people ask
Will it invent a price?
No. A price it states is one on your catalogue, and a reply that names a number is checked against the catalogue before it sends. Anything else goes to a person as a brief, and the assistant sends what the person writes.
Our prices are calculated per enquiry. Does it still help?
That is the case it was built for. It captures the fields the calculation needs, refuses to guess, and hands your desk an enquiry that can be priced in one pass rather than three messages later.
Can it send a PDF quote?
Yes, alongside the message. The number stays in the text as well, because a customer on a phone reads the message and skips the attachment.
What if the customer keeps pushing for a ballpark?
It explains what it needs and why, once, and asks again. The block is enforced outside the model, so it cannot be argued past. A rep can always step in and quote by hand.
Read next
Ready to put your sales on autopilot?
Start freeNo coding required. No credit card required.