Overview

This screen shows everything about one introduction — who is involved, the current status, scores, matchmaker notes, and the full history. You can change the status, swap direction, or delete the introduction from here.

Labels match brand mek (en) in Admin.

Compare-only view

Side-by-side preview of two members before you save an introduction — opened from Check Match on potential matches or from the add-introduction dialog.

verified — The URL uses a special compare mode (not a saved introduction id). The page loads scores and profile summaries from a read-only compare API — nothing is written until you click Create This Now.

How to open

  • View Potential Matches → Check Match on any stored score row.
  • Add/New introduction dialog → Check Match after picking initiator and responder.

What you still see

SectionOn compare view?
Both parties (names, ages, avatars, profile links)Yes
Bio scores and predictor header bandYes
Decline history and party settingsYes
Match advisor (AI) on compareSometimes — when list ranking already stored match checks, rank narrative, and/or pitch text for this pair, Admin shows them under the same card title (no introduction id yet). Empty when ranking never ran. Not the saved-row advisor job (Run match advisor now, list contradiction count, scoring feedback). Full field guide: compare list rank (reference).
Match Advisor on saved introduction (feature on)No until after Create This Now — then open the numeric detail page for run-now, auto-promotion, and list contradiction count
Personality conflictsYes — computed from both profiles’ current AI analysis values (live preview). Same card title as on a saved introduction, with copy that explains the numbers are from today’s profiles, not a stored introduction row.
Header Status pickerNo — there is no saved status yet
Logs, chat stats, pending reasoningNo — no introduction timeline exists until created
Approve / decline / swap / TBD / delete / resetNo

Sole action: Create This Now

verified — Creates a real introduction row with the scores on screen and navigates to the saved detail page. Use when matchmakers or admins want to introduce a pair that automatic suggestion gates might skip (for example deal-breaker visibility in Admin but ops-approved exception).

Manual create validation still applies: both profiles must be active UUIDs, no duplicate open pair, and same-matchmaker duplicate guard when a matchmaker is already on the row. See create introduction → errors.

Related: Search Suggestions refreshes stored scores; compare previews one pair without saving. When ranking already ran, see compare list rank (reference) for match checks and rank narrative on this preview.

Introduction details

The header summarizes key facts. Managers with Edit permission can also change Status from the status control in the page actions area (a reason dialog appears for most changes).

When status is FROZEN, a member parked the suggestion (not for now) from the app. Only that member can re-open or release it — there is no Admin un-freeze button. The other party was already offered a new suggestion when the freeze happened. See frozen (reference) for member choices (freeze vs decline vs not available at all) and re-activation rules.

FieldWhat it shows
Date and time the introduction was created (hover for full timestamp).
Last Updated:When the introduction last changed status or was edited.
Pred Score:Plain-language predictor label derived from the overall predictor score (for example “Great match” at 76+, “Reasonable match” at 51–75). Hidden when no predictor snapshot exists for this pair.
Score (initiator)Bio compatibility percentage for the initiator’s direction. Prefers live stored match scores when available.
Score (responder)Bio compatibility percentage for the responder’s direction.
SLAMust respond until — shown while status is RAW or INITIATOR APPROVED (deadline for the current party to act). On premium brands with extend introductions enabled, members may buy extra time with tokens from the Potential Matches suggestion card — you will see an Extenstion log row when they succeed. Full rules: response deadlines (reference).
Created By:Auto for matcher-created introductions, the staff name for manual create, or Swapped after staff use Swap Direction (or after a member re-activates a frozen suggestion that reversed direction). This field is informational — it does not change who is initiator by itself.
Initiator / Responder ID (admin chips)Copyable profile UUIDs for support and cross-linking.

Both parties

Profile cards for initiator and responder — attribute comparison, photos, and quick links.

The Parties Details section shows side-by-side cards. Click a name to open that person’s end-user profile.

Header row on each card

ElementWhat it shows
Age / height / location / genderQuick facts with colour hints when a value matches or conflicts with the partner’s stated preferences (green = good fit, red = mismatch).
Image policy chipWhen your brand hides men’s photos until a certain introduction stage, a small chip above the avatar explains whether the partner can see this person’s photos in the app vs matchmaker-only visibility. Hidden while status is New on the shidduch queue.
Resume / share iconsDownload or share a printable resume bundle when your brand enables resumes. Opens a dialog to pick which images and fields to include.

