Monitoring Dates and Conversations

The monitoring workflow allows admins to oversee active dates, inspect message exchanges, and intervene when necessary.

Accessing Date Conversations

There are two ways to view date conversations:

From Pairing Tab
Via API

Navigate to Pairing tab

Scroll to the Active Dates section below available users

Click eye icon

Click the eye icon on any date card

Conversation modal opens

Displays dual phone panel view with full message history

Fetch messages programmatically:

GET /api/tpo/admin/messages?dateId={dateId}
Headers: { 'x-internal-api-key': string }

Response: {
  messages: [
    {
      id: string
      createdAt: string
      fromPhone: string
      toPhone: string
      body: string
      blocked: boolean
    }
  ]
}

The conversation modal displays a dual phone panel interface:

Left Panel: User A

Messages sent by User A appear as user bubbles (blue)
Messages received (from User B or system) appear as bot bubbles (gray)
Phone number shown in header
Chronological message order

Right Panel: User B

Same structure, but from User B’s perspective
Messages sent by User B appear as user bubbles
Messages received appear as bot bubbles

This side-by-side view makes it easy to:

See how each user experiences the conversation
Identify delivery or timing issues
Verify scheduling coordination is clear to both parties
Detect conversation quality problems

The modal is read-only. Admins cannot send messages directly through this interface.

Message Data Structure

Each message contains:

Field	Type	Description
`id`	string	Unique message identifier
`createdAt`	string	ISO timestamp
`fromPhone`	string	Sender phone number (or “system”)
`toPhone`	string	Recipient phone number
`body`	string	Message text content
`blocked`	boolean	Whether message was filtered/blocked

System Messages

Messages with fromPhone: "system" indicate:

Scheduling proposals
Match notifications
Automated prompts

Example:

{
  "fromPhone": "system",
  "toPhone": "+15551234567",
  "body": "let's get the date on the calendar. how does thursday at 7pm work for you?",
  "blocked": false
}

Monitoring Active Dates

Date Card Information

Each active date card shows:

User avatars: Overlapping circular profile photos
User names: “Alice & Bob” format (from dlName)
Message count: Total messages exchanged (useful for engagement tracking)
Creation date: When the pair was created
Actions: View conversation, end date

Key Metrics to Monitor

Message Count

Low message counts may indicate:

Users haven’t started conversing
Scheduling stuck
Technical delivery issues

Conversation Recency

Check createdAt of latest message:

Stale conversations (>48 hours) may need intervention
Active exchanges indicate healthy engagement

Blocked Messages

Messages with blocked: true indicate:

Profanity filter triggered
Inappropriate content detected
May require admin review

Scheduling Progress

Look for scheduling coordination:

Time proposals from system
User confirmations
Finalized date/time

Identifying Issues

Stalled Scheduling

Symptoms:

Few messages after match creation
System proposed time, but no user response
Back-and-forth without resolution

Investigation:

Open conversation modal
Check if User A responded to initial proposal
Verify system generated follow-up prompts
Look for user confusion or technical errors

Possible Actions:

End the date if unresponsive for >1 week
Check SMS delivery logs (outside admin panel)
Verify scheduling logic is working correctly

One-Sided Conversation

Symptoms:

One user sending messages, other silent
System messages sent but no replies

Investigation:

Check if SMS delivery failed (requires backend logs)
Verify both users’ phone numbers are valid
Review last message timestamps

Possible Actions:

End date and notify active user
Re-pair engaged user with new match

Inappropriate Content

Symptoms:

blocked: true on messages
Reported issues from users

Investigation:

Review blocked message content in modal
Check conversation history context
Determine if block was correct or false positive

Possible Actions:

Ban user if content violates guidelines
End date immediately
Delete user account for serious violations

Ending Dates

To terminate an active date:

Navigate to date card

Find the date in the Active Dates section

Click 'end' button

Confirmation not required (action is immediate)

Date status updates

Status changes to ENDED
endedAt timestamp set
Both users return to available pool
Conversation portal disabled for users

POST /api/tpo/admin/end-date
Headers: { 'x-internal-api-key': string }
Body: { dateId: string }

Response: { success: true }

Ending a date does NOT send notifications to users. Consider sending manual SMS if you want to explain the termination.

Date Lifecycle Monitoring

Stage 1: Scheduling (0-48 hours)

Expected behavior:

System sends initial time proposal to User A
User A responds with acceptance or counter-proposal
System coordinates with User B
Date/time finalized

Red flags:

No response from User A within 24 hours
Multiple counter-proposals without resolution
Confusion about date location or format

Stage 2: Pre-Date Conversation (1-7 days)

Expected behavior:

Light conversation to build rapport
Confirmation reminders as date approaches
Logistics coordination (meeting place, etc.)

Red flags:

Complete silence after scheduling
One user dominating conversation
Inappropriate or aggressive messages

Stage 3: Post-Date (After scheduled time)

Expected behavior:

