Reference (partial) — Maps introduction Status values to the matchmaker queue. Verified against Admin Shidduch Request actions and introduction status handlers (July 2026). For day-to-day matchmaker UI steps, see Shidduch Requests.

Overview

On brands with matchmakers enabled, an introduction that reaches MATCHED (both members approved) can enter a matchmaker workflow. The same introduction row appears on Admin Matches with MM_* statuses and on My Matches with shorter labels (for example Available, Taking On).

Matchmakers advance the pair from first assignment through contact, recorded answers, dating, and engagement. Each advance updates the introduction status, may reset the Must respond until deadline from your brand’s matchmaker SLA settings, and writes matchmaker log entries.

If your brand does not use matchmakers, members may chat after MATCHED without these MM_* stages — see introduction statuses → Matched and beyond.

Support tickets? Stuck queue, no matchmaker, or overdue Shidduch rows — start at Support troubleshooting → Stuck Shidduch (matchmaker).

Status name mapping

One introduction row — two label styles depending on which Admin screen you are on.

Introduction list / detailShidduch Requests labelPlain meaning
MATCHED New verified — Both members approved. Waiting for a matchmaker to pick up the case (or for staff to assign one). Primary action on Shidduch detail: advance to Available.
MM AVAILABLE Available verified — Open slot on the matchmaker queue. A matchmaker can accept responsibility. Advance moves to Taking On.
MM TAKING ON Taking On verified — Assigned matchmaker is actively working the introduction. Advance records first contact → Contacted.
MM CONNECTED Contacted verified — Matchmaker has reached out. Advance opens a dialog to record each party’s answer (interested / busy / unmatch / ignore).
MM RECORDED Answers Recorded verified — Both parties answered interested. Advance opens the record date dialog (date number + optional comment) → DATING.
DATING Dating verified — Couple is dating. Status chip may show date number (1st date, 2nd date, …). Advance records the next date or Mark engaged moves to ENGAGED.
ENGAGED Engaged verified — Engagement recorded. May trigger admin notification templates. Introduction detail status change to engaged fires the same downstream comms as other engagement paths.
ENGAGEMENT BROKEN Engagement broken (when recorded on introduction detail) verified — Engagement through this introduction ended. Both members return to active profile status; pending engagement SME payments cancel. Full ops steps: Engagement broken — ops playbook.
ON HOLD Busy / On Hold verified — Temporarily paused. Set via put on hold flow: confirm both sides contacted, then pick 1 day / 3 days / 1 week / 1 month. Extends the due deadline on the row.
ENDED Ended verified — Closed without engagement. Unmatch dialog captures per-party reasons (text and optional voice note when voice transcription is enabled).
MM TIMEOUT Timed Out verified — Matchmaker did not advance before the SLA deadline. Can be Revived from the Shidduch list when your role allows.

Typical progression

verified — Happy path after both members approve:

  1. MATCHED → matchmaker accepts → MM AVAILABLE
  2. MM AVAILABLE → matchmaker takes case → MM TAKING ON
  3. MM TAKING ON → contact logged → MM CONNECTED
  4. MM CONNECTED → both interested → MM RECORDED
  5. MM RECORDED → date recorded → DATING (date number increments on later dates)
  6. DATING → ENGAGED (or MARRIED via manual status change on introduction detail)

Branches:

  • At MM CONNECTED, if either party is busy or ignore (and the other is not unmatch), Admin opens a second dialog with only two choices: Continue Waiting (keep status Contacted and store both answers on the row) or End match (end-shidduch flow). Put on hold with a duration is not on that dialog — use the Pause/End match menu when you are ready to pause the whole case. See Party answer flags.
  • At MM CONNECTED, if either party is unmatch, Admin opens the End shidduch dialog directly (reasons required).
  • At any MM stage before dating, Decline or End shidduch can close the introduction (ENDED or matchmaker decline with reason).
  • When a matchmaker declines, the next id in the next queue (if any) can be promoted to current — see assignment below.

SLA / Due column: Each status change recalculates Must respond until from your brand’s matchmaker SLA minutes for that status name (except ON HOLD, which uses the hold duration you pick in the dialog). See Matchmaker SLA settings for where to edit those minutes in Admin.

Matchmaker SLA settings

How the Due column and overdue warnings on Shidduch Requests get their deadlines.

verified — After each matchmaker workflow advance (or when a matchmaker is assigned), the system sets Must respond until on the introduction row:

  • Normal MM statuses — Adds a number of minutes looked up from Settings → App Settings for your brand. Each introduction status name (for example MATCHED, MM_TAKING_ON, MM_CONNECTED) can have its own row. The Description column on App Settings usually shows the status name; the Current Value is how many minutes the matchmaker has before the row becomes overdue.
  • On hold — Does not use those SLA rows. The matchmaker picks 1 day, 3 days, 1 week, or 1 month in the put-on-hold dialog; that duration becomes the new deadline.
  • Timed out — When Must respond until passes without the expected advance, status may move to MM TIMEOUT (Timed Out on the Shidduch list). Staff with the right role can Revive from Shidduch detail.

