Does a message identify who wrote it?¶

Not automatically. A message record usually identifies a sending account, number, device or service identity. Personal authorship requires evidence connecting the relevant event and access route to the person who typed, dictated, selected or caused it to be sent.

Start with the technical sender¶

Preserve the service, stable account and message IDs, thread, time, application, session and device records. A displayed name may be a local contact label or chosen profile, while the message might come through a linked computer, shared workplace account, compromised session, bot or scheduled process.

Also establish whether the content is original, forwarded, quoted, copied or generated by another application.

Build the authorship bridge¶

Compare who controlled the sending device and session with account login, linked-device and local artefacts. Add contemporaneous communications, location or access records, photographs, knowledge within the text, conduct and admissions where relevant.

Language and style can support a wider conclusion but are rarely unique. Later possession of a device does not prove its user at the message time.

Report the proven layer first: the service recorded the message from the identified account or device. Name the author only where independent technical and contextual evidence justifies that additional step.