Portal may remain open for feedback
Users may exchange follow-up messages
Date typically ends naturally or admin closes

Red flags:

Negative feedback reported
Requests to end early
Blocked messages spike

Admins can still take user-level actions on paired users:

Ban User in Active Date

POST /api/tpo/admin/user-action
Body: { userId: string, action: "ban" }

Consequences:

User status → BANNED
Active date automatically ended
Other user returns to available pool
Banned user moved to Blocked tab

Delete User in Active Date

POST /api/tpo/admin/user-action
Body: { userId: string, action: "delete" }

Consequences:

All messages deleted
All dates (including active) deleted
User record removed
Phone can re-register fresh

Deleting a user in an active date will orphan the conversation for the other user. Consider ending the date first, then deleting.

Monitoring Best Practices

Daily Check-in

Review active dates daily:

Check message counts for engagement
Identify stalled scheduling flows
Look for blocked messages
End dates older than 2 weeks with no activity

Blocked Message Review

When you see blocked: true:

Read full context in conversation modal
Determine if filter was appropriate
Take action on user if content violates guidelines
Adjust profanity filter rules if needed (backend)

User Feedback Integration

If users report issues:

Pull up conversation in admin panel
Verify technical delivery (backend logs)
Check for patterns across multiple dates
Document issues for engineering team

Privacy Considerations

Conversation data is sensitive:

Only access when necessary for support or safety
Do not share conversation content externally
Document reason for accessing user data
Follow data retention policies

API Reference

Fetch Date Messages

GET /api/tpo/admin/messages?dateId={dateId}
Headers: { 'x-internal-api-key': string }

Response: {
  messages: TpoDateMessage[]
}

Messages are sorted by createdAt ascending (oldest first).

Fetch All Active Dates

GET /api/tpo/admin/dates?status=ACTIVE
Headers: { 'x-internal-api-key': string }

Response: {
  dates: [
    {
      id: string
      status: "ACTIVE"
      portalEnabled: boolean
      createdAt: string
      userA: { id, phoneNumber, photoUrls, dlName, ... }
      userB: { id, phoneNumber, photoUrls, dlName, ... }
      _count: { messages: number }
    }
  ]
}

End Date

POST /api/tpo/admin/end-date
Headers: { 'x-internal-api-key': string }
Body: { dateId: string }

Response: { success: true }

Sets status: "ENDED" and endedAt timestamp.

Create Pairings

Learn how to match users

User Review

Approve applications before pairing

Overview

User Guide

Admin Guide

Monitoring Dates and Conversations

Accessing Date Conversations

Left Panel: User A

Right Panel: User B

Message Data Structure

System Messages

Monitoring Active Dates

Date Card Information

Key Metrics to Monitor

Message Count

Conversation Recency

Blocked Messages

Scheduling Progress

Identifying Issues

Stalled Scheduling

One-Sided Conversation

Inappropriate Content

Ending Dates

Date Lifecycle Monitoring

Stage 1: Scheduling (0-48 hours)

Stage 2: Pre-Date Conversation (1-7 days)

Stage 3: Post-Date (After scheduled time)

User Actions During Active Dates

Ban User in Active Date

Delete User in Active Date

Monitoring Best Practices

API Reference

Fetch Date Messages

Fetch All Active Dates

End Date

Create Pairings

User Review

Build docs developers (and LLMs) love

Overview

User Guide

Admin Guide

​Accessing Date Conversations

​Conversation Modal

​Left Panel: User A

​Right Panel: User B

​Message Data Structure

​System Messages

​Monitoring Active Dates

​Date Card Information

​Key Metrics to Monitor

Message Count

Conversation Recency

Blocked Messages

Scheduling Progress

​Identifying Issues

​Stalled Scheduling

​One-Sided Conversation

​Inappropriate Content

​Ending Dates

​Date Lifecycle Monitoring

​Stage 1: Scheduling (0-48 hours)

​Stage 2: Pre-Date Conversation (1-7 days)

​Stage 3: Post-Date (After scheduled time)

​User Actions During Active Dates

​Ban User in Active Date

​Delete User in Active Date

​Monitoring Best Practices

​API Reference

​Fetch Date Messages

​Fetch All Active Dates

​End Date

​Related Pages

Create Pairings

User Review

Build docs developers (and LLMs) love

Accessing Date Conversations

Conversation Modal

Left Panel: User A

Right Panel: User B

Message Data Structure

System Messages

Monitoring Active Dates

Date Card Information

Key Metrics to Monitor

Identifying Issues

Stalled Scheduling

One-Sided Conversation

Inappropriate Content

Ending Dates

Date Lifecycle Monitoring

Stage 1: Scheduling (0-48 hours)

Stage 2: Pre-Date Conversation (1-7 days)

Stage 3: Post-Date (After scheduled time)

User Actions During Active Dates

Ban User in Active Date

Delete User in Active Date

Monitoring Best Practices

API Reference

Fetch Date Messages

Fetch All Active Dates

End Date

Related Pages