EMAIL & POST

One letter, two clearly recorded journeys.

A physical letter and an email copy can be useful together, particularly when a recipient needs the same document in more than one format. Epistles is planning a workflow in which the finalised letter is identified once, while the email and postal journeys are recorded separately. This makes the correspondence easier to follow without losing important differences between delivery channels.

Client workspace available · Postal services quoted separately
EPISTLES / EMAIL & POST
E.
Documented. Organised. Understood.✳
PRACTICAL GUIDANCE

The correspondence workflow in practice.

An email provider may accept an outgoing message but return a bounce later. A postal order may be printed while still awaiting carrier handover. Customers should see both states clearly, with the date and source of every available update.

Operational emails also need responsible sending controls: authenticated domains, sensible rate limits, privacy-aware document delivery and clear separation from marketing campaigns. Sensitive material may need protected links rather than ordinary unencrypted attachments.

01 / 03

An example: an electronic copy and a paper original

A business may want an email copy to accompany a physical letter. The two routes should refer to the intended final document, but their recipient details and outcomes may differ. Check whether email delivery is appropriate for the particular correspondence and use the contact information authorised for that purpose.

Describe how you want to handle an email bounce, an address correction or a recipient asking for another copy. Decide whether the email should carry an attachment or use an appropriately controlled access route when that option is provided. These choices affect the experience and the records needed for support. Epistles' public website does not currently send customer letters. Use this page to plan the proposed email workflow and the separate postal events that need to remain visible beside it.

02 / 03

An electronic copy that is part of the same record

Where the recipient's email address is available and email delivery is appropriate, Epistles should be able to send an authorised electronic copy of the issued letter. The message, finalised document version, recipient, dispatch reference and relevant delivery events should be linked to the corresponding postal record. This avoids the familiar problem of having a paper record in one place and an unrelated email thread elsewhere.

Sensitive letters may need protected document links rather than ordinary attachments. Any delivery system must also handle invalid addresses, retries, bounce notifications and provider failures. Automatic operational notifications should not be confused with promotional marketing, and the sending domain must be properly authenticated before customer correspondence is enabled.

03 / 03

Postal progress and email progress are separate

Sending one letter by post and email creates two delivery journeys. An email service may accept a message without confirming that anyone opened it. A postal order can be paid for and printed before it is handed to a carrier, and carrier handover does not necessarily mean final delivery. Epistles should show these stages separately and record the source of each status.

The customer should be able to understand what is completed, what is still pending and what needs attention. If an email bounces but the postal letter is dispatched, the correspondence record should show both facts, not one misleading green tick. This level of clarity helps people decide whether to follow up, correct an address or retain supporting evidence.

GOOD TO KNOW

Questions worth asking.

Clear answers about the workflow and its limits. The service described is being developed; availability is confirmed only when a feature is launched and tested.

Can a letter go by post and email?

The proposed journey supports both when authorised and operationally available.

Does an email sent status mean it was read?

No. Submission, acceptance, bounce and any independently reported delivery events must be distinguished.

Can the email include the final PDF?

That is planned where appropriate; sensitive documents may instead use restricted access links.

What happens if the email fails?

The correspondence record should preserve the failure and allow an authorised corrective action.

Will the post and email share a reference?

They connect to one letter reference but retain distinct delivery identifiers and events.

Public resources are available now.

The client workspace, document records and QR verification are available at my.epistles.uk. Postal requests start with a quotation. Contact Epistles to discuss your requirements.

CONTACT EPISTLES

Bring us the correspondence task you want to improve.

Tell us what you need, who is involved and the outcome you want to achieve. We will discuss the right next step.