Overview

An introduction links two end users: one who initiates (the proposer) and one who responds. This screen shows all introductions for your brand, with filters to narrow by status and date. Click any row to open the full introduction record.

Labels match brand mek (en) in Admin.

Member-centric view

When you already know which member you are helping, use their profile instead of scanning the full brand list.

TaskUse this listUse Introductions History
Browse every introduction in the brandYes — filters by status, date, internal test accountsNo — scoped to one member
See both parties and match scores on one rowYes — initiator and responder columns side by sideNo — one partner per row (bio/pref sub-rows)
Count how many times a member approved, declined, or was ignoredNo — use intro statistics on their profileYes — chips link here with matching filters
Compare a member’s bio/prefs to each partner in the tableNoYes — bio summary card + partner age/height rows
Find one introduction by IDYes — Matches searchOpen from member profile or use global search
Support: “show me all of Sarah’s matched couples”Search Sarah on End Users, then open profile introductions with Matched filterYes

Open path: Singles Management → Singles Management → member profile → Introductions History (requires View User Interactions Statistics page permission). Full guide: Introductions History.

The list

Go to Singles Management → Admin Matches. Each row is one introduction and shows:

ColumnWhat it shows
Intro IDThe unique introduction number. Use this when contacting support or tracing logs.
CreatedDate the introduction was first created (day and month, no year).
DueMust respond until — response deadline while the introduction is waiting on a member action. verified — Admin shows this date only when status is RAW (initiator’s turn) or INITIATOR APPROVED (responder’s turn); every other status leaves the column blank even if a deadline is stored on the row. For how deadlines are set, extended, and what happens when they pass, see response deadlines (reference).
Initiator photoSmall avatar for the proposer (thumbnail).
First - IntiatorName of the person who will propose the connection. Click the name to open their end-user profile.
Age (initiator)Initiator’s current age from their profile.
% Match (initiator column)Bio compatibility score for the initiator’s direction (percentage). When stored match scores exist for the pair, Admin prefers that live score over the value saved on the introduction row.
Inspected (initiator column)Eye icon when the initiator has opened the responder’s profile at least once while reviewing this introduction. Hidden when they have not opened it yet. The log on the detail page shows Inspected_full, Inspected_half, or a blank suffix — see inspection type codes.
Responder photoSmall avatar for the person receiving the suggestion.
Second - ResponderName of the person who receives the suggestion. Click to open their profile.
Age (responder)Responder’s current age.
% Match (responder column)Bio compatibility score from the responder’s direction (same data rules as initiator).
Inspected (responder column)Eye icon when the responder has opened the initiator’s profile at least once for this introduction. During RAW the responder cannot inspect yet — the icon stays empty until status moves to INITIATOR APPROVED and they open the profile.
ContradictionsCount of hard contradictions from Match Advisor (shown in red when greater than zero). Column appears only when Match Advisor insights are enabled for your brand. Empty when the advisor has not run yet or when there are zero hard flags — open the introduction detail page for the full list and talking points. See view introduction → Match Advisor.
Soft DBWarning icon when the matcher stored soft deal-breaker attributes on this introduction (one or both sides). Hover lists every attribute key from initiator and responder combined. Does not hide the row in Admin — it flags rows that usually stay in PENDING APPROVAL until staff review even when Match Advisor hard contradictions are zero. Open Close but blocked on detail for per-party chips and optional explanation text. Hidden when none apply.
AI conflictBrain icon when the matcher recorded a personality conflict between the pair’s AI analysis traits (one side clearly wants the opposite of the other’s trait on the 1–9 scale). Hover lists the trait keys involved. Hidden when none apply. On detail, open Personality conflicts for plain-language lines per party. When your brand holds conflict introductions for staff review, these rows can stay in PENDING APPROVAL alongside soft deal breakers — see stuck in pending approval.
StatusCurrent step in the introduction lifecycle. Statuses that belong to one side of the pair show that person’s first name instead of the words Initiator / Responder — so Initiator Approved reads Sarah Approved, and Responder Declined reads David Declined. If a name has not loaded yet, the row keeps the general wording rather than showing a blank status. See Introduction statuses or the full status reference.
ActionsView opens the introduction detail page.

