Use Order Story to keep the transaction together

A signing can generate a surprising amount of communication.

Instructions change. Documents arrive. Someone asks a question. A signer calls. Scans are requested. An appointment is rescheduled. Shipping information is added.

**Order Story** gives that activity a home inside the transaction it belongs to.

### Keep context with the order

Use Order Story for communications, notes, and activity that help explain what happened during the life of the transaction.

Instead of relying on your memory or searching through unrelated messages later, important context can remain connected to the order.

### Build a useful history

A useful Order Story should help you understand the transaction when you return to it later.

Record information that matters to the order rather than treating the Story as a place to duplicate every field already stored elsewhere.

The goal is context.

If something happened that would help explain the order later, Order Story is where that history belongs.

### Control who should see information

Not every piece of transaction information belongs in front of every participant.

When visibility options are available, choose the audience appropriate for the communication or information you're adding.

Information intended only for your own business records should remain private rather than being shared simply because other participants have access to parts of the transaction.

### A completed order still has a story

Order Story remains useful after the signing is finished.

If a payment question, document issue, client concern, or other question comes up later, the transaction history can help you reconstruct what happened without starting from scratch.

An order records the transaction.

Order Story records the context that makes the transaction understandable.