Reference (partial) — Status names match the Admin list and detail screens. “Verified” rows were traced in Admin, backoffice API, and introduction service code (July 2026). Member-app screenshot upload steps: support troubleshooting → Member-app screenshot capture.

Overview

An introduction links two end users: an initiator (proposer) and a responder. The Status column shows where they are in the journey.

Most introductions are created automatically by the matching system. Admins with Add New permission can also create them manually. Automated suggestions may start in PENDING APPROVAL, AVAILABILITY CHECK, or RAW depending on brand settings (see Pending approval workflow).

When a status advances toward the member app, the system may set a Must respond until deadline using your brand’s “minutes until first/second react” settings.

Before members see a suggestion

StatusPlain meaningWho acts nextWhat members see
PENDING APPROVAL verified — Waiting for a matchmaker or admin to approve before the initiator receives the suggestion. Admin with Edit on view introduction: Approve, Decline, or TBD. Neither party sees the suggestion yet.
ADMIN REJECTED verified — Staff declined the introduction before it reached members (reason stored in logs). No further action unless you create a new introduction. Neither party sees this suggestion.
AVAILABILITY CHECK verified — System asks the initiator a short “available for intro?” question in Lora chat before showing the full suggestion (when your brand enables availability check). Initiator answers in the app; system then moves to RAW or closes the intro if they never answer after all reminder steps. Initiator sees a Lora question, not the full match card yet. Full step-by-step: Availability check workflow. Reminder rows: reminder types.
TBD verified — Paused for internal review (“to be decided”). Ops use this when they need more information before continuing. Staff change status manually from the introduction detail header when ready. Flow is on hold; members typically see no new progress until status changes.

Availability check workflow

When your brand enables the intro availability check app feature, new introductions may pause in AVAILABILITY CHECK before the initiator sees the full match suggestion.

When an introduction enters this stage

  • verified — Staff click Approve on PENDING APPROVAL (instead of jumping straight to RAW).
  • verified — Automated matching creates the row directly in AVAILABILITY CHECK when your brand’s algorithm settings route new suggestions through this gate (same feature flag).
  • verified — Manual create still defaults to PENDING APPROVAL; availability check runs only after staff approve (if the feature is on).

What the initiator sees

verified — The member app posts a Lora question (not the full introduction card). Wording comes from your brand’s configured availability questionnaire step in Admin — ask your brand lead which questionnaire row to edit if copy needs to change.

Lora chat showing the availability-check question before the full match suggestion
Waiting for screenshot. Capture: initiator’s Lora chat during AVAILABILITY CHECK — the short “available for intro?” question before the full match card appears.

The responder does not see anything yet. On the introductions list, the initiator’s Inspected eye icon stays empty — inspection rules start at RAW.

Member answer outcomes

Member choice (typical)Plain meaningIntroduction status afterWhat happens next
Yes / I’m available verified — Initiator confirms they want to receive this suggestion now. RAW Full suggestion flow begins — initiator must open the partner profile, then approve or decline. Question / Answer rows appear in Logs, then a Status Change to RAW.
I’m busy (when offered) verified — Initiator pauses chat notifications for this conversation thread. Stays AVAILABILITY CHECK Introduction remains open; reminder waves continue until they answer or the final timeout closes the row.
No answer through all reminder steps verified — Initiator never completed the question after every scheduled nudge. TERMINATED Final reminder wave closes the introduction. Initiator may be snoozed from new suggestions for a period set in App Settings (snooze after availability check). See TERMINATED paths.

When the system skips the question

verified — Even with the feature on, the platform may move straight to RAW without posting the Lora question when either of these is true:

  • The initiator already answered the same availability question within the last 24 hours (stored on their profile).
  • They already have another open introduction waiting on them as initiator (RAW) or as responder (INITIATOR APPROVED).

Admin logs show a Status Change from AVAILABILITY CHECK → RAW with an automated reason — no Question row on that path.

Reminder waves (App Settings)

Timing is controlled under App Settings → Reminders (mobile app category):