Attribute tables

Below the header, each card lists bio and preference attributes configured for introduction review:

  • On standard introduction detail, rows use the same attribute table component as end-user profiles (respecting visibility and per-attribute pre-validation unless your brand bypasses matchmaker pre-validation).
  • On matchmaker shidduch detail, a dedicated shidduch attribute layout may show paired bio/pref columns.
  • Free-text about me / looking for blocks appear when configured on your brand, with the same review toggles as on the member profile page.

AI Analysis Compatibility (admin-only section below the cards) shows side-by-side AI-scored traits for internal match review — separate from the standard bio/pref grid.

Soft deal-breaker attribute names for this introduction appear in Soft deal breakers when recorded on the row.

Personality conflicts from the matcher appear in Personality conflicts when recorded on the row (or on compare preview from live profile values).

Close but blocked

Why the matcher flagged this pair as a near-miss on preference tolerance — and what the member was asked.

When this section appears

  • You opened a saved introduction (not the compare-only preview).
  • At least one soft deal-breaker attribute name is stored on this row for the initiator or responder.

When nothing was recorded, the card and left-nav link are hidden. On the introductions list, the warning icon under Soft DB appears when either party has at least one stored key — hover lists all keys from both sides combined.

verified — The card stays visible after status moves on (matched, declined, closed) so ops can see which preference areas each party was asked about.

What each block shows

On screenMeaning
Intro line (The responder is being asked whether the following near-miss is really a deal breaker:) Plain-language framing above the chips — often that the responder must confirm a near-miss (initiator-side flags use the same layout when only the proposer holds the soft flag).
First - Intiator block Outlined chips: attribute keys where the introduction initiator triggered a soft deal-breaker check-in. Match keys on attributes.
Second - Responder block Same for the introduction responder. Either side can have chips; both can appear on one row.
Paragraph under a party’s chips Brand copy when the system stored an explanation id for that party. When no brand text exists, you only see chips — use questionnaire answers to interpret the ticket.
Empty-state message inside the card Rare — refresh the page; if it persists, treat as a support/engineering data check.

Chip labels are internal keys, not the sentences members see in chat.

What happens in the member app (high level)

Soft deal breakers are not hard blocks in Admin. They pause automatic release so the member can confirm whether a near-miss is acceptable:

  • When the initiator holds the soft flag, the introduction may park in a close but blocked (initiator) stage until they answer — then it can move to RAW or decline.
  • When the responder holds the soft flag, staff Approve may move the row to a close but blocked (responder) stage until the responder answers — then toward INITIATOR APPROVED or decline.
  • Answering yes promotes along the normal path; answering no maps to the appropriate decline status for that side.

Exact status labels: introduction statuses (reference).

Stays in pending approval — When soft deal breakers are present, automated Match Advisor promotion keeps the row in PENDING APPROVAL for staff review even if hard contradictions are empty (see Match Advisor and stuck in pending approval).

Related screens

Configure soft-block attributes on attribute settings → Soft deal breaker. Before an introduction exists: potential match scores. Tolerance chips on Pending reasoning are a separate “matcher relaxed a strict preference” signal — both can appear on the same row. Support: soft deal breakers (troubleshooting).

Personality conflicts

When AI personality analysis shows a clear opposite between one member’s wish and the other member’s trait (1–9 scale).

When this section appears

  • Saved introduction — at least one conflict was stored when the matcher created or refreshed the suggestion (initiator and/or responder lists).
  • Compare preview — both profile IDs are loaded and a live check finds at least one conflict from today’s profile values (nothing stored yet).

When no conflict applies, the card and left-nav link are hidden. On the introductions list, the brain icon under AI conflict appears when either party has at least one stored conflict — hover lists trait keys from both sides combined.

What each line means

verified — Each red line follows the pattern: one person’s name, the personality trait label from your attribute catalog, the number they want in a partner, the other person’s name, and the number that describes their trait. A conflict means one side is clearly low (1–3) while the other is clearly high (7–9), or the reverse — middle values (4–6) do not count as evidence.

