Discuss access
For individuals organising important personal correspondence.
What to tell us
- Kinds of letters and records
- Expected storage and retrieval needs
- Any occasional sending requirements
Pricing is currently provided by enquiry. Tell us whether you need personal correspondence, a shared business workflow or enterprise integration, and we will discuss the requirements before a proposal.
Client workspace available · Postal services quoted separatelyEnquiry-based pricing · Paid services quoted separately
For individuals organising important personal correspondence.
For teams managing shared correspondence, reviews and follow-up.
For complex organisations, multiple entities and connected systems.
Tell us about printing, page counts, destinations and delivery requirements where they apply. A proposal must identify the scope and any implementation, custom-work or provider charges. No postage allowance or unlimited usage is implied by these enquiry categories.
Explore the postal workflow →Epistles currently uses enquiry-based pricing. Tell the team whether you are considering personal correspondence, a shared business workflow or a wider enterprise requirement. The purpose of the first conversation is to understand the service you need and the questions that must be resolved before a proposal can be made. The public website does not take a subscription payment or activate a paid plan.
You do not need a detailed specification to start. A description of the current process, the people involved and the most important improvement is useful. Estimates of volume or storage are welcome where exact figures are not yet known. The team can then identify which assumptions require confirmation.
For personal use, explain the types of letters you would like to organise and how often you expect to add or retrieve them. You might be looking for a clearer record of household correspondence, a way to connect related replies, or occasional help with preparing an outgoing letter. These needs differ from a multi-user business workflow.
If postal sending is relevant, mention it separately from document organisation. An occasional printed letter and a continuing correspondence archive involve different costs and operating arrangements. No postage allowance, storage limit or recurring rate should be assumed from the public examples. Your enquiry is an opportunity to discuss those details before choosing a service.
For a business proposal, describe the number of people who prepare, review or manage correspondence. Explain whether letters belong to individual staff, a department, a customer account or several separate organisations. Those relationships influence permissions, shared folders, reporting and approval responsibilities.
Approximate monthly letter volumes and the balance between incoming records and outgoing communication help explain the work involved. If you already use another system, identify it and describe the information you want to exchange. A list of systems is less useful than a short description of what should happen when a record is created, approved or updated.
Physical delivery needs to be discussed separately from software access. Relevant variables include destination, page count, print format, enclosures, envelope requirements and the delivery service being considered. Tell the team which of these are predictable and which vary from letter to letter.
Provider charges, implementation, custom development and other work need an explicit commercial scope where they apply. A proposal should identify what is included and what remains subject to confirmation. This public page does not advertise a carrier rate, a dispatch cut-off, an unlimited allowance or a guaranteed delivery outcome. There is no postal checkout to complete here.
A larger organisation may need more than a standard workspace discussion. Multiple entities, staff permissions, approval stages, retention needs and links to existing systems can affect delivery scope. Explain the stakeholders who need to approve the approach and any important rollout dependencies.
If migration is involved, describe the types of records and approximate scale without sending the records themselves through the enquiry form. A first proposal can identify discovery, data preparation, configuration, testing and training work that needs to be agreed. Production credentials, private documents and customer exports belong in an authorised implementation process rather than an initial pricing message.
Choose the enquiry route closest to your requirements, verify your email and send a concise description. Include the outcome you need, approximate scale, existing tools and any important timing constraint. You will receive an enquiry reference when the submission is accepted. Keep it for follow-up and let the team know if a material assumption changes.
Sending an enquiry does not place an order, reserve capacity or commit you to a subscription. The client workspace is available at my.epistles.uk. Paid services and postal fulfilment require an agreed quotation and provider configuration. Use the public guides and templates to explore your workflow and discuss commercial scope with Epistles.
Practical information about this page and the public Epistles service.
No. Pricing is currently provided by enquiry, and no payment is taken by this pricing page.
No inclusion or allowance is implied. Discuss printing and postage separately so the proposal can identify the applicable scope and charges.
No. It starts a conversation about your requirements.
Yes. Describe the system, approximate scale and intended workflow without sending credentials or a customer-data export.
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.
Tell us what you need, who is involved and the outcome you want to achieve. We will discuss the right next step.