Setting row (description in Admin)Plain meaning
Intro availability check times verified — Scheduled delays for nudging initiators who have not answered yet. Each wave logs Reminder Sent with label introAvailabilityCheck. Intermediate waves may clear a stale answer so the question can be asked again.
Intro availability check answered times verified — Follow-up schedule when the initiator already said they are available but the introduction has not advanced to RAW within expected timing. Logs introAvailabilityCheckAnswered.
Snooze after availability check verified — After the final unanswered reminder, how long (days) the initiator is snoozed from receiving new suggestions.

Full reminder label catalog: introduction log types → Reminder types.

What you see in Admin

  • Filter the introductions list by AVAILABILITY CHECK to find rows waiting on the initiator.
  • Must respond until is usually empty at this stage — the SLA clock for approve/decline starts when status becomes RAW.
  • Open Logs on the detail page: expect Question when the Lora prompt was sent, then Answer when the member responds, or a chain of Reminder Sent rows if they stall.
  • While status is AVAILABILITY CHECK, the initiator does not receive additional new RAW suggestions — the platform treats them as having zero free introduction slots until this row advances or closes.

Staff override

Managers with Edit can pick any status from the header control — for example move to RAW manually if the member confirmed availability by phone. A reason is required and appears on the Status Change log row. Prefer letting the member answer in the app when possible so Question / Answer history stays complete.

Member review

StatusPlain meaningWho acts nextWhat members see
RAW verified — Suggestion is with the initiator for approve or decline. Initiator in the member app. Must open responder’s profile (logged as Inspected in Admin) before approve is allowed. Initiator sees the suggestion in Lora / suggestions; responder does not yet. See member-app screenshot (RAW).
INITIATOR APPROVED verified — Initiator said yes; suggestion is now with the responder. Responder in the member app. Must open initiator’s profile before approve (cannot inspect during RAW). Responder sees the suggestion; initiator waits.
INITIATOR DECLINED verified — Initiator said no. Introduction is closed. None. Suggestion disappears from active flows.
INITIATOR IGNORED verified — Initiator did not respond before Must respond until. None (may trigger reminder communications depending on brand). Suggestion expires for the initiator.
RESPONDER DECLINED verified — Responder said no after initiator approved. None. Closed for both parties.
RESPONDER IGNORED verified — Responder did not respond in time. None. Closed for both parties.

How Must respond until is set, extended, and what happens when it passes: Response deadlines.

Response deadlines

How the Due / Must respond until column works for pre-match suggestions (RAW and INITIATOR APPROVED).

On the introductions list and detail page, the deadline shows how long the current party has to approve or decline before the introduction is auto-closed as ignored (not TERMINATED). Matchmaker stages use separate SLA rows — see matchmaker SLA settings.

When the clock starts

StatusWho must actDeadline set whenApp Settings row (typical description)
RAW Initiator verified — Status becomes RAW (after staff approve, availability check completes, or automation publishes the suggestion). Minutes until first react — number of minutes added to “now” for Must respond until.
INITIATOR APPROVED Responder verified — Initiator approves in the member app (status advances from RAW). Minutes until second react — same pattern for the responder’s turn.

verified — AVAILABILITY CHECK usually has no approve/decline SLA on the list (deadline starts at RAW). MATCHED and later stages use matchmaker minutes or hold durations instead.

Reminder waves before the deadline

verified — While status is RAW or INITIATOR APPROVED, scheduled jobs compare Must respond until to your brand’s introduction waiting times setting (comma-separated minute offsets under App Settings → Reminders). Each wave that fires logs Reminder Sent with label introductionWaiting on the detail Logs tab and may post a short Lora nudge on the suggestion thread.

Full reminder catalog: introduction log types → Reminder types and communication trigger events → Reminder parameters.

When the deadline passes with no action

verified — A scheduled job finds rows where Must respond until is in the past:

  • RAW → INITIATOR IGNORED
  • INITIATOR APPROVED → RESPONDER IGNORED

The list may still show the old deadline for a short window after it passes — introduction waiting reminder waves can still fire until the auto-ignore job runs. Refresh the detail page; once status becomes ignored, the deadline column clears.

Compare with TERMINATED (member not available at all, frozen release, availability timeout): Ignored vs TERMINATED.

App Settings rows (where to edit timers)

Open Settings → Settings, search the Description column, edit New Value, then Publish. Rows live in the Mobile app category unless your brand groups them elsewhere.

