{"id":6487,"date":"2026-05-26T11:19:25","date_gmt":"2026-05-26T09:19:25","guid":{"rendered":"https:\/\/help.ino.cx\/?post_type=ht_kb&p=6487"},"modified":"2026-05-26T11:19:26","modified_gmt":"2026-05-26T09:19:26","slug":"voice-calls-in-the-banner","status":"publish","type":"ht_kb","link":"https:\/\/help.ino.cx\/index.php\/help-center\/voice-calls-in-the-banner\/","title":{"rendered":"Voice calls in the Banner"},"content":{"rendered":"\n
\"Smart<\/figure>\n\n\n\n

[Reading time: 9 minutes<\/em>]<\/p>\n\n\n\n

Overview<\/h2>\n\n\n\n

Voice is a real-time<\/strong> channel: customer and agent are connected at the same moment and the conversation must be handled live. Most voice calls are presented to the agent through an incoming call popup<\/strong> as soon as they are dispatched, so the agent answers (or declines) immediately.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The Banner also has a dedicated Voice<\/strong> module that lists the calls visible to the agent (Calls in pool<\/em>): calls being presented, calls the agent is currently handling, and calls waiting in queues the agent supervises. From that list a call can be picked up manually with the Take this call<\/strong> action \u2014 though in day-to-day work, calls are most often answered directly from the popup.<\/p>\n\n\n\n

This article covers how the agent handles voice calls from the Banner, both incoming<\/strong> and outgoing<\/strong>, in Smart<\/strong> and Direct<\/strong> modes. Outbound calls launched through a campaign (power dialer, progressive, preview) follow a different flow and are covered in dedicated articles.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

1. How a call arrives in the Banner<\/h2>\n\n\n\n

1.1. Smart routing<\/h3>\n\n\n\n

This is the most common mode. When a customer dials one of your inbound numbers:<\/p>\n\n\n\n

    \n
  1. The Smart Routing of the voice flow handles the call first (welcome message, IVR menu, DTMF or speech recognition, business rules, etc.).<\/li>\n\n\n\n
  2. The call is qualified and dispatched to a distribution queue<\/strong> (or a distribution group) that matches the request.<\/li>\n\n\n\n
  3. The ACD assigns the call to an available agent of that queue and the agent receives an incoming call popup<\/strong> in the Banner.<\/li>\n<\/ol>\n\n\n\n

    Note: Calls can also be accessed from the small Banner. This right can be enabled\/disabled in the queue.<\/em><\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    1.2. Direct routing<\/h3>\n\n\n\n

    A call can also arrive directly to a specific agent \u2014 for example because the caller dialled the agent\u2019s extension or because an internal call is being placed. The popup is displayed without going through a queue, and only that agent is solicited.<\/p>\n\n\n\n

    2. The incoming call popup<\/h2>\n\n\n\n

    2.1. Popup content<\/h3>\n\n\n\n

    The popup displays the most useful information to qualify the call before answering:<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n
    Field<\/th>Description<\/th><\/tr><\/thead>
    Caller<\/strong><\/td>Caller phone number (and the contact name if it is known in the CRM).<\/td><\/tr>
    Queue<\/strong><\/td>Queue the call has been dispatched from (Smart routing only).<\/td><\/tr>
    Wait time<\/strong><\/td>Time the caller has spent in the queue before being assigned.<\/td><\/tr>
    Transfer<\/strong><\/td>If the call is the result of a transfer: the agent who is transferring it and the type of transfer.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    The path followed in the Smart Routing and any variables collected during the IVR (DTMF entries, speech recognition results, etc.) are not displayed on the popup itself, but are accessible from the Datas<\/strong> tab of the active call panel once the call has been accepted.<\/p>\n\n\n\n

    2.2. Popup color<\/h3>\n\n\n\n

    The popup color helps the agent identify the type of call at a glance:<\/p>\n\n\n\n

    Color<\/th>Type of call<\/th><\/tr><\/thead>
    Raspberry red<\/td>Smart routing or campaign call<\/td><\/tr>
    Ocean blue<\/td>Direct call from an external contact<\/td><\/tr>
    Sky blue<\/td>Direct call from an internal user (colleague)<\/td><\/tr>
    Lilac<\/td>Preview call (the agent reviews the call before launching it)<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    2.3. Accept or decline<\/h3>\n\n\n\n

    Two buttons are available on the popup:<\/p>\n\n\n\n

      \n
    • Accept<\/strong> (check icon): the agent takes the call. The active call panel opens in the central area of the Banner.<\/li>\n\n\n\n
    • Decline<\/strong> (cross icon): the agent refuses the call, which goes back to the distribution queue and is offered to another available agent.<\/li>\n<\/ul>\n\n\n\n

      A countdown shows the remaining time before automatic redistribution if the agent does nothing.<\/p>\n\n\n\n

      2.4. Auto-accept<\/h3>\n\n\n\n

      If the agent profile is configured with auto-answer<\/strong>, the call is accepted automatically when the popup is displayed. The agent does not need to click \u2014 the conversation starts directly. This is typically used in headset-only environments.<\/p>\n\n\n\n

      3. The active call interface<\/h2>\n\n\n\n

      Once the call is accepted, the central panel of the Banner displays the active call interface, with the caller\u2019s information at the top and a set of controls to manage the call.<\/p>\n\n\n\n

      \"\"<\/figure>\n\n\n\n

      3.1. Call timer<\/h3>\n\n\n\n

      A timer at the top of the panel shows the elapsed duration of the call.<\/p>\n\n\n\n

      3.2. Mute \/ unmute the microphone<\/h3>\n\n\n\n

      The Mute my mic<\/strong> button silences the agent\u2019s microphone \u2014 the agent still hears the caller, but the caller no longer hears the agent. While muted, the button turns red and changes to Reactivate my mic<\/strong> to restore the microphone.<\/p>\n\n\n\n

      3.3. Hold \/ unhold the call<\/h3>\n\n\n\n

      The Place on hold<\/strong> button puts the caller on hold; an on-hold music or message can be played to the caller (depending on the configuration). The button changes to Exit the hold<\/strong> to resume the conversation.<\/p>\n\n\n\n

      3.4. Send DTMF tones<\/h3>\n\n\n\n

      The Phone keypad<\/strong> opens a numeric pad (0\u20139, *, #) inside the call interface. Each key press sends the corresponding DTMF tone on the call \u2014 useful for navigating an external IVR or providing codes during the call.<\/p>\n\n\n\n

      3.5. Call recording<\/h3>\n\n\n\n

      If recording is allowed on the agent\u2019s profile and the queue, the agent can manually start and stop the recording with Start the recording<\/strong> \/ Stop the recording<\/strong>. While recording is active, the button blinks to make it visible.<\/p>\n\n\n\n

      Some queues are configured to record automatically \u2014 in that case, the recording starts on its own when the call begins.<\/p>\n\n\n\n

      3.6. Hang up<\/h3>\n\n\n\n

      The Hang up<\/strong> button ends the call. The agent then enters the post-call phase (see section 7).<\/p>\n\n\n\n

      4. Transfer a call<\/h2>\n\n\n\n

      An active voice call can be transferred to four kinds of destinations. In each case, the agent picks the destination from a list (or enters a phone number for an external transfer) and chooses whether the transfer is blind or attended.<\/p>\n\n\n\n

      4.1. Destinations<\/h3>\n\n\n\n
      Destination<\/th>Description<\/th><\/tr><\/thead>
      User<\/strong><\/td>Transfer to another agent of the company.<\/td><\/tr>
      Queue<\/strong><\/td>Transfer to a distribution queue, the call goes back through the ACD.<\/td><\/tr>
      Smart Routing<\/strong><\/td>Transfer to a Smart Routing, the call is re-qualified by the routing tree.<\/td><\/tr>
      Directory<\/strong><\/td>Transfer to a contact stored in the directory of the platform.<\/td><\/tr>
      Number<\/strong><\/td>Transfer to an external phone number entered manually.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

      4.2. Blind or attended transfer<\/h3>\n\n\n\n
        \n
      • Transfer and hang up<\/strong> (blind): the agent transfers the call and disconnects immediately. The recipient has no context other than what is provided by the system (caller info, queue, etc.).<\/li>\n\n\n\n
      • Start the attended transfer<\/strong>: the agent stays on the line, talks to the recipient first to introduce the caller and the request, then completes the transfer (or cancels and resumes the call).<\/li>\n<\/ul>\n\n\n\n

        An ongoing transfer can be cancelled before it is completed; the system shows a status banner with the transfer state and the reason in case of failure.<\/p>\n\n\n\n

        5. Merge two calls (3-way)<\/h2>\n\n\n\n

        If the agent is on two voice calls at the same time (one active, one on hold), the Merge<\/strong> action joins them into a single 3-way conversation. This is the way to set up a small conference between the agent, the customer and a third party.<\/p>\n\n\n\n

        If the agent has only one voice interaction in progress, the merge action is not available.<\/p>\n\n\n\n

        6. Make an outbound call<\/h2>\n\n\n\n

        6.1. Direct outbound call<\/h3>\n\n\n\n

        The agent can initiate a call from the Banner using the New call<\/strong> action:<\/p>\n\n\n\n

          \n
        1. Click New call<\/strong>.<\/li>\n\n\n\n
        2. Choose between Make a call to a number<\/strong> (external phone number) and Make a call to an extension<\/strong> (internal user).<\/li>\n\n\n\n
        3. Enter the destination and click to launch the call.<\/li>\n<\/ol>\n\n\n\n

          The agent\u2019s outbound caller ID is set according to the queue or profile configuration.<\/p>\n\n\n\n

          6.2. Smart outbound call<\/h3>\n\n\n\n

          If the agent profile has the right to send Smart outgoing voice interactions, an additional option is offered when starting a new call: launch the call through a Smart Routing<\/strong>. The call then goes through the configured routing tree (for example to apply business rules, opening hours, or to record additional metadata) before being placed.<\/p>\n\n\n\n

          6.3. Call back from a CRM card<\/h3>\n\n\n\n

          From a CRM contact card or an interaction history entry, the agent can use the Call back<\/strong> action. The phone number is pre-filled from the contact and the call is launched as an outbound call.<\/p>\n\n\n\n

          Note<\/strong>: outbound calls launched through voice campaigns (power dialer, progressive, preview) follow a different flow and are not covered here. See the Voice campaigns<\/strong> articles of the help center.<\/p>\n\n\n\n

          7. Post-call processing<\/h2>\n\n\n\n

          When the call ends (either side hangs up), the agent enters the Post-interaction<\/strong> status. During this phase, the agent finalises the interaction without taking new calls.<\/p>\n\n\n\n

          Available actions during post-call:<\/p>\n\n\n\n

            \n
          • Qualification<\/strong>: fill in the qualification form configured on the queue (categories, reasons, comments, etc.).<\/li>\n\n\n\n
          • Tags<\/strong>: label the interaction.<\/li>\n\n\n\n
          • CRM and cases<\/strong>: associate the call to a contact card, create or update a case, etc.<\/li>\n\n\n\n
          • Extend the post-interaction time<\/strong>: if the configured duration is too short, the agent can extend it. The remaining and total times are displayed.<\/li>\n\n\n\n
          • End the post-interaction<\/strong>: ends the post-call phase early and makes the agent available again.<\/li>\n<\/ul>\n\n\n\n

            8. Missed calls and voice mailbox<\/h2>\n\n\n\n

            If the agent does not answer in time (popup countdown reaches 0) or declines the call, the call goes back to the distribution queue and is offered to another agent. When the popup expires without the agent reacting, a Missed call<\/strong> notification is shown to the agent.<\/p>\n\n\n\n

            If no agent picks up the call within the queue\u2019s waiting limits, the call can be redirected to a voice mailbox<\/strong> (when the Smart Routing is configured to do so). The customer leaves a message, which is then made available \u2014 with optional transcription and email notification \u2014 to the configured recipients.<\/p>\n\n\n\n

            9. Notifications<\/h2>\n\n\n\n

            Voice notifications are configured in Maker > User > Notifications<\/strong>. The most common ones for voice are:<\/p>\n\n\n\n

            Notification<\/th>Triggered when<\/th><\/tr><\/thead>
            Incoming call ringtone<\/strong><\/td>A voice call popup is presented to the agent.<\/td><\/tr>
            Missed call<\/strong><\/td>The agent did not answer or declined an incoming call.<\/td><\/tr>
            Transfer requested<\/strong><\/td>A transfer (blind or attended) is initiated by another agent.<\/td><\/tr>
            Call ended<\/strong><\/td>The voice call has just ended.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

            Each notification can be enabled, disabled, set to sound only, desktop only, or both, per agent.<\/p>\n","protected":false},"excerpt":{"rendered":"

            [Reading time: 9 minutes] Overview Voice is a real-time channel: customer and agent are connected at the same moment and the conversation must be handled live. Most voice calls are presented to the agent through an incoming call popup as soon as they are dispatched, so the agent answers (or declines) immediately. The Banner…<\/p>\n","protected":false},"author":5,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","meta":{"footnotes":""},"ht-kb-category":[105],"ht-kb-tag":[],"class_list":["post-6487","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-using-ino"],"_links":{"self":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb\/6487","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/comments?post=6487"}],"version-history":[{"count":5,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb\/6487\/revisions"}],"predecessor-version":[{"id":6571,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb\/6487\/revisions\/6571"}],"wp:attachment":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/media?parent=6487"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb-category?post=6487"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb-tag?post=6487"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}