DS Dialer
This section demonstrates how to configure the extra steps required for the DS Dialer to work correctly with Omni, allowing users to receive calls in an integrated way.
⚠️ Important: All other standard Omni configurations must be performed normally.
🧭 In Omni, the media used must be configured as Dialer, and all reports and configurations related to this flow must be associated with this media.
Organization Configuration
Access the Companies menu and, within the desired organization, fill in the following mandatory parameters to enable integration with the DS Dialer:
- Dialer key
- Dialer server
- WebRTC server
⚠️ Important: This data must be obtained from the team responsible for the dialer, who will provide the correct credentials and configurations for integration.
🔐 Certificate: The DS Dialer API requires a certificate in the X.509 Base64 format (.CRT, .CER, or .PEM extensions).

User Configuration
In the registration of each user who will use the Dialer, it is necessary to fill in the following parameters so that the system can automatically connect to the dialer:
- Enable Use dialer
- Dialer username
- Dialer password
⚠️ The information provided must be exactly the same as registered in the dialer system.

Service Configuration with AGV
If there is a transfer AGV, it will be necessary to register a Service in Omni that contains the AGV extension as an identifier for receiving transfers.

Service Linkage by Queue Code (DS)
To ensure that calls delivered by the Dialer are routed to the correct service in Omni and include their respective custom disposition tags, you must establish the link using the queue identifier.
In the configuration of the desired service, navigate to Administrative > Services and fill in the field:
- Queue code (DS): Enter the queue code (CodQueue / Service Group) configured in the dialer campaign.