Typical Admin descriptionWhat it controlsWhen it applies
Minutes until first react verified — Length of the initiator’s approve/decline window when status becomes RAW. Each time a suggestion reaches RAW (after staff approve, availability check, or automation).
Minutes until second react verified — Responder’s window after the initiator approves (INITIATOR APPROVED). When status advances from RAW → INITIATOR APPROVED.
Introduction waiting times verified — Comma-separated minute offsets for introduction waiting reminder waves (under the Reminders category). While status is RAW or INITIATOR APPROVED and the member still owes a response. Pair with a Reminder communication template — see reminder parameters.
Minutes for extend verified — How many minutes one token extend purchase adds to Must respond until. The server converts to whole hours (for example 120 minutes → 2 hours; 90 minutes → 1 hour). Admin Extenstion log rows show hours added. Member Extend on premium brands with extend introductions enabled.

Matchmaker Due on Shidduch rows uses different SLA minutes per status — not these react timers. See matchmaker SLA settings.

Member extends deadline (tokens)

When your brand enables both the premium and extend introductions app features, members who are waiting on a suggestion may buy extra time with in-app tokens. The button does not appear on brands without premium, or when extend introductions is off.

TopicPlain meaning
Where in the app verified — Small Extend pill on the suggestion card on Potential Matches (not-replied suggestions) and on the home pending suggestions avatar row. It is not shown on the inline suggestion strip inside an open Lora chat thread.
Who can tap it verified — Only while status is RAW (initiator’s turn) or INITIATOR APPROVED (responder’s turn). The member must be one of the two parties on that introduction. Support can confirm the acting party from the empty Inspected eye icon on the introductions list.
What it does verified — Adds time to Must respond until for that introduction only. An Extenstion log row appears on Admin detail (By: N hours). Members may extend more than once — there is no coded cap on how many token purchases apply to the same row.
How much time verified — Controlled by minutes for extend in App Settings. Stored as minutes but applied as whole hours only (90 minutes adds 1 hour, not 1½). Admin Extenstion log rows show the hour count added.
Token cost verified — Price comes from your brand’s payments hour extends token package (hourly rate ÷ 24, rounded up to whole tokens). If the member’s balance is below that cost, the app opens the token purchase flow or an info screen (extend suggestion trigger with no tokens param) instead of extending.
After confirm verified — Tokens deduct through the payments service; deadline moves forward immediately. Failed payment (for example insufficient balance after purchase attempt) leaves the deadline unchanged — no Extenstion log row.
Extend pill button on a pending suggestion card in the member app
Waiting for screenshot. Capture: Extend pill next to the time-left chip on a RAW or INITIATOR APPROVED suggestion on Potential Matches (slug introductions-extend-suggestion).

Support checklist when a member says Extend failed

  1. Confirm status is RAW or INITIATOR APPROVED on the introduction detail page.
  2. Confirm premium and extend introductions are enabled under App Settings → App Features (publish settings after changes).
  3. Check the member’s token balance vs your brand’s hour extends package price in payments settings.
  4. Refresh detail after they claim success — look for a new Extenstion row and a later Must respond until.

Platform pause (system shutdown)

verified — When ops turn system shutdown off after a maintenance window, open introductions in RAW, INITIATOR APPROVED, and certain matchmaker stages get their Must respond until pushed forward by the shutdown duration. Admin logs an Extenstion row with reason After Pause (hours added match the pause length).

What you see in Admin

  • Due on the list — hover or open detail for the full timestamp.
  • After a member extends — refresh detail; Must respond until moves later and Extenstion appears in Logs.
  • Changing status manually (staff picker) cancels pending introduction reminders for that row — extensions from shutdown or tokens are separate log types.

See App Settings rows above for which timer rows to edit. Per-brand values differ — confirm with your brand manager before changing production timers.

Engagement broken — ops playbook

When staff record that an engagement through the platform did not continue — and what changes for members, matchmakers, and payments.

Use this status when the couple had reached ENGAGED (or you imported a row as Broken Engagement) and the engagement is over, but you want to keep the introduction record for reporting — not when a match simply ended before engagement.

When to use ENGAGEMENT BROKEN vs other closes

