Overview

Ended Matches is a brand-wide review table for introductions that have fully ended. Each row shows both parties, how well they matched on paper, who managed the case, and what reasons were recorded when the introduction closed.

Use this screen when you need to spot patterns across matchmakers or time — for example high-scoring pairs that still declined, or couples who met in person before unmatching. It complements (but does not replace) per-member decline history on view introduction → Decline history and the Ended Shidduchim table on an end-user profile.

Go to → Ended Matches. Rows load in pages as you scroll; the newest endings appear first.

Who can open this page

RequirementMeaning
Ended Matches page permission Your role must include access to this menu item. Without it, the page is hidden from the sidebar.
Matchmaker feature This list is most useful on brands that run the matchmaker workflow. The page can still load on other brands, but rows are sparse when introductions rarely reach an unmatched close.

What appears in the list

verified — Only introductions whose status is UNMATCHED (ended) are included. Active, pending, matched, and dating rows never appear here.

QuestionAnswer
Does this list include member not interested taps before a match? Only when the introduction row itself reached UNMATCHED. Early declines that never created a full introduction record appear on profile introductions with decline/ignore filters instead.
How is this different from decline chips on view introduction? Detail-page chips summarize one member’s answers to configured decline-reason questions across many introductions. This list is one row per ended introduction for the whole brand.
How is this different from Ended Shidduchim on a profile? The profile table shows only introductions involving that member. This page shows every ended introduction for the brand (subject to your filters).
What if no matchmaker was assigned? The matchmaker column shows No MM Assigned. The row still appears when the introduction ended.

Table columns

ColumnWhat it showsNotes
Matchmaker Avatar and first name of the matchmaker currently responsible for this introduction (head of the matchmaker queue on the row). Blank chip text means No MM Assigned.
Updated When the introduction record was last updated — typically when it moved to UNMATCHED. Rows sort newest first.
Initiator photo Small avatar for the proposer. —
First - Intiator Initiator’s display name. Click to open their end-user profile.
Type (initiator) The initiator’s user type profile attribute (your brand’s category label). Capitalized for display.
Age (initiator) Initiator’s age from their profile. —
Score (initiator) How well the initiator’s bio/preferences matched the responder, as a whole number percentage. Stored on the introduction when scores were calculated; rounded in the table.
Reason (initiator) Free-text unmatch reason recorded for the initiator when the matchmaker ended the shidduch. May include transcribed voice note text. Empty when only coded reasons were used.
Responder photo Small avatar for the second party. —
Second - Responder Responder’s display name. Click to open their end-user profile.
Type (responder) Responder’s user type attribute. —
Age (responder) Responder’s age. —
Score (responder) How well the responder’s bio/preferences matched the initiator (whole number %). Can differ from the initiator score when preferences are asymmetric.
Reason (responder) Free-text unmatch reason recorded for the responder. Same voice-note behavior as initiator column.
Reason (overall codes) Comma-separated labels from your brand’s unmatch reason general codes — selected on the Shidduch detail end shidduch dialog. Multiple codes can apply to one case.
Other reason Additional free-text explanation entered when ending the shidduch (matchmaker notes). Separate from per-party reason fields above.
# Date How many in-person dates the couple had recorded before the introduction ended (0 = never met). Drives the Met / Not met filter. Also shown on the Shidduch request chip during DATING.

Hidden columns (enable in the table column picker)

Two columns are hidden by default:

ColumnWhat it shows
Edu Group (Initiator) Initiator’s education-group attribute value, color-tinted when it does or does not match the responder’s preference for that attribute.
Edu Group (Responder) Responder’s education-group value with the same color hint.

Colors follow the same green / amber / red hints used elsewhere when comparing bio answers to preferences. Show these columns when reviewing whether education-group mismatches correlate with declines.

Filters

FilterWhat it doesWhen to use it
Matchmaker Shows only rows where the selected matchmaker is the current responsible matchmaker on the introduction. Monthly review with one SME; coaching on unmatch quality.
Met Couples who recorded at least one date (date # is not empty). Focus on in-person outcomes that still ended.
Not met Couples who ended before any date was recorded (date # empty). Screening-stage declines; compare to scores before first meeting.

Filters combine: you can view, for example, not met endings for a single matchmaker. Clear filters to return to the full brand list.

Understanding decline reasons

Ended introductions can carry up to four kinds of reason text. They are captured on the Shidduch request detail when a matchmaker ends the case — not on the generic introduction detail page.

Field on this listWho enters itTypical content
Reason (initiator) Matchmaker on end shidduch What the initiator said about why the match ended — typed or transcribed from a voice note.
Reason (responder) Matchmaker on end shidduch What the responder said.
Reason codes (overall) Matchmaker — multi-select from unmatch reason codes in General codes Standardized categories for reporting (for example personality, location, timing).
Other reason Matchmaker — optional notes field Extra context that does not fit a code.

Member-app not interested taps before matchmaker involvement use different decline-question answers — those appear on view introduction → Decline history, not necessarily in these columns.

Full dialog field list: matchmaker workflow → Shidduch detail dialogs.

Row actions

Each row has two icon actions at the right:

IconOpensUse when
Lightbulb View introduction for this introduction ID You need logs, chat stats, match advisor text, or per-member decline chips.
Group Shidduch request detail for the same ID You need matchmaker workflow history, date counter, or the original unmatch dialog values.

Coaching and quality review

Suggested review habits:

  • High score + declined before meeting — open view introduction and check soft deal-breaker flags and pending reasoning; may indicate preference wording or tolerance issues.
  • Low score + sent anyway — confirm whether staff manually created the introduction or tolerance rules applied; see create introduction.
  • Met + early date # — read per-party reason columns; compare with stuck Shidduch troubleshooting if the case was rushed.
  • Repeated codes for one matchmaker — filter by matchmaker and scan the overall reason codes column for the same label.

For live cases still in progress, use My Matches instead — this declines list is for closed UNMATCHED rows only.