Client sends become part of the system record.
Email Software
Submission history that makes client sending inspectable.
Omelion records what was sent, when it was sent, who received it, and what format was used so delivery teams can work from actual submission history instead of memory.
What It Covers
Submission History
Track candidate submissions across recipients, jobs, file formats, secure links, duplicate warnings, and timestamps so every send can be reviewed later.
Trace every send
Submission activity stores candidate, job, recipient, and format data for each send.
Duplicate awareness
Recent-submission logic can warn teams before candidates are sent again too soon.
Format visibility
The platform keeps a record of whether formatted CVs, raw CVs, or secure links were used.
Operational Signals
How this page fits the wider operating model.
ReviewUsers can revisit what was sent before deciding to resend, backfill, or escalate.
ControlSubmission history supports operational accountability around client communication.
ContinuityThe send log connects mail activity to jobs, candidates, and delivery state.
Operational Depth
The detail behind this function.
These are the product capabilities that make this part of Omelion feel operationally serious instead of generic.
Duplicate-send windows make the workflow safer for busy teams.
Submission history stays attached to the operating context that created it.
Teams can answer questions about who received which candidates and when.
Next Step
Review how submission history fits your recruitment operating model.
Omelion is built for agencies that want their commercial process, delivery work, submissions, portal visibility, and governance connected in one system.