| Type (Admin label) | Plain meaning | Message column | Typical 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 type | Member action that creates it | Support 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) | Meaning | Message | Author |
| 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. |
— |
— |