Lines are grouped under First - Intiator and Second - Responder:

  • Initiator block — conflicts where the initiator’s partner-wish scores clash with the responder’s trait scores.
  • Responder block — the reverse direction (responder’s wishes vs initiator’s traits).

This is separate from AI Analysis Compatibility (the side-by-side trait grid for internal review) and separate from bio/preference deal-breaker lists on potential match scores.

Pending approval and staff review

When your brand is configured to hold personality-conflict introductions for staff review, automated release from PENDING APPROVAL can stay blocked while conflicts remain on the row — similar to soft deal breakers, but driven by AI trait data rather than questionnaire soft-block attributes. Hard Match Advisor contradictions are a third, independent gate.

Staff still use Approve, Decline, Swap Direction, or TBD per brand policy after reading the lines. See stuck in pending approval.

Before the introduction exists

On View Potential Matches, the AI fit column shows a fit score plus the same brain icon when the stored matcher run recorded conflicts — see potential match scores → AI fit.

Actions

Which buttons appear depends on status and your role:

ActionWhen availableWhat happens
Approve Status is PENDING APPROVAL; you have Edit permission. Moves the introduction to AVAILABILITY CHECK when intro availability check is enabled for your brand; otherwise to RAW so the initiator receives the suggestion in the member app. See availability check workflow when the feature is on.
Decline PENDING APPROVAL with Edit permission. Opens a reason dialog, then sets ADMIN REJECTED and returns you to the previous screen.
Swap Direction PENDING APPROVAL with Edit permission only — hidden after you approve or on any other status. Exchanges who is proposer vs responder on this row. Status stays PENDING APPROVAL until you click Approve or change status. See Swap direction.
TBD PENDING APPROVAL with Edit permission. Opens the status-change reason dialog, then sets status to TBD for internal hold (members see no new progress until staff change status again).
Status change Any saved introduction; Edit permission. Lets managers pick another lifecycle status. Most changes require a written reason. Triggers the same downstream member notifications as automated status updates when applicable.
Status → ENGAGEMENT BROKEN Manual change from ENGAGED (or other post-match stages) when ops record that an engagement ended. Reason (required). Both parties’ profile status returns to active. Pending matchmaker engagement payments for this introduction are cancelled automatically. Members no longer treat this row as an active match. See Engagement broken — ops playbook.
Delete Introduction Delete permission (typically S-Manager). Permanently removes the introduction after confirmation.
Reset Introduction S-Manager on this page, and both parties must be marked internal test accounts. Clears logs, inspections, Lora Q&A, chat conversation, and deadline extensions, then moves status back to PENDING APPROVAL so you can re-test the flow. Use only on test pairs.
Create This Now Compare-only view (not a saved introduction yet). Creates the introduction with the scores on screen and navigates to the new record.
Copy both sides as context Saved introduction detail or compare preview when both profile IDs are loaded. Copies a JSON snapshot of both parties’ bios, preferences, decline insights, and (on saved rows) stored compatibility scores to your clipboard for pasting into an external AI assistant. Does not change profiles or the introduction. See Copy context for AI review.

On matchmaker brands, MM workflow buttons (advance, decline, record answers, end shidduch) live on My Matches detail — not on this page. See matchmaker workflow (reference).

Copy context for AI review

Export human-readable profile text for matchmakers or support who paste into an external AI tool — not a member-facing feature.

verified — The outlined action Copy both sides as context appears in the page header when you open a saved introduction (numeric id in the URL) or the compare preview with both initiator and responder profile IDs loaded.

StepWhat you see
1. Click Copy both sides as context The button disables briefly while Admin loads data.
2. Success A short confirmation alert — the JSON is already on your clipboard.
3. Failure An error alert — retry; if it persists, check that both profiles still exist and you still have access to this introduction.

What is in the clipboard

Admin builds one JSON document. Plain-language rules (no code paths on this page):

  • Both parties — For initiator and responder: bio attributes and preference attributes only (not every custom field on the profile). Values use the brand’s default language labels where translations exist; encrypted or empty values are omitted.
  • Prior declines — Short text lines from the decline-investigator digest (same family of insights as Match Advisor), when stored for that profile.
  • Saved introduction only — Introduction id, both profile ids, export timestamp, and optional stored bio/predictor scores (from the matcher score table when present, otherwise the scores shown on the introduction header).
  • Compare preview only — Both profile blocks without introduction id or algorithm score block (no saved row yet).

