Find a practical answer.

Enter an email address you can access in the secure Contact form. The website requests a six-digit code for that address. Keep the contact page open and check your inbox. The code lasts ten minutes. It is for this enquiry process only; it does not activate an Epistles customer account or verify your identity for another service.

Enter all six digits without adding spaces or extra characters. After successful verification, the enquiry fields appear. Choose the closest topic, add your name, give the request a descriptive subject and explain the outcome you need. Your organisation name is optional. The verified enquiry access lasts thirty minutes; if it expires, verify again before trying to send.

You do not need to include the contents of your private correspondence to ask about the product. A general description is usually enough for the first conversation. For example, explain that your team needs to organise customer replies and approval stages, rather than pasting a customer's personal letter. The form does not accept document attachments. Use the privacy and data rights topic for a privacy request.

When a submission is accepted, retain the displayed reference. An acknowledgement is also requested for your verified email address. If the page reports a temporary problem, follow that message or use the telephone and registered-office details in the footer. Do not send the verification code to a member of staff or enter it on another website.

Check that the address you entered is correct and inspect your Junk or Spam folder. Some workplace mail systems quarantine automated messages before they reach the inbox, so your organisation's mail administrator may be able to help. Avoid repeatedly requesting codes in a short period: the contact service limits requests to protect genuine users and the mail system.

The code expires ten minutes after it is issued. If it is no longer valid, use the option to start again and request a new one. Use the code associated with the current verification request; a code from an earlier attempt may no longer match. Keep the same browser session open while you complete the enquiry. Clearing site data or moving to another browser can disconnect the verification steps.

If a valid code is repeatedly rejected, check that you entered exactly six digits. The service also limits incorrect attempts. Wait before starting a new request when the page reports too many attempts. Neither the contact form nor a member of the team needs your mailbox password.

Email availability and filtering are controlled by several systems, so the website does not promise immediate inbox delivery. If verification remains unavailable, contact the team by telephone or write to the registered office shown in the footer. Explain the approximate time of the problem and the stage that failed. Do not include a live verification code, a screenshot containing private inbox contents or unrelated personal information.

Open the Templates library and choose the example closest to your purpose. Expand its preview before using it. The brackets identify information you must replace, such as names, dates, addresses and references. Read the guidance above the example as well as the letter itself. An example may contain optional lines that should be removed when they do not apply.

Copy the text into your preferred document editor or use the text-file download. Downloads contain plain text so they can be opened without an Epistles account. Applying your own letterhead and formatting does not change the need to check the content. Keep the subject specific and explain the action you are asking the recipient to take.

The copy button uses your browser's clipboard facility. If the browser does not allow it, select the text in the preview and copy it using your usual keyboard or device controls. Download is also available as a separate link. You can still read the previews and use the download links when JavaScript is unavailable.

These templates are general writing examples. They are not a substitute for a specialist document, an organisation's required form or professional advice where a matter needs it. Before sending, search for any remaining brackets, check the recipient and compare the enclosure list with the actual attachments. Save the final version separately from your working draft. Downloading an example does not send a letter or open a customer account.

Start with the actual document. Record the date shown on the letter separately from the date you received it; those dates may differ. Add the sender, subject and any reference printed by the sender. Use a short title that will still make sense several months later, such as 'Insurance renewal question — October' rather than 'scan final 2'.

Keep the envelope when its markings or arrival details are relevant to your own records. If you scan a letter, check that all pages are present, the orientation is correct and the text can be read. Do not assume that a scan is complete simply because the first page looks clear. Note any missing page instead of silently treating an incomplete copy as the original.

Group related replies, enclosures and notes under the same matter. Record the next action separately from the document title: who needs to respond, what they need to do and the date you will review progress. An action reminder is easier to manage than adding 'URGENT' to several file names. If nothing is required, say that the item is for information.

These record-keeping steps can be used with your existing tools. Customer accounts and private uploads are available in the separate client workspace at my.epistles.uk. Do not send private letter contents through the general contact form. Read the Resources guide for a worked example of organising an exchange from the first letter to closure.

