Text Message Behavioral Metrics: What Textimony Quantifies

The short answer

Text message behavioral metrics describe counts, timing, direction, and defined patterns in a supplied conversation. Direct measurements count the parsed record; software candidates flag messages for a person to review. A candidate count is not a count of proven incidents. Each result needs its definition, denominator, date range, and source context. A metric is not a legal conclusion, clinical diagnosis, or safety plan. Category availability depends on the completed run, and each candidate should be checked against the message, surrounding context, participant direction, and available source fields.

A review framework—not a guaranteed output list

Who uses these metrics

Legal professionals can use source-linked metrics to triage large records, find issue windows, prepare authentication questions, and decide what needs deeper review. Therapists, clinicians, and advocates can use client-supplied records as structured context while keeping clinical judgment, mandated reporting, and safety planning separate from Textimony output. Consumers and survivors can use metrics to organize what happened, preserve context, and create review packets for counsel, advocacy, mediation, or personal records. Parents and co-parents can separate custody-interference records from general relationship conflict so parenting-time, exchange, school, medical, and communication issues stay visible. Review teams can compare counts, severities, date ranges, participant roles, and confidence notes instead of arguing from memory or selected screenshots.

Why source-linked metrics beat vibe labels

A label such as “abusive,” “harassing,” or “interfering” can hide more than it explains. Useful review language identifies the exact words, date range, direction, candidate category, and surrounding messages while keeping the legal or clinical conclusion separate. Clear category language helps a reader understand what was observed, inspect the relevant messages, and see where software output stops and human judgment begins.

How Textimony calculates carefully

Validate one supported two-participant export before analysis begins. Normalize messages while retaining the source identifiers, timestamps, sender labels, and text the export actually supplies. Keep direct counts, rule candidates, model candidates, and reviewer decisions separate. Use candidate records and selected excerpts to return to source context; daily chart points remain aggregates rather than citations. Keep uncertainty visible when sender identity, missing media, timezone, deleted content, or file conversion constraints affect interpretation. Separate observed message behavior from legal conclusions, diagnoses, admissibility opinions, and safety recommendations.

Denominators and scope keep rates honest

A candidate count has little meaning without its denominator and scope. State the total eligible messages, participant orientation, start and end dates, skipped or unknown rows, category definition, analyzer status, and whether the count comes from rules, models, or reviewer selections. A large raw count can arise inside an even larger history of ordinary logistics. A small count can still contain an important message. The denominator prevents one kind of misreading, but it does not decide relevance. The reviewer still needs the actual source text.

A reproducible calculation names its inputs

Direct counts should be reproducible from the same normalized messages, participant map, case timezone, date boundaries, and definition. If any of those inputs change, the number may also change. A chart is not independently reproducible when its input choices are hidden. Where a metric depends on an analytical choice—an inactivity window, a pairing rule, a minimum eligible message, or a candidate threshold—record that choice when the workflow exposes it. If the current report does not expose a parameter, do not claim that it does; describe the available run metadata and limitation instead.

Direction balance: who sent how much in this record?

A direction-balance ratio compares sent and received counts for two confirmed participant lanes. The numerator and denominator must be named, because message count, character count, and conversation turns measure different things. Unknown-direction rows should be visible rather than forced into one side. There is no universal healthy ratio and no fixed value that establishes harassment, withdrawal, or burden shifting. Some logistical threads are naturally one-sided; some records are incomplete. Compare periods under the same definition, then read the exchanges that produced the change. A ratio of 1.0 means equal values under the chosen formula. It says nothing by itself about relationship quality.

Response timing requires a pairing rule

Response latency is elapsed time between a message and a later reply under a defined pairing method. Consecutive messages from one person, unanswered messages, group records, missing timestamps, and conversations that continue by phone complicate that definition. Medians, ranges, or distributions can describe the observed timing more honestly than one average. A change may be worth reviewing, especially around a time-sensitive request, but it does not prove deliberate silence, emotional withdrawal, fear, or hyper-reactivity. State the case timezone and source timestamp precision. Define which message is paired with which reply. Keep unanswered and unknown-direction messages visible. Compare like periods under the same method. Read the message content before assigning significance to elapsed time.

Conversation density describes activity in a window

