A full correspondence register inside Odoo — with approval workflows you design yourself, automatic document reading in Arabic and English, and AI that summarizes, classifies and drafts the reply. Your team approves.
An incoming letter arrives by email or on paper, gets logged in a book or a spreadsheet, then is forwarded internally. Two weeks later nobody knows: was it answered? who approved it? where is the signed copy? And when an auditor asks for the full history of one specific letter, the search through inboxes and drawers begins.
The problem is not the absence of a system; it is that the register is separate from the approval, the approval separate from the document, and the document separate from the audit trail. The correspondence system we built brings them into one record inside Odoo.
Each letter is one record carrying its sequence number, direction, parties, classification, priority, responsible department, due date, attachments, and a complete audit trail. Records appear in a Kanban board by direction, with overdue items highlighted.
No single approval flow fits every organization, so workflows are designed from the interface: create an approval type, add its stages in order, and set for each stage the approver (user or group), which stage starts the flow, which ends it, and which allows rejection.
A real example from the system: an “Outgoing Document Review” flow that starts with a QC check, moves to technical manager review, then to “Finalized & Ready to Send” as the final stage, with a rejection path from the review stage. Every transition is written to the audit trail with the approver's name and timestamp.
Incoming documents are read by OCR supporting Arabic and English, then analyzed by AI which returns a content summary, a type classification, a priority level, the suggested handling department, whether a reply is required, and a suggested response time — each with a confidence score.
For replies, the system drafts a response based on the letter's content and the file's context, presented to you for review and editing before approval. Nothing is sent automatically.
On dispatch, the system produces an official transmittal frozen with its content and attachments, carrying a digital fingerprint that proves it was not altered afterwards. Electronic signature on outgoing documents is supported.
External parties get their own portal: they view correspondence addressed to them and upload their replies and attachments, without any access to your internal system.
A dashboard covering incoming and outgoing volumes, average response time, overdue correspondence, and distribution by department and classification. Fine-grained multi-company permissions define who sees what and who approves what — with meetings and minutes linked to correspondence.
Yes. Interface, classifications, reports and printed documents in Arabic with full right-to-left support, and OCR reading that supports both Arabic and English.
That is your decision. AI models can run locally inside your environment with no data leaving it, or through a provider if your policy allows. We settle this in the discovery session, before implementation.
Yes. Workflows are designed from the interface and need no code changes — add a stage or change an approver whenever you need to.
Yes. A designated mailbox can automatically create incoming correspondence from arriving messages, including their attachments.
Tell us about your business and what you want to improve. We reply within one business day — in Arabic or English — with a clear next step.