How to track referrals in your CRM

Direct answer

To track referrals properly, record three things in structured fields: where the lead came from as a referral, who referred them, and what has happened since. A note that says "came via John" cannot be reported on or followed up. This checklist covers the fields, how to link the referrer to the person or company that referred them, how to keep the referrer informed, and how to report by referrer. It does not design a referral programme or suggest rewards, and it makes no claim about how many referrals you will receive. It is about recording them well. It also touches on consent, because a referral involves information about at least two people.

What counts as a referral

Decide the definition before adding fields. A referral is usually an introduction made by a named person on behalf of the prospect, not a mention in passing. Write down what counts: a personal introduction, a partner passing on a lead, a customer recommending you. Being clear here stops the referral report from becoming a catch-all. It also settles the overlap with lead source: referral is one source among others, and lead source tracking setup explains how sources fit together.

Fields to add

A small set is enough:

• Source value set to referral, from the same list your other sources use
• Referrer, as a link to a person or company record rather than typed text
• Relationship of the referrer to the prospect or to you, chosen from a short list
• Date of the referral
• Referral status, for example received, contacted, converted or not proceeding

Linking to the referrer record

Store the referrer as a linked record. Then you can open a referrer and see everyone they introduced, and the introduced records point back to the same person. If a referrer is not yet in the CRM, create the record instead of typing a name, and check for an existing one first to avoid duplicates (preventing duplicate leads). Other fields your service business may need are listed in CRM fields for a service business.

Thanking and status updates

Referrers usually want to know what became of their introduction. Decide what you will tell them and when: an acknowledgement when the lead is contacted and a short update when there is an outcome. Only share what the prospect has agreed you may share. A task on the referral record can remind the owner to send it, so it does not depend on memory.

Reports by referrer

Once the referrer is a linked record, a report by referrer becomes possible: who has introduced whom, and what status each introduction reached. Keep it as a view your team can use, not as a ranking. We make no claim about the volume or value of referrals you will see; the report shows what your records contain.

What not to capture without consent

A referral typically involves personal details of someone who did not contact you directly. Record only what you need to follow up, and check that the referrer had the prospect's agreement to pass on their details. Avoid storing personal notes about the referrer or the prospect that they would not expect you to keep. What applies to you depends on your location and industry, and it is a question for your own adviser. Note the consent basis on the record where you can.

Build scope

LATYNEX adds the referral fields, linked record, status and follow-up task to your existing CRM, and a simple view by referrer, with documentation for your team. See CRM and sales workflow implementation for how this is delivered.