Where to edit: Open Settings → App Settings → find rows in the Mobile App or matchmaker-related category whose description matches an introduction status label (for example New / Available / Taking On). Change the New Value column, then Publish settings so live Shidduch deadlines use the updated minutes.

Which statuses use SLA minutes

verified — Each time a matchmaker workflow advance updates the introduction (except ON HOLD), the system looks up minutes for the new status name and sets Must respond until. Typical rows in App Settings map like this:

Introduction status after advanceShidduch list label (typical)SLA lookup
MATCHED New verified — Minutes for MATCHED (also used when a new matchmaker is promoted onto the case).
MM AVAILABLE Available verified — Minutes for MM_AVAILABLE.
MM TAKING ON Taking On verified — Minutes for MM_TAKING_ON.
MM CONNECTED Contacted verified — Minutes for MM_CONNECTED.
MM RECORDED Answers Recorded verified — Minutes for MM_RECORDED.
DATING Dating (date chip) verified — Minutes for DATING until the next date is recorded or the couple is marked engaged.
ON HOLD On Hold verified — Not from SLA rows. Deadline = hold duration chosen in the dialog (1 day / 3 days / 1 week / 1 month).

If a status has no matching App Settings row (or the value is zero), Must respond until may be empty and the Shidduch Due column shows no deadline for that step.

Shidduch list urgency: Rows within about 24 hours of the deadline show urgency styling and tooltips on the Due column (Overdue / Tomorrow). The stats bar warning filter counts overdue actionable introductions — not a separate manual “mark urgent” flag.

Per-brand SLA labels and minute values differ — confirm with your brand manager before changing production numbers. PM review of wording on App Settings rows is still recommended (see program backlog).

Matchmaker assignment

Who owns the introduction today, who is queued next, and how Admin changes assignees.

verified — Each introduction stores matchmaker ids in two JSON lists on the introduction row:

FieldMeaning
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

ActionWho sees itWhat 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):

  1. The declining id is removed from the head of current.
  2. The backend walks next in order and picks the first active matchmaker.
  3. That id becomes the new head of current; remaining next ids stay queued.
  4. 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.

Edge cases

Situations that change which buttons appear or what happens behind the scenes.

SituationWhat you seeWhat happens
No matchmaker assigned Shidduch list highlights No MM Assigned. On detail, an S-Manager who clicks the primary advance button is sent to Reassign first instead of advancing the status. verified — Case cannot progress until a matchmaker is in the current list.
Matchmaker declines Decline (or reassign flow) at Available or earlier. verified — Required decline reason. If a next queue exists, the first id there moves into current and the introduction stays on the queue for the new matchmaker.
Snooze at New Not Available on New / MATCHED. verified — Opens matchmaker snooze (marks the SME temporarily unavailable) and removes this case from their queue — different from the decline dialog used at Available.
Party busy / unmatch while New or Available Row highlighted; Action Required shows a party-specific hold or unmatch message; list may offer Dismiss (hides row locally only). verified — Party flags stored on the introduction until cleared via dismiss, hold flow, or advancing past Contacted.
Multi-matchmaker brands Add Matchmakers on detail when the MultiMMS app feature is on. verified — Adds ids to current without removing existing assignees; notifications go to all current matchmakers.
Leaving ENGAGED Manual status change on introduction detail (for example to ENGAGEMENT BROKEN or ENDED). verified — Both members’ profile status returns to active when engagement or marriage milestones are reversed. Pending engagement SME payments for this introduction are auto-cancelled; paid rows stay for finance review. Step-by-step: Engagement broken — ops playbook.
Revive after timeout or end Revive in the detail header. verified — Status returns to Contacted; unmatch reasons cleared; both parties marked interested so outreach can resume.

Detail buttons by status

Operator summary of the Required Action bar on Shidduch detail. Step-by-step list view help: Shidduch Requests → Detail page actions by status.

