What belongs in an email or SMS follow-up record?
A useful communication record connects the exact message to its sender, destination, permission evidence, and subsequent outcome. A current template or a “sent” badge cannot answer all of those questions by itself.
Reviewed
Keep what was actually sent
Templates change. Sender signatures change. A prospect’s email address can change. When reviewing an old communication, the team needs the rendered message and details that applied to that communication, not a reconstruction from today’s settings.
Baton’s shared communication process records the canonical message and its content digest before provider transport. Verified sender details and applicable footer content are resolved for that message. Later changes should not rewrite the historical communication.
- Exact message content and channel
- Sender and destination used for that message
- The relevant consent decision and evidence
- Timestamps and the provider’s reported outcomes
Treat permission as channel and destination specific
A form containing a phone number does not by itself demonstrate permission to text. Email and SMS need separate evidence, and permission associated with an old address should not silently transfer when a destination changes.
In Baton, consent history is append-only: a later opt-out becomes another event. The practical benefit is that a reviewer can follow what changed rather than seeing only a current yes-or-no field. When evaluating software, ask to see the original submission, the applicable destination, and a subsequent opt-out in one example.
Preserve failures and distinguish engagement from intent
A failed send still explains what the team attempted and why the prospect may not have received it. Provider acceptance, delivery, failures, and retries should remain visible as outcomes rather than replacing the original message.
An email open or link click is provider-recorded activity. Privacy tools and security scanners can generate it, and blocked images can hide an open. A clicked unsubscribe link also does not establish that an opt-out was completed. Records and reporting should describe the observed event accurately.
Understand the optional protected archive
Every Baton Runner workspace keeps an append-only communication history and provider outcomes. Optional managed archiving adds protected copies in a dedicated firm archive, a secondary compliance-inbox copy, integrity checks, and retained-record exports. Its configured retention has a six-year minimum. New protected copies use S3 Object Lock in Governance mode: ordinary application credentials cannot delete them or shorten retention, but a separately authorized administrator can override that protection. This is not an unbypassable retention guarantee or a promise that software alone satisfies a firm’s obligations.
A content digest can help detect a changed record, but it is not an Object Lock policy. Ask to see the configured archive branch, how failures affect sending, and how an authorized user retrieves retained records. In Baton’s managed-archive mode, required archive steps must succeed before provider transport.
Evaluate the whole retrieval process
Run a practical demonstration with a successful message, a failed delivery, and an opt-out. Ask the people who will use the records to locate the relevant evidence and explain it. Confirm which roles can access records and what an export contains.
Another dedicated archive or an existing CRM-connected archive may fit better if your main need is preserving communications across a wider set of business systems. Baton focuses on the communications passing through its follow-up workflow; do not assume it captures every mailbox or outside channel. Your firm should determine its own retention and review requirements with its responsible advisers.