verified — Each introduction stores matchmaker ids in two JSON lists on the introduction row:
| Field | Meaning |
Current (matchmakers.current) |
Matchmakers actively responsible — they receive notifications, may advance status from Shidduch detail, and appear in the Assigned to header. On multi-matchmaker brands, every id in this list is active (not only the first). |
Next (matchmakers.next) |
Ordered fallback queue. When the active matchmaker declines (or Admin reassigns via the decline path), the system promotes ids from here into current. |
Who may drive the introduction
verified — Any matchmaker listed in current may update introduction status, add comments, and use the primary action buttons on Shidduch detail — not only the first id in the list. The Shidduch list filter No MM Assigned matches introductions with an empty or missing current array.
Admin actions on Shidduch detail
| Action | Who sees it | What it does |
| Reassign |
Brand Manager on Shidduch detail; hidden when status is ENGAGED. |
Opens the reassignment dialog. Shows current + queued matchmakers in order, then lets you pick one replacement from the autocomplete. Confirm calls the decline introduction API with the chosen id — the previous head of current is removed and the pick is promoted (same backend path as a matchmaker decline with a hand-picked nextMM). |
| Add Matchmakers |
When the MultiMMS app feature is on (any admin who can open the dialog from the action bar or by clicking Assigned to). |
Multi-select autocomplete. Saving merges the chosen ids into current without removing existing assignees; the next queue is left unchanged. |
| Assigned to (header click) |
Brand Manager. |
Without MultiMMS: opens the assigned system user when one exists, otherwise opens Reassign. With MultiMMS: opens Add matchmakers instead. |
Automatic promotion on matchmaker decline
verified — When a matchmaker declines at Available or earlier (and reassignment is allowed for that status):
- The declining id is removed from the head of current.
- The backend walks next in order and picks the first active matchmaker.
- That id becomes the new head of current; remaining next ids stay queued.
- The introduction returns to the matchmaker available step so the new assignee gets the resume-style notification email.
If the decline dialog or Admin reassignment supplies a specific nextMM, that id is moved to the front of next before promotion so it is chosen first.
When no active matchmaker remains in next, both lists are cleared and members may receive the NO_MM end-user email — the case stays on the Shidduch queue with no assignee until someone uses Reassign or Add matchmakers.
No matchmaker gate before advance
verified — On Shidduch detail, when there is no boUser / empty current list, an S-Manager who clicks the primary advance button is redirected into Reassign instead of advancing status. The introduction cannot progress until at least one matchmaker sits in current.
Manual create with a matchmaker
Creating an introduction from Admin with a matchmaker on the row can start at MM TAKING ON instead of PENDING APPROVAL, with that matchmaker seeded into current.
See also Edge cases for snooze-at-New, party busy, and multi-matchmaker notification behaviour.