Reference (partial) — Log types were traced in the introduction detail API (July 2026). Rows marked verified match what Admin displays today. Member-app screenshot placeholders for RAW and MATCHED flows are linked from the view introduction guide.

Overview

On the view introduction page, the Logs section is a single chronological timeline. It merges status history, member activity, Lora questions, reminders, deadline extensions, and phone-share events for this introduction.

Entries are sorted oldest → newest. The Author column shows a member’s first name when the event came from the initiator or responder; staff names appear on admin-driven status changes; some system rows leave author blank.

This reference explains each Type label and how to read the Message text. For what a status change means for members, see introduction statuses.

Log columns

ColumnWhat it shows
Date / time When the event happened (local formatting in Admin).
Author Who triggered the row: initiator first name, responder first name, staff full name on manual status updates, or blank for some automated rows.
Type Category label (for example Status Change, Question). See table below.
Message Details — status name, question text, answer text, reminder label, hours extended, phone-share action, etc.

Where log rows come from

verified — The timeline is assembled server-side from several stores, then sorted by date.

Source dataLog type producedNotes
Introduction status history Status Change Includes optional reason text in parentheses.
Profile inspections on this introduction Inspected Message prefix Inspected_ + inspection kind. Author column uses the inspecting member’s profile id.
Scheduled reminders (non-canceled only) Reminder Sent Canceled reminders are excluded so ops do not see nudges that never fired. Message may append the linked communication name when a comm id is stored.
Lora questions on the introduction thread Question / Answer Hidden questions are omitted unless they are AI follow-up questions (unique wording still matters for support).
Lora plain-text lines (non-hidden) Message Separate from question/answer pairs — system text bubbles in the introduction chat.
Deadline extensions on the introduction row Extenstion Hours added to Must respond until (member purchase or system resume).
Initiator/responder swap audit Swapped Logged when staff use swap direction on a pending introduction.
Chat phone-share messages (when both parties have app accounts) Share Phone Request / Share Phone Message Rows built from the matched-pair chat store when the workflow posts request/share chips. Message text is Requested to share phone number / Shared phone number (no “(app)” suffix).
Member-app analytics (matched window) Share Phone Request / Share Phone Message / Phone Share Number Viewed verified — Same introduction id, scoped to the chat-stats activity window (first MATCHED through first closing status). Request/share analytics messages end with (app). Phone Share Number Viewed is analytics-only (no chat chip): … (match list) vs … (after request) vs plain Viewed partner phone number. If analytics is temporarily unavailable, these rows are skipped — chat-store rows above may still appear.

Merge behavior: When you open introduction detail, the server loads status history, inspections, reminders, Lora Q&A, extensions, chat-store phone-share messages (when both profiles have user accounts), then app analytics rows. Analytics failures are non-fatal — you still see chat-store share rows. Sort order is by timestamp only; duplicate type labels with slightly different message text are expected when both sources logged the same tap.

Entry types

