What identifiers should be included in a messaging-provider request?¶

Include the most stable identifiers available for the account, communication and time period, together with the exact record types required. Display names and screenshots are useful context but unreliable search keys.

Identify the object and the event¶

Account identifiers can include provider user ID, username, registered telephone number or email and profile URL. Preserve historical values when a username or number may have changed, using a stable account ID to connect them where possible.

For activity within the account, supply relevant conversation, group, channel, participant, message, attachment and call identifiers. Device and session IDs can target access or linked-endpoint questions. Retain each value in its original form, including prefixes, country codes, punctuation and leading zeros.

Define scope in provider terms¶

State the date range and time zone, event types and whether the enquiry concerns registration, sessions, security changes, group membership, message events, calls or readable content. A precise, relevant scope helps the provider identify the right system and avoids unrelated material.

Ask for original records, time basis and field definitions where available. Raw records and summaries serve different evidential functions and should both retain their provenance.