Lead recovery
Re-engage contacts that have gone cold by switching channels and passing to the salesperson when there is a sign of interest.
EmailSMSWhatsAppCall
Operational automation
Automate outreach without losing each person's context.
warning The pain it solves
Isolated channel approaches repeat messages, miss the lead's moment, and leave the team unsure which contact has occurred or what the next step is.
A workflow describes what starts the process, which conditions need to be checked, and what actions should happen next. This logic turns informal procedures into a trackable flow.
At OmniSmart, the process can combine customer service, sales, voice, and external integration events. A new lead, a pipeline change, a lack of response, or a due date can start a journey via email, SMS, RCS, WhatsApp, call, or voice broadcast.
The execution log is part of the design. It allows you to understand why a path was followed, identify failures, and review rules as operations change.
Features
Automation with clear rules and history
Model repetitive processes, connect systems, and track the outcome of each execution.
bolt
Triggers and actions
Start flows by event, schedule, or integration and execute defined steps.
rule
Conditions
Create different paths based on data, status, or responses.
How it works
From event to result
1
Triggers
An event, schedule, or webhook starts the process.
2
Evaluates
Conditions check data and choose the path.
3
Executes
Actions update modules or authorized systems.
4
Records
The history shows steps, results, and exceptions.
Multichannel journeys
One strategy, multiple channels, and an intelligent flow
The workflow combines channels, wait times, responses, and CRM data to decide the next contact. Thus, email, SMS, RCS, WhatsApp, call, and voice broadcast participate in the same approach without turning the journey into a blind sequence of dispatches.
mailEmail
smsSMS
mmsRCS
chatWhatsApp
callCall
record_voice_overVoice torpedo
Example · Lead recovery without return
ACTIVE AND TRACEABLE FLOW
Trigger
Lead without response
48 hours without new interaction in CRM
First contact
Send email
Personalized message by source and interest
Condition · 24 h
Opened, clicked, or replied?
Behavior chooses the next path
Yes
chatWhatsApp
add_taskTask in CRM
callCloser calls
No
smsSMS
mmsRCS
record_voice_overVoice torpedo
ruleResponse is a condition, not the end of history. When the contact reacts, the workflow can stop the next triggers, update the score, move the pipeline stage, and hand the conversation over to a person.
Workflows for each journey goal
The same builder can organize different approaches. The design combines trigger, audience, message, interval, exit condition, and human responsibility.
Immediate activation
Receive the lead from a form or integration, confirm interest, and trigger the team while the intention is still hot.
FormWhatsAppTaskCall
Collections
Organize reminders before and after due dates and escalate the contact according to status, value, and customer response.
EmailWhatsAppSMSVoice
Sale
Connect content, proof, offer, and sales action to the behavior observed at each stage of the opportunity.
EmailRCSWhatsAppCloser
Active approach
Distribute a cadence across channels and responsible parties, respecting schedules and stopping the sequence when there is a response.
EmailCallSMSWhatsApp
Nurturing
Deliver content in stages and adapt the next message to the topic consumed, the click, and the contact's stage.
EmailWaitConditionRCS
Lead warming
Combine education, interest recognition, and scoring until the contact meets the criteria defined for sales approach.
ContentCliquesScoreCRM
Qualification
Collect responses, query data, and route each application to automation, SDR, Closer, or discard according to rules.
WhatsAppValidationScoreRouting
scheduleIntervals and schedules
Define wait time, contact window, and frequency for each step.
alt_routeConditions and exits
Change the path based on response, click, status, score, or CRM data.
privacy_tipPermission by channel
Plan consent, unsubscribe, and rules compatible with each audience.
historyExecution history
Record contacts, decisions, failures, and results to evolve the journey.
On screen
Schedule a demo arrow_forward
See where each process is
Track executions, errors, and dependencies to fix the flow without searching multiple tools.
check_circleEvent or schedule triggers
check_circleVisual conditions and branches
check_circleLogs for analysis and reprocessing
boltTriggerNew ticket openedHelpdesk · any channel
alt_routeConditionIs priority High?Checks ticket fields
notifications_activeIf yesNotify supervisor1-hour SLA
inboxIf noSend to default queueAutomatic distribution
Product in context
Track the process within the platform itself
The screenshots below show how flows are organized and consulted during operation.
Frequently asked questions