Manage outgoing, incoming, and internal correspondence from one official channel
Receive the letter, register it, route it to the right division, run it through the approvals, then send the reply to the external party from your organization's official email and under your organization's identity. Every correspondence item, number, attachment, reply, and status stays in one searchable, trackable chain.
No sprawling email threads, no official copy lost among folders, and no repeated question about the last action on a transaction.
What is an administrative correspondence system?
An administrative correspondence system is a solution for managing outgoing, incoming, and internal letters across their whole lifecycle: from registration, numbering, and routing, through review and approval, to sending, reply, and archiving. Mstnd links a correspondence item to documents, tasks, workflows, external parties, and the action log, and lets you use your organization's official email when sending externally.
A supplier's letter lands in an employee's inbox, they forward it to Procurement, then the reply is created in a separate file and sent from another email. Later it's hard to prove the receipt date, the party that handled it, the approved copy, and whether the external reply is linked to the original letter.
Mstnd registers the incoming letter, extracts its data, and numbers it, then routes it to the right division and links it to tasks and approvals. The outgoing reply is created from the same context, sent from the organization's official email and under the organization's identity, and the external party's reply returns to the same correspondence chain.
A connected record of outgoing, incoming, attachments, and replies — searchable, with a provable path from receipt to closure.
Email carries the message, but it doesn't manage the transaction
When letters are run through email and separate folders, copies multiply and the link between an incoming letter and its outgoing reply is lost. A correspondence item might reach an employee but not the right division, a letter might go out before approval is complete, or an external party's reply might sit in a personal inbox invisible to the rest of the team.
The problem here isn't sending the letter. The problem is proving its path: When did it arrive? Who received it? Where was it routed? Which copy was approved? Was the reply sent? And what correspondence is linked to it?
A complete correspondence cycle inside Mstnd
Register the incoming item and tie it to its origin
You can register the incoming letter manually or upload the original document. Mstnd uses OCR and AI to extract the text and fill in registration data such as the sending party, letter number, date, subject, and priority, then lets the employee review it before approval.
Route the correspondence to the right division
After registration, the correspondence is referred to the relevant organizational unit or owner, manually or by the active business rules. It appears to the division within its scope and can be linked to a task or an approval path so it doesn't stop at mere receipt.
Create the outgoing letter from a template or official editor
Create an outgoing letter, add the attachments, set the recipient, and link it to the earlier incoming item if there is one. The letter passes through the defined review-and-approval path before it's issued, then gets its official number per the approved numbering rules.
Send to the external party from your organization's official email
Mstnd lets you use your organization's official email as the sender address, so the message arrives from your approved email and domain instead of a generic system address. The email carries your organization's identity and the data you specify, with a secure link to view the letter and attachments without creating an account. The party can be enabled to reply or carry out the requested action, so their reply returns to the correspondence context inside Mstnd instead of staying in a separate inbox.
Keep the outgoing-and-incoming chain
You can link the outgoing reply to the incoming letter, and link a later reply to the same chain. This way the team sees the full exchange history instead of hunting for each message and copy separately.
Create internal correspondence between divisions
Internal correspondence uses similar logic for routing, tracking, and approval, but within the org structure. The sending and receiving division are known, and the reply and action stay documented inside the system.
Identity and security that authenticate the correspondence
- A unique outgoing or incoming number per your organization's template.
- An administrative label carrying the transaction data, party, date, and attachments.
- A QR code to verify the correspondence or the official reply when this feature is enabled.
- An official copy that can be saved and referred back to.
- A watermark and access settings for sensitive content.
- An encrypted external link with an OTP verification code or Nafath verification when needed.
- A log of statuses and actions from draft to closure and archiving.
A claim from a supplier reaches the Procurement division. An administrative-communications employee uploads it, records its number and date, then routes it to Procurement. A review task starts, and a reply is drafted that passes through Finance and then the approver. After approval, the letter is issued with an official number and sent to the external party. The supplier submits their reply through the secure link, so it appears within the same chain and the transaction status updates.
Frequently asked questions
Does Mstnd support outgoing, incoming, and internal correspondence?
Yes. The module covers incoming and outgoing correspondence and internal exchange between divisions, linking it to tasks, workflows, documents, and external parties.
Can an outgoing letter be linked to an earlier incoming one?
Yes. Correspondence can be linked to form a chain that shows the transaction's origin, its replies, attachments, and related statuses.
Does the external party need an account in Mstnd?
No. They can view, submit a reply, or carry out the allowed action through a secure link, according to the sharing and verification settings.
Can correspondence be sent from the organization's official email?
Yes. You can use your organization's official email as the sender address, so the correspondence arrives from your approved domain and identity, and replies return to the linked correspondence chain inside Mstnd.
Can you search inside uploaded letters?
Yes. OCR turns scanned letter content into searchable text, in addition to searching by number, party, subject, date, and metadata.
How is correspondence approved before it's sent?
You can tie a correspondence type to a workflow template that defines the reviewers, approvers, and step order, so it doesn't move to sending until the required path is complete.
Make every letter a manageable transaction, not an attachment lost in email.
Book a Mstnd correspondence demo