01How it lands
Owner reads the row by hand
A service-manager-owner triages each referral within one business day. They reach out to your peer first; you only loop in if the peer asks who flagged them.
// /refer · peer referral
Pass SecondShift to a peer who’d actually use it.
Service managers who already run on the bench pass SecondShift along when a peer shop is drowning in non-billable callbacks and doesn’t trust AI to ghost-write replies to a homeowner. The clue isn’t the AI — it’s the bench: when the engine is uncertain, a tradesperson returns a signed second opinion. That’s the bit your peer needs to see.
PEER REFERRAL
// 7 fields · 4 read on the desk by handFlag a peer who’d want this on the bench.
Your side is for context; the trade + email fields are what the owner triages on.
What the owner does with a referral
02How it lands
Why we ask for these fields
Three referrer fields (you) are for accountability — the peer hears who flagged them. Four peer fields let the owner open the conversation with the trade, the shop, and the inbox they actually use.
03How it lands
Quiet unsubscribe
One follow-up email if the row goes cold; after that the referral column is closed and the inbox entry is retired. Your name is not in a drip sequence.
// your shop first?
If it’s actually your shop that’s drowning — not a peer’s.
The peer-referral intake isn’t the right shape for a setup-fit. The setup intake is four fields — company, vertical, fleet size, current dispatch software — and an owner calls you back within a day.