Use the secure enquiry form to ask about personal correspondence, business requirements, postal services or planned integrations. Start by verifying an email address you can access. Once verified, you can choose an enquiry type, add a subject and explain what you would like to achieve. An organisation name is optional. Your contact request does not create an Epistles customer account or place a postal order.
We keep the support mailbox out of public page content. The form sends accepted enquiries to the Epistles team through the server-side mail service and gives you a unique reference. Keep that reference for follow-up. An acknowledgement is also requested for your verified address; email-provider filtering or delivery delays can affect when it reaches your inbox. If the page reports a temporary delivery problem, use the telephone or postal contact information in the footer.
For a personal enquiry, describe the kind of correspondence you want to organise without including the contents of private letters. For a business enquiry, useful context includes the approximate team size, your existing process, any required approval stages and the outcome you need. For an integration discussion, name the system you would like to connect and describe the intended exchange of information. Do not include API credentials, passwords, access tokens or confidential customer records.
The verification code is valid for ten minutes. Check your spam folder if you cannot find the message. If it expires, start again to request a new code. A verified email session remains valid for thirty minutes, after which you will need to verify again. Verification establishes access to the email address for this enquiry; it is not an identity check or a customer-account activation. To exercise a privacy right, choose the privacy and data rights topic or contact Britixo using the telephone or registered-office details below. Describe the request first; the team can explain any additional information needed. Customer accounts, letter sending, billing and public document verification remain under development and are not activated by this form.
Help written for the question someone actually has
A helpful answer starts with the task. “How do I add a letter I received?”, “Can I keep attachments with it?” and “How will I know whether my letter was posted?” are more useful starting points than a long list of internal system names. Every guide should explain steps in plain language and show what information the system records.
Where the answer depends on a postal provider, a signature method or a future integration, the documentation must say so. Support articles should be reviewed when a feature changes, and obsolete instructions should be redirected or retired rather than remaining in search results indefinitely.
Useful for everyday life, not only offices
Important letters do not arrive only at work. People receive correspondence about housing, healthcare, utilities, education, insurance, banking and family matters. A personal workspace should let someone upload a received letter, add a date and subject, place it in the right folder and find it later without learning specialist records-management terminology.
The experience should feel calm and predictable. A customer who keeps ten letters should not be forced through an enterprise setup wizard. As needs grow, they can add reminders, group related correspondence into cases and arrange an outgoing letter. The value is a clearer record of what happened and what still needs attention.
Correspondence across a whole organisation
Teams face a different problem from individuals: several people may prepare, approve, send and respond to letters for the same customer or matter. A business workspace should make responsibilities visible without allowing unrestricted access to every document. It should support authorised shared folders, internal assignments, activity histories and consistent templates.
For a growing company, reliable references and organised records reduce unnecessary duplication. Staff can see whether a reply has already been sent, check the relevant version and understand which stage requires attention. Advanced integrations should use scoped credentials and preserve the same permission and audit rules as the web interface.
Pricing that is clear before someone commits
A subscription for managing correspondence and a one-off charge for printing and posting are different products. Epistles should show them separately, including any extra pages, paper choices, postage classes, enclosures and applicable taxes before a customer authorises an order. A price calculator must not invent prices if provider rates have not yet been agreed.
Individuals may prefer a simple personal plan or occasional transactions, while firms may need team seats, storage allowances and volume rates. The public website should explain the pricing model clearly even before final commercial figures are published. It should not display fictional savings or ambiguous “free” promises.
Keep external systems connected without losing control
Organisations may already use a CRM, ERP, accounting system or case-management platform. An integration should be able to create or retrieve authorised correspondence records without moving confidential data through uncontrolled channels. API keys need restricted scopes, event delivery must be verifiable, and automated requests should be idempotent so retries do not accidentally generate duplicate letters.
The external system may initiate an action, but Epistles should remain clear about which document was finalised and which delivery operations actually occurred. Webhooks and status updates should preserve event timestamps and sources. The interface should also make it possible for administrators to revoke a connection without affecting unrelated tenant data.
Privacy is part of the service, not an afterthought
Correspondence often contains sensitive personal, financial or business information. Access control, secure transport, protected storage and careful document sharing have to be designed into the workflow from the beginning. Individuals should see only their own records, while organisations should be able to grant carefully scoped access to colleagues.
Public QR verification, analytics and search indexing must not become shortcuts around those restrictions. Retention should reflect legitimate requirements rather than promising to keep everything forever. Customers need clear explanations of how records are stored, who can handle postal fulfilment and what happens when they request deletion or export.