Sample Report

See exactly what ChatMend reveals

This is a complete, anonymized analysis of a fictional conversation. Real reports follow this same structure, built entirely from the messages you provide.

🔒

Fictional example. No real person or conversation is shown here. When you run your own analysis, the conversation text is processed to generate your report and isn't retained afterward — saved results live in your account, and you can delete them anytime.

Participants
Alex & Jordan
Relationship
Romantic partner
Messages
847
Span
6 weeks
At a Glance

The whole report, in one card

Before the detail, ChatMend distills the dynamic into a single snapshot: the dominant pattern, how confident the read is, the evidence behind it, and whether repair is actually happening.

  • One headline pattern, not a wall of scores
  • A confidence level you can trust or question
  • Evidence pulled straight from the messages
ChatMend Report
847 messages

Relationship Pattern

Anxious–avoidant loop

B−HEALTH
Pattern confidence78%

Evidence

Jordan

Been super busy, we’ll figure out a time.

Alex

Did I do something? You’ve been quiet all week.

Repair capacity

Attempts after conflict

Moderate
B-

Relationship Health

Emotional tone: Warm but uncertainState: Connected, with a recurring strain

This conversation shows strong connection and genuine emotional interest, alongside repeated ambiguity after vulnerable moments. The core issue is not a lack of care — it is inconsistency in the moments right after emotional closeness.

Attachment Signals

How each person tends to connect

Presented as signals, not diagnoses. These are tendencies the conversation suggests — not fixed labels.

AlexAnxious-leaning signals

Seeks reassurance after silences and escalates emotional bids when responses slow down.

Strengths
+Names feelings directly and invites repair
+Initiates reconnection after conflict
Watch for
!Reads delayed replies as withdrawal of care
!Sends rapid follow-up messages when anxious
JordanAvoidant-leaning signals

Creates distance after emotionally intense or vulnerable exchanges, then re-engages warmly later.

Strengths
+Returns and re-engages rather than disappearing
+Communicates clearly about logistics and plans
Watch for
!Goes quiet when conversations turn vulnerable
!Rarely names the reason for pulling back
Attachment Map
SecureAnxiousAvoidantFearful
Alex
Jordan
The Core Pattern

A pursue-withdraw cycle around closeness

Secure

Low anxiety · low avoidance

Anxious

High anxiety · low avoidance

Avoidant

Low anxiety · high avoidance

Fearful / Disorganized

High anxiety · high avoidance

pursue–withdraw cycle
A
J
AVOIDANCE →

Plotted across anxiety and avoidance, the two people sit in different corners. Alex leans anxious — moving toward connection under stress. Jordan leans avoidant — moving away to manage overwhelm. The dashed line is the loop that forms between them.

AlexHigh anxiety, low avoidance
JordanLower anxiety, high avoidance
The cycle, stage by stage

Vulnerable message

Alex

Delay / withdrawal

Jordan

Reassurance seeking

Alex

Conflict

Both

Repair attempt

Jordan
1
Closeness

A vulnerable or emotionally warm message is shared.

2
Withdrawal

Jordan goes quiet for several hours without explaining why.

3
Pursuit

Alex follows up for reassurance, then repair happens the next day.

The cycle is not driven by lack of interest. It is a timing mismatch: one person moves toward connection under stress, the other moves away. Naming the rhythm is usually more useful than assigning fault.

Pattern Evidence

Every finding links to the messages

No vague interpretations. Each signal points to what actually happened in the thread.

Inconsistency after closeness

Pattern observed

Withdrawal following emotionally vulnerable messages, then warm re-engagement a day later.

Why we think this

The delay consistently follows disclosure — not logistics — and warmth returns without repair being requested.

Evidence

Alex

I felt really close to you last night.

Jordan

(next reply 4h 12m later) Sorry, crazy day — how are you?

Alternative explanation

Genuine external stress could explain some delays. ChatMend weighs this, but the timing tied to disclosure keeps confidence moderate rather than low.

Confidence
Moderate
Pursue-withdraw cycle

Consistent 3-5 hour response delays following vulnerability-based messages, paired with warm re-engagement the next day. This pattern appeared 12 times across the conversation.

Reassurance-seeking

After a delayed reply, Alex sent 2-4 follow-up messages within an hour (“did I say something?” / “it’s fine, ignore me”) in 9 of 12 instances.

Repair is present

In 8 of 12 cycles the connection returned to warmth within 24 hours, usually initiated by Alex and accepted by Jordan. Repair happens — it is just slow and one-sided.

What To Watch
Asymmetric repair loadMedium

Reconnection after distance is initiated almost entirely by one person. Over time this can build quiet resentment and burnout.

Unspoken withdrawalMedium

Distance is rarely explained, so the other person fills the silence with worst-case interpretations.

Escalating reassurance loopsLow

Rapid follow-up messages during anxiety can increase the very distance they are trying to close.

What's Working
Both people consistently return to the relationship after friction.
Affection and warmth are expressed openly and often.
No contempt, stonewalling-to-punish, or hostile language detected.
Repair attempts are accepted, not rejected.
How It Changed Over Time

The pattern formed gradually

Weeks 1-2
Warm

High message frequency, fast replies on both sides, lots of playful and affectionate exchanges. Secure-looking baseline.

Weeks 3-4
Shifting

First vulnerable conversations appear. The first response delays follow, and the pursue-withdraw rhythm begins to form.

Weeks 5-6
Patterned

The cycle is now recognizable and repeating. Warmth remains, but the timing of distance is predictable around emotional closeness.

What To Do Next

Grounded steps, not generic advice

Suggestions are tailored to the actual pattern in this conversation.

01

Name the pattern without blame

Describe the timing, not the character. The goal is a shared observation, not an accusation.

02

Make repair a two-way habit

If one person always initiates reconnection, agree on a small signal the other can use to reach back first.

03

Reduce the reassurance loop

When a reply is slow, one clear message lands better than several. Distance often eases when the bid is calm.

A way to open the conversation

I’ve noticed that when I share something personal, you sometimes go quiet for a while, and I start to worry. I’d like to understand what happens for you in those moments — not to fix it, just to get it.

This opens dialogue without blame — an invitation to understand, not a verdict.

ChatMend organizes patterns and language to support reflection and therapy preparation. It does not diagnose and is not a replacement for a licensed professional. AI analysis can be wrong and cannot see the full context of your relationship.

Run this on your own conversation

Paste a thread or upload a file. You will get a report like this one — built only from your messages.