SituationPick this statusWhy
Couple was ENGAGED through this introduction; engagement called off ENGAGEMENT BROKEN verified — Both profile statuses return to active. Pending matchmaker engagement payments auto-cancel. History stays tied to this introduction id.
Couple was dating or in matchmaker stages but never engaged ENDED (Shidduch End shidduch / unmatch flow) verified — Captures unmatch reasons and matchmaker notes. Does not imply a broken engagement milestone.
One member declined before MATCHED Decline / ignore statuses (for example INITIATOR DECLINED) Automated member action — not an ops engagement reversal.
Leaving ENGAGED to any status other than ENGAGED Any manual change (including ENDED) verified — Both members’ profile status also returns to active when you leave ENGAGED or MARRIED for another status. Pending engagement SME payments cancel when the previous status was ENGAGED.

How to record it in Admin

  1. Open Singles Management → Admin Matches and find the row (filter by ENGAGED or search by introduction id / member name).
  2. Open the introduction detail page.
  3. From the header Status control, choose ENGAGEMENT BROKEN (Engagment Broken in the picker).
  4. In the Status change dialog, enter a clear Reason (required) — for example who reported the break and the date ops confirmed it.
  5. Confirm. The page refreshes; a Status Change row appears on Logs with your reason.

There is no separate Shidduch-detail button for this status — use the introduction detail status picker (matchmakers with only Shidduch access should ask an admin with introduction Edit permission, or use the introduction link from the Shidduch row).

What happens automatically

AreaEffect
Member profile status verified — Initiator and responder profile status both change to active (no longer engaged). Confirm on each member’s Profile Status Changes — a new row should appear with an automated reason and blank Changed By unless you drove the change manually.
Introduction row verified — Status becomes ENGAGEMENT BROKEN. The row is not treated as an active suggestion or open match in member flows (same class as other closed milestones).
Reminders verified — Pending introduction reminders for this row are cancelled.
Matchmaker engagement payments verified — When the previous status was ENGAGED, any still-pending SME payment rows with reason engagement for this introduction are auto-cancelled with an internal note. Paid engagement payments are not reversed — finance reviews those manually.
Admin engagement notification verified — Unlike moving into ENGAGED, this change does not fire the New engagement admin-channel template. No dedicated “engagement broken” admin notification was traced in code (July 2026).
Member app chat / suggestions verified — Members do not continue this introduction as an active match. They may become eligible for new suggestions again when your brand’s usual rules allow (profile active, not snoozed, etc.).
Chat stats on detail verified — S-Manager chat analytics may still load for closed introductions when chat was used earlier (same rules as ENDED).
Member-facing communications verified — No dedicated introduction-status push/email fires for ENGAGEMENT BROKEN (unlike moving into ENGAGED, which can trigger admin New engagement notifications). Both members’ profile status returns to active with reason introduction engagement broken, which may trigger a published Profile Status Updated communication when your brand configured one for that transition — check communication trigger events and Communications for param patterns like active leaving engaged. If members report silence, send a manual comm or confirm with your brand lead — there is no built-in “engagement broken” member template.

After you save

  • Filter the introductions list by ENGAGEMENT BROKEN to audit broken engagements for reporting.
  • On matchmaker brands, the Shidduch list may still show the row under an ended-style label depending on import history — trust the introduction detail status as source of truth.
  • Check Payments if you expected a pending engagement payment — it should show cancelled when auto-cancel ran.
  • Do not use Reset introduction on production pairs — that test tool is only for internal accounts.

Related: view introduction → Actions, matchmaker workflow → Leaving ENGAGED.

Frozen (not for now)

A member can park a suggestion they are not ready to decide on yet — without declining the match.

StatusPlain meaningWho acts nextWhat members see
FROZEN verified — One party chose not for now while the introduction was still RAW or INITIATOR APPROVED. The suggestion is saved on their frozen list only. The member who froze it. They can re-open it later (returns to RAW) or release it (closes as TERMINATED for both). Freezer — sees the suggestion under their frozen / parked list in the member app and can inspect the partner profile again. Other party — the suggestion disappears from their active queue; the system may offer them a new suggestion instead.

