Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Ingroup BATMAN allows a call to ring instead of answering it. It can reject the call with a Busy signal, allowing inbound vendors to reroute calls easily and help clients avoid paying for calls when they have no Users ready. BATMAN checks for Users available at intervals and keeps ringing for the configured max seconds.

...

  • Custom One: Max Rings in Seconds [ integer ]

    • How long until the call times out. (the caller has waited long enough, now do something with it)

    • Typically set to 2 min (120 sec)10 sec, though you should verify with the client

  • Custom Two: Check Interval in Seconds [ integer ]

    • Tells TLD how often to check to see if an User is available in seconds

    • Typically set to 2 seconds 1 second since that is about the time it takes for a call to route to an User

  • Custom Three: Fallback [ HANGUP | BUSY ]

    • This is what will happen when the call times out

    • Typically want to use Busy since it is a clear indicator of what is happening with the call, where as Hang-up can be interpreted many different ways

  • Custom Four: Show in Queue [ 0 | 1 ]

    • 0 = the calls will not show up in live Users. Data can only be found in the Queue Logs

    • 1 = the calls will show up in live Users with a Ring indicator on the right side

...

  • Custom One: Enter the State Route Prefix [ EX:SRI_ ]. 

    • Defaults to "SRI_". The state that the call is being routed to will be updated to reflect the state the call is coming from (id. SRI_FL)

  • Custom Two: Fallback Ingroup [ INGROUPID | HANGUP | BUSY ] 

    • If set to Hang Up or Busy and no User is found that has the necessary State Route Ingroup the dialer will hangup hang-up or play a busy signal

    • If set to Ingroup, the call will be routed to the Ingroup configured on the DID.

  • Custom Three: Max Rings in Seconds [ integer ]

    • How long until the call times out. (the caller has waited long enough, now do something with it)

    • Typically set to 2 min (120 sec) 10 sec, though you should verify with the client 

  • Custom Four: Check Interval in Seconds [ integer ] 

    • Tells TLD how often to check to see if an User is available in seconds

    • Typically set to 3 seconds since that is about the time it takes for a call to route to an User

  • Custom Five: Show in Queue [ 0 | 1 ]

    • 0 = the calls will not show up in live agents. Data can only be found in the Queue Logs

    • 1 = the calls will show up in live agents with a Ring indicator on the right side

...

  1. When setting Custom Five to 1 (Show in Queue) it will appear on the Live Agents screen. This will indicate there is a call waiting and will have the Status “Ring”

Image RemovedImage RemovedImage AddedImage Added

Queue Log

This will keep track of all the different calls that come in via BATMAN or State Routing. The last 3 columns are important. When a call is not answered or connected to an agent they will only appear in the Queue log, not the Call Log

...