Conversation density is message or character volume divided by a stated interval. Hourly, daily, and episode-based windows answer different questions. Textimony’s current topography uses completed-run daily aggregates under the frozen case timezone; it should not be described as a universal hourly density analyzer. A dense period can reflect an argument, live event, emergency, travel planning, technical troubleshooting, or ordinary back-and-forth. No fixed number of messages proves flooding or identifies the moment a relationship entered crisis. Use density to select a period, then read it.

Topic persistence is a review concept, not a motive

Topic persistence describes how many consecutive turns remain on a defined subject under a stated coding method. Topic boundaries are interpretive: one message can address several subjects, and two reviewers may reasonably code a transition differently. Textimony does not claim that its current workflow calculates an exact, verified number of semantic loops or proves that a person refused to let a subject go. Search and candidate lanes can help a reviewer locate recurring language; the reviewer should document the topic definition and examples used.

De-escalation language must be read with what follows

Words such as “I’m sorry,” “let’s pause,” or “can we return to the schedule?” may be de-escalation language. Their function depends on surrounding text. An apology can be sincere, strategic, partial, rejected, accepted, or followed by renewed disagreement; the message alone may not resolve that question. Configured rules can surface apology or repair-language candidates. Textimony does not certify good faith, co-parenting capacity, or whether another person accepted a repair. A reviewer can quote the language, describe the next messages, and leave motive to the appropriate factfinder. Document the words and sequence. Do not convert politeness into a character judgment or custody recommendation.

Repeated shapes in a timeline need manual comparison

Several periods may show a similar sequence: ordinary logistics, more messages, candidate language, and then less activity. A daily chart can help a reviewer notice those shapes, but visual similarity does not prove the same cause or a predictable relationship cycle. Textimony does not infer that a repeated shape was designed to maintain volatility. Compare the underlying messages, participants, dates, external events, and source completeness. If the periods differ, preserve those differences rather than forcing them into one story.

A no-reply period is an observation with many explanations

A no-reply period means the supplied record shows no qualifying reply during a stated interval. The conversation may have ended, moved to another channel, resumed outside the date range, or been affected by missing records. “Conversation collapse” should not be treated as a clinical or causal fact. When silence follows a candidate threat or financial message, chronology can be documented without claiming the first caused the second. Textimony cannot prove psychological impact or establish the elements required for a protective order. Those questions require the full facts and applicable law.

What behavioral metrics can Textimony quantify in text messages?

It reports message and daily-direction counts, and can surface rule or model candidates across several review categories where those are configured and the run completed. The caveat matters more than the list: a candidate count is a count of messages the software flagged for a person to read, not a count of proven incidents. Which categories are available depends on the completed run.

Is a behavioral metric the same as legal proof?

No. A metric counts something observable — how often, at what hour, in which direction — and counting is not proving. It cannot reach intent, credibility, or whether conduct meets a legal standard, and a high count may have an innocent explanation the messages do not contain. Metrics are useful because they make a long record navigable and give a reviewer somewhere to look, not because they establish anything by themselves.

Can therapists use Textimony behavioral metrics?

They can use client-supplied records as context, which is often more reliable than reconstructing a timeline from memory in session. What the metrics cannot do is diagnose, assess risk, or substitute for clinical judgment — they describe message patterns, not people. Therapy, diagnosis, crisis response, and any decision that follows from them stay with the professional and their own standards of practice.

Why not just use screenshots?

Because a screenshot captures a moment and these metrics describe a pattern over time. Repetition, timing, direction balance, and escalation are only visible across the whole record, and the screenshots people keep are by definition the ones that stood out — which makes them the least representative sample available. Metrics computed from a curated selection mostly measure the selection.

Published by

Textimony. Editorial status: Source-linked informational guide. Updated: 2026-10-23.

Sources

CDC NISVS FAQ: forms of intimate partner violence measured; CDC: Stalking and intimate partner violence; Technology-Facilitated Abuse in Intimate Relationships; Federal Rule of Evidence 901; Federal Rule of Evidence 106; Federal Rule of Evidence 1006; Federal Rule of Evidence 902; NIST: Guidelines on Mobile Device Forensics; SWGDE: Digital evidence standards and guidance