How freezing works

  • verified — Available only during RAW (initiator) or INITIATOR APPROVED (responder). It is not the same as Decline — the pair is not permanently closed for the freezer.
  • verified — Each brand limits how many frozen suggestions one member may keep at once (App Settings max frozen introductions; default 2 when unset). When the cap is reached, the app shows a limit message and does not freeze another row.
  • verified — After a freeze, the platform triggers new suggestions for the other party so they are not left waiting on a parked introduction.
  • verified — If the freezer was the responder (“not first”), re-activating may swap initiator and responder so the freezer becomes the proposer again — same pattern as staff Swap Direction on pending approval.

Member info screens for frozen flows

Publish Active screens on these trigger events so members see your copy instead of a blank failure:

Trigger eventWhen it firesOps tip
Frozen limit reached Member already holds the maximum frozen suggestions and taps not for now again. Explain the cap and how to release an existing frozen row. Screenshot slug introductions-frozen-limit-reached pending upload.
Frozen partner unavailable Re-activate blocked because partner is snoozed, inactive, or has no intro slot. Offer release or wait copy. Slug introductions-frozen-partner-unavailable pending upload.
No available slot Re-activate blocked because the freezer has no available introduction slot. Link support to available intro count reasons on the member profile.

Full trigger catalog: Info screens — trigger events.

Member choices on an active suggestion

While status is RAW or INITIATOR APPROVED, the member app offers more than approve / decline. Support staff should know the difference:

Member actionPlain meaningResult in AdminOther party
Approve (after opening the profile) Interested — move to the next step. INITIATOR APPROVED or MATCHED Responder sees the suggestion, or both enter chat when matched.
Not interested / decline Permanent no for this pair. INITIATOR DECLINED or RESPONDER DECLINED Closed; the other party may receive a new suggestion.
Not for now (freeze / hold) verified — Park on their frozen list without closing the match. FROZEN — Status Change log verified — Suggestion leaves their active queue; platform requests a new suggestion for them.
Not available at all (from snooze / pause flow) verified — End this suggestion immediately and continue to account pause. TERMINATED verified — Both parties return to the suggestion pool.

Re-open or release a frozen suggestion

verified — Only the member who froze the row can act. From their frozen suggestions strip on the potential-matches screen (snowflake badge on the avatar), or from the frozen partner profile:

  • Re-activate — Returns to RAW for the freezer. If they were the responder, initiator and responder may swap first (same idea as staff Swap Direction) — watch for a Swapped log row. Re-activation is blocked when the held partner is snoozed, deleted, or has no free introduction slot; the app shows a partner-unavailable message and offers release instead.
  • Release — Closes the introduction as TERMINATED and frees both members for new suggestions.
Frozen suggestions row with snowflake badges on the member potential matches screen
Waiting for screenshot. Capture: frozen suggestions section on the member potential-matches / suggestions screen — avatar row with snowflake icon (slug introductions-frozen-list).

What you see in Admin

Frozen rows appear in the introductions list like any other status (filter by FROZEN to find them). The detail page shows FROZEN in the status control. There is no separate Admin action to un-freeze — the member re-opens or releases from the app.

A Status Change log row records when the member froze the suggestion. Re-activation logs another change back to RAW; release logs TERMINATED. To see who froze it, open Logs and look for the status change to FROZEN — the author column shows that member’s first name.

Member info screens (freeze limits)

verified — When freeze or re-activate is blocked, the member app shows branded info screens (not Admin errors). Publish active screens for these trigger events under info screens:

When it appearsTypical member messageSupport note
Member tries to freeze another suggestion at the brand cap Frozen limit reached info screen Cap from App Settings max frozen introductions (default 2). They must release or re-activate an existing frozen row first.
Member tries to re-activate but partner cannot match now Partner unavailable info screen — offers release Partner may be snoozed, scheduled for delete, or out of introduction slots. Not an Admin bug — check both profiles’ activity and available intro count.
Member tries to re-activate but they have no free slot No available slot style message Freezer’s available introductions count is zero — same reasons as paused suggestions (pending intro, inspection backlog, etc.).

Support playbook: Support troubleshooting → Frozen suggestion issues.

Matched and beyond