Rows are sorted by last update (most recent first). Click anywhere on a row to open the detail page.

Large lists: Admin loads the table in pages (up to 200 introductions per page). Within a page, rows arrive in batches of 20 so the grid stays responsive on busy brands — if you jump to a later page, wait a moment for every row in that page to finish loading before you compare counts or select checkboxes.

verified — Same introduction id twice on one page: If the server returns the same introduction number more than once while a page is loading, Admin keeps the first row and drops later copies so checkboxes and bulk actions do not double-count. That guard does not fix paging across pages — see list paging duplicates (support).

verified — Sort order: Rows sort by last update (newest first). When many introductions were touched at the same moment, order among those ties can look arbitrary when you move between pages. Use the Matches search when you know the exact id.

Filters

FilterWhat it does
MatchesType an introduction ID to jump directly to that record. verified — When the search box contains only digits, Admin loads a single matching row (no extra background batches for that search). Use this when you know the exact id; use status and date filters when you need a slice of the brand list.
StatusMulti-select dropdown. Choose one or more statuses to show only introductions at those stages. The dropdown keeps the general status names (Initiator Approved, Responder Declined, …) because it filters across everyone — only the column on each row swaps in a person’s name.
DateDate range on Created. Leave empty to see all dates.
showInternalWhen off (default), rows where the initiator is marked as an internal test account are hidden. Turn on to include those introductions in the list.
Profile SourceBrand managers only, and only when your brand enables the profile-source filter feature. Narrows the list to introductions whose creation metadata includes the chosen profile-source value (same attribute used on end-user profiles). Hidden when the feature is off or you are not a manager.

Note: Introductions with status ADMIN REJECTED are excluded from the default list entirely.

Bookmarking (address bar)

Most filters are chosen on the page and are not written into the browser address. Two optional query parameters are supported for saved links and reports — there is no on-screen toggle for them:

URL parameterEffect
?createdBy=auto verified — Shows introductions created by the matching system (automation). Rows where creation metadata is empty or labeled Auto stay in this view.
?createdBy=manual verified — Shows introductions created or reassigned by staff (a named person in the Created By: field on introduction detail — not Auto).

Example: /introductions?createdBy=manual (exact path depends on your Admin host). Invalid values are ignored and the list behaves as if no parameter was set. Combine with your usual status and date filters on the page after the list loads.

On introduction detail, Created By: shows the same distinction: Auto vs a staff name. See view introduction.

Bulk approve and export

Toolbar actions above the table (same area as other save actions on list screens).

Bulk approve pending introductions

verified — When you need to release many staff-pending introductions at once. The server applies each approval only when your role has Edit on view introduction (the same permission as Approve on introduction detail — not a separate “list only” permission). You may see the toolbar button while browsing the list, but rows you are not allowed to edit will fail and count toward the partial-failure message.

  1. Filter the list to PENDING APPROVAL if you only want those rows.
  2. Select the checkbox on each row you want to approve. Any row can be ticked (for the LLM export below), but bulk approve only acts on the ticked PENDING APPROVAL rows.
  3. Click Approve Selected (@count) (the label shows how many ticked rows are PENDING APPROVAL; it stays disabled when none are).
  4. Confirm in the dialog (Approve Selected Introductions). The body asks you to confirm the same count you selected.

Each approved introduction moves to the same next step as when you click Approve on introduction detail: AVAILABILITY CHECK when your brand uses the availability-check feature, otherwise RAW for the initiator.

verified — After you confirm, Admin approves each ticked PENDING APPROVAL row one at a time. When every row succeeds, you see Selected introductions approved successfully.. If at least one row fails (missing Edit on view introduction, open-introduction conflict, or another server error) while others succeed, you see Some introductions could not be approved. Please review and try again. — the message does not list which ids failed. Admin clears all checkboxes and refreshes the list either way; filter back to PENDING APPROVAL and finish any remaining rows from detail. Playbook: status change errors and stuck in pending approval.

