GoHighLevel
Partner Pipeline in GoHighLevel
Sample data. Valisthea Psychiatry is a fictional practice, so every name and number is synthetic.
Referral partners start sending patients elsewhere when nobody follows up. I built a GoHighLevel board that tracks each relationship and keeps follow-up from slipping.
1 min
from a card move to the intro email
- The problem
- Referral partners go quiet when nobody follows up.
- The result
- The intro email went out a minute after the card moved, and 10 idle cards became tasks.
What it does
- Each partner is a card on a board with five columns: identified, contacted, meeting held, active partner and dormant. Operations owns every card.
- Move a card to Contacted and the partner gets an intro email: who the practice sees, the insurance it takes and a short ask for 15 minutes.
- 5 days later operations gets a reminder to follow up, unless the partner has already written back.
- Move a card to Meeting Held and the partner gets a thank you with how to send a patient over.
- If a card sits untouched, operations gets a task to contact the partner, move the card or mark it dormant.
What keeps it safe
- The referral email tells partners to call intake or use a secure route, and never to put patient details in a regular email.
- Nothing is sent when a card reaches Active Partner, because nothing needs sending there.
- In the demo the idle check is set to 2 days so I could test it. A real practice would use about 10.
- Demo partners use my own test email addresses, so no real clinic is ever emailed from a demo.
How I tested it
- The intro email reached the inbox about a minute after the card moved.
- 10 untouched cards became 10 idle tasks for operations, all due the next day.
- A card moved straight to Meeting Held got the thank you email, and a card moved to Active Partner sent nothing, as designed.
- The 5 day follow-up task was created with its due date, but I have not yet seen one come due.
Built with
- GoHighLevel
Want one like this for your business?
Tell me what is slowing your team down. I will tell you what to automate, and what not to.