Type (Admin label)Plain meaningMessage columnTypical author
Status Change verified — Introduction moved to a new lifecycle status (automated or staff). Status name, plus reason in parentheses when one was recorded (for example RAW (auto)). Staff name when a backoffice user changed status; system or numeric id for automated paths.
Inspected verified — One party opened the other’s profile while reviewing this introduction. Starts with Inspected_ followed by an inspection kind from the member app (for example Inspected_half or Inspected_full). See Inspection messages. Profile id of the member who opened the partner profile (Admin shows their first name when it matches initiator or responder).
Reminder Sent verified — System scheduled a reminder nudge for this introduction (before a deadline or during availability check). Reminder label (translated when possible). See Reminder types. Profile id of the member who should act.
Question verified — Lora sent a visible question tied to this introduction (availability check, icebreaker, etc.). Question text as shown to the member. Hidden questions are omitted except AI-generated follow-up questions, which still appear because their wording is unique to this turn. Profile id of the member who received the question.
Message verified — A non-hidden Lora text line in the introduction chat (not a question/answer pair). Plain message body. Usually blank or system — check date/time for ordering.
Answer verified — Member answered a logged Lora question for this introduction. Answer text (comma-separated when multiple choices were selected). Profile id of the member who answered.
Extenstion verified — Response deadline (Must respond until) was extended. By: N hours — number of hours added. Common paths: member token purchase while status is RAW or INITIATOR APPROVED (requires premium + extend introductions app features); platform pause after system shutdown ends (After Pause in status reason). See response deadlines. Usually blank.
Swapped verified — Staff used Swap Direction while the introduction was pending approval; initiator and responder were reversed. Swapped Blank.
Share Phone Request verified — The man confirmed the request step in the share-phone workflow (matches-list phone-callback icon or equivalent). Requested to share phone number from chat history, or Requested to share phone number (app) from member-app analytics. You may see both for one action — same type label, slightly different message text. Member who sent the request (typically the man).
Share Phone Message verified — The woman confirmed her share step; her saved phone number was posted in chat. Shared phone number from chat history, or Shared phone number (app) from analytics. One successful share per workflow — not one row per tap on acknowledgment screens. Member who shared (typically the woman). Requires a phone number on her user account.
Phone Share Number Viewed verified — The man opened the partner-number popup after the woman shared (view-only — does not send a new chat chip). Viewed partner phone number (match list) when he used the matches-list phone-in-talk icon; … (after request) when he opened the number from the post-request flow; otherwise Viewed partner phone number. Member who viewed (typically the man). Analytics-only — no separate chat chip row.

Share phone workflow — when these rows appear

verified — These log types are merged from the matched-pair chat store and from member-app analytics during the same matched activity window — not from Admin button clicks. They appear on the introduction detail timeline only when:

  • Status is MATCHED or later (both parties approved).
  • Your brand enables the share phone app feature (and usually chat).
  • Both members have user accounts linked to their profiles so Admin can resolve a chat conversation id.
  • At least one member completed a share-phone step (matches-list icon, matched profile button, or a Lora home chat share phone link for the woman).

Rows are merged when you open detail — they do not create a Status Change row by themselves. Share Phone Message is created when the woman completes her share step. Share Phone Request when the man completes his request step. Repeat taps on acknowledgment screens do not add extra chat chips. The man can open view partner number only after her share exists in chat; that open logs Phone Share Number Viewed (analytics) but does not post another share message.

Two sources, similar rows: Chat-store rows use plain message text (Shared phone number). Analytics rows for the same tap may also appear with (app) in the message. Treat them as one member action — sort by time and author, not by duplicate type labels. If analytics is down, you may see only the chat-store row (or only analytics when chat sync lags — refresh detail after a minute).

In the member app chat thread, both steps appear as phone-icon chips (not typed messages). Row subtitles and icons on the Matches list update when chat syncs — see Support troubleshooting → Matches list row states and chat thread chips for sender vs partner wording and Admin log mapping.

Info screens that guide each step (before share, after share, blocked, view partner number) are configured under info screens → share phone workflow. If members report missing logs but chat shows the exchange, refresh detail — logs load from the conversation store, not the introduction row alone.

Support checklist when members cannot share or logs are missing: Support troubleshooting → Share phone in chat.

Log typeMember action that creates itSupport tip
Share Phone Request Member taps to request exchanging phone numbers with their match. Partner must still complete the share step — request alone does not reveal numbers.
Share Phone Message Woman confirms and sends her number through the workflow. One row per successful woman share — not one per tap. The man’s separate Share Phone Request row (if he requested first) does not reveal digits by itself.
Phone Share Number Viewed Man opens the read-only partner-number screen after she shared. Confirms he saw the number — not the same as her Share Phone Message. Message text shows whether he opened from the matches list or the post-request flow.
Type (legacy / unused)MeaningMessageAuthor
Status Reason TBD — Reserved in code for standalone admin termination / rejection reasons; not emitted in current log API responses (reasons appear on Status Change rows instead). — —
Requested Feedback / Feedback Received TBD — Listed in older client models only; not returned by the current introduction logs API. — —