StatusPlain meaningTypical next steps
MATCHED verified — Both said yes. They can chat (when chat is enabled) and, on matchmaker brands, enter the Shidduch queue as New. Matchmaker accepts from Shidduch detail → MM AVAILABLE; or staff change status manually. See matchmaker workflow. Member chat screenshot: view introduction → What members see.
MM AVAILABLE verified — Open on the matchmaker queue (Available on Shidduch Requests). SLA deadline applies. Matchmaker takes case → MM TAKING ON.
MM TAKING ON verified — Assigned matchmaker is working the case (Taking On). Log first contact → MM CONNECTED.
MM CONNECTED verified — Matchmaker contacted parties (Contacted). Record answers dialog → MM RECORDED, hold, unmatch, or wait.
MM RECORDED verified — Both parties answered interested (Answers Recorded). Record date → DATING.
MM TIMEOUT verified — Matchmaker missed the SLA for the current stage (Timed Out). May be revived from Shidduch list. Reassign matchmaker or revive per brand policy.
DATING verified — Couple is dating; date number may show on Shidduch status chip. Log next date or mark ENGAGED.
ENGAGED verified — Engaged through the platform. May fire admin notification templates. Celebration comms; may move to MARRIED.
MARRIED verified — Marriage recorded in Admin. Archive / reporting.
EXTERNALLY ENGAGED verified — Created when either profile is already engaged outside this introduction (for example manual create while one party is engaged). Ops follow brand policy for external engagements.
ENGAGEMENT BROKEN verified — The couple was ENGAGED (or on a matchmaker path toward engagement) but the engagement did not continue. Admin shows this label as Engagment Broken (same numeric status as in imports labeled “Broken Engagement”). Staff set this manually from the introduction detail status control (reason required). See Engagement broken — ops playbook for when to choose this status vs ENDED.
ON HOLD verified — Paused with a chosen hold duration (1 day – 1 month on Shidduch detail). Must respond until extends to the hold end. Resume from Shidduch detail when ready.

Closed or excluded

StatusPlain meaning
INITIATOR IGNORED verified — The initiator did not approve or decline before Must respond until while status was RAW. Automated nightly job closes the row — not the same as TERMINATED.
RESPONDER IGNORED verified — The responder did not act before the deadline while status was INITIATOR APPROVED. Same automated expiry job as initiator ignored.
TERMINATED verified — Ended before a successful match through an explicit close path (member not available at all, frozen release, availability-check timeout, or staff manual change). See How introductions reach TERMINATED.
ENDED verified — Natural end of the introduction journey after MATCHED (for example matchmaker unmatch). Chat stats may still be available for managers.
NOT COUNTED verified — Exists in the database but excluded from statistics (duplicate, test, or ops correction). Rare on live brands; staff set manually from the introduction detail status picker.

Decline statuses (INITIATOR DECLINED, RESPONDER DECLINED, ADMIN REJECTED) are also closed — see Member review and Before members see a suggestion.

How introductions reach TERMINATED

Support staff often confuse TERMINATED with ignored deadlines or ENDED after a match. Each path below was traced in the introduction service (July 2026).

TriggerStarting statusWho actsWhat members see next
Member — not available at all RAW or INITIATOR APPROVED Either party, from the snooze / pause flow in the member app verified — Introduction closes; both parties return to the suggestion pool. Distinct from not for now (FROZEN).
Member — release frozen suggestion FROZEN Only the member who froze the row verified — Row closes; both parties can receive new suggestions. Partner may already have moved on when the freeze happened.
Availability check — final reminder with no answer AVAILABILITY CHECK System (scheduled reminders) verified — Initiator may be snoozed from new suggestions for a period set in App Settings (snooze after availability check). Reminder Sent rows precede the final Status Change — see log types → reminders.
Staff — manual status change Any Admin with Edit on view introduction Depends on prior status. Use a clear reason in the status-change dialog; it appears on Logs. Prefer ENDED or decline statuses when a match already existed — see Ignored vs TERMINATED.

Not TERMINATED: When a member misses the approve/decline deadline on RAW or INITIATOR APPROVED, the nightly job sets INITIATOR IGNORED or RESPONDER IGNORED instead — unless your brand maps that path differently in a custom integration (default traced July 2026).

Ignored vs TERMINATED

Both close an introduction before MATCHED, but the cause and member impact differ.

