🇬🇧
Omnileads Docs
ComunidadForo
English
English
  • 👶Introduction to OMniLeads
    • OMniLeads General Specs
    • Architecture and components
  • 🚀OMniLeads installation methods
    • Deploy using Docker
      • Deploy with Docker-Destkop
      • Deploy with Docker for VPS Cloud or VM
      • Deploy with Docker for VPS Cloud or VM with External Bucket
    • Deploy with Ansible
      • AIO (All-In-One) Deploy
      • AIT (All-In-Three) Deploy
      • HA (High Availability) Deploy
      • Backups, Restores, Upgrades and Rollbacks
      • Migration from CentOS7
    • OMniLeads Enterprise
    • Development Enviroment Deploy
    • First Login
    • TLS/SSL Certificates
    • Monitoring and observability
    • Security considerations
  • ⚙️Initial Configuration
    • External Authentication
    • Text To Speech (TTS)
  • 🎯CX Survey (Pro)
    • Reports
  • 📈Premium Reports (Pro)
    • Activity Reports
    • Analyzing Results
  • 🎞️Video Calls (Pro)
    • Wordpress Plugin
    • Initial Configuration
    • Webphone Demo
    • Embedding the Webphone
  • ☎️Voice Channel Configuration
    • General SIP trunk parameters
  • 🆗Whatsapp Channel Settings (Pro)
    • OMniLeads & GupShup
    • Register WhatsApp Business in GupShup
    • Message Templates and Time Groups
    • Providers
    • Lines
  • 🚧Wallboard for Business (Pro)
    • Creating a Wallboard
    • Adding Widgets and Realtime Pages
    • Exploring Widgets and Metrics
  • 📤Whatsapp Bulk Messaging (Pro)
  • 💬Contact Campaigns
    • Inbound Campaign
      • Incoming Call Routing
      • Forwarding incoming calls from the PBX
      • Time range conditioned routing
      • IVR - Interactive Voice Response
      • Incoming Caller ID
      • Ejecución de dialplan personalizado
    • Manual Campaign
    • Preview Campaign
    • Dialer Campaing
    • Whatsapp Campaign (Beta)
  • 🎧Agent handbook
    • Login Logout
    • Manual calls from contact list
    • Preview Calls
    • Dialer inbound calls
    • Inbound calls
    • Calls between agents
    • Contact List
    • Whatsapp Messages
  • 🛑Reports, recordings and monitoring
    • Recordings
    • Incoming Campaign Reports
    • Outbound Campaign Reports
    • General call report
    • Agent reports
    • Whatsapp reports (Beta)
    • Conversation Reports
    • Supervision
  • 📊Backoffice - Management audit
  • ☎️Integration between OMniLeads and PBXs
  • 🛠️IT administrator's tasks
  • 🧩CRM Integration
    • Interaction from OMniLeads to CRM
    • Interaction from CRM to OMniLeads
  • 🔐Security considerations
  • 📌OMniLeads RESTful API
    • Agent Session API in Asterisk
  • 🗒️Release Notes
  • ❤️Community
  • 🎇About us
Con tecnología de GitBook
En esta página
  • Time range conditioned routing
  • Time Groups
  • Time validations
  1. Contact Campaigns
  2. Inbound Campaign

Time range conditioned routing

AnteriorForwarding incoming calls from the PBXSiguienteIVR - Interactive Voice Response

Última actualización hace 11 meses

Time range conditioned routing

In this section, we work with the concept of Time-based Inbound Call Routing to configure the flow of incoming calls to different internal destinations by comparing the date/time when a call arrives and a related pattern (of dates and times), so that we can plan in advance whether a call should go to one destination or another based on the result of this comparison. For example, a call could go to an inbound campaign within the customer service date and time range and to an IVR that plays an announcement about the service hours when the call comes in outside of this defined range.

Figure 1: Time condition There are 2 modules that work together and allow implementing this type of configuration, which are detailed below.

Time Groups

This module allows you to group date and time patterns as an object, so that they can then be invoked by time conditional objects. To define or edit time groups, you must access the Resources -> Time Groups menu. To add a new group, press the "New" button. The time groups screen is shown in the following figure:

Figure 2: Time groups Once the time groups have been generated, we can invoke them from the Time Validations add-on module.

Time validations

This module allows you to compare the date and time at the time of processing a call, with a time group assigned as a comparison pattern. Then, based on whether or not it matches any date/time range in the group, the call is sent to the positive or negative destination of the comparison.

A conditional node of this class can be invoked by other nodes:

  • Inbound Routes

  • IVR Options

  • Inbound campaign Failover

  • Others

To generate a time-conditional element, you must access the Telephony -> Time Validations menu. The configuration screen is similar to the following figure:

Figure 3: Time validations Finally, we have this routing element available to be used, for example, as a destination for an incoming route.

💬