Reminder types

When Type is Reminder Sent, the message column shows one of these labels (after translation when available).

Reminder labelWhen it firesWho receives it
introductionWaiting verified — Scheduled before Must respond until while status is RAW (initiator) or INITIATOR APPROVED (responder). May also post a short Lora reminder message on the suggestion thread. The party who must approve or decline next.
introAvailabilityCheck verified — Early nudge during AVAILABILITY CHECK when the initiator has not answered the “available for intro?” question. On intermediate reminders the system may clear a stale “available” answer so the question can be asked again. Initiator.
introAvailabilityCheckAnswered verified — Follow-up reminder when the initiator already answered “available” but the introduction has not moved forward within brand timing. Initiator who already has an “available for intro” answer on file.
DNFReminder / PendingParentReminder verified — rare on intro logs — Profile-level reminders (did-not-finish onboarding, pending parent approval). They appear here only when the reminder row is stored with this introduction id. Most timelines never show these. The profile that received the reminder.
CommDelayed / BulkCommDelayed verified — rare on intro logs — Scheduled communication sends. Listed only when the delayed job was tied to this introduction id. Varies by campaign.

Availability check — what happens if the initiator never answers

verified — Brand timing settings define several reminder steps. Early steps log introAvailabilityCheck rows (see table above). After the final step with no answer, the introduction moves to TERMINATED and the initiator may be snoozed from new suggestions for a period set in App Settings (snooze after availability check). Full operator guide: introduction statuses → Availability check workflow.

When the initiator does answer and the flow advances, you will see Question / Answer rows in the log, then a Status Change to RAW.

Inspection messages

When a member opens their match’s profile while reviewing an active introduction, the app records an Inspected log row. The Message column shows Inspected_ plus a short type code (see Inspection type codes).

The introductions list shows a separate Inspected eye icon per party when they have opened the partner profile at least once for this introduction (any logged inspection). The log timeline lists each logged inspection with its type code.

Members must open the partner profile before they can approve a suggestion. On brands with the two degrees profile app feature enabled, the first open logs half; approve stays blocked until they reveal the rest of the profile and a full inspection is logged — see type codes.

Silent opens (no log row) — When a member opens a matched partner from chat history, the app may refresh profile data with a silent inspection call. That path does not add a new Inspected row to this timeline (the eye icon on the list still reflects earlier logged opens).

Inspection type codes

Suffix after Inspected_ in the log Message column.

Code (Admin message)Plain meaningWhen it is recordedMember-app effect
Inspected_full verified — Member opened the partner’s full profile (all visible sections for this introduction). Logged on first open when the two degrees profile app feature is off; or when the member taps to reveal the rest of the profile on brands where that feature is on. The app treats this as a complete inspection — approve and decline unlock. Eye icon appears on the Admin list.
Inspected_half verified — Member opened a limited (“first look”) profile view before revealing the rest. Only when the two degrees profile app feature is on: first tap on a suggestion from Lora or the suggestions list opens a partial view and logs half. Eye icon may appear in Admin after the first open, but approve stays blocked until Inspected_full is logged (member taps through the reveal step).
Inspected_ (blank suffix) verified — Profile was opened without a type label stored on the row. Older app builds, rare API paths, or rows created before type codes were added. Counts toward the list eye icon. Approve rules follow the same full vs half logic using whatever types are stored on the introduction.

A member may generate more than one Inspected row per introduction (for example half then full). The list-page eye icon stays on after the first inspection.

When members can inspect

StatusWho can inspectWhat happens if they try too early
AVAILABILITY CHECK verified — Initiator only (availability question in Lora). Inspection is not the focus at this stage. Responder still cannot open the partner profile.
RAW verified — Initiator only. Responder cannot open the partner profile; the app returns an error if they try.
INITIATOR APPROVED verified — Responder (and initiator can re-open). Normal profile open flow; inspection logged on open.
MATCHED and later active statuses verified — Both parties from chat, suggestions, or profile links tied to this introduction. Inspections still log when opened from an introduction context.
FROZEN verified — Only the member who froze the suggestion (their profile is stored on the introduction as the freezer). They can re-open the partner profile to decide whether to re-activate or release. The other party cannot inspect this introduction while it is frozen for them.

