Campaign lifecycle
Goal, schedule, attempts, number, flow, and status are managed from the workspace.
Outbound sales AI
Who is this for?
What problems does it solve?
What can OMO do?
Goal, schedule, attempts, number, flow, and status are managed from the workspace.
XLSX data receives a preview, format validation, and duplicate checks before launch.
Interest, need, timing, objection, and next action are stored as separate fields.
A callback has a scheduled time, attempt history, status, and resulting owner or outcome.
How it works
Define the audience, offer, calling window, and success criteria.
LiveKit SIP creates the outbound call from the configured business number.
A Pipecat flow records only confirmed signals and handles defined objections.
The outcome becomes a meeting, callback, transfer, rejection, or do-not-call state.
Evidence retained
System boundaries
Direct answers
Yes. XLSX data is previewed and validated first; invalid numbers and duplicates are visible before launch, and campaign outcomes can be exported.
Qualification uses signals actually stated in the conversation, including interest, need, timing, decision role, and objections. Unconfirmed values remain empty.
A callback task is created with a scheduled time and status. The next attempt follows the campaign and allowed-hours policy.