How to open it
- From an end-user profile, click Introductions History in the top action bar.
- From the same profile, S-Manager users can click a chip on the Intro Statistics card — the page opens with that filter already selected.
The page shows a compact My Profile & What I'm looking for summary for the member at the top, then a filterable table of their introductions below.
Profile status on this page is read-only — you cannot change the member’s status here. Use View end user for status changes and full profile tools.
| Area | What you see | Notes |
| Page title |
Member’s first name. |
— |
| Profile header |
Avatar, name, Created, Last Login. |
Read-only snapshot — not the full editable header from View end user. |
| Profile & Status (left nav) |
Profile status chip and reason area. |
Read-only — status picker is disabled; change status on the main end-user profile. |
| My Profile & What I'm looking for (left nav → card) |
Bio / Pref summary rows — see Bio and preferences summary. |
— |
| Introductions (left nav → card) |
Filter dropdown + introduction table. |
Card title mirrors the active filter (for example Matched). When no filter is selected yet, the title area may be blank until you pick a bucket. |
| User ID (actions sidebar) |
Numeric user id for the member. |
For support tickets — the table uses profile ids on partner rows when you drill in. |
There is no Save button on this page — it is a read-only history and comparison view.
The first card repeats key bio and preference fields in two labeled rows (Bio and Pref) so you can compare partners in the table without switching tabs. Labels come from attribute configuration (same wording as elsewhere in Admin).
| Row | Fields shown (in order) |
| Bio | Age, gender, location (city), marital status, body type, height, identify-as-Jewish (when configured on your brand). |
| Pref | Preferred age range, preferred gender, how far (distance), preferred marital status, preferred body type, preferred height range. |
Age and location on the Bio row are taken from the profile record (not only stored answers). Preference ranges show as a single line with a dash between min and max when applicable.
This card is for quick context only — edit answers on View end user → Bio and preferences.
On View end user → Intro statistics, the horizontal chips at the top of the card show how many introduction rows fall into each bucket. S-Manager users can click a chip to open this page with that filter already selected. Other roles see counts only.
The same card also shows Member app snapshot below the chips — unique-partner counts that mirror the singles app. Those numbers follow different rules and will not match chip totals; see View end user → Member app snapshot and reference → Member app snapshot.
Chip labels abbreviate the first word and replace Me with the member’s first name — for example App. By Sarah for Approved by [name].
| Chip label (pattern) | What the count includes |
| Introductions | Open suggestions: RAW when this member is initiator, or INITIATOR APPROVED when they are responder. |
| Matched | Active relationship stages: MATCHED, matchmaker stages (MM AVAILABLE through MM RECORDED), DATING, ENGAGED, ON HOLD. |
| Approved by [name] | This member approved or moved past approval on their side — includes their INITIATOR APPROVED, MATCHED, and post-match stages, plus cases where they were responder on MATCHED after the other party approved. |
| Approved by other | The other party approved first — responder on INITIATOR APPROVED, or both on MATCHED or later. |
| Declined by [name] | This member declined (INITIATOR DECLINED or RESPONDER DECLINED). |
| Declined by other | The other party declined this member. |
| Ignored by [name] | This member missed a deadline (INITIATOR IGNORED or RESPONDER IGNORED). |
| Ignored by other | The other party missed their deadline. |
| Terminated | TERMINATED — closed before a match. |
Counts and table rows use the same status sets — a chip count of zero means the matching filter will also show an empty table.
Default when you first open the page: If you use the top-bar Introductions History button (no filter in the address), the table loads every introduction for this member — all statuses — until you pick a filter. For open suggestions only, choose Introductions from the dropdown above the table.
Bookmarking and chip links: When an S-Manager clicks an intro-statistics chip on the end-user profile, Admin opens this page with ?filter=… in the address (for example ?filter=matched) and the matching bucket is pre-selected — that URL can be bookmarked or shared. Changing the filter with the dropdown on this page does not update the address bar; refreshing after only using the dropdown returns to the all-statuses view unless you arrived from a chip link or typed the query yourself.
URL filter value | Dropdown label (with member’s name) |
introductions | Introductions |
matched | Matched |
approvedByMe | Approved by [name] |
approvedByOther | Approved by other |
declinedByMe | Declined by [name] |
declinedByOther | Declined by other |
ignoredByMe | Ignored by [name] |
ignoredByOther | Ignored by other |
terminated | Terminated |
The introductions card title matches the active filter name (with Me replaced by the member’s first name).
| Filter (general name) | What rows include | Typical support use |
| Introductions |
Open suggestions waiting for action: RAW when this member is initiator, or INITIATOR APPROVED when they are responder. |
“What does this member still need to approve or inspect?” |
| Matched |
Both sides said yes and the row is in an active relationship stage: MATCHED, matchmaker stages (MM AVAILABLE through MM RECORDED), DATING, ENGAGED, or ON HOLD. |
Active couples, chat, or Shidduch pipeline. |
| Approved by [name] |
Introductions where this member approved (or moved past approval) — includes their INITIATOR APPROVED, MATCHED, and post-match stages on their side, plus MATCHED when they were responder after the other party approved. |
Confirm who said yes and when. |
| Approved by other |
The other party approved first — this member is responder on INITIATOR APPROVED or both are on MATCHED or later. |
Responder-side pending or matched history. |
| Declined by [name] |
This member declined: INITIATOR DECLINED as initiator or RESPONDER DECLINED as responder. |
Member-initiated “not interested” outcomes. |
| Declined by other |
The other party declined this member. |
Explain why a suggestion closed from the partner side. |
| Ignored by [name] |
This member missed a response deadline: INITIATOR IGNORED or RESPONDER IGNORED. |
Auto-closed after Must respond until passed without action. |
| Ignored by other |
The other party missed their deadline. |
Pair closed because partner did not respond in time. |
| Terminated |
TERMINATED — closed before a match (for example not available at all, frozen release, or staff change). |
Distinguish from ignored — see ignored vs TERMINATED. |
Not in these filters: The nine buckets above cover member-facing outcomes (open suggestions, matched pipeline, approve/decline/ignore sides, terminated). They do not map one-to-one to every lifecycle status in Admin.
| Status (examples) | On this page | Where to look instead |
| PENDING APPROVAL, TBD, ADMIN REJECTED |
Visible when you open the page with no filter (all statuses) or when the row’s status column shows it — not a named dropdown bucket. |
Introductions list — filter by status; bulk approve pending rows there. |
| AVAILABILITY CHECK |
Same — all-statuses view or status column on a row. |
Stuck in AVAILABILITY CHECK · initiator-only Lora question. |
| FROZEN |
May appear in all-statuses view; not counted on intro-statistics chips. |
Frozen (reference) — member must re-activate; no Admin un-freeze. |
| ENGAGEMENT BROKEN, NOT COUNTED |
All-statuses view only. |
View introduction logs · ENGAGEMENT BROKEN support. |
Status meanings: Introduction statuses (reference).
| Column | What it shows | Notes |
| Group label | Partner’s first name on the bio row; Pref on the second row. | Tree grouping — expand/collapse in the grid. |
| Photo | Partner’s avatar thumbnail. | Hidden on the Pref sub-row. |
| Name | Partner’s first name. | — |
| Status | Current introduction status for this pair. | Same status enum as the global list. |
| Inspected | Eye icon when this member opened the partner’s profile at least once for this introduction (tooltip: “[name] has inspected”). | Empty during RAW on the responder side until they can inspect. See inspection rules. |
| First | Trophy icon when this member is the initiator (proposer) (tooltip: “[name] is initiator”). | — |
| Age | Partner’s age on the bio row; preferred age range on the Pref row. | — |
| Height | Partner height on bio row; preferred height range on Pref row. | Formatted like elsewhere in Admin. |
| Created | When the introduction was first created. | Same on both sub-rows. |
| HL (hours left) | Whole hours remaining until Must respond until (rounded down from the current time). The cell is blank when there is no deadline, the deadline is in the past, or less than one full hour remains — use introduction detail for the exact timestamp. Only meaningful while the pair is waiting on a member action (for example RAW or INITIATOR APPROVED). | Hover column header for “Hours Left”. Compare with response deadlines. |
| Actions | View opens the introduction detail page. | — |
Columns not in this grid: Unlike the bio summary card, the table does not repeat gender, location, marital status, or body type for each partner — only Age and Height (plus preference ranges on the Pref sub-row). Use the bio card at the top for this member’s full snapshot, or open the partner profile for their complete bio tree.
Row click: Clicking a data row (not the View button) opens the partner’s end-user profile in Admin — useful when you need both sides’ activity cards.
Sort order: Rows sort by introduction Created — newest first.
Compare with the global list: The brand-wide Introductions list shows both parties on one row with match scores and advisor score. This page is member-centric and adds bio/pref context for each partner. Admin includes every introduction row for the member (including algorithm suggestions that never reached a matchmaker); the matchmaker mobile app may hide pre-assignment rows — do not assume the member app shows the same count.