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.
- Filter the list to PENDING APPROVAL if you only want those rows.
- 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.
- Click Approve Selected (@count) (the label shows how many ticked rows are PENDING APPROVAL; it stays disabled when none are).
- 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.
- Tick the introductions you want (the button sits just before Export Dating Couples and shows how many are ticked).
- 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.
- Optionally set the Date filter on Created — the export uses the same from/to dates as the list (leave empty to include all dates).
- Click Export Dating Couples above the table.
- 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.
- Click Export. Your browser downloads a file named like dating_couples_YYYY-MM-DD.xlsx.
The spreadsheet columns are:
| Column | Meaning |
| # | Row number in the export (not the introduction id). |
| Girl's Name / Guy's Name | Member 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). |
| Status | Same 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 / Updated | When 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.