Transaction communication: keeping the conversation connected to the record

A business conversation is easier to understand when it is attached to the transaction it concerns. A question about an invoice, a revised delivery expectation or a supplier clarification can otherwise become detached from the document that gives it meaning.

The communication should identify the relevant document and the response needed. A message saying “Please check this” is less useful than a clear request explaining the issue, deadline and responsible recipient.

Communication in DNA

DNA's sales and purchase transaction detail views use a communication panel with the transaction reference and customer or supplier context. The panel includes email and WhatsApp-related flows, with real sending dependent on the configured connection and available recipient information.

The email composition flow can include a generated document link. Replies carry conversation references so that they can remain associated with the conversation being answered. A message connected to the correct record is more useful for later review than an unreferenced exchange.

Review the recipient and document

Contact information can be supplied from the transaction or related party data. That convenience does not establish that the selected recipient is appropriate for every message. The sender should confirm the intended person, document and content before sending.

The reviewed panel also has a preview mode that does not send a real reply. A preview acknowledgment is not evidence of delivery. In a real flow, a successful send response is still distinct from a recipient reading and accepting the message.

Channel-specific conditions

The WhatsApp reply flow checks its configured conversation window and redirects to a template flow when free-form replying is unavailable. It also handles missing numbers and unprovisioned connections. These are conditions of the implemented flow, not a promise that every message will be accepted by an external service.

A useful communication record explains what was requested, which transaction it concerned and what response followed. Sending an invoice link does not itself approve the invoice, collect payment or settle a commercial dispute. Those outcomes require their own records and evidence.