StagePrimary (example label)Result statusOther controls
New / MATCHED I Am Available MM AVAILABLE Not Available (snooze MM at New; decline dialog at Available)
Available / MM AVAILABLE Accept this match MM TAKING ON Decline
Taking On / MM TAKING ON Contacted both sides MM CONNECTED —
Contacted / MM CONNECTED Record answers MM RECORDED, ON HOLD, or ENDED (via record-answers branches) —
Answers Recorded / MM RECORDED Record new date DATING Mark Engaged; Pause/End match menu
Dating / DATING Record new date DATING (next date #) Mark Engaged; Pause/End match menu
On hold / ON HOLD Follow Up MM CONNECTED (clears party flags) Pause/End match menu

verified — Revive (header action) on Timed Out or Ended sets status to Contacted with both parties marked interested and prior unmatch reasons cleared. Reassign / Add Matchmakers are header actions for admins; see Shidduch Requests → Header and admin actions.

Dialogs on Shidduch detail

Field-level help for modals opened from the Shidduch Request detail page (not from the generic introduction detail status picker).

DialogFieldsWhen it appears
Record answers Per party: Interested, Busy, Unmatch, or Ignore (radio). Both must be chosen before Confirm. Advancing from Contacted (MM CONNECTED).
Record date Date number (+ / − counter), optional comment (multiline). Increments which date you are logging (1st, 2nd, …). Advancing from Answers Recorded or logging another date while DATING.
End shidduch (unmatch) Per-party reason text (initiator / responder), optional additional notes, optional voice recording per field when voice transcription is enabled, both sides dated checkbox (shows date counter when checked), both sides contacted confirmation checkbox. At least one reason (text or voice) required. End shidduch menu or unmatch branch from record answers.
Put on hold Both sides contacted checkbox, then hold duration: 1 day, 3 days, 1 week, or 1 month. Put shidduch on hold menu when status is not already on hold.
Decline (matchmaker) Decline reason (multiline, required). May reassign to next queued matchmaker when reassign dialog is used. Decline button before MM TAKING ON; or when no matchmaker is assigned and S-Manager opens reassign.
Reassign / Add matchmakers Pick from available matchmakers (autocomplete). Reassign shows current + queued order. Add matchmakers allows multi-select when feature enabled. Admin actions on Shidduch detail.

Record answers — what each choice does

verified — After you pick an answer for both initiator and responder, the primary button outcome depends on the combination:

Initiator answerResponder answerTypical result
InterestedInterestedStatus → MM RECORDED (Answers Recorded).
BusyAny (except both interested)Second dialog: Continue Waiting keeps MM CONNECTED and stores both answers on the row, or End match opens End shidduch.
IgnoreAny (except both interested / unmatch-only paths)Same second dialog as busy — Continue Waiting or End match.
UnmatchAnyOpens End shidduch dialog (reasons required) → ENDED.
AnyUnmatchSame — either side unmatch ends the introduction.

Record answers — second dialog (mixed answers)

verified — When the combination is not both interested and not an immediate unmatch, Admin shows a follow-up dialog with exactly two buttons (no hold-duration picker on this step):

ButtonWhat happens
Continue Waiting Status stays MM CONNECTED (Contacted). Both answers are saved on the introduction row. If either answer was busy or unmatch while the request is still at New or Available, the Shidduch list highlights the row and shows a party-specific Action Required message until you clear or advance the case — see Party answer flags.
End match Opens the full End shidduch dialog with the answers you already selected pre-filled where applicable.

To pause the whole case with a calendar duration (1 day / 3 days / 1 week / 1 month), use Pause match from the Pause/End match menu on Answers Recorded, Dating, or when returning from hold — not from this second dialog.

Exact branch labels depend on your brand’s Shidduch detail copy — when in doubt, read the confirmation text on screen before clicking Confirm.

Party answer flags

Temporary per-party outcomes from Record answers — stored on the introduction row until cleared or the case advances.

verified — When a matchmaker records answers at MM CONNECTED, each party’s choice (interested, busy, unmatch, ignore) can be saved on the introduction under that party’s answer flag. Admin reads them on Shidduch detail (contact section shows a short response chip) and on the Shidduch list when they affect the queue.

AnswerPlain meaningList / detail effect
Interested Party wants to proceed toward dating. Both interested → advance to MM RECORDED in one step.
Busy Party is not ready yet but has not declined the match. While status is still New or Available, row highlights and Action Required names that member with a hold-style message. Matchmaker uses Continue Waiting, contacts the party, or Dismiss to hide the row locally.
Ignore Party did not engage / no clear yes yet (matchmaker judgment). Same follow-up dialog as busy at MM CONNECTED. Does not by itself trigger the early New/Available highlight — only busy and unmatch do.
Unmatch Party wants to end this introduction. Opens End shidduch. At New / Available, same highlight and unmatch action-required copy as busy.

Clearing flags

  • Dismiss on the Shidduch list (when shown) clears both party flags on the row without changing status — your personal queue view only.
  • Advancing from ON HOLD back to MM CONNECTED clears both flags as part of the resume action.
  • Recording both parties interested on the next Record answers pass replaces prior flags.

These flags are matchmaker workflow state — they do not appear on the generic view introduction status picker. For support tickets about “action required” on the Shidduch list, see Stuck Shidduch (matchmaker).

Introduction detail vs Shidduch detail

Admin Matches → open any row → view introduction:

  • Shows scores, logs, chat stats, Match Advisor, decline history, and party settings for the same introduction id.
  • Staff with Edit can change Status to any lifecycle value using the header status control — a reason dialog appears for most changes (see status change dialogs on the view introduction guide).
  • Does not show the matchmaker primary/decline action bar — use Shidduch detail for step-by-step MM workflow buttons.

Matchmaking → My Matches → open a row:

  • Same introduction id, optimized for matchmaker actions, due-date urgency, and reassignment.
  • Section-by-section layout (contact card, progress bar, attribute comparison, logs, comments): Shidduch Requests → Detail page sections.
  • Links to both party profiles and attribute comparison for the active case.