one project, every enquiry answered
A developer selling one or two towers has a narrow problem: every enquiry is about the same inventory, and almost every enquiry asks the same six questions. Metrik is configured against that inventory, answers those questions in the language the lead used, and only involves the sales team once there is a requirement worth their time.
inside the call
metrikNamaste, main Metrik se bol raha hoon — aapne is project ke liye enquiry ki thi. Do minute baat kar sakte hain?
leadHaan boliye.
metrikAap 2BHK dekh rahe hain ya 3BHK?
lead3BHK, but budget thoda tight hai.
metrikSamajh gaya. Roughly kitna soch rahe hain?
sample conversation · hinglish · not a customer recording
the challenge
Project enquiries arrive in bursts — after a hoarding goes up, after a portal listing refreshes, after a weekend campaign. The sales team is either on a site visit or on another call, so the enquiry sits until someone gets to it. By then the lead has spoken to three other projects.
The second problem is repetition. Configuration, carpet area, floor rise, possession date, payment plan: the same questions, dozens of times a day, answered slightly differently by whoever picks up. That inconsistency shows up later as leads who were told something the project cannot deliver.
the strategy
Metrik is loaded with the project as the sales team describes it — configurations, price bands, possession status and the answers to the questions that actually get asked. The agent calls the enquiry back while it is still warm, opens in the language of the enquiry, and answers within that boundary.
What it will not do is improvise. If a question falls outside what the project data supports, the agent says so and flags it for the salesperson instead of guessing.
the conversation
The opening turn identifies Metrik, references the enquiry and asks for permission to continue. That is the whole preamble — there is no menu, no keypad and no hold music, because every second before the first real question is a second the lead spends deciding to hang up.
From there the agent follows the property journey rather than a form. If the lead leads with budget, budget is where the conversation starts. If they switch from Hindi to English mid-sentence, the agent switches with them and stays switched.
the requirement
Configuration, budget range, possession preference, buying timeline, purchase intent and site-visit interest come out of the call as fields. Not a summary paragraph — fields, the same ones on every call, so a desk can sort and filter across them.
Ranges are preserved as ranges. "Around 90 lakhs, thoda upar ja sakte hain" is not rounded to a number; it is stored as a band with the flexibility noted, because that flexibility is the part a salesperson negotiates against.
the handoff
For a single-project deployment the routing question is simple: which member of the project sales team owns this lead. Assignment rules answer it, and the handoff lands on WhatsApp with the requirement summary and the requested next action.
The full transcript sits behind the summary. Nobody has to listen to a recording to find out what was already asked, which is the difference between a handoff and a forwarded lead.
outcome
The sales team stops being the first responder and becomes the second. Every enquiry still gets a call, in the language the person is comfortable in, with consistent answers about the project — and the team spends its day on the conversations that already have a requirement attached.
Everything the agent said is on record, turn by turn, with the routing decision and the cost of the call beside it.