This export is for internal review (drafting support replies, matchmaker notes, training prompts). It does not send data to a built-in AI inside Admin except when you separately use Match Advisor. Treat clipboard content as sensitive — same confidentiality as opening both end-user profiles.

To export many potential-match rows at once (member plus selected candidates), use Download candidates on View Potential Matches (reference).

Swap Direction

Reverse proposer and responder on a suggestion that is still waiting for staff approval — before either member receives it in the app.

verified — Use this when the matcher picked the right pair but the wrong person should be the proposer (for example brand policy, who goes first preferences, or ops correcting direction before release).

TopicWhat happens
When the button appears Only while status is PENDING APPROVAL and your role has Edit on Introductions. It disappears after approval or any manual status change away from pending.
Status after swap Stays PENDING APPROVAL — members still do not see the suggestion until staff click Approve (or you move status manually).
Who becomes initiator The former responder becomes proposer; the former initiator becomes responder. Party cards, profile links, and the initiator trophy on profile introductions follow the new roles after the page refreshes.
Created By: Header shows Swapped (replacing Auto or the prior staff name). This helps support spot a direction correction in tickets.
Logs A Swapped row is added with the swap timestamp (same log type as member frozen re-activation when direction reverses). See introduction log types.
Bio Score columns After swap, Admin reloads compatibility percentages for the people now in each role (stored scores may still be keyed to the old direction until refresh). If percentages look attached to the wrong name, refresh the page — detail view aligns scores to the current initiator/responder columns.
After you approve The new initiator receives the next step (AVAILABILITY CHECK or RAW) — same as if the pair had been created in that direction originally.
When swap is not available After status leaves PENDING APPROVAL (for example RAW, AVAILABILITY CHECK, or MATCHED), the swap button is hidden. Staff cannot reverse proposer/responder from Admin on a released introduction — see swap direction on pending approval (post-release row).

Who goes first warning

Before swapping, Admin checks each party’s saved who goes first preference (see Party settings):

  • If the current initiator’s preference is first, or the current responder’s preference is second, a confirmation dialog appears — swapping conflicts with that preference.
  • If neither side triggers that rule, swap runs immediately with no extra dialog.

Member frozen re-activation can also reverse direction without staff — watch for Swapped in logs and use the same troubleshooting as manual swap. Playbook: Swap direction on pending approval.

Status change dialogs

Modals that appear when you change status or reject a pending introduction.

DialogOpens whenFieldsAfter confirm
Decline (pending) You click Decline while status is PENDING APPROVAL. Reason (multiline, required) — why staff rejected the suggestion before members saw it. Status → ADMIN REJECTED; you return to the previous screen. Reason appears on a Status Change log row.
Status change You pick a new status from the header status control, or click TBD on a pending introduction. Reason (multiline, required) — internal note for why the status was changed manually. Status updates; page refreshes; downstream member notifications run when applicable (same pipeline as automated updates). A Status Change log row stores the new status and reason.
Swap Direction warning Either party has who goes first set (first on initiator or second on responder) and you swap on pending approval. Confirmation only — explains the preference conflict. Initiator and responder swap; Swapped log row added.
Reset Introduction S-Manager reset on internal test pairs. Confirmation warning — lists what will be cleared (logs, inspections, Lora Q&A, chat, deadline extensions). Status → PENDING APPROVAL; test data cleared.
Delete Introduction Delete permission on the page actions. Standard delete confirmation. Introduction removed permanently.

Matchmaker-specific modals (record answers, unmatch with voice notes, put on hold duration) are documented on matchmaker workflow → Shidduch detail dialogs.

Manual status picker

Managers with Edit permission see a Status dropdown in the page header (not on compare-only pages).

verified — The picker lists every introduction lifecycle status your brand stores in Admin general codes (same labels as the introductions list status filter). Picking a new value always opens the Status change reason dialog unless you use the dedicated Decline button on PENDING APPROVAL (which uses the rejection dialog instead).