verified — Bulk approve is a staff release, not a second matcher run. Rows that stayed in PENDING APPROVAL because of Match Advisor hard contradictions, soft deal breakers, or Personality conflicts can still be approved in bulk when ops sign off — the same as approving one row on detail. Scan warning icons and open detail for any pair that needs a judgment call before you tick the checkbox. See introduction statuses → Pending approval workflow and stuck in pending approval.

Export LLM context

Downloads a JSON file of the ticked introductions (any status) to paste into an outside AI assistant — the same bio, preferences and decline context as Copy both sides as context on introduction detail.

  1. Tick the introductions you want (the button sits just before Export Dating Couples and shows how many are ticked).
  2. Click Export LLM context (@count). verified — You can export at most 40 introductions in one download; if more rows are ticked, Admin shows an error and does not start the file (untick extras or export in batches).
  • Every ticked introduction shares one member (one person with several partners): the file is in the Download candidates format — that member once, then each partner as a candidate with its introduction id (intro-candidates-….json).
  • Different couples: one entry per couple, both sides (intro-couples-….json).

The same button is on an end user's introductions tab; there the export is always against that member.

Export Dating Couples

verified — Downloads an Excel workbook (.xlsx) of introductions for matchmaker or ops reporting. Use it when you need a spreadsheet of couples and assigned matchmakers, not when you only want to browse in Admin.

  1. Optionally set the Date filter on Created — the export uses the same from/to dates as the list (leave empty to include all dates).
  2. Click Export Dating Couples above the table.
  3. In the dialog, choose one or more statuses to include (multi-select). The dialog opens with DATING and ENDED pre-selected — typical for active dating couples plus closed shidduchim. Add or remove statuses (for example ENGAGED, MATCHED) before you confirm.
  4. Click Export. Your browser downloads a file named like dating_couples_YYYY-MM-DD.xlsx.

The spreadsheet columns are:

