The problem
Referral operations cross several identities at once: the registered referrer, the referred prospect, the receiving salesperson and the CRM account. A mismatch in one identifier can detach the lead from the relationship that created it.
The working context
The problem
Referral operations cross several identities at once: the registered referrer, the referred prospect, the receiving salesperson and the CRM account. A mismatch in one identifier can detach the lead from the relationship that created it.
My contribution
I designed and implemented the workflow chain that registered referral users, found the correct account context, created leads, preserved explicit ownership and synchronized updates between operational systems.
I have kept the organisation, product and people private. I also left out exact figures and internal details that could identify the work. The status above tells you how far the implementation actually went.
How I worked through it
If you are working on a similar system, these are the decisions I would examine before choosing tools or adding more automation.
I kept the referrer, referred lead and sales owner as distinct records and roles. That prevented a shared email or contact field from silently changing the meaning of the relationship.
When an approved sales owner already existed, the workflow preserved that assignment instead of allowing a general routing rule to replace it.
Every update needed enough identifiers and response detail to trace what the workflow changed and which system supplied the value.
Expert insights from the work
These are the lessons I took from the work. I would use them as questions for your own implementation, not as a universal recipe.
Do not reduce referral attribution to a source label. Your system needs a durable link between the referrer, the new lead, the account and the commercial owner.
If a workflow can assign or replace an owner, document the exact condition. Hidden routing behavior is difficult for your sales team to trust and even harder to debug.
What I would strengthen
The workflows connected the necessary records, but I would make the relationship easier to inspect without opening several systems. Your operations team should be able to see who referred whom, who owns the lead and where the latest update came from.
Connected disciplines
Continue through the work
If this overlaps with a system you are thinking through, start a relevant conversation.