Picker groupWhen ops use itCaution
Early / review (PENDING APPROVAL, TBD, ADMIN REJECTED, AVAILABILITY CHECK) Hold, release, or correct a suggestion before members see it. Prefer Approve / Decline buttons on pending rows when those are the intended outcomes — they use the correct dialog and navigation.
Member review (RAW, INITIATOR APPROVED, decline/ignore statuses, FROZEN, TERMINATED) Correct a stuck row after support investigation. Changing to RAW or INITIATOR APPROVED may re-notify members depending on brand comms — document your reason clearly.
Matched / MM / dating (MATCHED, MM *, DATING, ON HOLD) Backfill or fix data when Shidduch detail was not used. Matchmaker workflow buttons on Shidduch detail also update SLA deadlines and MM logs — manual picker skips those side effects.
Milestones (ENGAGED, MARRIED, ENGAGEMENT BROKEN, EXTERNALLY ENGAGED) Record engagement outcomes or reversals. ENGAGEMENT BROKEN returns both profiles to active and cancels pending engagement payments — see ops playbook.
Closed (ENDED, NOT COUNTED, ignore statuses) Close duplicates, test rows, or post-match cleanup. NOT COUNTED removes the row from reporting — use only with ops approval.

Every manual change writes a Status Change log row with your reason. Downstream member notifications use the same pipeline as automated updates when applicable. For status meanings and which paths are member-driven vs staff-driven, see introduction statuses (reference) and log types → status-change patterns.

Pending reasoning

When your brand enables pending introduction reasoning and the introduction is in PENDING APPROVAL, a dedicated section explains why matching held the suggestion:

  • Tolerance attributes — chips listing profile attributes where matching had to relax strict preferences.
  • Any declined history — for each party who has a recent “any declined” flag, a table of attribute change log rows (date, who changed it, new value, reason, linked question/answer when automatic).

If neither tolerance nor decline history applies, the section shows a short empty message.

Match Advisor

AI-generated talking points and hard contradiction flags for a saved introduction — not a second compatibility score.

When this section appears

  • Your brand enables Match Advisor insights (app feature).
  • You opened a saved introduction detail page — not the compare preview (compare two profiles hides this card entirely).

There is no status gate (unlike chat stats): you can open Match Advisor on PENDING APPROVAL, RAW, matched stages, and closed rows alike.

What each part shows

On screenMeaning
Run match advisor now Queues a fresh advisor run for this introduction. Shown only when your role has Edit permission on introductions. While the request is in flight the button is disabled; success shows a short “queued” confirmation and failure shows an error alert. Refresh the page after a minute to read new text.
AI match analysis is not ready yet. It runs shortly after a new suggestion is created. No advisor payload stored yet — common immediately after create before the background job finishes.
Last updated Timestamp of the last successful advisor write (or last error save).
Advisor could not complete Advisor job failed (for example model timeout or bad JSON). The message is informational for support — use Run match advisor now to retry when the underlying issue is fixed.
Hard contradictions Bullet list of plain-language “hard” mismatch lines returned by the advisor. When at least one line exists, the card opens expanded and list rows on Introductions list show the count in red under Contradictions.
No hard contradictions found Shown after a successful run when the hard-contradiction list is empty — not the same as “advisor never ran” (that stays on AI match analysis is not ready yet. It runs shortly after a new suggestion is created. until the first finish).
Suggested message for the initiator / Suggested message for the responder Suggested copy per side (multi-line text). The member app may surface the initiator pitch as “why we matched you” on incoming suggestions once the introduction is live — ops use these blocks for coaching, not as editable member-visible templates in Admin.

Automatic runs vs manual

verified — When automated matching creates an introduction in PENDING APPROVAL, RAW, or AVAILABILITY CHECK, the system queues an advisor job in the background. After the advisor finishes while the row is still PENDING APPROVAL:

  • Hard contradictions — Row stays pending for staff; contradiction count appears on the list and detail.
  • No hard contradictions — Row may auto-promote to RAW or AVAILABILITY CHECK when brand rules allow (no soft deal breakers on the row, pending-introduction mode, tolerance/decline-history gates, minimum match-score floor, and similar).
  • Advisor error — Row may still auto-promote when other gates pass (treat as “release without contradiction block”).