Approve button vs inspection type

verified — The member app checks which inspection types are stored on the introduction before enabling approve:

  • When two degrees profile is off, the first profile open logs full and approve is available immediately (after the open completes).
  • When two degrees profile is on, the member sees a limited first screen (half). The primary accept control first reveals the rest of the profile (logs full) — approve does not complete until that second step. Not interested / decline stays available on the partial view while status is RAW or INITIATOR APPROVED, so a member can decline without completing the full reveal.

Effect on new suggestions

verified — If a member has too many open suggestions they have not opened yet (no inspection row where they are the opener on that introduction), the platform sets their “available introductions” count to zero and pauses new RAW or INITIATOR APPROVED suggestions until they review existing ones. The cap comes from your brand’s max raw non-inspected row in App Settings. When that setting is missing or empty, this pause does not run.

Only logged inspections count toward this cap — silent opens from chat history do not add rows and do not clear the backlog by themselves.

This is separate from the Inspected eye icon on a single row — that icon reflects only whether this introduction was opened at least once (any logged inspection).

Troubleshooting “no new suggestions”

What to check in AdminWhat it means
Member has RAW rows where they are initiator and their Inspected eye is empty verified — Each such row counts toward the non-inspected backlog until they open the partner profile in the app.
Member has INITIATOR APPROVED rows where they are responder and their eye icon is empty verified — Same rule for the responder’s turn.
Count of those rows ≥ your brand’s max raw non-inspected setting verified — Matcher treats them as having zero available introduction slots until backlog drops below the limit.
Detail Logs shows Inspected_full or Inspected_half after the member taps the profile That introduction no longer counts as non-inspected; new suggestions may resume when total backlog is under the cap.

Step-by-step for support: Support troubleshooting → Inspection backlog · introductions list → Inspection backlog cap.

Common status-change patterns

Most Status Change rows show the new status name in the Message column, sometimes with a reason in parentheses. Use this table when triaging a closed introduction.

Log sequence (typical)Final statusPlain meaning
Reminder Sent (introductionWaiting) → Status Change → INITIATOR IGNORED INITIATOR IGNORED verified — Initiator missed the deadline on RAW. Automated nightly job — not TERMINATED.
Reminder Sent (introductionWaiting) → Status Change → RESPONDER IGNORED RESPONDER IGNORED verified — Responder missed the deadline on INITIATOR APPROVED.
Reminder Sent (introAvailabilityCheck × N) → Status Change → TERMINATED TERMINATED verified — Initiator never completed availability check after all reminder waves. Initiator may be snoozed — see statuses → TERMINATED paths.
Status Change → FROZEN (member author) FROZEN verified — Member chose not for now. Other party may already have a new suggestion.
Status Change → TERMINATED (member author) after FROZEN TERMINATED verified — Freezer released the parked suggestion.
Status Change → TERMINATED (member author) from RAW / INITIATOR APPROVED TERMINATED verified — Member chose not available at all (distinct from decline and freeze).
Status Change → FROZEN → later Status Change → RAW; optional Swapped RAW verified — Member re-activated a frozen suggestion. Swapped appears when the freezer was the responder and parties reverse roles.
Status Change (staff name) → any status + reason text Varies Manual change from introduction detail status picker. Reason stored on the same Status Change row.
Inspected_half → Inspected_full → Status Change → INITIATOR APPROVED or MATCHED Advances verified — Normal approve path on brands with two-step profile reveal.
Status Change (staff name + reason) → ENGAGEMENT BROKEN ENGAGEMENT BROKEN verified — Staff ended an engagement from introduction detail. Both members’ profile status logs should show a new active row — see profile status logs. Pending engagement SME payments may auto-cancel.

Status meanings and member impact: introduction statuses. Ignored vs terminated comparison: Ignored vs TERMINATED.