QuestionINITIATOR / RESPONDER IGNOREDTERMINATED
Typical cause verified — Missed Must respond until on RAW (initiator) or INITIATOR APPROVED (responder). verified — Member chose not available at all, released a frozen row, failed availability check after all reminders, or staff closed manually.
Automated or manual? verified — Automated nightly job when deadline passes. Mix — member-initiated, availability reminders, or staff picker.
Return to suggestion pool? verified — Both parties typically become eligible for new suggestions when your brand’s usual rules allow (active, not snoozed, under inspection cap). verified — Same for member not available at all and frozen release. Availability-check timeout may also snooze the initiator.
What to look for in logs Status Change to INITIATOR IGNORED or RESPONDER IGNORED; may follow Reminder Sent (introductionWaiting). Status Change to TERMINATED; availability path may show several introAvailabilityCheck reminders first.
After MATCHED Does not apply — these statuses are pre-match only. Use ENDED (unmatch) or matchmaker flows instead of TERMINATED when the couple had already matched.

Log pattern reference: introduction log types → Common status-change patterns.

Pending approval workflow

When automated matching creates PENDING APPROVAL instead of sending straight to the initiator.

Your brand controls this with pending introductions mode in App Settings (under Algorithm / mobile settings):

  • Always — every new automated suggestion waits for staff approval.
  • Never — suggestions skip approval (they may still use availability check or go straight to RAW).
  • No tolerance — approval is required when matching had to relax (“tolerance”) on certain attributes, or when either party has a recent “any declined” flag on their profile.

Additional rules:

  • If either side’s bio score is below minimum go to pending (when that setting is above zero), the introduction goes to pending approval.
  • When staff click Approve, the next status is AVAILABILITY CHECK if your brand enables intro availability check; otherwise RAW. See Availability check workflow for member question, reminders, and timeout behavior.
  • Open the Pending reasoning section on the detail page (when enabled) to see tolerance attributes and decline history that explain why the pair was held.

Manual create from Admin defaults to PENDING APPROVAL as well (not RAW), unless a matchmaker is assigned on create (MM TAKING ON) or either profile is already engaged (EXTERNALLY ENGAGED).

Automated release vs staff approve

verified — After the matcher creates a PENDING APPROVAL row, a background Match Advisor pass may run. The system can move the introduction forward without a staff click only when advisor checks pass and your brand’s admin-review gates are clear. When any gate still applies, the row stays in PENDING APPROVAL until someone with Edit on view introduction acts (detail Approve or bulk approve on the introductions list — same server permission for both).

Signal on list or detailBlocks automated release?Staff Approve (detail or bulk approve)?
Contradictions > 0 (hard contradictions) Yes — advisor finished with blocking bullets. Yes — same next step as a clean row (AVAILABILITY CHECK or RAW). Conflict data may remain on the row for audit; members proceed once status advances.
Close but blocked / list warning icon Yes — soft deal-breaker attributes recorded on the pair. Yes — coordinate with brand policy and member in-app steps before approving.
AI conflict brain icon / Personality conflicts Yes when your brand is configured to hold personality-conflict introductions for review. Yes — read per-party lines on view introduction → personality conflicts first.
Checks before suggesting on compare or list rank icon (before staff approve) Yes — Jev pair checks returned a hold (high-confidence topic flag). Automated release waits; staff can still approve after review. Yes — read flags on compare or potential matches; tune questions on Match check questions if the brand fires too often.
Declined before / earlier-decline stop Yes — pair was introduced before and someone declined; code check does not auto-release. Decline or override per brand policy; do not re-suggest without staff sign-off.
Match Advisor Advisor could not complete (advisor job failed) Usually no for Jev-only holds that exist because the Jev call failed — promotion may follow your brand’s “advisor failed” path. Yes for code stops (earlier decline) and for Jev holds when the advisor job succeeded but Jev returned an error. Read compare flags anyway; retry advisor when appropriate. See match check worked examples → When Match Advisor fails.
Pending reasoning tolerance or decline chips only Sometimes — depends on pending mode, scores below minimum go to pending, and attribute flags. Yes — review chips on Pending reasoning before sign-off.

Automated promotion never replaces staff judgment when your brand requires approval for every suggestion (always pending mode). Support playbook: stuck in pending approval.