Keep the next sales conversation from starting over

At a glance

Frappe ERP's core CRM records include Leads and Opportunities, with conversation context, assignment and a route to quotations. Use those records to make the next sales conversation informed rather than repetitive. This guide covers CRM within the ERP, not the separate Frappe CRM application, and does not assume the applications have identical features or data models.

Start with the handover

A prospect calls back while the salesperson who spoke to them is on leave. The colleague answering can find an email address but not the delivery constraint discussed yesterday. The prospect repeats the requirement, and the team sends another introductory message instead of answering the question already on the table.

Frappe's core Lead documentation includes notes, comments and communication records, with assignment to a user. Those give the sales team a place to preserve context for the next person. The useful improvement is a specific conversation that can continue without depending on one person's memory.

The official sources cited here describe version 13 of the ERP's CRM records. Check the fields, reminders and communication setup available in your chosen ERP release. Do not borrow a feature demonstration from the standalone Frappe CRM app and assume it proves the same behavior here.

Keep the useful context

Record the reason the person contacted you. A note that says interested gives a colleague almost nothing to work with. A note describing the required product and the unresolved delivery question tells them what to prepare before replying.

The Lead documentation supports multiple contacts and addresses, as well as notes and events. Use that structure to distinguish the purchasing contact from the person evaluating the requirement. Keep their roles clear so a technical response goes to the person who can assess it rather than another colleague who must forward it again.

Avoid collecting detail merely because a field exists. Agree which information is needed for follow-up and restrict access appropriately. A shared sales record should improve continuity without becoming a place for unrelated personal information or private commentary that would be difficult to justify to the customer.

Give the next action away

A lead owned by everyone is easy to leave untouched. Assign responsibility for the next action, with enough detail that the person can complete it. Send specification sheet after confirming compatibility is a different task from call customer, and the distinction affects what must happen before contact.

Frappe's documented core Lead and Opportunity records include follow-up fields and assignment features. Confirm the reminder mechanism on your release and test its notification setup. The existence of a date in a record does not prove the intended salesperson receives or sees a reminder at the right time.

Include absence cover in the routine. A manager should be able to identify work awaiting an unavailable colleague and reassign it with the existing context intact. Do not solve the handover by creating a duplicate lead, which can leave two people following up separately and neither seeing the other's conversation.

Qualify a real opportunity

Frappe describes an Opportunity as a qualified lead and allows opportunities against existing customers as well as leads. That is useful for repeat business: another buying requirement need not become an unrelated contact record just because the customer is considering a new purchase.

Agree what qualified means for your team. A genuine requirement with an identified next decision is different from somebody downloading a brochure. The point is not to impose a complicated scoring scheme; it is to keep the working pipeline focused on conversations that have a business reason to continue.

Use the opportunity to describe the requirement and the unresolved condition. If the customer is waiting for an internal budget decision, say so. Do not record a firm expected order date merely because the sales review requires every row to contain a date. Your pipeline should preserve uncertainty where the customer has not made a commitment.

Follow up with something useful

Prepare the reply around the last conversation. If the customer asked whether a part can arrive before a shutdown, a general company introduction is not progress. The salesperson should confirm the delivery assumption with operations and return with the information needed for the customer's next decision.

Frappe documents creating a Quotation from an Opportunity, carrying relevant values forward. Use that route once the offer is ready, while checking that the quotation reflects the latest discussion. A linked document is helpful continuity; it is not permission to skip a commercial review of price or scope.

Respect a request to stop contact. The core Lead documentation includes a Do Not Contact status. Your process and any connected outreach tool must honor the customer's instruction. A status label by itself is not a guarantee that every external messaging system has been updated.

Review promises, not activity

Worked example, hypothetical and not an ERPNova result: a team schedules 24 follow-ups and completes 18 by the agreed date. That is a 75% completion rate, leaving six follow-ups unresolved. It is a work-management measure, not a conversion rate or evidence that the contacts produced revenue.

Review the unresolved work for its cause. Some tasks may need a technical answer before the salesperson can respond. Others may have an unrealistic date or no clear owner. Counting messages sent will not reveal which customer decisions remain blocked.

The Opportunity documentation includes recording reasons for lost opportunities. Use a brief, specific reason when the conversation ends. Keep no decision distinct from an explicit rejection where that distinction helps your sales review. A lost record should teach the next reviewer something without inventing certainty about a customer's private reasoning.

Bring ERPNova an anonymized lead handover and a typical quotation request to an ERP audit. Ask us to demonstrate the core ERP records, a follow-up with absence cover and the transfer into a quotation. Our quote-to-cash guide follows the next stage, when the customer accepts the offer and operations takes responsibility for delivering it.