Full support checklist: stuck in pending approval. Soft deal breakers always keep pending until staff act — see soft deal breakers.

Manual Run match advisor now uses the same backend job as the automatic queue — useful after you edit profiles or when an error row needs a retry.

List page shortcut

The global list does not show a separate advisor score column — only Contradictions (and the soft-deal-breaker warning icon when applicable). Use this detail section for pitches and the full contradiction list.

Chat stats

S-Manager analytics summary for matched couples — counts from the member app event stream, not a live chat-server dashboard.

When this section appears

The Chat stats card and left-nav link are shown only when all of the following are true:

  • Your role includes S-Manager access on the introduction detail page.
  • The chat app feature is enabled for your brand.
  • Status is MATCHED or ENDED.

On other statuses (for example RAW, matchmaker stages, or TERMINATED), the section is hidden entirely — use Logs instead.

Activity window (what the dates mean)

Every metric is counted only inside the activity window shown on the first row:

BoundaryWhen it is setWhat it means for counts
Window start First time this introduction reached MATCHED (from the status history). Events before the couple matched are excluded — pre-match Lora chat and inspection do not appear here.
Window end First later status change to TERMINATED, UNMATCHED, ENGAGEMENT BROKEN, ADMIN REJECTED, or NOT COUNTED — if any. Chat after that closing event is excluded. When no closing event exists yet, the end shows as open (…) and counts run through “now”.

Hover the Activity window chip for the full date and time range. Column labels for messages and media use each party’s display name when Admin has it (full name, otherwise username).

Metrics

Counts come from member-app analytics events scoped to this pair (initiator ↔ responder). They are not pulled from the chat database in real time — allow a short delay after app use before expecting numbers to update.

MetricWhat it measures
Activity windowStart and end timestamps for the counted period (see table above). Hover for full precision.
Chat startedYes when at least one chat started analytics event fired for this pair inside the window; otherwise No.
Last activityMost recent message sent or media sent event in the window. Shows — when none were logged yet.
Messages (per party)Text chat messages sent by initiator and responder (separate columns).
Media (per party)All media attachments sent by each party (photos + videos combined).
PhotosPhoto-only count — initiator / responder (two numbers separated by /).
VideosVideo-only count — initiator / responder.
Call events (total)Voice plus video call events for this pair in the window.
Video callsVideo call events only.
Voice callsVoice call events only.
Break the ice — startedHow many times an icebreaker flow was started in chat.
Break the ice — answeredHow many icebreaker prompts received an answer.
Break the ice — chat messagesFollow-up chat messages logged as break-the-ice message types.
Daily mood messagesMessages from daily mood / status-line features.
Other message typesRemaining tracked message types for your brand inside the window.

Empty and error states

What you seeMeaning
Section missing from the page Status is not MATCHED / ENDED, chat feature is off, or your role is not S-Manager on this page.
Stats are not available yet (or similar) inside the card Status qualifies, but the introduction has no MATCHED row in status history yet (for example manually set to ENDED without ever matching). No window → no counts.
Red load-error message Analytics query failed — retry later. If it persists, note the introduction id for engineering (BigQuery / analytics pipeline).
Window shows but all counts are zero Pair matched but no chat analytics events were recorded in the window yet — common right after MATCHED or when members have not opened chat.

Support playbooks for “member says they chatted but stats are empty” and related cases: support troubleshooting → Chat stats.

Member-app screenshot of a matched chat thread (for context next to logs): What members see — figure introductions-matched-chat in the upload queue.

Logs

One chronological timeline for this introduction. For every type label and reminder name, see the introduction log types reference.

ColumnWhat it shows
Date / timeWhen the event occurred.
AuthorInitiator or responder first name when the event came from a member; staff name on manual status updates; sometimes blank for automated rows.
TypeCategory — for example Status Change, Question, Answer, Reminder Sent, Inspected, Extenstion, Swapped, phone-share rows.
MessageDetails: new status (with reason), question or answer text, reminder label, hours extended, Inspected_… profile opens, phone-share actions.

Inspection and approve