Routing and Disposition Rules
Upon receiving the call from the mailing list on screen, Omni identifies the queue code transmitted by the dialer and behaves as follows:
- 🎯 Populated Queue Code: The interaction is automatically created within the service corresponding to the provided code. The disposition tags displayed to the agent during and after the call will exclusively be those registered for this specific service.
- 📦 Empty or Unlocated Queue Code (Default): If the field is blank or the system does not locate any service linked to the provided code, the interaction will be opened under the Default Service (the organization's default service), using the list of tags already configured for it.
💡 Disposition Identifier: When configuring the completion tags for the service linked to the dialer, make sure to associate the respective Contact Disposition ID (external campaign qualification code) so that the call disposition is properly synchronized between both platforms.

Pause Registration
The pauses used by the dialer must be registered in Omni with the following considerations:
- The naming must be exactly the same as that used in the dialer.
- The Status ID field must be filled in correctly according to the registration in the dialer.

Configuration Finalization
After all the configurations described above:
✅ The Dialer will be ready to operate with Omni.
🔄 The user just needs to log out and log back in to the system so that the integration works together with the dialer, which will be responsible for generating the mailing.
Operation Modes: Predictive and Preview Dialing
Omni provides distinct active dialing modes so that operations can perfectly adapt to the profile of each campaign or client. Through the Predictive and Preview models, managers have the power to balance high productivity in volume with the quality of personalized contact.
The choice between these modes defines how the system manages the delivery of contacts to agents, optimizing team occupancy time and ensuring that each approach occurs at the most efficient moment and in the most effective way for the business.
It is important to emphasize that the definition of the dialing mode (Predictive or Preview) is a configuration performed exclusively by the Telecom team directly in the Dialer. Omni acts as the receiver of these calls, with no parameterization for switching between these models within Omni’s administrative interface.
Interface and Visualization in Attendance
Regardless of the mode used (Predictive or Preview), the Attendance interface and the arrangement of information on Omni’s screen remain the same. This ensures a standardized experience for the operator and facilitates data management.
- Customizable Fields: All information and personalized fields that appear during Attendance are configured by the Telecom team through the Dialer.
- Visual Difference: The only distinction in the interface between the models is the presence of action buttons and a timer, which are exclusive to the Preview mode. In the Predictive model, the agent receives the call already in progress without the need for accept/reject buttons to initiate dialing.

Editing and Synchronizing Mailing Data
During active calls or ongoing service in the Dialer (whether in Preview or Predictive mode), the agent can directly edit the information received from the mailing within the service interface, keeping the record updated in real time.
✏️ How to Edit Mailing Data
- In the service/dialer data block on screen, locate the contact information.
- Make the necessary changes or additions in the available fields (each field accepts up to 1,000 characters, except for phone numbers and area codes).
- To manually save changes at any time during the conversation, click the Synchronize Mailing button.
Editing and synchronizing mailing data during service

🛡️ Rules and Data Synchronization
- 🔒 Protected Field (CodMailing): The unique record identifier (CodMailing) is strictly locked for editing, ensuring the integrity and tracking of the original upload.
- ⚠️ Mandatory Persistence via Button: Data is only saved using the Sincronizar Mailing button. If the agent disposition/tabs the service without clicking synchronize beforehand, unsaved changes will be discarded.
- 👥 Lock in the Contact File: During an active dialer service, direct editing through the general Contacts tab remains restricted, concentrating all changes exclusively in the on-screen service mailing card.
- 📅 Persistence in Reschedules: Properly synchronized data is saved permanently; if the call returns to the screen as a scheduled call, the record will present all previously made updates.
- 🧩 Destination in Custom Fields: Edited data originating from the mailing is persisted and updated directly within the Custom Fields of the contact's file in Omni.
- 🔍 Viewing in Interaction Tracking: In the tracking module, the ticket/call history displays in detail all edits made to the synchronized information blocks.
Record of mailing changes in interaction tracking

Predictive Dialer
In the Predictive model, the absolute priority is to maximize the agent’s talk time, ensuring they spend as much time as possible in direct contact with customers. The system works proactively, making multiple automatic calls based on mailing lists and delivering to the operator only the interactions where a real person is on the other end of the line.
🔄 How It Works in Practice:
- Automatic and Intelligent Distribution: The call appears instantly on Omni’s screen. Unlike other models, the agent does not wait for the phone to ring; when the call appears, it is already in progress or fully connected, ready for dialogue.
- Agent’s Role: The process is 100% transparent and free of manual dialing intervention. The operator’s role is purely focused on human interaction, starting the conversation as soon as the system establishes the connection and delivers the contact.
- Operational Advantage: Drastically reduces idle time, eliminating waiting for busy tones, voicemails, or invalid numbers.
Preview Dialer
Unlike the Predictive model, the Preview model focuses on quality and personalized contact. It is ideal for complex sales operations, specific collections, or any service that requires the agent to know the customer’s history before starting the conversation. This mode offers strategic “breathing time,” allowing the operator to properly prepare for the approach.
📋 Mailing Import Requirement
For dialing to work correctly and the system to identify destinations, the mailing must be sent with contact data following the naming and format below:
- Mandatory Format:
NU_DDD_1=XX|NU_PHONE_1=XXXXXXXXX| - Example:
NU_DDD_1=11|NU_PHONE_1=999999999|
❗ Important Note: The functionality of the call button and the trigger of the automatic call (after the timer ends) depend exclusively on the presence of these fields exactly as described. If the mailing is imported with different naming, the system will not be able to process dialing, invalidating the Preview model operation.
⏱️ The Preview Call Cycle:
- Delivery and Case Study: The call appears on Omni’s screen with all available contact information, but the call is not initiated immediately. The agent can read notes, check history, and understand the profile before calling.
- Analysis Time (Safety Timer): The system provides configurable preparation time (set in Company Menu, default 60 seconds). This timer is visually displayed, ensuring fair analysis time without compromising workflow.
- Conscious Decision Making: During analysis time, the operator decides:
- Green Button (Call): Starts dialing manually when ready.
- Reject Button: If contact is not viable, the agent can refuse. In this case, tabulation and completion tags must be filled.
- Automatic Trigger: To avoid stagnation, if the timer reaches zero without manual action, Omni automatically initiates the call.

💡 Strategic Advantage:
The great strength of Preview is preparation. The agent enters the call already knowing the customer’s name, last interactions, and possible objections, greatly increasing the chances of success.
⚙️ Timer Configuration (Preview)
Although dialing strategy is defined by Telecom, the analysis time in the Preview model is configured directly in Omni’s admin interface. This allows balancing case study time with productivity needs.
Steps to adjust analysis time:
- Go to Settings > Companies.
- Locate Advanced Settings.
- In Timer for preview call response (in seconds), enter the desired value.
- Default is 60 seconds, adjustable up to 24h (86400 seconds).
- Click Save or Update.

Redialing
The Redialing feature allows operators to quickly and strategically retry active calls without reimporting the mailing or manually searching the contact in the database.
Whenever a call ends, disconnects, or is unanswered (without effective customer contact), the dialer status enters Pending Tabulation. At this point, the platform enables redialing tools.
Ways to Execute Redialing
Interface behavior and redialing options vary depending on the active dialer mode in your campaign, adapting to your operation’s strategy.
🤖 Predictive Mode
In Predictive mode, the focus is maximum productivity and time optimization. Call rhythm is automated, keeping the operator’s flow agile. Redialing follows a simplified pattern:
- 🟡 Standard Redial (Yellow Button): The operator clicks the yellow button with the phone + circular arrow icon (bottom bar). The system immediately dials the Phone 1 (Primary) registered.
⚠️ Important Note for Predictive Dialing: When the operator is using the Predictive mode and there is an active call on screen with pending tabulation, only the yellow redial button will be available to make calls.
In this situation, the numeric keypad and manual phone number entry are completely blocked in the interface. The operator will not be able to enter a new number manually, since the yellow button is reserved exclusively for redialing the number linked to the active call that remains on the screen.
👁️ Preview Mode
In Preview mode, the strategy prioritizes flexibility and agent autonomy. Redialing can be executed in three ways:
- 🟡 1. Yellow Button: Direct immediate call to Phone 1 (Primary).
- 📱 2. Direct Click on Data Sheet: The operator clicks any phone number listed in Customer Data (Phone 1, Phone 2, etc.). Omni instantly dials the clicked number.