For general Pipedrive instructions, please refer to Pipedrive’s extensive Knowledge Base.
If you’re working on a client case using Pipedrive or recording some of your Sellai sales activities in Sellai Pipedrive, here are some best practices:
If it’s not in the CRM, it didn’t happen.
All relevant data should be entered into Pipedrive. This includes contact details, communication history, and sales activities.
The CRM system is an organisation’s common memory. Writing down relevant contacts and meeting notes enables us to get more sales. For our clients, it makes the hard sales work visible while they are still waiting for the next deal to close.
What data should I enter in Pipedrive?
Most sales information is listed under Deals in Pipedrive. If you’re unfamiliar with Deals, please review the Pipedrive’s article How is Pipedrive data organized?
In general, a deal should have:
A contact person and their contact information (i.e. phone number, email address).
An organisation (i.e. the company that is related to the deal)
All sales activities and their notes related to that deal
In the deal view, there are also other data fields, such as deal value, expected close date, target market and tags. All this information is not required, but filling them in helps Sellai to better understand its clientele. Important fields are highlighted by Pipedrive.
Check for duplicates
Before creating a new deal, it's always good to run a quick search with the contact person or company name. Chances are that some one else has been speaking to the same company earlier. In general, humans don't like being sold to multiple times over.
If there is a recent discussion (less than three months) with the client, it's always good to check with the deal owner and make sure there is no conflict.
If you find an old deal and it's obviously passive, go ahead and reach out to them. You might find some valuable information in the note and activity history.
Activity durations in Pipedrive
Please refer to the main article here: Activity durations in Pipedrive