Before a member can approve a suggestion, they must open the partner’s profile in the member app. On brands with the two degrees profile app feature, a partial open logs Inspected_half; they must complete a full reveal before approve completes (Inspected_full). Not interested remains available on the partial view — members can decline without revealing the full profile. During RAW, only the initiator can inspect; the responder’s eye icon stays empty until the initiator approves.

Silent opens from chat history refresh profile data without adding a new log row — see introduction log types → inspection messages.

Full catalog of inspection log messages: introduction log types → inspection type codes.

Common log patterns

  • Pending → RAW — Status Change rows when staff approve or when automation advances; may be followed by Question / Answer during availability check.
  • RAW / INITIATOR APPROVED — Reminder Sent rows before deadlines; Inspected when someone opens the partner profile; Extenstion when extra response time is granted.
  • RAW / INITIATOR APPROVED → FROZEN — Status Change when a member chooses not for now in the app. See frozen (reference).
  • FROZEN → RAW — member re-activated a parked suggestion; Swapped may appear if initiator and responder were reversed.
  • MATCHED — status change to matched; later Share Phone Request / Share Phone Message if the pair uses the share-phone workflow in chat; Phone Share Number Viewed when the man opens the read-only partner-number screen (analytics only). Support playbook: Share phone in chat · view partner number.

Share phone in chat — When your brand enables the share phone app feature, matched pairs may exchange numbers through guided info screens and chat messages (not by typing digits in the thread). Admin merges those events into Logs. Woman uses the matches-list phone-forward icon, profile button, Lora chat share phone link, or the same icons on the Introductions tab Approved matches box (for matches that have not started chat yet when chat is on — see Approved matches box); man sends a request from the matches-list phone-callback icon (or views her number via phone-in-talk after she shares — logs Phone Share Number Viewed, not a second share message). Full troubleshooting: Support troubleshooting → Share phone · row icon states · view partner number.

What members see (member app)

Logs are Admin-only. These figures show where related member actions appear in the app. Upload instructions and the full introduction slug queue: support troubleshooting → Member-app screenshot capture.

Initiator viewing a RAW introduction suggestion in Lora chat
Waiting for screenshot. Capture: initiator’s suggestion card in Lora / suggestions while status is RAW (slug introductions-raw-suggestion).
Matched pair chat screen in the member app
Waiting for screenshot. Capture: conversation screen after both parties approved (MATCHED) (slug introductions-matched-chat).
Frozen suggestions row on the member potential matches screen
Waiting for screenshot. Capture: frozen suggestions avatar row with snowflake badge (slug introductions-frozen-list). See frozen (reference).

First Ask Declines / Responder Declines

Two separate sections on the detail page — one per party. They summarize that person’s decline history across introductions, not only this pair.

My Declines

Each section loads answers from your brand’s configured decline reason questions (App Settings). For choice-based answers, Admin shows chips: each chip label is the answer text and the number is how many past introductions used that reason. Click a chip to open the linked introduction(s) in a new tab.

Other Reasons — free-text decline answers appear as a list below the chips. Each row links to the introduction where the member typed the reason.

Ended Shidduchim (matchmaker brands)

When your brand enables matchmakers, a table lists introductions that ended for this profile with an unmatch reason:

ColumnWhat it shows
IDIntroduction number — click the row to open that introduction.
ReasonSelected unmatch reason from your general codes list.
Other reasonFree-text explanation when the member or matchmaker added one.
Me / PartnerWho initiated the unmatch and who was named as the other party in the reason record.

These sections help you see patterns before approving a new introduction between the same people or similar profiles.

