Feature Spotlight

Matches Intelligence Dashboard

A central relationship CRM to manage match profiles, conversation history, extracted traits, and relationship stage progression in one place.

Try Matches Dashboard — Sign Up Free

What to Do When Trying to Keep Track of Multiple People You're Talking To

Modern dating often means conversing with several potential matches across different platforms like Hinge, Bumble, and Instagram. Keeping details straight—who works in tech, who has a dog named Barnaby, who is vegetarian, or who you agreed to meet for coffee—becomes confusing quickly.

The Matches Intelligence Dashboard serves as your private dating CRM. It unifies match profiles, extracted facts, conversation logs, and relationship stage tracking in one organized hub.

How the Matches Dashboard Works Step-by-Step

Step 1

Automatic Creation

Generating openers or running analyses auto-links or creates a match record in match_profiles.

Step 2

Fact Merging

Approved facts automatically merge into profile fields (occupation, city, food preferences, communication style).

Step 3

Stage Progression

Track progress from First Match to Date Planned, Active Dating, or Archived.

Match CRM Capabilities

Structured Profile Records: View basic info, contact details, social handles, and notes in one view.
Relationship Timeline: Log key milestone dates (matched on date, first message date, first meet date).
Personality & Behavioral Insights: Store identified attachment styles, communication pace, and love languages.
Match Profile Deletion: Permanently purge any match and its associated facts (DELETE /api/matches/:id) whenever a connection ends.

Why Purpose-Built Match Intelligence Beats Spreadsheets

Using manual notes or spreadsheets is tedious and disconnected from your tools. The Matches Dashboard is natively integrated with Cloudflare D1:

Every fact approved from Opener Engine or Chat Analysis updates your match record in real time, and selecting a match automatically feeds their stored preferences into the First Date Ideas Generator.

What the Matches Dashboard Doesn't Do

We believe in clear technical transparency:

It does not scrape private dating app messages or social media profiles without your input.
It does not automatically modify match records without user approval for extracted facts.
It is strictly private to your account ID and cannot be viewed by other users or matches.

Real Scenarios: When to Use the Matches Dashboard

Scenario 1: Sorting Matches by Relationship StageFilter connections by First Match, Date Planned, or Active Dating to focus texting effort on active conversations.

Scenario 2: Reviewing Chat Analysis History Before a CallClick into a match record to view past Ghosting Risk scores, red flag warnings, and attachment indicators before calling.

Scenario 3: Purging Stale Matches and DataWhen a connection ends, click Delete Match to execute `DELETE /api/matches/:id`, permanently purging the profile, queued facts, and analyses from D1 storage.

How This Compares to Alternatives

Notion or Excel Templates: General note apps require manual copy-pasting of every text detail and don't integrate with AI analysis tools.

Dating App Contacts: Dating app chat screens hide key details inside endless message threads. VibeMetricsAI organizes traits into structured D1 database cards (`match_profiles`) connected directly to date planning tools.

Frequently Asked Questions

How does data flow into the Matches Dashboard?

Extracted profile details from Opener Engine, Chat Analysis, and Vibe Check flow into an approval queue that updates your match CRM once approved.

Can I manually update match details?

Yes. You can edit basic info, contact details, social handles, relationship status, and personal notes directly inside each match profile.

Can I connect matches to date planning?

Yes. Matches stored in your dashboard can be selected directly inside the First Date Ideas Generator to build tailored date blueprints.

What tables store match profile records in the Cloudflare D1 database?

Match profile records are stored in dedicated database tables (match_profiles and match_extracted_facts), isolated strictly by user ID for data privacy.