How can we help?

Open the new-enquiry screen, choose the customer, and add the enquired item lines with quantity, drawings and any specifications, then record the enquiry source. The system creates an auto-numbered enquiry document at the Enquiry Received status. Because it is a real commercial document, its item lines and references carry straight through to the quotation and order with no re-keying. See Lead & Enquiry Capture.

A lead is a raw prospect captured before qualification — a name, a company and an interest. An enquiry is a qualified request for a quote, with the specific items and quantities the customer wants priced. Qualified leads become enquiries, and the enquiry is the document that enters the estimation-and-quotation pipeline. See Lead & Enquiry Capture.

Every enquiry advances through a defined lifecycle: Enquiry Received (31), Under Feasibility (32), Under Estimation (33), Quotation Sent (34) and Order Received (35), with an Enquiry Regretted (36) path for enquiries that will not be pursued. The current stage is stored on the document and every transition is kept in its status history, so nothing sits in an inbox unaccounted for. See the pillar guide.

Leads can be entered on the desk screen or on a mobile-friendly capture form, so a salesperson can log a prospect from an exhibition stand or a site visit without waiting to get back to the office. Each lead carries its source and owner, and qualified leads convert into enquiries that keep the reference back to where the interest began. See Lead & Enquiry Capture.

Each enquiry records how it arrived — referral, campaign, website, exhibition or an existing customer — against a reference type. That lets you run source-wise conversion reporting to see which channels actually turn into orders, not just which generate the most enquiries, so marketing spend follows the sources that close. See Lead & Enquiry Capture.

Yes. A web enquiry form can push submissions straight into the pipeline as enquiry documents, and WhatsApp automation can turn an inbound message into a captured enquiry and send quote and order updates back out. Either way the enquiry lands as a real document ready to be estimated and quoted. See WhatsApp Automation.

After capture, an enquiry is assessed for feasibility and then costed by building an estimation structure against a BOM/BOR — the same engine the factory uses. The estimation rolls up material and process cost so the quoted price is derived from real numbers, and a techno-commercial review can finalise it before the quote goes out. See Feasibility & Estimation.

Raise a quotation referencing the source enquiry, so the items and context carry over. Configurable quotation parameters set the commercial terms and text that print on the quote, and sending it moves the enquiry to the Quotation Sent status. From there it sits on the quotation follow-up dashboard until the customer decides. See Quotation Management.

A quotation is versioned: when price or terms change, a revision is raised that preserves the earlier version rather than overwriting it, so the negotiation history stays intact. Each quote is gated by an approval step before release, and a comparison view lines up revisions or competing options side by side so the right one is chosen with the numbers visible. See Quotation Management.

When a quotation is won, it converts into an Order Acceptance — the confirmed customer order — and the enquiry reaches the Order Received status. The order can be created directly or imported from the winning quotation, so the items, rates and terms flow through without re-entry. This order is the handoff document to production and billing. See Order Acceptance.

An order acceptance moves through a controlled workflow — it is checked, then released, then completed — so a confirmed order is verified before it is acted on downstream. Order priority and execution can be set and changed, and the released order is what production plans against and billing invoices. See Order Acceptance.

Yes. Sample orders and tooling orders are tracked as order-acceptance sub-types, each with its own follow-up dashboard — useful for automotive and NPD work where a sample or tool has to be approved before series production is quoted. They follow the same check-release-complete discipline as a standard order. See Order Acceptance.

One follow-up screen is parameterised by document type, so the same dashboard chases each pipeline stage — open leads, open enquiries, sent quotations awaiting a decision, and confirmed orders in progress. An order-status roll-up and a payment follow-up view sit alongside it, so a manager can see the whole funnel and what is ageing in one place. See Follow-up & Customer 360.

Every follow-up captures a note and the next action with a due date against the open lead, enquiry, quotation or order, and the full follow-up history stays attached to the document. Calls placed through the integrated telephony log automatically too, so the record shows exactly what was said and when the next contact is due. See Follow-up & Customer 360.

Conversion analytics compare enquiries against orders and break the funnel down reference/source-wise and salesperson-wise, so you can see which sources and which people convert. A sales dashboard rolls up the KPIs and funnel. It turns the pipeline from a feeling into a number you can manage. See Dhruv AI Analytics.

Tasks are entered and allocated to a team member with a priority, due date and a status workflow, and each task links back to a customer, enquiry, order or document so it never floats free. Task action, current status and due date are updated as work progresses, and reason codes explain delays. See Tasks, Calls & Activities.

Yes. A drag-and-drop kanban board moves tasks across status columns — to-do, in-progress and done — and a team task view shows the whole group's load. A calendar places task groups by date with an all-user status view, and task dashboards and graphs summarise what is open, done and overdue. See Tasks, Calls & Activities.

A telecalling view lists today's and pending calls with click-to-call and outcome codes such as lead received, not interested or transfer, against call targets. Field visits are planned with a priority, activity, client name and location, and a visit report captures what happened. Sales targets track it all against plan. See Tasks, Calls & Activities.

Customer 360 is the party-centric view built on the shared customer master. From one screen you see a customer's contacts, addresses, references, notes, agreed item rates and full document history — every enquiry, quotation and order they have ever had — so a salesperson picks up any account with the whole relationship in front of them. See Follow-up & Customer 360.

The customer record holds agreed item rates and discounts, so a quotation can pull the right price for that customer automatically, plus party references, contact groups and free-text notes. Customers can go through an approval step before they are used, keeping the master data clean. See Follow-up & Customer 360.

Fast CRM integrates cloud IVR and click-to-dial. Inbound calls route and log automatically against the customer's enquiry, order or ticket, and outbound follow-up calls dial straight from the record. Calls surface on the follow-up and service dashboards, tying every conversation to the party and the deal — no separate call log to reconcile. See Telephony & IVR.

The released order acceptance is the handoff artifact. Fast Production and Fast ERP consume it as the order to plan and build — generating process sheets and work orders against it — and Fast Billing invoices and dispatches against the same order. Because it is one platform on one shared customer and document chain, the enquiry a salesperson captured becomes the order the factory builds with zero re-entry. See Fast ERP & Billing.

Dhruv AI is our AI and BI layer for sales. It adds role dashboards over live pipeline data with AI insight summaries, answers plain-English questions through a safe read-only query sandbox restricted to whitelisted views, and clusters enquiry and feedback remarks into named recurring themes — so patterns in why deals are won or lost name themselves. See Dhruv AI Analytics.

Both. Fast CRM is normally licensed with Fast ERP and Fast Billing — the order it produces is the order the factory builds and invoices — but it can also run as a standalone sales-office deployment that hands orders to an external ERP. It deploys cloud or on-premise, and suits manufacturers of every kind, across India and worldwide. See the integrations overview.