Code-backed checklists when members or matchmakers report a stuck introduction
Last updated: 2026-10-28
Overview
Use this page when support receives a ticket about introductions — before changing status manually. Each section lists what to verify in Admin, what it usually means, and where to read the full workflow.
verified — The snapshot block mirrors the singles app My introductions summary (unique partners). The horizontal Intro Statistics chips count introduction rows. Both are correct for different questions — do not expect the same integer.
Quick decision tree
Ask what the member is looking at. App My introductions screen (five stat rows, no Total) → compare those five labels to Admin Member app snapshot. Ops audit of every introduction row → use chips or profile introductions table.
Declined vs didn’t pick up. Explicit not interested / decline → You declined. Missed deadline, busy, self-end, or freeze after the card was shown → You didn't pick up. See Member app snapshot → Declined vs didn’t pick up.
Compare partner count, not row count. If chips are higher, search profile introductions for the same partner twice (re-suggestion). The snapshot keeps the stronger outcome only.
“Didn’t pick up” disputes. Open the introduction → Logs. If no suggestion reached that member’s Lora chat, the snapshot correctly omits them from didn’t-pick-up buckets even when Admin shows TERMINATED or expired RAW.
Declined vs still open. A single open RAW row does not change You declined unless that partner’s best counted outcome is a decline.
After unmatch.Matched may still include a partner the couple later UNMATCHED — the app treats that as “we matched once.” Current workflow stage is on the introduction row, not the snapshot.
Stale app screenshot.verified — My introductions refetches counts only when the member opens that screen again (no live update while they stay on the page). Admin refetches when you reload the end-user profile. Ask both sides to refresh before escalating.
On the end-user profile, open Activity Information and read Available Introductions. When the count is 0, hover the field — Admin shows a short reason (same wording the matcher stored for support).
Reason shown on profile (tooltip)
Plain meaning
What to check next
Profile is not active.
verified — Profile status is not active (snoozed, pending approval, blocked, engaged, etc.).
Profile Status Changes — restore active when appropriate, or explain why matching is paused.
Too many non-inspected introductions.
verified — Too many open suggestions the member never opened.
Inspection backlog (step-by-step) · inspection rules — member must tap into partner profiles from the suggestion card (eye icon / Inspected logs).
Has a pending availability check on an introduction.
verified — Member is initiator on an AVAILABILITY CHECK row.
verified — Brand caps how many introductions one person may have in a category (raw / pending / match / dating) for their gender.
App Settings — rows describing max introductions per category and new raw available (Algorithm category). Close or advance older rows in that category.
Reached the monthly introduction limit.
verified — Monthly introduction cap for the brand is exhausted.
App Settings — max introductions monthly (or equivalent description). Wait until next month or adjust with brand manager approval.
Count is 0 but the tooltip shows no reason?verified — the member has used up the brand’s total introduction allowance: all active introductions across every category (suggestion, match, pending, dating) counted together, set per subscription plan in App Settings (max introductions rows for Free / Basic / Medium / High, Mobile App category). A brand may split that total per gender using the matching … female / … male rows next to them; leaving a gendered row empty means everyone on that plan shares the plan-wide number. A per-member override on the profile takes precedence over both. The allowance that actually binds is the lower of this total and the per-category cap above, so raising one without the other may change nothing. Close or advance an existing introduction to free a slot.
If the count is above zero but the member still sees nothing, check Potential Matches for stored scores and whether the matcher job has run recently — see potential match scores (reference).
Inspection backlog — too many unopened suggestions
Use when the profile tooltip shows Too many non-inspected introductions., or support suspects the member is blocked because they never opened existing suggestion cards.
verified — The matcher pauses newRAW and INITIATOR APPROVED suggestions when someone has at least as many “unopened” rows as your brand’s max raw non-inspected limit in App Settings (Algorithm or Mobile App category — search App Settings for that phrase). When the setting is blank or missing, this pause does not run.
What counts as unopened
Introduction status
Which party
Counts when…
RAW
Initiator
verified — Their Inspected eye icon is empty on the introductions list (no logged inspection where they opened the responder’s profile).
INITIATOR APPROVED
Responder
verified — Same rule on the responder’s side — it is their turn to open the initiator’s profile.
Does not count:FROZEN, MATCHED, closed statuses, or rows where the member is waiting on the other party. Opening a profile from chat history without logging an inspection does not clear the backlog — the member must open from the active suggestion card on Potential Matches (or the equivalent home/Lora entry point).
Diagnose in Admin (about 2 minutes)
On the end-user profile, confirm Available Introductions is 0 and the tooltip names the non-inspected reason.
On introductions list, filter by RAW and INITIATOR APPROVED; search the member’s name.
For each row where they must act, check their column’s Inspected eye icon. Count empty icons.
Compare the count to your brand’s max raw non-inspected setting. At or above the limit → backlog block is expected.
After the member opens one card, refresh and open detail Logs — expect Inspected_half or Inspected_full. When total unopened rows drop below the limit, Available Introductions should rise on the next availability refresh.
What to tell the member
Open each waiting suggestion from Potential Matches (tap the card — not only the chat thread).
On brands with two degrees profile, they may need to tap through the partial view first; approve is not required to clear the inspection — opening the profile is.
Decline or not for now on unwanted rows also removes them from the active backlog (different status).
When ops should not raise the cap
Raising max raw non-inspected without coaching the member may flood them with suggestions they ignore. Prefer clearing the backlog first. If the brand genuinely needs a higher cap, change App Settings with brand-manager approval and publish settings.
Match Advisor shows AI match analysis is not ready yet. It runs shortly after a new suggestion is created. for a long time
Background job not finished yet, or page not refreshed after a run.
Wait a few minutes and refresh; use Run match advisor now (requires Edit) to retry. If Advisor could not complete appears, retry after engineering fixes the model/config issue.
Close but blocked section or list warning icon
Matcher recorded soft deal-breaker attributes — promotion rules keep the row in PENDING APPROVAL even when hard contradictions are empty.
AI conflict brain icon on list or Personality conflicts on detail
Matcher stored AI personality conflicts (clear opposites on the 1–9 trait scale). When your brand holds these for staff review, promotion from PENDING APPROVAL can stay blocked even when hard contradictions and soft deal breakers are empty.
Read per-party lines on Personality conflicts. Confirm whether brand policy allows Approve despite the conflict, or whether profiles need updated AI analysis first. Compare preview shows live conflicts before save — useful when manually creating an introduction.
Checks before suggesting on compare (same pair) or rank icon on potentials
Jev hold from configured match-check questions after ranking or advisor follow-up — automated release stays blocked until staff review.
Open compare or potential matches for flag text; adjust thresholds on Match check questions if ops agrees the question is too sensitive. Manual Approve still available when brand policy allows.
Declined before (stop)
Pair was introduced before and a member declined — code check blocks auto-release regardless of advisor pitches.
Do not approve without explicit override policy; see earlier decline in the topic catalog.
Advisor could not complete on detail but compare shows only soft (orange) Jev flags
Match Advisor job failed; soft band flags alone do not hold automated release. A failed Jev call during a failed advisor pass also does not add a new hold gate.
Retry Run match advisor now when engineering clears the error; read red holds and stops before bulk approving. Threshold tuning: worked examples.
Advisor succeeded; row still pending; compare shows red Jev holds
High-confidence match-check hold (pending due to match checks) or another admin-review gate still active.
Open Match check questions if ops agrees the question is too sensitive; manual Approve when policy allows.
Hard contradictions empty; advisor finished; still pending
Brand pending introduction mode, soft deal breakers, personality conflicts, tolerance/decline-history chips, low match scores below minimum go to pending, or other admin-review gates — not an advisor failure.
Read Pending reasoning and status reason chips; approve manually when ops sign off.
Row auto-moved to RAW / AVAILABILITY CHECK without staff click
Expected when Match Advisor completed, no hard contradictions, and admin-review gates passed (or advisor failed but release rules still allowed promotion).
Confirm Logs for a status change with an automated reason; set member expectations that the suggestion is now live in the app path for that status.
Many rows need release at once
Same gates as above — automation will not clear them without staff action.
Filter to PENDING APPROVAL, review warning icons, then use Approve Selected (@count) on the introductions list (only ticked pending rows are approved). Same effect as Approve on each detail page.
Bulk approve shows partial failure
verified — Some ticked rows could not change status (permission denied, invalid pair, or server error) while others succeeded.
Refresh the list; approve remaining PENDING APPROVAL rows from detail. Confirm the user’s role includes Edit on view introduction — list access alone is not enough. See status change errors.
Soft deal breakers
Member reports a “close but blocked” suggestion, or the list shows the Soft DB warning icon.
verified — Soft deal breakers flag a near-miss on a configured attribute. They are softer than hard deal breakers on potential matches: the member must confirm in the app before the introduction advances.
Symptom
What to verify in Admin
Typical action
Initiator says they cannot see a suggestion yet; status looks like “close but blocked” on initiator side
Detail → Close but blocked shows chips under First - Intiator. Logs may show a recent status parked before RAW.
Ask initiator to complete the in-app check-in (accept or decline the near-miss). Do not manually force RAW unless brand policy allows bypassing member consent.
Responder says they were asked an extra question after staff approved
Chips under Second - Responder on detail; status may be responder-side close-but-blocked before INITIATOR APPROVED.
Responder must answer in the app. Staff Approve alone does not skip this when soft flags exist on the responder.
Support does not understand chip names (for example heightPref)
Match chip text to attributes; read optional explanation paragraph under that party’s chips (brand copy).
Explain the near-miss in plain language to the member; adjust attributes only through normal profile/questionnaire workflows — not by editing the introduction row.
Icon on list but detail card missing
Compare-only URL or stale list row — refresh list and open the saved introduction id again.
Re-open from introductions list; card requires at least one stored soft-DB attribute on the row.
Row matched long ago; card still visible
Expected — card is historical context, not “currently blocked.”
Use for coaching; no action unless a new ticket is about the original near-miss.
Staff questions about AI pitches, red contradiction counts, or “advisor never ran.”
Prerequisites: Brand enables Match Advisor insights (app feature) for the full saved-row advisor card (run-now, scoring table, list contradiction count). Compare preview can still show stored list-rank checks and pitches without a saved row when ranking already ran — see compare list rank (reference).
Symptom
What to verify
Action
AI match analysis is not ready yet. It runs shortly after a new suggestion is created. for a long time
Background job queue delay or failure row (Advisor could not complete).
Wait a few minutes and refresh. If error text persists, use Run match advisor now (requires Edit) after engineering clears model issues.
Red count on list; staff unsure what failed
Open detail → Hard contradictions bullet list.
Review lines before approving pending rows. Empty list after refresh means advisor cleared hard flags — count on list should drop to blank.
Ops expected auto-release from pending; still waiting
Hard contradictions non-empty, soft deal breakers on row, or brand minimum-go-to-pending / tolerance rules.
Suggested message for the initiator / Suggested message for the responder on detail (suggestions for staff — not editable templates in Admin).
Coach using pitch text; member-visible copy comes from brand comms and app surfaces, not from editing this card.
Compare screen had no Match advisor (AI) section
verified — Normal when no list-ranking assessment exists for this pair yet (no stored match checks, rank detail, or pitches).
Review bio scores and attributes on compare; run your brand’s rank-potentials batch if ops needs checks before manual create. After create, open saved detail for Match Advisor run-now and pending auto-release. Guide: compare list rank → When the section appears.
Compare shows checks but staff expected saved-row advisor
Compare loads assessment-store data; saved advisor runs on introduction id after create.
Use compare evidence to decide on Create This Now; then use detail Run match advisor now if pitches are stale or pending release still blocked.
Staff reversed proposer and responder before releasing the suggestion — or support is reconciling a Swapped log row.
verified — Swap Direction is available only on introduction detail while status is PENDING APPROVAL (requires Edit). Full field guide: view introduction → Swap direction.
Symptom
What to verify
Action
Ticket says “wrong person is proposer” before members saw the intro
Status still PENDING APPROVAL; swap button visible.
Click Swap Direction, confirm warning if who goes first preferences conflict, then Approve so the new initiator receives RAW or AVAILABILITY CHECK.
Created By: shows Swapped
Expected after staff swap or member frozen re-activation that reversed direction.
Confirm Swapped log timestamp matches the ticket; no member notifications went out if status never left pending before swap.
Bio Score percentages look swapped between names right after swap
Display realigns on page refresh; stored introduction scores may lag one load behind role columns.
Refresh detail; if still wrong, compare with potential matches for the current initiator — do not re-swap unless direction is still incorrect.
Member already on RAW but ops want to reverse direction
Swap Direction is hidden after pending — swap is not available post-release.
Do not use status picker to mimic swap; escalate to engineering/product — closing and recreating may be required depending on brand policy.
Whos First preferences (party settings)
verified — On introduction detail, scroll to First Asked Settings / Responder's Settings. The Whos First row shows what the member saved in premium account settings (plain strings such as first, second, or random).
What you see
Support note
first on initiator before swap
Expect an extra confirmation when staff click Swap Direction — member wanted to stay proposer.
second on responder before swap
Same confirmation — member wanted to stay responder.
random, empty, or other text
Swap proceeds without that warning. If ticket text mentions “me / other / random” from the member app, compare the exact Value column on detail — only first and second trigger Admin’s warning today.
Delete icon on a settings row
Removes that key from the profile, not from the introduction. Use only when ops intentionally clear a bad preference — member can set it again in the app.
verified — Only the initiator sees the Lora availability question. The list Due column is usually empty at this stage.
Confirm intro availability check is enabled under App Settings → App Features.
Ask the member to open Lora chat and answer the short availability question (not the full match card yet).
On detail Logs, look for Reminder Sent rows labeled introAvailabilityCheck — reminders continue until they answer or the final wave closes the row.
If they chose I’m busy, status stays AVAILABILITY CHECK until they answer or time out.
If logs show Status Change → RAW with no Question row, the system skipped the question (answered within 24 hours or another open suggestion exists) — member should see the full card on Potential Matches.
verified — The member Extend control appears only when all of the following are true: your brand enables both premium and extend introductions under App Settings → App Features (publish after changes); the introduction status is RAW or INITIATOR APPROVED; and the member is viewing the suggestion on Potential Matches or the home pending-suggestions avatar row — not inside an open Lora chat thread.
Support checklist (about 3 minutes)
Open introduction detail — confirm status is RAW or INITIATOR APPROVED and Must respond until is still in the future (or recently passed — extend only helps before auto-ignore runs).
Under App Settings → App Features, confirm premium and extend introductions are on; run publish settings if you changed them recently.
Check the member’s token balance vs your brand’s hour extends package in payments settings — price is hourly rate ÷ 24, rounded up to whole tokens.
Ask where they tapped Extend — if only inside Lora chat, explain the button lives on the Potential Matches card instead.
After they retry, refresh detail — success adds an Extenstion row (By: N hours) and moves Must respond until later. No log row means payment failed or features were off.
What the member reports
Plain meaning
What to do
Button not visible at all
verified — Premium and/or extend introductions disabled; wrong status; or they are in Lora chat instead of Potential Matches.
Walk through checklist steps 1–4 above.
Tapped Extend → token purchase screen
verified — Balance below the hour-extends package cost.
Member must buy tokens first; app may show an extend suggestion info screen with a no tokens param.
Paid but deadline unchanged
Rare payment callback failure or they refreshed before sync.
Wait one minute and refresh Admin; escalate with introduction id if still no Extenstion row.
Hours added seem too short
verified — App Settings minutes for extend converts to whole hours only (90 minutes → 1 hour, not 1½).
Explain rounding; brand manager adjusts the setting if policy requires longer extensions.
When Add New on the introductions list fails, the dialog or API message maps to:
Message (typical)
Plain meaning
Fix
Profile is not active or not found
verified — One or both profile ids are wrong, deleted, or status is not active (engaged pairs may be allowed when one is engaged with the other).
Verify UUIDs on end-user profiles; restore active status when appropriate.
introductionAlreadyExists (duplicate pair)
verified — An open introduction already links this pair for your brand (any active status). The database blocks a second row for the same two profile ids.
Search list by both names or ids; use existing row instead of creating a duplicate.
You already have an active match for this couple…
verified — The creator is a matchmaker who already holds a live introduction for this same couple (same matchmaker id in current). A different matchmaker may still open the pair; the same matchmaker cannot create a second live row.
On My Matches, find the existing case with these two members and advance or close it. Common when staff click Add twice for the same pair.
Invalid profile id format
Id is not a valid UUID.
Copy id from the profile header chip, not phone or email.
Use when a ticket mentions My Matches, a matchmaker queue, or “no one is working my case.” Open the row on Shidduch Requests and compare status, Due, Action Required, and matchmaker assignment to the table below.
No matchmaker assigned
What you see
Plain meaning
What to do
No MM Assigned in the matchmaker column; row highlighted on the list
verified — The introduction reached MATCHED (or later) but no matchmaker id is in the current queue.
An S-Manager opens Shidduch detail → Reassign (or Add Matchmakers when multi-matchmaker is on). The primary advance button redirects to reassignment until someone is assigned — see matchmaker workflow → No matchmaker assigned.
Matchmaker declined — queue empty
What you see
Plain meaning
What to do
Status still MATCHED or MM AVAILABLE; No MM Assigned; members report “no matchmaker” email
verified — Every id in current and next declined or was inactive; the system cleared the queue and sent both members an end-user matchmaker email with parameter NO_MM (no matchmaker available).
Assign a new matchmaker via Reassign. Add ids to next when you want a backup order. Full assignment rules: matchmaker workflow → Assignment.
One matchmaker declined; another name appears
verified — The first id in next promoted into current; SLA deadline reset from MATCHED minutes.
Confirm the new matchmaker is active on SME Profiles; no action if the case already moved forward.
Matchmaker became unavailable (busy or deleted)
What you see
Plain meaning
What to do
Matchmaker status changed to busy or deleted on SME Profiles; members received matchmaker unavailable message
verified — Open introductions at MATCHED, MM AVAILABLE, or MM TAKING ON for that matchmaker are auto-declined with reason matchmaker busy. The system tries to promote next the same way as a manual decline.
Check Shidduch list for affected rows; reassign if the queue is empty. Members who chose that matchmaker on their profile may need a new SME — see communications reference for mmUnavailable templates.
Overdue on Shidduch list
What you see
Plain meaning
What to do
Due shows Overdue or Tomorrow; urgency icon (tooltip You are late to take an action in this match)
verified — Must respond until is within about 24 hours or already past. This is automatic — not a manual “mark urgent” flag.
Matchmaker should advance the case or use decline / put on hold. Filter the list stats bar by warning to see all overdue actionable rows.
Overdue at New or Available for a long time; matchmaker may have been auto-declined
verified — A scheduled job declines overdue MATCHED / MM AVAILABLE rows (SLA pass) and may promote next or clear the queue.
Refresh the list; check whether a new matchmaker was assigned or NO_MM was triggered. Reassign if the queue is empty.
Status MM TIMEOUT (Timed Out on Shidduch list)
verified — Matchmaker did not advance before the SLA deadline after reminders.
Staff with the right role: Revive on Shidduch detail → returns to Contacted with both parties marked interested. Or close via End match if the case should end.
Action required — party busy or wants to end
What you see
Plain meaning
What to do
Row highlighted; Action Required names one party and “hold” or “unmatch”
verified — At New or Available, a party flag is stored on the introduction (busy or unmatch) until staff clears it or advances past Contacted.
Contact the named party; use put on hold, end shidduch, or record answers to resolve. Dismiss on the list only hides the highlight in your browser — it clears the party flags via a status update but does not close the introduction.
Status ON HOLD (Busy / On Hold)
verified — Matchmaker paused the case until the hold date chosen in the dialog (1 day / 3 days / 1 week / 1 month). Member Available Introductions may show 0 with reason Has an introduction on hold..
Use when a member chose not for now on a suggestion, or cannot re-open a parked match from their frozen list.
verified — FROZEN means one party parked the row on their frozen list. Admin cannot un-freeze it — only that member can re-activate (back to RAW) or release (closes as TERMINATED for both). Full lifecycle: introduction statuses → Frozen (not for now).
“I can’t freeze another suggestion”
What the member sees
Plain meaning
What to do
Limit-reached message when tapping not for now
verified — They already have the maximum number of frozen suggestions allowed per brand (App Settings max frozen introductions; default 2 when unset). The app shows a branded popup (info screen event frozen limit reached) — not a generic error.
Ask them to release or re-activate an older frozen row first, or decide on an active suggestion (approve / decline). Filter introductions list by FROZEN and check Logs for who froze each row.
“I can’t re-open my frozen match”
Check in Admin
Plain meaning
What to do
Status FROZEN; ticket is from the other party
verified — Only the freezer may re-activate or release. The other party already received a new suggestion when the freeze happened.
Explain that the parked row belongs to the freezer; the other member should use their active suggestions instead.
Available Introductions is 0 on the freezer’s profile
verified — Re-activation needs a free introduction slot on the freezer’s account (same rules as new suggestions).
Resolve the reason on the profile tooltip (no new suggestions table) — close another open row, clear inspection backlog, finish availability check, etc.
Held partner is snoozed, deleted, or not active
verified — Re-activation is blocked when the partner cannot receive a Zuug introduction right now. The app shows a partner not available info screen and offers release instead (event frozen partner unavailable).
Check the partner’s profile status and snooze schedule. When the partner is active again with a free slot, the freezer can retry re-activate — or release to close the row.
Freezer’s slot is zero for a different reason (not partner)
verified — Re-activation recalculates slots; if the freezer has no free introduction allowance, the API returns a no available slot style error even when the partner is fine.
Fix the freezer’s blocking reason on their profile (no new suggestions table) — pending intro, on hold, inspection backlog, etc.
Held partner’s Available Introductions is 0
verified — Same partner-unavailable gate: the held match cannot return to RAW until the partner has an open slot.
Fix the partner’s blocking reason (pending intro, on hold, non-inspected backlog, etc.) or advise the freezer to release.
Member was the responder when they froze; re-activate succeeds
verified — System may swap initiator and responder so the freezer becomes the proposer again — watch for a Swapped log row, same as staff Swap Direction on pending approval.
Expected behavior — confirm status returned to RAW and the partner can respond again.
“The frozen match disappeared from my list”
What you see
Plain meaning
What to do
Member released the row from the app
verified — Status → TERMINATED; both parties return to the suggestion pool.
Normal close — no Admin action unless policy requires a follow-up call.
Status still FROZEN in Admin but member cannot find it in the app
App build or account mismatch — rare.
Confirm they are signed into the correct account; check Logs for the Status Change → FROZEN row (author = freezer’s first name). Escalate with profile id + introduction id if the app list is empty but Admin shows FROZEN.
Member-app visuals:
Waiting for screenshot. Capture: frozen suggestions avatar row with snowflake badge (slug introductions-frozen-list).
Waiting for screenshot. Capture: branded popup after tapping not for now when the member already has the maximum frozen rows allowed (info screen event frozen limit reached; slug introductions-frozen-limit-reached).
Waiting for screenshot. Capture: partner not available info screen with release offer when re-activate is blocked (event frozen partner unavailable; slug introductions-frozen-partner-unavailable).
Use when members or matchmakers report a broken engagement, still see engaged on a profile, ask why they were not notified, or wonder when they can match again.
Recording the break is an ops action on the introduction detail page — not a Shidduch-detail primary button. Full step-by-step: Engagement broken — ops playbook.
“We’re still shown as engaged in the app”
Check in Admin
Plain meaning
What to do
Introduction status still ENGAGED
verified — Staff have not recorded the break on this row yet (or a different introduction id is still engaged).
Open introduction detail → status picker → ENGAGEMENT BROKEN with a documented reason. Confirm both Profile Status Changes show active after save.
Introduction is ENGAGEMENT BROKEN but one profile still engaged
Rare sync issue or member signed into wrong account.
Refresh profile; check status logs for introduction engagement broken automated reason. Escalate with both profile ids if mismatch persists after refresh.
Member engaged with someone else on a different open row
verified — Profile status follows the current engaged introduction. Search all introductions by member name for another ENGAGED row.
Resolve or break the other row before expecting active on the profile.
“Nobody told us the engagement ended”
What to verify
Plain meaning
What to tell members / ops
No dedicated engagement broken member message in Communications
verified — The platform does not ship a default push/email tied only to ENGAGEMENT BROKEN introduction status.
Do not promise an automatic “engagement broken” notification unless your brand added a custom comm.
Published Profile Status Updated comms exist
verified — When both profiles return to active, the system may send comms configured for that profile-status transition (if published). Check Communications filtered by Profile Status Updated — see communication trigger events.
If nothing is configured, members only see the profile status change in the app after they refresh — ops may send a one-time manual comm.
Matchmaker end-user matchmaker email templates
Separate from introduction status — used for MM queue events (for example NO_MM), not engagement broken.
Route matchmaker comm questions to Shidduch workflow docs, not this status.
“When can we get new suggestions again?”
Confirm both profiles are active (not snoozed or pending approval) on end-user profiles.
Read Available Introductions on each profile — should be above zero when no other blocker applies (open pending intro, on hold Shidduch, inspection backlog, monthly cap, etc.). See No new suggestions.
ENGAGEMENT BROKEN rows do not block new slots the way an open ENGAGED row does — the milestone is closed for matching purposes.
Matchmaker engagement payments
verified — Pending SME payment rows with reason engagement for this introduction auto-cancel when staff change status away from ENGAGED (including ENGAGEMENT BROKEN). Already-paid engagement payments are not reversed automatically — finance reviews those. Check Payments after you save the status change.
List paging duplicates or “missing” rows
When the global introductions list shows the same couple twice on one page, or an introduction seems to vanish when you change pages.
Symptom
What is happening
What to do
Same Intro ID appears twice while one page is still loading
verified — Chunked loading can briefly deliver duplicate rows from the server. Admin collapses them to a single visible row (first copy wins) so bulk approve and LLM export do not count the pair twice.
Wait for loading to finish; refresh the page if the grid still looks wrong. Use Matches search when you need exactly one row.
Introduction shows on page 2 but not page 1 (or the reverse), with no filter change
verified — The list sorts by last updated time. When thousands of rows share the same timestamp (common after bulk jobs), the database may return tied rows in a different order on each page request. Engineering tracks a stable tie-breaker; until then paging across ties is not guaranteed stable.
Search by introduction id or filter by status/date to narrow the set. Open the member’s profile introductions tab when you know which person is involved.
Numeric id search shows one row, then extra blank batches
verified — Digit-only Matches search loads only the first chunk; later background chunks are skipped so the same id is not repeated.
When the Status change dialog fails after you pick a new status and enter a reason.
Message (typical)
Plain meaning
What to do
Open introduction already exists
verified — The database blocks this status change because one of the members would have two conflicting open introductions (for example moving into ENGAGED or DATING while another open row already exists for that person).
Search the introductions list for each party’s name; close or advance the other open row first, then retry. Do not create a duplicate pair — use the existing introduction id.
Generic error / page does not refresh
Network or rare server failure.
Refresh detail; check Logs for a new Status Change row. Escalate with introduction id and exact time if the error repeats.
Approve or bulk approve does nothing / access denied
verified — Status changes require Edit on view introduction, even when the button appears on the introductions list.
Ask a manager to grant edit access on view introduction, or have someone with that permission approve the row.
Some introductions could not be approved. Please review and try again. after Approve Selected (@count)
verified — At least one ticked PENDING APPROVAL row could not change status while others may have succeeded. Common causes: missing Edit on view introduction, Open introduction already exists for one pair, or a transient network error. Admin does not show which introduction ids failed.
Refresh the list; filter to PENDING APPROVAL; open each remaining row on detail and approve individually. Check Logs on rows that did advance. See also stuck in pending approval.
Manual create duplicates use the same introduction already exists family of errors — see Manual create errors.
Share phone in chat
Use when members report a missing share phone button, a blocked info screen, or when Admin Logs do not show a phone exchange that happened in chat.
verified — On brands with the share phone app feature, matched pairs may exchange numbers through a guided workflow (info screens + chat messages), not by typing digits freely in the thread. Admin merges chat-store events and member-app analytics into Logs as Share Phone Request, Share Phone Message, and Phone Share Number Viewed rows — see introduction log types.
Approved matches box — when rows appear
verified — On the member app Introductions home screen, the Approved matches section lists the same row widget as the Matches tab (same phone icons, subtitles, and share-phone handlers). Which introductions appear in each place depends on whether chat is enabled for the brand:
Chat app feature
Approved matches box shows
Matches tab shows
Support note
On
Active MATCHED introductions with no chat messages yet (conversation exists but no first message).
Active matches that already have at least one chat message.
verified — Once the conversation has any message — including a share-phone chip (woman share or man request), not only typed chat — the row moves off Approved matches and appears on the Matches tab only. Share-phone icons work in both places while last message is still empty; guide members who have not started the thread yet to the Introductions tab box.
Off
Every active match (there is no Matches-tab fallback).
Not used for listing (chat is off).
verified — Phone-share and other match actions still use this box; there is no separate Matches list to check.
Rows leave Approved matches when the introduction is no longer active (ended, unmatch, etc.) — same rules as the Matches tab.
Waiting for screenshot. Capture: member app Introductions tab — Approved matches box with at least one MATCHED row showing the trailing phone icon (slug introductions-approved-matches-box).
Where members tap (member app)
verified — Share phone is not a free-text chat field. Members move through branded info screens tied to the Share phone workflow trigger event. If a required screen is missing or not published, the app does not show a fallback popup — the tap simply does nothing useful until Content publishes the step.
Screen
Who
What they tap
What happens
Matches list row
Woman, eligible pair
Small phone-forward icon on the right of the row
verified — Opens female before share info screen → on confirm, posts allowed to share in chat → female after share ack → Admin log Share Phone Message.
Matches list row
Man, eligible pair
Small phone-callback icon (not the row title tap)
verified — Opens male before share → on confirm, posts share request in chat → male after share ack → Admin log Share Phone Request.
Partner profile (matched)
Woman, eligible pair
Primary bottom button (allow phone share wording on most brands)
verified — Same share flow as the matches-list icon above.
Partner profile (matched)
Man, eligible pair
Primary bottom button may show request wording, but the action opens the blocked / ineligible info screen until the woman has shared
verified — Expected: man must use the matches-list phone-callback icon (or wait for her share) to start the request flow. Do not treat a blocked screen on profile tap alone as a misconfigured request button.
Matches list row
Man, after woman shared
phone-in-talk icon replaces the request icon on the row
verified — Opens view partner number info screen with her number (from chat or profile). Tapping the request icon when she already shared also jumps here instead of sending a second request.
Lora home chat message
Woman, eligible pair
Tappable link or button wired to share phone in a Lora message (brand-configured)
verified — Same share flow as the matches-list phone-forward icon. If she is not eligible (wrong gender, matching-process answers, or feature off), the tap does nothing.
Introductions tab → Approved matches box
Woman or man, eligible pair
Same trailing phone icons as the Matches list row (not the row title tap)
verified — The introductions home screen reuses the same match row layout and share-phone handlers as the Matches tab. Support can guide members to either tab — icons and subtitles behave the same.
Matches list row
Either party — pair not eligible for app share
Primary action
verified — Start chat when chat is on; otherwise no share-phone actions. No share-phone log rows.
Matches list row — icon and subtitle states
verified — On eligible MATCHED introductions, the small circular phone button on the right of the row (and the subtitle under the partner name) change together. Tapping the row title or avatar still opens chat or the partner profile — only the phone icon starts the share workflow.
Who
Stage
Trailing icon
Subtitle under partner name (typical English)
Tap icon →
Woman
Has not shared yet
phone-forward
Allow phone share
female before share → share message in chat → female after share
Woman
Already shared her number
phone-in-talk
Phone number shared
female after share acknowledgment only (no second chat message)
Man
Partner has not shared yet; he has not requested
phone-callback
Request phone share
male before share → request message in chat → male after share
Man
He already sent a request; partner has not shared
phone-callback
Request sent (subtitle stops repeating the request CTA)
male after share acknowledgment only
Man
Partner shared her number in chat
phone-in-talk
Phone number shared
view partner number info screen (number from chat or profile)
Support tip: if a man says the row still shows Request phone share after he tapped, ask him to pull to refresh the Matches tab — the subtitle updates when the app detects his request message in chat. After the woman shares, his icon switches to phone-in-talk automatically when chat syncs.
View partner number (man, after she shared)
verified — After a Share Phone Message exists in chat (woman completed her share step), the man can open a read-only info screen that shows her number. This step does not post another chat chip — it only logs Phone Share Number Viewed in Admin when analytics is available (same matched activity window as Chat stats).
How the man opens the number
Typical Admin log message
Support note
Matches list trailing phone-in-talk icon on the row
Viewed partner phone number (match list)
Most common after chat sync shows her share chip.
Profile primary action or request flow when her share already exists in chat
Viewed partner phone number (after request)
Same screen — different wording in Logs so support knows which entry path he used.
Other paths (rare)
Viewed partner phone number
Generic analytics label when the source is not one of the two common paths above.
If members report “I shared but he still cannot see my number”, confirm Share Phone Message appears in Admin logs and chat shows her chip — Phone Share Number Viewed alone only proves he opened the popup later, not that she shared successfully.
Two ways to open the same screen (both create a Phone Share Number Viewed log row):
Matches list — After chat sync, tap the trailing phone-in-talk icon on the row. Admin usually shows Viewed partner phone number (match list).
Request / profile path — Tap phone-callback (or another entry) when her Share Phone Message already exists; the app opens the number popup instead of sending a second request. Admin usually shows Viewed partner phone number (after request).
Support can use the log wording to see which entry path the member used — the on-screen info screen is the same; only the analytics label differs.
Waiting for screenshot. Capture: MATCHED man after woman shared — view partner number info screen (workflow param view partner number) from phone-in-talk on the matches list or post-request flow (slug introductions-view-partner-number).
What members see inside the chat thread
verified — Successful share steps post special chat rows (not free-typed digits). Each appears as a centered chip with a phone icon — the same visual style for both steps below. Members cannot type a phone number into the thread to bypass the workflow.
Step (member action)
What the sender sees in chat
What the partner sees in chat
Matches list subtitle when this is the latest message
Admin log row
Woman shares her number (after female before share)
You shared your phone number (brand wording)
They shared their number — brand copy may append her digits (typical English ends with the phone number)
Phone number shared
Share Phone Message
Man requests phone share (after male before share)
You shared your phone number (same chip wording as above — it is still a workflow chip, not a typed message)
They shared their number — no digits on the request step (her number is not in the message yet)
Phone number shared (same preview text as the woman’s share step)
Share Phone Request
Support tips:
Do not expect the man’s request chip to show the woman’s phone number — he opens view partner number only after her Share Phone Message row exists in Admin logs (and chat syncs).
After either chip is sent, the introduction may leave the Approved matches box on brands with chat on — the workflow message counts as conversation activity even when no one has typed ordinary chat yet.
On the Matches list, when the latest message is either share-phone type, the subtitle under the partner name shows Phone number shared instead of the request CTA — use the trailing phone icon column (see row states) to see whether share or request is still available.
Waiting for screenshot. Capture: member chat on a MATCHED introduction — at least one centered phone chip after a woman share or man request (slug introductions-share-phone-chat-chips).
Admin Logs merge chat chips and analytics into Share Phone Message / Share Phone Request rows (and Phone Share Number Viewed when the man opens the number) when you open introduction detail. You may see two similar rows for one tap — message text with or without (app) — see introduction log types → Share phone workflow. If chat shows the chips but logs are empty, see “We shared numbers but Admin logs are empty” below.
Matching-process eligibility (both profiles)
verified — In-app phone share is allowed only when both members’ answers to your brand’s matching process profile question support app-based sharing. The app reads each profile’s stored answer to that question (the same value you see on the end-user profile in Admin). If either answer is empty or does not resolve to an allowed option, the pair stays on start chat only — Admin cannot override this from the introduction row.
verified — Eligibility is symmetric: each person’s answer must “work” with the partner’s answer. A let my partner decide choice counts only when the partner’s answer is one of the app-share options below (or they also chose let my partner decide).
Matching-process answer (typical label)
Allows in-app phone share for this profile?
Support note
Smart Matching
Yes
Direct app-share option.
Smart Matching & Coordinator
Yes
Direct app-share option.
Let my partner decide (defer-to-partner)
Depends on partner
Allowed only when the partner’s answer is Smart Matching, Smart Matching & Coordinator, or the same defer choice.
Coordinator-only / other / not answered
No
Pair sees start chat when chat is on; no share-phone icons.
Check both end-user profiles before escalating “missing share button” tickets. Changing answers requires the member to update their profile (or a support-guided profile edit), then retry on a MATCHED introduction.
Phone number on the woman’s account
verified — When the woman confirms her share step, the app sends her saved phone number in chat. If her account has no phone number on file, the send fails and the app opens phone settings so she can add one — no Admin log row is created until she completes the step successfully.
The man’s request step does not require his phone number first; he only needs a number when viewing the partner’s shared number later.
After someone already shared (repeat taps)
verified — The app does not post duplicate share messages when someone taps again on the same introduction:
Woman — If she already sent her share message, another tap on phone-forward or a Lora share phone link shows only the female after share acknowledgment screen (no second Share Phone Message log).
Man — If he already sent a request, another tap on phone-callback shows the male after share acknowledgment only (no second Share Phone Request log).
Man after she shared — The matches-list icon switches to phone-in-talk. Tapping it (or tapping request again) opens view partner number directly.
Support tip: a single Share Phone Message row is expected per successful woman share — not one row per tap.
verified — Share phone feature off, or this pair’s profile answers do not allow Mekudeshet-style app phone share on both sides.
Review matching-process answers on both profiles; enable share phone feature if brand expects the button.
Man sees request on profile but gets a blocked screen
verified — Profile primary tap opens blocked / ineligible until the woman shares; the actual request flow uses the matches-list phone-callback icon.
Guide the member to the matches list icon, or wait for her share step — not an Admin misconfiguration by itself.
Member taps primary action and nothing happens
verified — Required info screens for the share-phone workflow are missing or not published (before-share steps). The app does not show a generic error — the tap is ignored until Content publishes the step.
Content → Info screens — publish active screens for event Share phone workflow with params female before share / male before share (and related steps). See info screens → share phone workflow.
Woman confirms share but lands in phone settings
verified — Her user account has no phone number saved yet.
Guide her to add a phone in the app (or update via support if your brand allows). Retry the share step on the same MATCHED introduction.
Blocked / ineligible info screen
verified — Man-side member when woman has not shared yet, or pairing fails eligibility while share phone is on.
Expected until the woman completes her share step, or until profile answers allow the flow — not an Admin bug by itself.
“We shared numbers but Admin logs are empty”
Confirm introduction status is MATCHED or later — logs are not expected during RAW / INITIATOR APPROVED.
On each end-user profile, confirm a linked user account exists (phone share logs load from the chat conversation, which requires both user ids). Profiles without accounts skip the Dynamo lookup entirely.
Refresh introduction detail — Logs load share events when you open the page, not continuously.
Look for Share Phone Request before Share Phone Message — request alone does not reveal numbers to the partner.
If chat shows the exchange but logs stay empty after refresh, escalate with introduction id + both profile ids — possible conversation id mismatch, analytics delay, or missing chat message types.
If you see duplicate share rows with the same type but one message ends in (app), that is normal — chat history and analytics both logged the same member action. See introduction log types.
Phone Share Number Viewed appears only from member-app analytics inside the matched window — never from chat-store rows. If chat chips exist but you never see viewed rows, the man may not have opened the popup yet, or analytics was temporarily unavailable (refresh detail; chat-store share rows may still be present).
If the introduction already left MATCHED (for example UNMATCHED or ENDED) before analytics processed, older share events may fall outside the activity window — compare Logs dates with Chat stats → Activity window.
Log row
Member action
Support note
Share Phone Request
Man confirmed the request step in the workflow.
Partner still must complete her share step — numbers are not exchanged yet.
Share Phone Message
Woman confirmed sharing her number through the workflow.
Man may then see view partner number info screen; each successful share creates at least one row (chat and/or analytics).
Phone Share Number Viewed
Man opened the partner-number popup after she shared.
Analytics-only — confirms he viewed the number; not a second share message in chat.
Member app visuals
These screenshots show the guided workflow in the member app (not Admin). Upload pending — slugs are queued in Documentation screenshots.
Waiting for screenshot. Capture: woman-side MATCHED matches-list row — tap the small phone-forward icon, or the female before share info screen after the tap (slug introductions-share-phone-woman-share).
Waiting for screenshot. Capture: man-side MATCHED matches-list row — tap the small phone-callback icon (not the row title) to open male before share, or show that info screen after the tap (slug introductions-share-phone-request).
Waiting for screenshot. Capture: blocked / ineligible info screen (workflow param blocked ineligible) when the man opens partner profile primary action before the woman shared, or when share phone is on but matching-process answers disallow app phone share (slug introductions-share-phone-blocked).
Operator playbook for uploading introduction figures to Admin → Documentation screenshots → Waiting for upload. File name must match the slug exactly. Capture from the member mobile app (simulator or device) — not Admin.
Before you start
Pick a brand — mek (The Circle) is the usual staging brand for introduction captures. Zuug and other brands work when the same app features are on.
Confirm app features — Share-phone slugs need the share phone app feature. Availability-check slug needs intro availability check. Extend slug needs premium + extend introductions on the test account.
Prepare test profiles — Two end-user profiles in ACTIVE status with phones saved on the user account (required for chat and share-phone logs). For share phone, both must answer matching-process questions so in-app phone share is allowed (not “matchmaker only”).
Drive the introduction in Admin — Use introductions list + view introduction to confirm status, parties, and deadlines before capturing in the app.
Upload — Admin → Documentation screenshots → Waiting for upload → upload PNG; file name = slug column below. After the image appears on the public doc site, remove the doc-screenshot--pending class from the doc HTML in a follow-up PR (or ask docs maintainer).
MATCHED; woman already shared (Share Phone Message in chat/logs); log in as man.
View partner number info screen — capture either path: (A) matches list phone-in-talk → expect Admin log (match list); (B) phone-callback when her share already exists → expect (after request). Hide status bar; show partner number field from workflow copy.
When support compares member claims to the Chat stats card on view introduction.
Prerequisites: S-Manager role, chat app feature on, status MATCHED or ENDED. Counts cover only the window from first MATCHED until the first closing status (TERMINATED, UNMATCHED, ENGAGEMENT BROKEN, ADMIN REJECTED, or NOT COUNTED) — see the feature page for the full metric table.
Symptom
Likely cause
What to check
Card missing entirely
Status not MATCHED / ENDED, chat off, or role lacks S-Manager on introduction detail.
Confirm status and app features. Use Logs on MM stages instead.
Stats are not available yet
No MATCHED row in status history (never truly matched).
Scan Logs for a Status Change to MATCHED. If status was set manually without that history, stats cannot compute a window.
Member says they chatted; all counts are zero
Analytics delay, chat outside the window, or events not tagged to this pair.
Confirm Activity window dates include when they messaged. Check Chat started vs message counts. Compare with Logs for MATCHED timestamp. Retry after 24h if BigQuery lag is suspected.
Chat started = Yes but message counts are 0
Member opened chat (chat started event) but has not sent a text or media message yet.
Normal for a new match. Last activity stays — until first message or media.
Counts stop before member’s last message
Window ended at a closing status (for example UNMATCHED or TERMINATED).
Read window end date on the card. Post-close chat is excluded by design.
Red error loading stats
Analytics query failure.
Retry. Escalate with introduction id if persistent — engineering checks BigQuery access and profile_events pipeline.
Quiet-chat or comms ticket; stats look “too low”
Stats count analytics events, not read receipts or system messages.
Cross-check It's Quiet Here comms and Logs. Stats do not replace comms investigation.
Phone Share Number Viewed missing in Logs but member opened partner number
Analytics-only row uses the same activity window as this card (first MATCHED through first closing status). Events before match or after UNMATCHED / TERMINATED / etc. are excluded.
Compare the member’s tap time with Activity window on Chat stats. Chat-store Share Phone Message rows may still appear when analytics rows do not. See log types → Share phone workflow.
Member-app visual for matched chat: upload slug introductions-matched-chat — see screenshot capture queue.
“I can’t see my match’s photo”
When the member sees a blank or hidden partner image on a suggestion or public profile — not the same as matchmaker-only image policy.
Check in Admin
Plain meaning
What to tell the member
Reporter’s party settings include hidePartnerImage = true (or string "true")
verified — The member turned off partner photos in premium / account settings. The app hides the other person’s picture for this viewer.
They can turn partner photos back on in the member app (same place they enabled hide). Deleting the key on View end user → Profile settings also clears it — only with ops approval.
Photo owner’s image policy attribute is only matchmaker
Photos are not shared in the dating app — matchmaker brands only.
Expected for that profile; not fixable from introduction detail.
Status RAW / INITIATOR APPROVED with two degrees profile on
Staged reveal — partial photo until full inspection.
Member must open the profile through the suggestion flow until Inspected_full appears in Logs — see Cannot approve in the app.