03 · Referral Performance

When the intake operating system determines a matter is out of scope, it generates a unique referralId and posts a structured handoff payload to the vetted partner via webhook: matter type, jurisdiction, urgency score, and client consent token. The handoff is timestamped and logged against the originating conversation.

As the matter progresses, the partner's system POSTs outcome events back to MB's webhook endpoint: client.engaged → matter.opened → matter.closed, each with a structured payload (outcome type, date, optional settlement value). Partners without API capability can use an email-triggered link or a simple partner portal form.

At matter close, MB — not the partner — triggers a satisfaction survey to the client, using the referralId to attribute the response. This keeps the NPS signal independent of the partner relationship and attributable back to the referral source, pathway, and originating intake channel.

All outcome events flow into the operating dashboard you're viewing now. Revenue, engagement rate, satisfaction, and outcome type are attributed to the originating referral source, partner, and matter type. This is the "closed loop" — the source of the data above.