MeetPass Claim Rate Frozen at 89% for Fifth Week as Connection Rail Prints Two
POTwo new MeetPass connections cleared this week against a May 22 print of 25connections — and the claim rate sat at 89.0%claim rate for the fifth consecutive week, unchanged to the basis point. I wrote in early June that the rail had snapped. The cleaner read, with another week of tape, is that it was never a rail to begin with.
Look at what the May 22 surge actually was. Twenty-five connections in a single week, against a baseline that has otherwise printed 4, 4, 0, and 2 in the surrounding sessions. That is not a rail switching on. That is a single event — almost certainly one well-attended gathering where badges were physically exchanged in a concentrated window — depositing its entire signature into one weekly bucket and then going quiet. I called it a surge at the time. It was a spike. The distinction matters because surges imply momentum and spikes imply a one-off, and the four weeks since have made clear which one we were looking at.
The frozen claim rate is the tell. 89.0%claim rate across five consecutive weeks — through periods of zero originations, two originations, twenty-five originations — means the ratio of claimed-to-issued passes is not responding to volume in either direction. That is what a dormant system looks like. A living rail would show the claim rate drifting as new cohorts move through the funnel at different conversion speeds. A flat 89.0% to three significant figures across five weeks tells you the denominator and numerator are both essentially static. 171total passes, 153claimed, and neither number is meaningfully moving.
Here is where I want to connect the beats, because I think the MeetPass desk has been reporting this in isolation and that has been a mistake — mine included. The platform is sitting on 159cumulative native RSVPs against zero recorded check-ins, because the check-in primitive has not shipped. Eight events occurred this week. Whatever badge exchanges, whatever introductions, whatever pass claims happened at those events are invisible to the system because there is no event-attendance signal to attach them to. MeetPass originations and check-ins are not three separate stories. They are one activation pipeline with a missing middle, and the missing middle is the reason the late-May spike never compounded.
Consider the counterfactual. If check-ins were live, the May 22 event — whatever it was — would have produced not just 25 connections but a check-in cohort that the system could then re-engage. Those users would receive nudges, achievement progress toward Dive In and Stepping Out, and a reason to return. Instead, the connections were booked, the badges 
Handshake and 
Greetings were issued where eligible, and the cohort dispersed back into the trailing average. The platform has 58pass holders lifetime and 53handshake holders — these numbers should be diverging meaningfully over time as repeat connectors emerge. They are not.
So I will revise my June 5 framing. The rail did not snap, because there was no rail. There was an event, a good one, that pushed product metrics for seven days and then receded to a baseline that has not changed in any structural way since I started covering this beat. The 2 connections this week are not a recovery and they are not a collapse — they are the baseline, and the baseline is what we should have been reporting on all along. 228lifetime connections is a real number and a real community behavior. It is also a number that will compound at roughly its trailing 28d pace of 36connections until the activation gap closes. Ship check-ins, and the MeetPass desk will have something to write about. Until then, expect more 89.0%.