Overview

My Matches is the matchmaker’s working queue. Each row represents an introduction that has been assigned to a matchmaker (SME) and is being actively progressed through the workflow from first contact through to an outcome. Admins see all requests across matchmakers; matchmakers see only their own.

Admin stats bar

Total Requests, Monthly Avg, Matchmaker Avg, and Warning count appear above the table for users with BManager access.

Due date urgency

The Due column highlights overdue requests and requests due tomorrow so they are easy to spot at a glance.

List columns

ColumnMeaningNotes
Matchmaker / Shidduch IDAdmin users see the assigned matchmaker’s chip (avatar + name); non-admin users see the numeric shidduch ID (#N).BManager role required to see matchmaker identity.
CreatedWhen the introduction was first created.Always visible.
UpdatedWhen the request status last changed.Always visible.
DueTarget completion date. Shows Overdue or Tomorrow in red or orange when close or past.Always visible.
Initiator (avatar & name)The person who received the introduction suggestion first. Name is hidden for status NEW when the viewer is not an admin.Links to profile.
Responder (avatar & name)The second party in the introduction.Links to profile.
StatusCurrent workflow stage. Color-coded chip. At the DATING stage, a date number is shown on the chip.See Request statuses below.
Action RequiredWhat the matchmaker should do next. Usually matches the primary button on the detail page (for example Accept this match at Available).When one party is busy or asked to unmatch while still at New or Available, the cell shows a party-specific message instead of the default label. See Detail page actions by status.

Filters

  • Shidduch ID — search for a specific request by its numeric ID
  • Status — multi-select; admin users see request counts per status
  • Matchmaker — admin-only; show only requests for a specific matchmaker
  • Date range — filter by created or updated date
  • Met — when on, shows only requests where the couple has already recorded at least one date (status is Dating or later in the dating path)
  • Warnings (admin stats bar) — click to filter the list to overdue requests that still need matchmaker action

Rows with No MM Assigned in the matchmaker column are highlighted so admins can spot introductions waiting for assignment. On Shidduch detail, if no matchmaker is linked yet, an S-Manager who taps the primary advance button is routed to Reassign instead of changing status — see matchmaker workflow → Edge cases.

Support tickets? When a matchmaker or member reports a stuck queue, overdue Due date, or No MM Assigned, start at Support troubleshooting → Stuck Shidduch (matchmaker) before changing status manually.

Request statuses

A shidduch request moves through workflow stages that reflect the matchmaker’s progress with both parties.

StatusMeaning
NewIntroduction has been identified and a matchmaker is about to be assigned. No action taken with the parties yet.
AvailableBoth parties confirmed they are currently available for an introduction.
Taking OnThe matchmaker has accepted responsibility and is beginning to contact the parties.
ContactedThe matchmaker has reached out to at least one party.
Answers RecordedThe matchmaker has gathered responses from both parties about whether they want to proceed.
DatingBoth parties agreed; they are going on dates. The chip shows the current date number (1st date, 2nd date, etc.).
EngagedThe couple has become engaged. A highly positive outcome.
EndedThe introduction has ended without engagement. Decline or unmatch reason is recorded.
On Hold / BusyProgress is temporarily paused, for example while one party is unavailable.
Timed OutThe matchmaker did not advance the request within the allowed time. Can be revived.

List row actions

Each row ends with quick icons and one button. These do not change introduction status except when you open the detail page.

ControlWhat it doesWhen you see it
Urgency icon Automatic reminder — not a button you click. Appears when the Due deadline is today, tomorrow, or already past (tooltip: You are late to take an action in this match). Active requests before Dating / Engaged / Ended, when the SLA clock is running.
Profile resume icons Open each party’s end-user profile in a new context (initiator left, responder right). Enabled once the request is past New — names stay hidden for matchmakers at New, but resumes unlock after availability is confirmed.
View Opens the full Shidduch Request detail page with workflow buttons, contact details, progress, and logs. Default for most rows.
Dismiss Hides the row on your screen only — it does not close or change the introduction. Use when a New or Available row is waiting on a party’s busy / unmatch answer and you want to clear your queue view temporarily. Only when the row is highlighted because a party already chose busy or unmatch while the request is still at New or Available.

Detail page actions by status

Open a row to reach the Required Action section. Button labels come from your brand’s translations — examples below use the default English pack.

Unless noted, each successful advance updates the introduction status, resets the Due deadline from your brand’s matchmaker SLA for that stage, and writes a matchmaker log entry.

Primary and decline buttons

Shidduch statusIntroduction statusPrimary button (example)What happensDecline / secondary
New MATCHED I Am Available Moves to Available (MM AVAILABLE) — matchmaker confirms they can take the case. Not Available — opens the matchmaker snooze flow (marks the matchmaker temporarily unavailable and removes this case from their queue). S-Manager may reassign instead if no matchmaker is assigned yet.
Available MM AVAILABLE Accept this match Moves to Taking On (MM TAKING ON). Decline — decline dialog with required reason; may promote the next queued matchmaker.
Taking On MM TAKING ON Contacted both sides Moves to Contacted (MM CONNECTED) after you have reached out to the parties. — (decline button hidden from this stage onward on the action bar)
Contacted MM CONNECTED Record answers Opens Record answers — per party: Interested, Busy, Unmatch, or Ignore. Both interested → Answers Recorded. Any unmatch → end-shidduch dialog. Mixed answers (for example one busy and one interested) → second dialog with only Continue Waiting or End match — not a hold-duration picker. Put on hold from the Pause/End match menu instead. Full branch table: matchmaker workflow → Record answers. —
Answers Recorded MM RECORDED Record new date Opens Record date (date number + optional comment) → Dating (DATING). Mark Engaged — skips further dates and moves straight to ENGAGED (fires engagement admin notification when configured).
Dating DATING Record new date Logs the next date number (increments the counter shown on the status chip). Mark Engaged → ENGAGED.
On hold / Busy ON HOLD Follow Up Clears temporary party flags and returns the request to Contacted so you can continue outreach. Pause/End match menu — see below.

Pause/End match menu

From Answers Recorded, Dating, or On hold, the outlined menu offers:

  • Pause match — confirm both sides were contacted, then pick 1 day, 3 days, 1 week, or 1 month. Sets ON HOLD and extends Due by that duration.
  • End match — opens the end-shidduch dialog (per-party reasons, optional voice notes when your brand enables voice transcription, optional “both sides dated” date counter, confirmation that both sides were contacted). Closes as ENDED.

SLA timer on the action bar

Before Answers Recorded and Dating, a progress bar shows time left until Due (or Overdue in red). It is hidden during system shutdown and on late dating stages where the SLA bar is not shown.

Full dialog field tables: Matchmaker workflow reference → Dialogs · party answer flags on the list: Party answer flags.

Detail page sections

After you click View on a row, the detail page is organized into collapsible cards. Which cards appear depends on the current status and your role.

Use the left navigation (or stacked cards on a narrow screen) to jump between sections. The page title shows Request: #N — the same introduction id as on Admin Matches.

Request details (header)

FieldWhat it showsNotes
Created When the introduction was first created. Always visible.
Assigned To Names of matchmakers in the current assignment list (comma-separated when several). Brand Manager only. Shows No MM Assigned when the list is empty. Click opens Reassign (or Add Matchmakers when MultiMMS is on).
Update When the introduction status or matchmaker data last changed. Always visible.
Between Initiator and responder full names joined with &. At New (MATCHED), matchmakers who are not Brand Managers see initials only (for example J. S.) — same privacy rule as the list hiding initiator names. Admins see full names.

Contact person

verified — Contact card for outreach. Hidden while status is New (MATCHED) — names and contact details unlock after the case moves to Available or later.

For each party (initiator left, responder right):

LineMeaning
Name (underlined)Member’s display name.
Parent / Single lineWhen user type is parent, shows the parent contact name from the account; otherwise labels the row as Single.
Email and phoneClickable mailto: and tel: links for matchmaker outreach.
Photo policy lineWhether the member allows their photo to be shared in the app vs matchmaker-only — driven by the member’s image policy attribute (only matchmaker vs allowed in app).
Response chip (bold)After Record answers, shows the last recorded choice for that party (Interested, Busy, Unmatch, Ignore) until cleared or the case advances.

Required Action

Visible while the request is in an actionable matchmaker stage: New through On hold (MATCHED, MM AVAILABLE, MM TAKING ON, MM CONNECTED, MM RECORDED, DATING, ON HOLD). Contains the primary advance button, decline/snooze controls, SLA progress bar, and Pause/End match menu — see Detail page actions by status.

Not shown on Engaged, Ended, or Timed Out — use header Revive on closed rows instead.

Match progress

verified — Horizontal progress bar across matchmaker milestones: Available → Taking On → Contacted → Answers Recorded → Dating → Engaged. Completed steps highlight in teal; future steps stay grey. On hold is drawn at the Contacted position on the bar.

Hidden when status is Ended (UNMATCHED).

Singles details

Side-by-side profile cards for initiator and responder, plus an attribute comparison table below.

ElementWhat it shows
Profile card header Avatar, name (privacy rules same as header), link to end-user profile, optional resume icon when a PDF resume exists.
Image policy chip (above avatar) Whether this member’s photo is visible to the other party in the app vs matchmaker-only — based on the photo owner’s image policy attribute and the viewer’s saved preferences (for example hidePartnerImage on the other party’s profile settings). Hidden at New until availability is confirmed. Key catalog: party settings → hidePartnerImage.
Age / height / location / gender chips Quick bio facts with color hints: green when the value fits the partner’s stated preference, red when it does not, neutral when no preference is set. Hover for the partner’s preferred range.
Share actions (matchmaker brands) When photo policy allows in-app sharing and a photo exists, or when a resume exists (except at New), icons open a share dialog to send material to the other party through the workflow.
Attribute comparison table Rows for each comparable bio/preference attribute (identity fields like email and birth year are excluded). Each cell shows one member’s answer; background tint is green for an exact preference match and pink for a mismatch. Center column labels the attribute. Use Show more to expand long lists.

For algorithm scores and deal-breaker columns on the generic introduction page, see view introduction. This Shidduch view optimizes for matchmaker outreach and preference alignment.

Payroll

verified — Read-only payment rows tied to this introduction id. Appears only when your brand enables the Show SME Payments app feature.

ColumnMeaning
MatchmakerWhich SME receives or received the payment.
AmountPayment amount in brand currency.
TypeCategory from the payment-reason code (for example engagement bonus vs date milestone).
ReasonHuman label from the linked general code.
StatusPending or Paid chip.
Created / UpdatedWhen the payment row was created and last changed.

Brand-wide payment management: SME Payments.

Match Progress Update

verified — Chronological matchmaker activity log (not the same as introduction Logs on view introduction). Shown when you are a Brand Manager or the request has moved past New.

Entry typeWhat you read
Status changeWorkflow advance (for example moved to Contacted).
Date logRecorded date number and optional comment from the record date dialog.
Party answersInitiator/responder interested / busy / etc. appended when recorded.
Decline introductionMatchmaker decline with reason text.
Change requestMember-initiated hold/unmatch flag while still at New or Available (shown in red).
Unmatch reasons (on end)Per-party text, coded reasons, and Other reason pulled from the closed row — same fields as Shidduch Declines.

Brand Managers also see which matchmaker wrote each line.

Comments

Matchmaker-to-staff notes for this case only — not visible to members. Shown under the same visibility rule as Match Progress Update.

  • Earlier comments appear newest-last in the stream above the input box.
  • Type a note and press Enter or click the send icon to append — failures show an alert if the save does not complete.
  • Brand Managers also see Add shadchan info buttons per party — opens a dialog to attach external lookup data to that member’s profile (stored as admin-sourced external info, not shown on this introduction row).

Introduction-centric tools (chat stats, Match Advisor, admin status override, member decline chips): view introduction. Status mapping and assignment queues: matchmaker workflow (reference).

Header and admin actions

On the detail page, the top action bar (next to the request number) holds admin-only tools. Workflow buttons live in Required Action below.

ActionWhat it doesWhen it appears
Revive Reopens a closed or timed-out request: status returns to Contacted, clears prior unmatch reasons, marks both parties interested, and writes a revive log entry. When status is Timed Out (MM TIMEOUT) or Ended (ENDED).
Reassign Pick a different available matchmaker (shows current + queued order). Requires a decline reason; promotes the chosen id into the active slot. Admin (B-Manager) only; hidden when Engaged.
Add Matchmakers Adds one or more matchmakers to the current assignment list without removing existing ids (multi-matchmaker brands). When the MultiMMS app feature is enabled.

Click any row to open the full shidduch request detail view: contact details, attribute comparison, optional payroll (when ShowSMEPayments is on), matchmaker logs, and comments.

Status names: Shidduch screens use short labels (New, Available, …). The same row on Admin Matches uses MATCHED, MM AVAILABLE, etc. See the mapping table on matchmaker workflow (reference).

When a request is stuck

Use this checklist when support receives a ticket about the matchmaker queue — before reassigning or forcing status from introduction detail.

Symptom on this listStart here
No MM Assigned highlighted row No matchmaker assigned — S-Manager Reassign.
Member email “no matchmaker available” Matchmaker declined — queue empty — assign a new SME and refresh next backup ids.
Due shows Overdue or urgency icon Overdue on Shidduch list — matchmaker advance, hold, or SLA auto-decline.
Action Required names a party and “hold” / “unmatch” Action required — party busy — contact party; Dismiss only clears your list view.
Status Timed Out (MM TIMEOUT) Overdue on Shidduch list — Revive or end shidduch.

Full operator tables (MM unavailable cascade, permission gates, introduction detail vs Shidduch detail): Support troubleshooting → Stuck Shidduch (matchmaker).

Learn more