ColumnMeaning
#Row number in the export (not the introduction id).
Girl's Name / Guy's NameMember names sorted by gender on the account (not initiator/responder role). Empty if a profile name is missing.
MM Name(s)Every matchmaker currently responsible on the introduction, comma-separated when your brand assigns more than one (MultiMMS or handoffs).
StatusSame translated status labels you see in the list (from your brand's introduction status codes), not raw internal codes.
Date #Recorded date number while dating (1st date, 2nd date, …) when stored on the introduction; blank otherwise.
Created / UpdatedWhen the introduction row was first created and last updated in Admin.

The export includes every row that matches your chosen statuses and date filter — it is not limited to the rows currently visible on one table page. It does not apply the status multi-filter on the list unless you pick the same statuses again in the export dialog. showInternal and profile-source filters on the list do not change the export query; narrow by date and status in the export dialog instead.

Matchmaker-specific exports from the Shidduch queue may pass a matchmaker filter when that list is filtered — the global Introductions list export uses date + status only.

Introduction statuses

Each introduction moves through stages. Common statuses at a glance — the list’s Status column shows the relevant person’s first name in place of Initiator / Responder, while the names below stay general because they describe the stage itself:

StatusMeaning
PENDING APPROVALWaiting for staff to approve before the initiator sees the suggestion.
AVAILABILITY CHECKSystem checks whether the initiator is available (Lora question) before showing the match. See availability check workflow.
RAWWith the initiator for approve or decline.
INITIATOR APPROVEDInitiator said yes; with the responder.
MATCHEDBoth said yes — they may enter chat and matchmaker stages.
DATING / ENGAGED / MARRIEDRelationship milestones recorded in Admin.
INITIATOR / RESPONDER DECLINED or IGNOREDClosed because one side said no (DECLINED) or missed the response deadline (IGNORED). Ignored is automated — see ignored vs TERMINATED.
TERMINATEDClosed before match through member not available at all, frozen release, availability timeout, or staff change — not the same as ignored. See TERMINATED paths.
FROZENOne member parked the suggestion (not for now). They can re-open it later; the other party no longer sees it as active. See frozen (reference).
ENGAGEMENT BROKENEngagement ended — both profiles return to active; pending engagement payments cancelled. Ops playbook: Engagement broken.
TBDPaused for internal review — not “uncertain data”; ops use this to hold the flow.

For every status, who acts next, and what members see in the app, use the introduction statuses reference. On matchmaker brands, MM AVAILABLE through DATING are explained with Shidduch label mapping in matchmaker workflow.

Member response options (RAW / INITIATOR APPROVED)

While a suggestion is with a member, the app offers more than approve or decline. Support staff should know the difference — full table with Admin status outcomes: introduction statuses → Member choices on an active suggestion. In short:

  • Approve — moves to INITIATOR APPROVED or MATCHED.
  • Not interested — permanent decline for this pair.
  • Not for now — parks on the member’s frozen list (FROZEN); the other party may get a new suggestion.
  • Not available at all — closes as TERMINATED and returns both to the suggestion pool.

Member-app visuals for RAW, MATCHED chat, and the frozen list are on view introduction → What members see (screenshots queued under Documentation screenshots in Admin).

Inspection backlog cap

If a member has too many open suggestions they have never opened (no inspection logged where they are the party who must act), the platform pauses sending them new RAW or INITIATOR APPROVED suggestions until they review existing ones. Your brand sets the limit under App Settings — look for the row whose description mentions the max raw non-inspected cap. When that setting is not configured, this cap does not apply.

What counts toward the cap

  • RAW introductions where this person is the initiator and they have not opened the responder’s profile yet (empty Inspected eye icon on that row).
  • INITIATOR APPROVED introductions where this person is the responder and they have not opened the initiator’s profile yet.

Frozen (FROZEN), matched, and closed introductions do not add to this backlog. Silent profile opens from chat history do not add inspection log rows and do not clear the backlog by themselves.

How to diagnose in Admin

  1. Open the member’s end-user profile and note their open introductions (or filter this list by RAW / INITIATOR APPROVED and search by name).
  2. On each row where they must act, check the Inspected column on their side. Empty eye icons are the backlog.
  3. When the count of non-inspected rows reaches your brand limit, the member stops receiving new suggestions until they tap into at least one partner profile (you will see Inspected rows appear on the detail Logs tab).

Full rules and approve-vs-inspection behavior: introduction log types → When members can inspect. Support playbook: Support troubleshooting → Inspection backlog.

Creating an introduction

Users with Add New permission can create introductions manually. See Create introduction for the full workflow, compare view, and what happens after save.

Quick path: click the add button on this list → enter both profile IDs → Add. Use Compare in the dialog to preview scores before saving.

Support troubleshooting

When a member or matchmaker reports a stuck suggestion, start with the consolidated checklists on the support troubleshooting reference — before changing status manually.

  • No new suggestions — check Available Introductions on the end-user profile (tooltip explains why the count is zero).
  • Stuck in PENDING APPROVAL or AVAILABILITY CHECK — staff or member action required before the suggestion advances.
  • Deadline passed — auto-ignore runs on a schedule; Extenstion logs mean the member extended or the platform resumed after shutdown.
  • Extend failed — premium + extend introductions features, token balance, status RAW / INITIATOR APPROVED, and member on Potential Matches (not Lora chat).
  • Stuck Shidduch (matchmaker) — no matchmaker assigned, overdue Due, or Action Required on My Matches.
  • Inspection backlog — too many unopened RAW / INITIATOR APPROVED rows; eye icons empty on the member’s side.
  • Frozen suggestion — member cannot re-open not for now match, hit freeze cap, or partner unavailable.
  • Engagement broken — couple reports broken engagement, profiles still show engaged, or questions about matching again — record ENGAGEMENT BROKEN on introduction detail.
  • Status change errors — manual picker fails with Open introduction already exists when moving to engaged/dating while another open row blocks the pair.

Support troubleshooting (full reference) · List paging duplicates · Inspection backlog · Stuck Shidduch (matchmaker) · Frozen suggestion issues · Engagement broken · Status change errors · Extend failed · Share phone in chat

Learn more