Unique-partner counts shown under Intro statistics on the end-user profile
Last updated: 2026-10-21
Reference (partial) — Bucket rules below are verified from the introduction stats service used by the member app and Admin (October 2026). Edge cases for unusual status combinations may still need brand-specific notes.
Overview
On View end user → Member app snapshot, Admin shows six counters that use the same rules as the singles app My introductions summary. Each number is a count of unique partners, not introduction rows.
When a member and the same partner have more than one introduction over time, the snapshot keeps one outcome per partner — the strongest bucket wins (for example a match replaces an earlier ignore for that person).
Staff-rejected suggestions do not enter the snapshot. Closures with no member attributed (for example some system expirations) are also excluded from both sides’ “didn’t pick up” tallies.
Where members see this
The singles app has a dedicated My introductions page (screen title matches that phrase on most brands).
Members open it from the app’s main navigation when the brand exposes the feature — it is a read-only summary of counts, not the list of open suggestions (those stay on Lora chat / potential matches).
Five rows in the app, six on Admin: The member screen lists You declined, You didn't pick up, They didn't pick up, Matched, and Dated — it does not show Total. Admin adds Total at the top so support can sanity-check how many distinct partners have any counted outcome.
All five shared rows should match the member’s phone when both sides load fresh data. If only Total looks “wrong” compared to a screenshot, the member may simply not have a Total line — sum the five buckets mentally or use Total on Admin only.
Waiting for screenshot. Capture: logged-in member on My introductions with at least one non-zero row visible (declined, didn’t pick up, matched, or dated).
Support tickets often mix these two rows. They use different rules and different priority in the snapshot.
Row
Counts toward this bucket when…
Typical Admin clues
You declined
This member explicitly declined or tapped not interested on that partner’s best counted introduction — whether they were the initiator or the responder on that row.
Introduction status shows a declined outcome on their side (initiator declined vs responder declined labels differ by role). A still-open RAW row for another partner does not add here unless that partner’s best outcome is a decline.
You didn't pick up
This member did not move the suggestion forward — missed deadline, marked busy on a party-answer dialog, ended the suggestion themselves, or used not for now (freeze) — and the suggestion card was already delivered to their Lora chat.
TERMINATED or NOT COUNTED with this member recorded as the one who ended it; FROZEN when they froze; ignored / timed-out statuses when they were the side that owed action; party status busy on the introduction.
They didn't pick up
The partner was shown the suggestion card but did not move it forward, and this member’s outcome for that partner is weaker than matched or declined.
Partner still on RAW while this member already approved; partner ignored or closed on their side; you are waiting on them.
Priority reminder: If the same partner later matched or recorded a date, that stronger bucket replaces an earlier decline or didn’t-pick-up for snapshot totals — even if an old introduction row still appears on profile introductions.
Row definitions
Labels match the Member app snapshot block on the end-user profile.
Row
Counts a partner when…
Does not count when…
Total
Any bucket below applies (partner has a attributable outcome).
Only staff-rejected rows, or terminated-like rows with no terminator recorded.
You declined
This member declined as initiator or responder on that partner’s best counted introduction.
A stronger outcome for the same partner exists (for example they later matched).
You didn't pick up
This member missed a deadline, was busy, ended the suggestion, or froze it — and the suggestion card was shown in their Lora feed.
The suggestion never appeared in their feed (auto-expired before delivery).
They didn't pick up
The partner was shown the suggestion card but did not move forward, and this member’s outcome for that partner is not stronger.
Partner never received the card in Lora chat.
Matched
Both sides reached match or post-match stages, including couples that later unmatch after having matched.
Still only open suggestions with no match.
Dated
A date number is stored on the introduction for that partner (in-person dates in Shidduch-style flows).
Matched but no date recorded yet.
Priority order (simplified): dated > matched > you declined > you didn’t pick up > they didn’t pick up. The snapshot assigns each partner to the highest priority that applies, then totals each column.
When a suggestion counts as “shown”
“Didn’t pick up” buckets only apply when a suggestion card was delivered to that person’s Lora chat for that introduction — not merely because an introduction row exists in Admin.
This matches member expectations: auto-expired suggestions nobody was shown should not inflate “you didn’t pick up” in the app or on this Admin mirror.
If Admin shows RAW but the member says they never saw someone, check whether a Lora introduction message exists for that profile before trusting the snapshot row.
Inspection (eye icon on the suggestion card) is not required for visibility — only delivery of the suggestion card to Lora chat counts.
Statuses that count as matched
The Matched row uses the same “we got together” bucket as the singles app — not merely “Admin still shows an open suggestion.”
MATCHED and every later in-couple stage your brand uses — for example DATING, ENGAGED, MARRIED, matchmaker MM RECORDED / ON HOLD, and similar post-match workflow labels.
UNMATCHED or MM TIMED OUT when the couple had already reached a match stage — the snapshot still treats that partner as “we matched” even though the row later closed.
Dated is a separate, higher-priority row: when a date number is stored on the introduction for that partner, they appear under dated as well as contributing to matched totals.
Never counted in any snapshot row:
ADMIN REJECTED — staff declined before members were fully in the journey.
TERMINATED or NOT COUNTED when logs show no member as the one who ended it (system expiry cleanup) — neither “you didn’t pick up” nor “they didn’t pick up.”
Support scenarios
When a member quotes My introductions numbers that do not match Admin chips or the profile introductions table.
What the member or agent sees
Why it happens
What to verify
Status chip counts are higher than Member app snapshot for the same word (for example “matched”).
Chips count every introduction row; the snapshot keeps one outcome per partner.
Admin Member app snapshot already shows the new count; member’s My introductions screen still shows the old numbers.
The singles app loads snapshot counts once when the member opens that screen — there is no pull-to-refresh on the summary grid.
Ask the member to leave My introductions and open it again (or restart the app). Staff should reload the end-user profile in the browser after changing introduction status. See When numbers refresh.
Staff changed status five minutes ago; both sides still disagree.
Counts are computed live from the database on each load — not a nightly batch — but each client only refetches when its screen loads.
Confirm both sides refreshed. If still wrong after refresh, reconcile buckets with Declined vs didn’t pick up and introduction Logs — not chip totals.
When numbers refresh
Avoid “stale screenshot” tickets — both Admin and the member app re-query the same stats service, but only when each screen loads.
Where
When counts reload
What support should do
Member app — My introductions
verified — Each time the member navigates to that page (opening the screen runs a fresh request). Leaving and returning updates the grid; staying on the page after matching or declining elsewhere does not auto-update.
After you change an introduction in Admin, ask the member to back out and open My introductions again before comparing to a screenshot.
verified — Loads when you open that end-user profile (or switch to another member and back). A browser refresh on the profile page also reloads the block.
Reload the profile after status changes before telling the member their app is wrong.
Admin — status chips above the snapshot
Same profile load as the snapshot block — chips and snapshot refresh together, but still only on load.
Use chips for row-level audits; use snapshot for app parity after refresh.
There is no separate “publish” step for snapshot numbers — they always reflect current introduction rows and Lora delivery history at query time.