For a brand-wide table of every ended introduction (scores, matchmaker, unmatch codes, and date #), use Ended Matches under Matchmaking.

First Asked Settings / Responder's Settings

Read-only snapshot of each party’s saved preference flags at page load — notification toggles, “who goes first” preference, and other per-member options stored on their profile.

ColumnWhat it shows
KeySetting name (shown in readable Title Case).
ValueCurrent stored value (string, number, or boolean as saved).
ActionsDelete icon removes that key from the profile after confirmation. Changes save immediately to the member profile (not to the introduction row).

Swap direction warning — before staff swap on PENDING APPROVAL, Admin reads each party’s stored Whos First value (see table below). Only certain values trigger an extra confirmation — full flow in Swap direction.

Learn more: Full key catalog (introduction limits, hide-partner-photo, feelBrave matching preference, language, premium toggles) — Profile party settings (reference). Editable add/update lives on View end user → Profile settings. Photo hidden in the app? Support troubleshooting → Partner photo hidden.

Whos First (common values)

Members with premium plans can save a who goes first preference in the member app (My account → premium features). Support sees the saved string in the table below — not editable on introduction detail except by deleting the row (which removes that key from the member profile).

Value in AdminPlain meaningSwap on pending approval
first on the current initiator That member asked to be the proposer / go first when suggestions are created. Warning dialog before swap — direction change conflicts with their preference.
second on the current responder That member asked to be the responder (partner goes first). Warning dialog before swap — same conflict rule as above.
me (member app premium chip) Member chose “I go first” in My account — stored as the word me, not first. No Admin swap warning today — only first / second trigger the confirmation dialog. Compare the exact Value column before assuming a preference conflict.
other (member app premium chip) Member chose “my match goes first” — stored as other, not second. Same as me — swap proceeds without the who-goes-first warning unless the stored value is literally first or second.
random or blank No fixed proposer preference (default premium setting). Swap runs immediately when you click Swap Direction (no extra warning).

In the member app, paired introductions may also show a who goes first chip on the partner profile when the reveal who first app feature is on — that flow is separate from staff swap; tag-rule analytics may log Who first clicked. See tag rule events.

These settings sections appear below the decline sections on the page. They are not in the left navigation rail but scroll with the rest of the detail view.

Section map

SectionWhat you find there
Chat statsS-Manager analytics counts for matched chat — see Chat stats (hidden unless status is MATCHED or ENDED and chat is on).
LogsFull audit timeline — see Logs above and the log types reference.
First Ask Declines / Responder DeclinesPer-party decline chips, free-text reasons, and ended-shidduch table — see Decline history.
First Asked Settings / Responder's SettingsProfile settings key/value table with delete — see Party settings.

Support troubleshooting

When a ticket references this introduction id, compare Status, Must respond until, and Logs to the scenarios below before changing status manually.

What you see on this pageStart here
PENDING APPROVAL or AVAILABILITY CHECK for days Stuck in PENDING APPROVAL · Stuck in AVAILABILITY CHECK
Must respond until in the past; status still RAW / INITIATOR APPROVED Deadline passed but status unchanged · Response deadlines (reference)
Member says Extend failed Extend failed · confirm premium + extend introductions features
Approve greyed out in member app; empty Inspected icon Cannot approve in the app · inspection rules
Available Introductions is 0; tooltip mentions too many unopened suggestions Inspection backlog · list → Inspection backlog cap
MATCHED / MM AVAILABLE and ticket is about matchmaker queue Stuck Shidduch (matchmaker) · open the row on My Matches
FROZEN Frozen suggestion issues — re-activate blocked, freeze cap, partner unavailable · lifecycle (reference)
Couple broke off engagement; profile still shows engaged or members ask about payments / matching again Engagement broken (support) · Engagement broken — ops playbook
Status change fails with Open introduction already exists Status change errors
PENDING APPROVAL; ops need to reverse proposer before release, or Swapped in logs Swap direction · Swap direction on pending approval
Member already on RAW (or later stage); ticket asks to flip proposer Swap direction on pending approval (post-release) · When swap is not available
Party settings show Whos First; swap warning confused support Party settings → Whos First · Who goes first warning
Soft DB icon or “close but blocked” in the app Close but blocked · soft deal breakers (troubleshooting)
AI conflict brain icon on list or detail Personality conflicts · stuck in pending approval
Red Contradictions or advisor never finished Match Advisor · Match Advisor (troubleshooting)
Ticket about sharing phone numbers in chat; missing Share Phone Request / Share Phone Message in Logs Share phone in chat · log types → share phone
Chat stats missing, all zeros, or disagrees with what members report Chat stats (window rules + empty states) · Chat stats troubleshooting

Full checklists (no new suggestions on profile, manual create errors): Support troubleshooting (reference).

Learn more