Each role has an ownership and escalation path from creation onward.
Workflow & SLA Engine
Dispatch fallback makes unowned work visible before it becomes a delivery failure.
Omelion supports dispatch timing, fallback dispatchers, reminder hours, and escalation chains so new work does not stall silently in the handoff between creation and recruiter action.
What It Covers
Dispatch Fallback
Configure dispatcher ownership, reminder timing, fallback routing, and escalation behavior when roles are not accepted or progressed fast enough.
Dispatch ownership
Jobs store dispatch-owner context and rejection or resubmission state where needed.
Fallback routing
Teams can configure fallback dispatcher logic and timing for unclaimed or blocked work.
Reminder policy
Dispatch reminders and notify-on-create behavior make the handoff process more deliberate.
Operational Signals
How this page fits the wider operating model.
EscalationDispatch is a governed operating process, not just a one-time assignment event.
VisibilityManagers can review dispatch delay and fallback behavior as part of delivery oversight.
ProtectionFallback routing reduces the chance that a live role simply sits untouched.
Operational Depth
The detail behind this function.
These are the product capabilities that make this part of Omelion feel operationally serious instead of generic.
Admins can shape how quickly fallback should happen and who receives it.
Dispatch behavior becomes a measurable part of the operating model.
Dispatch states live on the job record with the rest of the role timeline.
Next Step
Review how dispatch fallback 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.