A document status should describe an event that can be supported. 'Draft' means the text is still being prepared. 'Final' identifies the version approved for the intended use. Neither label means that an email was sent or a paper letter was handed to a carrier. Keep preparation status separate from delivery status.

'Submitted' means that a request was passed to a service for processing. 'Dispatched' indicates the relevant handover or sending event. 'Delivered' should be used only in the context of the evidence reported by the delivery provider. A status must identify whether it refers to email or post; the same letter can have different outcomes on each route.

An email provider accepting a message does not establish that the recipient read it. A paper letter being printed does not establish carrier handover. If one route fails, record that event rather than replacing the entire correspondence history with a single success or failure label. Keep the timestamp and source beside the status so someone reviewing it later can understand what the event describes.

Epistles does not currently offer a postal checkout or live tracking service on this public website. For an item sent through another provider, use that provider's official tracking and support routes. The Resources section explains how to keep a separate record of the document, the delivery instruction and subsequent provider events without claiming more than the evidence shows.

Read the visible destination before following a QR link, and check the address shown in your browser after it opens. A familiar logo, an image of a padlock or a reference printed on paper is not by itself an independent check of the sender. Contact an organisation through a route you already trust if a letter asks for an unexpected payment, credential or urgent action.

The Epistles verification service recognises a finalised record through its complete QR link on my.epistles.uk. It shows the reference, finalisation time, fingerprint and revocation status. You can compare the exact PDF bytes without exposing the letter content. The public Verify page explains the scope of these checks. Do not upload a private document to a page merely because it says it can check a letter.

A digital file fingerprint concerns the exact bytes of a file. It does not independently prove who wrote a statement, whether its contents are correct or what happened to a printed copy. A QR link and a delivery event also answer different questions. Treat a claim of recognised document evidence separately from a claim that a recipient received or read it.

You can raise a general verification question through the secure Contact form without attaching the letter. Give the broad concern and a non-sensitive reference where appropriate. Do not include passwords, banking credentials or identity documents. If the enquiry concerns another organisation, use its independently established contact process to check its instructions.

Public pricing is currently handled by enquiry. Choose Personal, Business or Enterprise on the Pricing page to see the information that will help the team understand your requirements. No subscription, postal order or paid upgrade is purchased from the public website, and sending an enquiry does not activate an account.

For personal use, describe the kinds of records you want to organise and any occasional sending needs. For a business, useful details include the number of people who will work with correspondence, the approximate volume, approval responsibilities and whether several departments or organisations are involved. Give estimates where exact numbers are not yet available.

Printing and postage are different from ongoing software access. If you want to discuss postal services, explain the destinations, expected page counts, print requirements and the sort of delivery information you need. The team can identify which points require further confirmation before presenting a commercial proposal. Do not assume that a plan name includes postage, unlimited storage or a particular carrier service.

Create an account at my.epistles.uk and verify your email address to open your workspace. The public platform illustration is an explanation of the intended workflow, not a sign-in screen. Use the Contact form for questions about access, a business proposal or an integration discussion. Do not enter existing passwords into a preview or send them with an enquiry.

Use the privacy and data rights topic on the Contact form to explain a request about information handled by Epistles. Identify the interaction concerned, such as a website enquiry, and describe what you need. A paid account is not required to ask a privacy question. You can also use the telephone or registered-office details in the footer.

Provide enough information to locate the relevant interaction, but do not send identity documents or large collections of private correspondence in the first message. The team can explain any verification needed through an appropriate route. An enquiry reference can help connect a follow-up to the original request without repeating all of its contents.

The Privacy page identifies the operator and explains the public website's enquiry and measurement functions. The linked Britixo policy provides further information about rights, retention criteria and complaints. ICO registration details in the footer relate to the organisation's data-protection registration; they do not certify a particular software feature or document.

For an accessibility problem, describe the page address, the action you were trying to complete and what prevented it. If you can, include the browser or assistive technology involved. You do not need to disclose a medical condition to report a barrier. Tell the team which contact method or alternative format would help you. Keep private letter contents out of the report.