Professional Documents
Culture Documents
User Manual
Version 1.5
www.drishti-soft.com
Confidential
info@drishti-soft.com; www.drishti-soft.com DR-180908-APUM-V14 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
-1-
Drishti-Soft Solutions
Drishti-Soft Solutions Pvt. Ltd. provides this publication "as is" without warranty of any kind, either express or implied, including but limited to the implied warranties or conditions of merchantability or fitness for a particular purpose. Drishti-Soft Solutions will not be liable in any case for any loss of profits, loss of business, loss of use or data, interruption of business, or for indirect, special, punitive, incidental, or consequential damages of any kind, even if Drishti-Soft Solutions has been advised of the possibility of such damages arising from any defect or error in this publication or in DACX Ameyo.
Drishti-Soft Solutions reserves the right to change information in this document without prior notice. No part of this document may be photocopied or reproduced in any form or by any means - graphic, electronic or mechanical-including photocopying, recording, taping, or storage in an information retrieval system, without the prior written consent from Drishti-Soft Solutions Pvt. Ltd. Drishti-Soft Solutions cannot be challenged in any event whatsoever with respect to the contents of the said document.
Drishti-Soft Solutions Tel: 91 124 4771000 Fax: 91 124 4039120 Email: dacxsupport@drishti-soft.com Website: http://www.drishti-soft.com
H H
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
-2-
Drishti-Soft Solutions
Introduction
DACX Ameyo (Professional) is an all-in-one Call Center Solution that is perfectly equipped with inbound, outbound and blended capabilities to run customer support, telemarketing and sales, collections, technical support, marketing research, helpdesk and other processes across various verticals such as BPO, communications, financial services and technology. DACX Ameyo is comprehensive yet flexible to meet the ever-evolving Call Center requirements. It is an ideal solution for any kind of call center irrespective of size, technology (TDM or VoIP), or workforce distribution. The feature-rich solution offers top-of-the-line capabilities, such as Predictive Dialer, IP-PBX, IVR (Interactive Voice Response), ACD (Automatic Call Distributor), Voice Logger, Unified Contact Messaging, CRM and Reporting. It provides a powerful value proposition to its call center customers in form of easy scalability, ease-of-use, superior operational economy and ability to work seamlessly over TDM or VoIP.
Convention
Meaning
Bold
The labels (of buttons or fields) or tabs that are visible on the interface.
Italics
Examples of text or value entered in a field or selection from the dropdown menu.
Click
Double Click
Right Click
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
-3-
Drishti-Soft Solutions
Table of Contents
Table of Contents .................................................................................................................................... 4 Section 1 ................................................................................................................................................. 7 Overview ................................................................................................................................................. 7 1.1 System entities .............................................................................................................................. 7 1.2 Administration (Configuration and Supervision) ........................................................................... 7 1.3 Workbench .................................................................................................................................... 8 1.4 User Start Up ................................................................................................................................ 8 Section 2 ................................................................................................................................................. 9 System Configuration .............................................................................................................................. 9 2.1 Settings ......................................................................................................................................... 9 2.2 Routing .......................................................................................................................................... 9 2.2.1 Policies ................................................................................................................................. 10 2.2.2 Profiles ................................................................................................................................. 10 2.3 Dispositions ................................................................................................................................. 11 2.3.1 Disposition Classes .............................................................................................................. 11 2.3.2 Disposition Plan ................................................................................................................... 13 2.4 Filters........................................................................................................................................... 14 2.5 Blending Campaigns 2.6 Skills Section 3 ............................................................................................................................................... 16 User Management ................................................................................................................................. 16 3.1 Users ........................................................................................................................................... 16 Section 4 ............................................................................................................................................... 18 Campaign Management ........................................................................................................................ 18 4.1 Campaigns .................................................................................................................................. 18 4.2 Assigning Users .......................................................................................................................... 21 4.3 Call Context ................................................................................................................................. 22 4.4 Assigning Filters .......................................................................................................................... 22 4.5 Feature Context .......................................................................................................................... 23 4.6 Campaign Edit Section 5 ............................................................................................................................................... 26 Number Management ........................................................................................................................... 26 5.1 Basic Lead Settings .................................................................................................................... 26 5.2 Number Management ................................................................................................................. 28 5.2.1 Get Lead Summary .............................................................................................................. 28 5.2.2 Fetch .................................................................................................................................... 29 5.2.3 Churn.................................................................................................................................... 29 5.3 Excluded Dispositions ................................................................................................................. 30 Section 6 ............................................................................................................................................... 31 Queue Management ............................................................................................................................. 31 6.1 Queue.......................................................................................................................................... 31 6.2 Assigning Users .......................................................................................................................... 32 Section 7 ............................................................................................................................................... 34 Agent Workbench .................................................................................................................................. 34 7.1 Dialing ......................................................................................................................................... 34 7.2 Agent Status ................................................................................................................................ 35 7.3 Voice Status ................................................................................................................................ 35 7.4 Knowledge Base ......................................................................................................................... 37 7.5 Callback Management ................................................................................................................ 37 7.6 Call History .................................................................................................................................. 38 7.7 Users ........................................................................................................................................... 39
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
-4-
Drishti-Soft Solutions
Section 8 ............................................................................................................................................... 40 Supervision/ Monitoring......................................................................................................................... 40 8.1 Status .......................................................................................................................................... 40 8.1.1 Agent Information ................................................................................................................. 40 8.1.2 Customer Details .................................................................................................................. 42 8.1.3 User Summary ..................................................................................................................... 42 8.1.4 Last Calls.............................................................................................................................. 42 8.1.5 Minutes ................................................................................................................................. 42 8.1.6 Conferences ......................................................................................................................... 42 8.1.7 Lead Summary ..................................................................................................................... 43 8.2 Call Details .................................................................................................................................. 43 8.3 Call History .................................................................................................................................. 44 8.4 Settings ....................................................................................................................................... 45 8.5 Dialer Configuration .................................................................................................................... 46 8.6 Call Back Management ............................................................................................................... 48 8.6.1 To manage callback ............................................................................................................. 48 8.6.2 To configure callback ........................................................................................................... 49 8.7 Number Management ................................................................................................................. 50 8.8 DNC Management ...................................................................................................................... 50 8.8.1 General................................................................................................................................. 50 8.8.2 Media Exclusion ................................................................................................................... 51 8.9 Call Context Policy ...................................................................................................................... 52 8.10 Queue Details ........................................................................................................................... 54 8.11 Queue Mgmt. ............................................................................................................................ 54 8.12 Voice Prompt ............................................................................................................................. 55 8.12.1 Voice Prompt ...................................................................................................................... 55 8.12.2 Audio File ........................................................................................................................... 55 Section 9 ............................................................................................................................................... 57 Call Manager ......................................................................................................................................... 57 9.1 Voice Resources ......................................................................................................................... 57 9.1.1 To view / edit / add call manager ......................................................................................... 57 9.1.2 To view / edit call context details ......................................................................................... 58 9.2 Asterisk Resources ..................................................................................................................... 60 9.2.1 General Information ............................................................................................................. 60 9.2.2 To add Asterisk voice resource ............................................................................................ 61 9.2.3 Asterisk Voice Resource Settings ........................................................................................ 61 9.2.4 Asterisk Entities Details........................................................................................................ 63 Section 10 ............................................................................................................................................. 65 Reports .................................................................................................................................................. 65 10.1: Report Settings ........................................................................................................................ 65 10.1.1: Report Type ...................................................................................................................... 65 10.1.2: Report Duration ................................................................................................................. 65 10.1.3: Report Parameters ............................................................................................................ 65 10.1.4: Report Formats ................................................................................................................. 65 10.1.5: Report Authorization ......................................................................................................... 66 10.2: Report Category ....................................................................................................................... 66 10.2.1: Call History ........................................................................................................................ 66 10.2.2: Inbound ACD queue interval ............................................................................................. 67 10.2.3: Agent productivity report ................................................................................................... 67 10.2.4: Call Details ........................................................................................................................ 67 10.2.5: CRM Details Report .......................................................................................................... 68 10.2.6: Inbound Agent Call Detail ................................................................................................. 68 10.2.7: Inbound Call Log Details ................................................................................................... 69 10.2.8: Hourly Inbound Call Report ............................................................................................... 69 10.2.9: Inbound Campaign Report ................................................................................................ 70 10.2.10: User Session ................................................................................................................... 70 10.2.11: Hourly ACD Report ......................................................................................................... 71
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
-5-
Drishti-Soft Solutions
Section 11 System Advanced Options 11.1: Logging 11.1.1: License 11.1.2: System Parameter Appendix I ............................................................................................................................................. 72 I.1: How to add a new agent? ....................................................................................................... 72 I.2: How to upload a new lead? ..................................................................................................... 73 I.3: How to fetch voice logs? ......................................................................................................... 74 I.4: How to generate reports?........................................................................................................ 76 I.5: How to manage dialing?.......................................................................................................... 76 Appendix II ............................................................................................................................................ 80 IVR Designer ..................................................................................................................................... 80 II.1 Usage of Nodes ...................................................................................................................... 80 II.2: Events Descriptions ............................................................................................................... 93 II.3: Other IVR Components .......................................................................................................... 93 II.4: Some Special Cases .............................................................................................................. 94 Appendix III ........................................................................................................................................... 95 Configuring Polycom Phones with DACX Ameyo - On-Phone Configuration ................................... 95 III.1: Setting up IP Address manually ............................................................................................ 95 III.2: Setting up SIP Extensions manually ..................................................................................... 95 III.3: Changing the Setting of Digitmap ......................................................................................... 95
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
-6-
Drishti-Soft Solutions
Section 1 Overview
DACX Ameyo (Professional) is an all-in-one communications solutions for the contact centers. Coupled with the following features, Ameyo stands out in delivering the best to its clients: Scalable and Stable: Ameyo is built on a highly scalable and stable communications platform to contact centers. It has undergone rigorous testing for scalability and stability. Whether your contact center has 50 agents or 500 agents or more. Ameyo can scale up to your requirements. Supports a pure IP Environment: The IVR (Interactive Voice Response) solution works seamlessly with underlying TDM (Time Division Multiplexing), as well as VoIP technology, with minimal hardware and so you can skip the expenditure on expensive hardware. Thus, Ameyo delivers huge savings in your total cost of ownership. Flexible: Ameyo is a highly flexible solution designed to adapt to your chosen environment. Whichever network (IP, E1/T1, TDM), or phones (IP Phones, softphones, analog phones) or hardware (P4, Xeon) you use, the dialer can be configured to work for the same. 1. Optimum voice quality: Ameyo has been optimized to provide the required voice quality even in low bandwidth conditions. In addition, the quality of the voice is maintained in multi-party conferencing, snooping, barging etc. to ensure a positive experience for the dialed person. 2. Predictive Dialer: Ameyos Predictive Dialer (PD) uses a complex algorithm to pace calls based on number of outgoing lines, and number of agents etc. The result is maximum efficiency of the agents and a controlled idle time. 3. Supervision: Ameyo enhances the productivity of managers and supervisors by providing a simple, quick and interesting interface for campaign management as well as user management. 4. Reporting: Ameyo provides a comprehensive reporting functionality which helps you to analyze and improve the performance of your contact center.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
-7-
Drishti-Soft Solutions
1.3 Workbench
Workbench is the work area where all the customer interaction takes place. Ameyos Agent Workbench incorporates predictive as well as preview dialing providing flexibility as per the requirement. Workbench is an integrated interface that provides utmost ease and flexibility in dialing. The agents can transfer calls to other users in the application or any third party telephone. The agents can also conference any third party and can either participate in the call or transfer the call and return to the running application. The agents can put a call on hold through their interface. The agents can schedule callbacks at the time of disposing the call. The agents can also converse with one another as well as with the administrators and supervisors.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
-8-
Drishti-Soft Solutions
2.1 Settings
1. The Settings tab allows you to map the phone device with the respective agents machine. 2. Select the Mapper Type for the system, from the drop-down menu of the Contact Center Voice Settings field. 3. For the configuration of the mappers select the respective mapper from the Phone Mappers field and you can view the following information. a. IP Address: Refers to the IP address of the agents machine. b. Phone: Refers to the Identification of the phone on the PBX or IP-PBX c. Call Context Settings: Refers to the Service Provider or the softphone configuration in PBX / IP-PBX 4. To / add / edit / delete the mappings, click on the Add / Edit / Delete button. 5. Knowledge Base URL is the URL that the user can set for the contact center. This URL would be visible under the Knowledge Base tab of the agent workbench.
6. You can view the different break reasons for agents under the Break Reasons list. To add / delete a break reason click on the Add / Delete button.
2.2 Routing
The Routing tab allows you to configure call routing policies and profiles.
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
Confidential
-9-
Drishti-Soft Solutions
2.2.1 Policies
By clicking on the Routing tab, the window appears as shown in Fig 2.2.1. You can see the list of policies and their type. Type refers the channel of the VoIP provider. It is based on the dialers contact number and the receivers number.
1. To modify the name of the policy, click on the Policy Name field. 2. To add a policy, click on the Add button.
3. To assign profiles to the policy, click on the Assigned Profiles tab. The window appears as shown in Fig 2.2.2. 4. Select the profile from Available list and click on the > button. 5. To remove a profile, select the profile from the Assigned list and click on the < button.
2.2.2 Profiles
By clicking on the Profiles tab, the window appears as shown in Fig 2.2.3. You can see the list of profiles and their type.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 10 -
Drishti-Soft Solutions
1. To modify the name of the profile, change the name in the Profile Name field. 2. To add a profile, click on the Add button.
3. Click on the Profiles Plan tab to choose Action Type, Sub Action and Destination for the profile plan. 4. To add a profile plan, click on the Add Plan button and specify the necessary information. 5. To delete a profile plan, click on the Delete Plan button.
2.3 Dispositions
The Dispositions tab allows you to configure call disposition plans.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 11 -
Drishti-Soft Solutions
2. To add a disposition class, click on the Add button above the list. A window pops up as shown in Fig 2.3.2. Enter the class name and then click on the OK button. 3. To delete a disposition class, select a disposition class from the list and then click on the Delete button. 4. Under the General tab, you can view the list of disposition codes of the selected disposition class.
5. To add a disposition code, click on the Add button at the top right. A window pops up as shown in Fig 2.3.3. Enter the code and then click on the OK button. 6. To edit a code, click on then Edit button and modify the code name. 7. To delete a disposition code name, select a disposition code from the list and then click on the Delete button.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 12 -
Drishti-Soft Solutions
2. To add a disposition plan, click on the Add button above the list. A window pops up as shown in Fig 2.3.5. Enter the disposition plan name, check on the checkboxes for the desired features and then click on the Finish button. 3. To delete a disposition plan, select a disposition plan from the list and then click on the Delete button.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 13 -
Drishti-Soft Solutions
2.4 Filters
Not all the customer data needs to be used always, when contacting the customers. There might be some rules according to which you need to filter the data and use the selective records only. This can be accomplished by defining appropriate Table Filter(s). These filters can then individually be enabled or disabled as per the requirements. 1. Click on the Filters tab to view all the filters and their respective OR Clauses and AND Clauses as shown in Fig 2.4.1.
2. To add a table filter, click on the Add button. A window pops up a shown in Fig 2.4.2. 3. Enter a filter name and select the type of campaign. Then click on the Next button. The window appears as shown in Fig 2.4.3. Enter the OR Clauses and AND Clauses and click on the Finish button.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 14 -
Drishti-Soft Solutions
4. To edit /delete a table filter, select a table filter and then click on the Edit / Delete button. 5. To enable or disable the filter, click on the Enable / Disable button.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 15 -
Drishti-Soft Solutions
2.For blending Campaign settings, the user can feed the average wait time, Variance factor, Minimum Agent and Maximum Agent, under the General button as shown in Fig 2.5.2.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 16 -
Drishti-Soft Solutions
3.For Reloading Configurations like Metric, Processing, Logging, License and System parameter, the user can click on Advanced Options as shown in Fig 2.5.3.
2.6 Skills
Using this feature the administrator can assign different skills. 1.Click on the Skills tab. Click on Add button to add skill name and description, as shown in Fig 2.6.1.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 17 -
Drishti-Soft Solutions
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 18 -
Drishti-Soft Solutions
2 Click on the Skill Levels tab to assign skill levels and weightage as shown in Fig 2.6.2
3 Click on the Users tab to select from available user ids and assign skills to them, as shown in Fig 2.6.3
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 19 -
Drishti-Soft Solutions
3.1 Users
The following section elucidates the process of adding / deleting a user. 1. The window displays general information about all the users. 2. To view / edit details of a user, select the user. The respective information will be visible on the right under the General tab. After making the desired modifications (in the User Name and Description, click on the Apply button to commit the changes or on the Refresh button to roll back to the previous settings.
3. To add a user, click on the Add button. A window pops up as shown in Fig 3.1.2. Assign a user ID, enter the user name, generate password and specify the role of the user as shown in Fig 3.1.2.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 20 -
Drishti-Soft Solutions
4. Then click on the Next button. A window pops as shown in the figure below. Here you can see a list of all the campaigns.
5. To assign a campaign to the user, select a campaign from the Available Campaigns column and click on the > button. Then click on the Finish button. 6. To remove a user from the campaign, select a user from the Assigned Campaigns column and click on the < button.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 21 -
Drishti-Soft Solutions
4.1 Campaigns
The following section elucidates the process of adding / deleting a campaign. 1. The window displays general information about all the campaigns. 2. To view / edit details of a campaign, select the campaign. The respective information will be visible on the right under the General tab. After making the desired modifications (in the Campaign Name and Description, click on the Apply button to commit the changes or on the Refresh button to roll back to the previous settings.
3. To add a campaign, click on the Add button. A window pops up as shown in Fig 4.1.2. Assign a name in the Campaign Name field, select the type in the Campaign Type field (Interactive Voice Application for inbound campaign and Outbound Voice Campaign for outbound campaign) and write some remarks in the Description box and then click on the Next button. The window appears as shown in Fig 4.1.3.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 22 -
Drishti-Soft Solutions
4. To assign a user to the campaign, select the user from the Available Users and click on > button. 5. To remove a user from the selected campaign, select the user from the Campaign Users and click on < button.
6. Click on the next button. The window appears as shown in Fig 4.1.4. a. Preview URL: The URL used for Preview Dialing. b. CRM URL: Enter the CRM URL, e.g., http://ip/dcrm/10.10.2 c. Peak Call Count: In this field, you have to specify the maximum number of simultaneous calls, which the dialer should dial for a particular campaign. The dialer will never exceed this value. d. Caller Id: Call identification number for the customer. e. Wrap Timeout: Time taken by an agent to dispose the call and be available for the next call. f. Number of Last Calls: The number of last calls for which the information in available for supervision.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 23 -
Drishti-Soft Solutions
g. Enable AMD: Checking this implies that Answering Machine Detection is turned on. (The dialer would not throw the calls that are answered by an answering machine to the agents). h. File Format: Format of the voice log (In which recording is to be done) i. Voice Logs Enabled: Check on this if voice logs in this campaign are to be recorded j. Dial Phone Enabled: Check this in order to activate manual dialing.
7. Click on the next button. The window appears as shown in Fig 4.1.5. This is the window where the outgoing trunk for manual dialing as well as conference dialing to be used for the campaign is to be defined. a. Minutes: It refers to the Minute / VoIP provider. b. Setup Timeout: It refers to the maximum time till when the dialer will try any specific number. If the time expires and the number does not get connected, then it is treated as No Answer. c. Ringing Timeout: It refers to the maximum time that the dialer should allow any dialed number to ring, before assigning the Failed or No Answer status. When this time expires, then dialer may retry that number after some point of time, depending upon the settings of Setup timeout and retry times. d. User Profiler: It refers to an algorithm, which determines ringing timeout in runtime to get the highest pacing. It should be checked only if the minutes you are using are considered to be good minutes.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 24 -
Drishti-Soft Solutions
8. To delete a campaign, select the campaign from the list and then click on the Delete button.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 25 -
Drishti-Soft Solutions
1. You can view the available call contexts under the Call Context tab (Fig 4.3.1). 2. To assign a call context to the selected campaign, select a call context from the Available list and click on the > button. 3. To remove a call context to the selected campaign, select a call context from the Assigned list and click on the < button. 4. Then click on the Apply button to commit the change or on Refresh to roll back the changes.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 26 -
Drishti-Soft Solutions
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 27 -
Drishti-Soft Solutions
1. Select a feature from the Features list and you can see the respective information about its feature contexts in the right panel. 2. To add a feature context, click on the Add button. A window pops up as shown in Fig 4.5.2. Enter the name of the context in the Name field and upload the nodeflow in the Node Flow field. To upload the nodeflow, specify the directory path from the Browse button and click on the Upload button. 3. Then click on the Apply button. 4. To delete a feature context, select the feature context and click on the Delete button.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 28 -
Drishti-Soft Solutions
2.Configuring campaign CRM configuration file. User can upload numbers from Ameyo interface into Ameyo database as well as CRM database.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 29 -
Drishti-Soft Solutions
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 30 -
Drishti-Soft Solutions
2. User Mapping: To map users to the selected lead. a. Select a campaign and then click on the User Mapping tab. The screen appears as shown in Fig 5.1.2. b. To assign users to the campaign, select users from the Available and click on the > button. c. To remove a user from the selected campaign, select the user from the Assigned and click on < button. d. Click on Apply to commit or click on Refresh to restore previous state.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 31 -
Drishti-Soft Solutions
3. To create a lead Id, click on the Add button. To upload the file in the lead, click on the Choose Lead button and browse the required CSV file and click on the Upload File button. 4. In order to assign or modify Time Zone for a particular lead, click on the TimeZone button and select the required time zone from the drop-down menu.
5. To add a customer directly to a lead, click on the Add Customer button. A window pops up as shown in Fig 5.1.4. Here you can add details such as the timezone and upto three contact numbers of the customer.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 32 -
Drishti-Soft Solutions
Confidential
- 33 -
Drishti-Soft Solutions
Disposition: Displays the disposition of the calls Count: Displays the number of calls within the respective lead with reference to the particular status and disposition.
5.2.2 Fetch
In case, the outcome of a campaign is not satisfactory, there is a need to retry the numbers in different order. To facilitate this, Ameyo allows the users to fetch data as per different criteria and further churn it. Click on the Fetch button (Fig 5.2.1). The screen appears as shown in Fig 5.2.3. Campaign Id: Displays the campaign Id Customer Id: Displays the customer Id Date Modified: Displays the date on which the particular number was last modified. Last Churn Date: Displays the date on which the number was last churned. Last Dialed: Displays the date on which the number was last dialed. Last Disposition: Displays the disposition of the call. Last Status: Displays the last status of the call. Num Attempts: Displays the number of times the number was dialed. Phones: Displays the phone number(s) of the respective customer. Time Zone: Displays the time zone of the respective customer. You can select the desired number (s) and then click on the Churn button (at the top right of the Lead Details table) to retry the numbers. Or you can save the numbers data by clicking on the Extract button. Or you can remove customer(s) by clicking on the Remove Customer(s) button.
5.2.3 Churn
Churn (at the top right of the Selections panel in Fig 5.2.1) to directly churn the numbers without viewing the particular numbers.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 34 -
Drishti-Soft Solutions
1. Click on the Excluded Dispositions tab to the right of the Number Management tab. The window appears as shown in Fig 5.3.1. 2. The window allows the user to select the desired disposition parameters that should be excluded from churning. For example, a sale disposition need not be churned and therefore it can be marked as excluded disposition. 3. Click on the Apply button to commit or on the Refresh button to roll back to the previous settings.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 35 -
Drishti-Soft Solutions
6.1 Queue
The following section elucidates the process of adding / deleting a queue. 1. The window displays general information about all the queues. 2. To view / edit details of a queue, select the queue. The respective information will be visible in the right panel under the General tab. After making the desired modifications (in the Queue Name, Queue Priority, Queue Type, Schedular Type and Description, click on the Apply button to commit the changes or on the Refresh button to roll back to the previous settings.
3. To add a queue, click on the Add button. A window pops up as shown in Fig 6.1.2. Assign a name in the Queue Name field, assign priority in the Queue Priority field, specify the Queue Type, specify the Schedular Type and write some remarks in the Description box and then click on the Next button. The window appears as shown in Fig 6.1.3.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 36 -
Drishti-Soft Solutions
4. To assign a user to the queue, select the user from the Campaign Users and click on > button. 5. To remove a user from the selected queue, select the user from the Queue Users and click on < button.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 37 -
Drishti-Soft Solutions
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 38 -
Drishti-Soft Solutions
7.1 Dialing
1. After logging in, the agent has to make himself available for calling by clicking the Ready button in the bottom left panel of the screen. Now the agent will start getting calls from the system. In case of an inbound campaign, the ACD will direct incoming calls to the agents and in case of an outbound campaign, the dialer would throw calls to the available agents. 2. The agent can also dial a number manually in the following way. a. Enter the number in the Number field. b. Click on Dial Customer.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 39 -
Drishti-Soft Solutions
You can select the number and dial it manually by clicking on the Dial Customer button or you can preview information regarding the customer and then dial the number. d. To preview customer information, click on the Customer CRM tab button. The information gets displayed under the Customer CRM tab (Fig 7.1). 3. If the agent has to take a break, then click on the Ready button again and it would turn to the Break button. 4. If the agent wants to logout from the dialing session, then click on the Logout button.
c.
2. To put the call on hold, click on the Hold button (Fig 7.3.1). 3. To transfer the call to a third party and disconnect the call from your end, click on the Transfer Call button. The screen appears as shown in Fig 7.3.2. Enter the number in the Number field and then click on Transfer to Phone. By transferring the call, the ownership of the call is also transferred. You may transfer the call while in conference.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 40 -
Drishti-Soft Solutions
4. To enter into a conference with the customer and a third party, click on the Confer button (Fig 7.3.1). The screen appears as shown in Fig 7.3.3. Enter the number in the Number field and then click on Confer with Phone. The ownership of the call rests with the agent until he transfers the call.
5. By clicking on the IVR button (Fig 7.3.1), the call gets routed to the customer through the verifier (a third-party, who assists in the conversation between the agent and the customer in order to close a deal). 6. To disconnect the call from your end, click on the Hangup Self button (Fig 7.3.1). (In case the call was a conference, the agent gets out of the conference by clicking on this button while the remaining parties are still into conversation). 7. To disconnect the customer from the call, click on the Hangup Customer button (Fig 7.3.1). (In case the call was a conference, the customer gets out of the conference while the remaining parties are still into conversation). 8. To disconnect the ongoing conferences, click on the Hangup Confer button (Fig 7.3.1). 9. To set the disposition of the call, click on the Force Dispose button (Fig 7.3.4) and set the disposition.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 41 -
Drishti-Soft Solutions
10. To set call back, click on CallBack. A window pops up as shown in Fig 7.3.5.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 42 -
Drishti-Soft Solutions
4. To edit / delete any of the callback listed from the table, select the respective row and then click on the Edit / Delete button.
Call Id: Displays the Call Id Campaign Id: Displays the campaign Id Lead Id: Displays the lead Id Customer Id: Displays the Customer Id Phone: Displays the phone number of the customer Call Type: Displays whether the call was inbound, outbound autodial or manual dial. Dialing Comments: Displays remarks / comments about the customer, in case the agent was supposed to enter any. Call Result: Displays whether the call was connected or not, i.e, was it a Success or a Failure. Status: Displays the status of the call, whether the call was Call_Drop / Attempt_Failed / Number Invalid / AMD / Busy Recording File: Displays the name of the respective voice log. Setup Time: Displays the total time taken to setup the call. Ringing Time: Displays the time for which the call was ringing. Talk Time: Displays the talk time of the call. Disposition: Displays the disposition of the call. User: Refers to the user to which the call was connected to. Hangup Cause: Displays the Hangup cause of the call with respect to the performance of the Telephony service. Date Added: Displays the date on which the voice log was added.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 43 -
Drishti-Soft Solutions
7.7 Users
Apart from the customer user interaction, Ameyo allows all the users to interact amongst themselves for assistance and supervision. By clicking on in the bottom left corner, a window pops up as shown in Fig 7.7.1. The table provides the information about all the users and their status. 1. To converse with another user, select the user from the table and then click on the Dial User button in the bottom left of the window.
2. 3.
To chat with another user, select the user from the table and then click on the Chat button in the bottom left of the window. To send a common message to all the users, click on the Broadcast button in the bottom left of the window.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 44 -
Drishti-Soft Solutions
You may then select a particular campaign and view the corresponding statistics in the right panel. In order to give full screen space to the view of the right panel, right click on the Professional Monitoring View tab and click on Fast View as shown in Fig 8.2.
After selecting the desired campaign, the screen appears as shown in Fig 8.1.1.
8.1 Status
To start dialing, click on the Run button at the bottom left corner. The red button in front of Dialing will turn green.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 45 -
Drishti-Soft Solutions
Is working?: Displays whether the user is part of the campaign resource management i.e., whether he will receive calls for that campaign or not. On Hold: Displays whether the call is on hold or not. Number of Calls: Displays the total number of users who are party to the active call. For example if its a conference between an agent, customer and the supervisor, the value for Number of Calls would be 3. Connected To: Displays the number to which the agent is connected to. Status Duration: Refers to the time duration with respect to the last status change.
The following buttons allow the supervisor to perform certain actions on the agents of the campaign: Confer The feature enables the supervisor to enter into a three-way conference with the agent and the customer. It implies that the three of them can talk to and listen to each other. The supervisor can start as well as end the conference from this screen. Barge The feature enables the supervisor to jump into a running call. When an agent is having trouble with a customer or the customer asks for the supervisor, the supervisor can easily connect in between the call and disconnect the agent from the call in order to solve the problem. By barging in, the supervisor becomes the owner of the call i.e., he can dismiss others in call or hold or hang them up, whereas the agent looses the ownership of the call. Snoop The feature enables the supervisor to listen to the call and guide the agent (how to handle the call) without the customer being able to hear their conversation. The customer only hears the voice of the agent (not the supervisor). Hangup The supervisor can forcefully hang-up a call, which is being handled by an agent by clicking on the Hangup button on the right hand panel of the screen.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 46 -
Drishti-Soft Solutions
8.1.5 Minutes
The Minutes tab displays minutes summary about the campaign as shown in Fig 8.1.2. Avg. Call duration (sec) - It refers to the average duration of a call in a campaign. Post Dial Delay (ms) - It refers to the time duration from when the dialer connects a number and the time it is actually picked up by an agent. Ans Seizure Ratio (%) It refers to the percentage of successfully answered calls divided by the total number of calls attempted (seizures). Campaign Hangup Summary: It displays the number of calls with respect to their respective status codes.
8.1.6 Conferences
The Conferences tab displays general information about the ongoing conferences and its members in a campaign as shown in Fig 8.1.3. If you double click on the conference ID, you can also see the member details.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 47 -
Drishti-Soft Solutions
Call Id: Refers to a unique Call Id. Phone: Displays the phone number to which the call is connected to. Start Time: Displays the start time of the call Talk Time: Displays the time duration for which the agent was interacting with the customer. Call Type: Displays whether the call is an outbound manual dial / callback / auto dial or an inbound call. Status: Displays the status of the call, whether the call was Call_Drop / Attempt_Failed / Number Invalid / AMD / Busy Disposition: Displays the disposition of the call, whether the call was a Sale / Callback / Not interested etc.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 48 -
Drishti-Soft Solutions
Hangup Cause: Displays the Hangup cause of the call with respect to the performance of the Telephony service. Hangup Cause Code: Displays the codes that are mapped with respective Hangup Causes.
2. After choosing the desired set from the Selections panel, click on the Fetch button.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 49 -
Drishti-Soft Solutions
The output displays the following information: Call Id: Refers to the Call Id. Campaign Id: Refers to the Campaign Id. Lead Id: Refers to the Lead Id. Customer Id: Refers to the Customer Id. Phone: Displays the number to which the call was connected to. Call Type: Displays whether the call is an outbound manual dial / callback / auto dial or an inbound call. Dialing Comments: Displays remarks / comments about the customer, in case the agent was supposed to enter any. Call Result: Displays whether the call was connected or not, i.e, was it a Success or a Failure. Status: Displays the status of the call, whether the call was Call_Drop / Attempt_Failed / Number Invalid / AMD / Busy Recording File: Displays the name of the respective voice log. Setup Time: Displays the total time taken to setup the call. Ringing Time: Displays the time for which the call was ringing. Talk Time: Displays the talk time of the call. Disposition: Displays the disposition of the call. User: Refers to the user to which the call was connected to. Hangup Cause: Displays the Hangup cause of the call with respect to the performance of the Telephony service. Date Added: Displays the date on which the voice log was added. 3. The supervisor can select the desired voice log and click on Listen to listen to or on Download to save the voice logs.
8.4 Settings
1. 2. Basic Settings (Refer to Section 4.1) The right hand side of the Fig 8.4.1 shows the Minutes Provider and the Ringing Timeout for Manual Dial Profile Settings, Confer Dial Profile Settings and Auto Dial Profile Settings.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 50 -
Drishti-Soft Solutions
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 51 -
Drishti-Soft Solutions
2. Retry Time Settings: It displays the time duration after which the dialer will retry for those numbers, which do not get connected in the first attempt. Refer to Fig 8.5.3, Retry Time Settings. The value 03:00:00 corresponding to No_Answer implies that all those numbers for which there was no answer were redialed after 3 hours. 3. Progressive Algo Settings: a. Peak CC: Specify the maximum number of simultaneous calls, which the dialer should dial for a particular campaign. b. Max Pacing Ratio: The parameter controls the ratio of dialed calls to the free agents. A higher value implies an increase in the number of dialed calls. 4. Dialer Settings a. Min Cache Size: Specify the number of customers that the dialer would refer to at a particular time, from the database. b. Fetch Size: Specify the number of customers / calls for which the information can be fetched at a particular time.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 52 -
Drishti-Soft Solutions
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 53 -
Drishti-Soft Solutions
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 54 -
Drishti-Soft Solutions
2. Set the following parameters: a. Default Self Callback If enabled, it implies that the dialer would throw the callback to the same user who disposed the call as callback. b. Max Callback Days Number of days after which the callback would be deleted. c. Promote to Campaign expiry Time It refers to the number of days after which the Self Callback (if not attended by the respective agent) will get expired and transferred to the campaign (i.e. it can then be directed to any other agent of the campaign). d. Callback Retry Time Number of times that the dialer should retry the number incase it failed at the time of attempting callback. e. CallBack Reminder: Number of days after which the Callback would be reminded to the user. 3. Click on the Apply button to commit or on the Refresh button to reject.
8.8.1 General
1. Select an exclusion lead from the Exclusion Leads list and you can see the respective ID and name in the right panel. To enable / disable the exclusion lead, check / uncheck the Enable checkbox.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 55 -
Drishti-Soft Solutions
1. To add an exclusion lead, click on the Add button on the top right of the exclusion leads list. A window pops up as shown in Fig 8.8.2. 2. Enter a name in the name field and click on the OK button. 3. To delete an exclusion lead, select a lead from the Exclusion Leads list and click on the Delete button.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 56 -
Drishti-Soft Solutions
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 57 -
Drishti-Soft Solutions
All the available call context policies assigned to the campaign are listed under the Call Context Policy tab as shown in Fig 8.9.1. You can view these policies in the drop down menu of the different Dial Profile Settings under the Settings tab. Refer to Fig 8.9.2.
1. To add a call context policy, click on the Add button as shown in Fig 8.9.1. A window pops up as shown in Fig 8.9.3. 2. You can select whether you want to create a single call context policy or a policy with multiple contexts from the drop-down menu of the Policy Type field. 3. Then specify the name of the policy.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 58 -
Drishti-Soft Solutions
4. Afterwards, you can choose the call contexts from the Available list and assign to the policy by clicking on the > button. 5. In case you created a policy with multiple call contexts, the Campaign Call Contexts tab would be displayed to the right of the General tab as shown in Fig 8.9.4. Here you can see the list of al the available call contexts as well as the ones which you had assigned to the policy during step 4. You can assign other call contexts or remove the assigned call contexts from the selected multiple call context policy.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 59 -
Drishti-Soft Solutions
2. To add a prompt, click on the Add button. A window pops up as shown in Fig 8.12.2. Enter the name of the prompt in the Name field and the name of the file in the File Name field. Specify the directory path in the Select Path field and click on the Finish button. 3. To modify a prompt, click on the Modify button and make the desired changes.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 60 -
Drishti-Soft Solutions
2. To add an audio file, click on the Add button. A window pops up as shown in Fig 8.12.4.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 61 -
Drishti-Soft Solutions
3. To add a voice resource, click on the Add button. A window pops up as shown in Fig 9.1.2. Assign a name in the Voice Resource Name field, select the type in the Voice Resource Type field and write some remarks in the Description box and then click on the Next button. The window appears as shown in Fig 9.1.3. [Note: You can only proceed after you select the type of voice resource. You may also add a particular type of voice resource from the respective interface of that voice resource (in this case it is the Asterisk Voice Resource). 4. Fill in the relevant details and then click on the Finish button. 5. To delete a voice resource, select the voice resource from the list and then click on the Delete button.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 62 -
Drishti-Soft Solutions
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 63 -
Drishti-Soft Solutions
3. To add a call context, click on the Add button. A window pops up as shown in Fig 9.1.5. o Allow Incoming: Allow incoming calls using the selected call context. If not set, then the incoming calls on this call context would be automatically rejected. o Allow Outgoing: Allow outgoing calls using the selected call context. If not set, then the request for outgoing calls on this call context would be rejected. o Is Local: Whether the selected call context is 'Local', e.g. a SIP phone. VoIP providers are examples of call context which are usually not to be set as 'Local'. 4. To delete a call context, select the call context and then click on the Delete button. 5. Click on the Apply button to commit the changes or on the Refresh button to roll back to the previous settings.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 64 -
Drishti-Soft Solutions
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 65 -
Drishti-Soft Solutions
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 66 -
Drishti-Soft Solutions
2. Mgr Port Number: (Default 5038) The port number on which Asterisk Manager is listening for control connections 3. Username: (Default: ameyo). The username to be used to connect to the Asterisk Manager 4. Password: (Default: dacx) 5. Extension Configuration: Configuration to be appended to the Asterisk extension.conf (apart from the standard configuration). Configuration format is same as Asterisk extensions.conf. 6. Global SIP Configuration: Global configuration to be prepended in sip.conf to the SIP entity configurations (defined separately). Parameters like default context, bindaddr (The address to listen to for SIP requests), bindport (The port to listen to for SIP requests), disallow (the disallowed codecs), allow (the allowed codecs) are to be defined here. 7. Trunk Groups: 8. Global Zap Channel Configuration: ZAP Configuration applicable to all ZAP channels in all groups. Can be overridden by specifying custom configuration for a channel (from ASTERISK_ZAP_CHANNEL entity) 9. Number of Spans: Number of simultaneous trunks that can be connected to the ZAP hardware in use. 10. Trunk Type: Carrier type of each trunk currently connected to the ZAP hardware in use. Supported types: E1, T1.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 67 -
Drishti-Soft Solutions
1. SIP Entity Name: The name given to the entity. This name is used to identify the entity while defining a Call Context. 2. SIP Context: Same as the Asterisk SIP Context. Used by Asterisk in the names of the channels. 3. Port: The port on which to contact the SIP entity. (Usually 5060) 4. Hostname: The hostname or IP address on which to contact the SIP entity. 5. From Domain: Sets default From: domain in SIP messages when contacting the SIP Entity 6. NAT Supported: Whether or not NAT (Network Address Translation) is supported on the SIP Entity. (Usually set as No) 7. Can Reinvite: Whether or not the SIP Entity is able to support SIP Reinvites. (Usually set as No) 8. DTMF Mode: DTMF mode supported by the SIP Entity. (Usually rfc2833) Possible values:a. rfc2833 b. inband c. info 9. Number RE: The Number Regular expression to use when requesting a channel to Asterisk. The RE uses the '${VARIABLE_NAME}' format to refer to replaceable variables. The variables available are:d. NUMBER: The value is the actual number that has been requested to be dialed.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 68 -
Drishti-Soft Solutions
e. PROVIDER: The value is the SIP Context that was provided above. Examples:i. To request a channel to a SIP phone. SIP/${PROVIDER} ii. To request a channel to a SIP based VoIP provider (No prefix). SIP/${NUMBER}@${PROVIDER} iii. To request a channel to a SIP based VoIP provider (With '1234' as prefix). SIP/1234${NUMBER}@${PROVIDER} 10. Username: The username to be used for authentication with the SIP entity 11. Password: Set a password. 12. Custom Config: This field is used to configure parameters that are not controlled by any of the above configuration options. Eg: allow, disallow, fromuser, insecure. This is a free text field and care must be taken while making changes.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 69 -
Drishti-Soft Solutions
Section 10 Reports
Reports are generated via Ameyo Control Panel (ACP). You can generate a variety of reports to gauge the efficiency of the contact center resources and agents. After logging into ACP, you can access the user-friendly reporting interface. The report model adopted is explained in the following sections: 10.1 Report Settings 10.2 Report Categories
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 70 -
Drishti-Soft Solutions
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 71 -
Drishti-Soft Solutions
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 72 -
Drishti-Soft Solutions
Report
CRM Reports
User Disposition
Also, the inputs under Report Duration for this Report Category consists of two fields viz. Start Date and End Date. After providing the inputs, click on View (to see output on the screen) or Download (if you want you save the report in .csv format).
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 73 -
Drishti-Soft Solutions
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 74 -
Drishti-Soft Solutions
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 75 -
Drishti-Soft Solutions
11.1: Logging
This feature allows the user to reload the changes implemented on the Ameyo Server, without having to restart the server.
11.2: License
This tab provides the user with information related to product license.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 76 -
Drishti-Soft Solutions
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 77 -
Drishti-Soft Solutions
Appendix I
This section provides step by step instructions for routine tasks such as adding an agent, uploading a lead, fetching voicelogs, generating reports, managing dialing and daily monitoring.
Users General
9. To add an agent, click on the Add button. A window pops up as shown in the figure below. Assign a user ID, enter the user name, generate password. From the Description drop-down menu, select Agent.
Add User
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 78 -
Drishti-Soft Solutions
10. Then click on the Next button. A window pops as shown in the figure below. Here you can see a list of all the campaigns.
Assign Campaign
11. To assign a campaign to the user, select a campaign from the Available campaigns column and click on the > button. Then click on the Finish button.
Lead Management
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 79 -
Drishti-Soft Solutions
1. To create a lead Id, click on the Add button. A window pops up as shown in the figure below. Specify the lead name in the field provided.
Add Lead
2. To upload the CSV file in the lead, select the lead. 3. Then click on the Browse button as shown in the figure below, specify the directory path and click on the Upload File button. 4. For more details regarding lead management, refer to Section 5 Number Management.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 80 -
Drishti-Soft Solutions
agents, the leads, customer status, time duration, or disposition status for which he wants to fetch the voice logs.
2.
Thenafter, click on the Fetch button to view the voice logs as shown in the figure below. A window pops up as shown in the figure below. A supervisor can select a voice log and click on the Listen button to listen to it. The supervisor can also download the voice log by clicking on the Download button.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 81 -
Drishti-Soft Solutions
2. 3.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 82 -
Drishti-Soft Solutions
4.
Apart from the General settings, the supervisor configures the basic dialing parameters such as the Predictive Also Settings, under the Dialer Configuration tab as shown in the figure below.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 83 -
Drishti-Soft Solutions
Dialer Configuration
5. 6. 7.
For more details about the dialer configuration, refer to section 8.5. After the necessary configurations, the supervisor can initiate dialing by clicking on the Run button in the bottom left corner of the Status tab. The red dot turns green as the dialing starts. When the campaign is in process the supervisor monitors the status. He can monitor the status from the details given under the different panels of the Status tab as shown in the figure below. For example the Minutes tab in the bottom left panel shows key parameters such as the Average talk time, Post Dial Delay and Answer Seizure Ratio.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 84 -
Drishti-Soft Solutions
Monitor Status
8.
The Last Calls tab displays general information about the status and disposition of the last calls of the campaign as shown in the figure below. For more details about the Status, refer to section 8.1.
Last Calls
9.
After monitoring the status, the supervisor can make required modifications in the Settings or Dialer Configuration. He can modify call pacing ratio, change profile settings etc.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 85 -
Drishti-Soft Solutions
Appendix II
IVR Designer
IVR Designer is a powerful tool that is used to design IVR call flows for inbound campaigns. In this section you will learn about the functions and uses of different nodes and details about their attributes and events.
Attribute
crmurl
variablesString
dataProviderType
It refers to the http address of the CRM server. If specified, it will be overriding the crm url specified in respective campaign settings. It refers to the extra parameters that are to be passed with CRM url. For example we want to display the digit pressed by customer in the CRM url., to do this we need to store the digit pressed in a variable and use this variable in the CRM node. customer.query.node.data.provider CRM url is successfully pushed to Client. CRM url can not be made with the specified data
Events
success Failure system.error
Customer Query This node is used to fetch customer info from the database. When the customer calls, it finds out whether the customer is listed in the database or not.
Attribute
dataProviderType crm.default.node.data.provider
Events
customer.query.customer.not.found customer.query.customer.found customer.query.multiple.customer.f ound customer.query.same.lead.multiple. customer.found customer.query.db.down system.error In this case the customer is not found in the database. In this case the customer is found in the database. In this case multiple customers of the same name are found in the database. In this case multiple customers of the same name are found in the same lead. In case the database server is down.
Originate CRT (Call Runtime) The node is used to originate connection between customers and users.
Attribute
ringTimeout
It refers to the time duration after which the call will be disconnected in case it has been ringing for the specified time.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 86 -
Drishti-Soft Solutions
setupTimeout
It refers to the time duration after which the call will be disconnected if the specified setup time expires. Setup time is the time from the initiation of the call request till the time it starts ringing. customer.originate.node.data.provider confered.entity.originate.node.data.provider user.originate.node.data.provider
dataProviderType
Events
call.leg.already.there verification.failed In case where entity has a valid call leg, i.e. contact with an entity which is already in the call. Verification is done pertaining to the prerequisites that should be met before an attempt to call is made. There could be n number of ways of verification. Verification can fail if an entity is already in a call or originate for that entity is not allowed. In case the call was not successfully connected. In case the call was successfully connected. In case there is no answer from the other end. In case dialing failed.
MakeCall This node is used to bridge multiple call legs and make a call.
Attribute
dataProviderType voice.campaign.make.call.node.data.provider In case the prerequisites for making the call were not met. In case any of the call legs hung up. In case the call was successfully made. In case the call was not successfully made.
Events
Play This node is used to play the voice prompt or any sequence of message files.
Attribute Events
It refers to the name of the audio file to be played. play.prompt.annc.node.data.provider In case the prompt was successfully played and listened to. In case the prompt was not successfully played. In case the call was hungup while the prompt was being played.
PlayTTS This node is used to play the output for the DTMF input from an inbound query. For example a bank account holder can enter his pin number and ask for the balance. In this case the system will fetch information from the relevant database and play TTS (Text to speech) to the customer.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 87 -
Drishti-Soft Solutions
Attribute
It refers to the text which is to be read out to the customer. It refers to the tts type. TTS can be text, number, time, digits, or characters. play.tts.node.data.provider In case the TTS was successfully played In case the TTS failed to play. In case the call was hungup while the TTS was playing. In case there is no call leg on which this transcription can be played.
Events
success.play.tts failure.play.tts hungup.play.tts no.call.leg.play.tts system.error
StartMonitor This node is used to start voice recording. Note: this should be always come once we have successfully connected the customer.
Attribute
recordingFormat recordingFilePattern
forceMonitor
dataProviderType
It refers to the format in which the voice logs are to be recorded. It refers to the pattern that will be put as a tag on the voice records. For example, a voice log file can contain either of agents name, agents ID, campaign name, time, customer details, call disposition etc. In case there is an issue in recording, then this attribute is used to forcefully initiate recording. If it is already recording then it would start recording again. customer.start.monitor.node.data.provider In case it is already recording. In case the recording was successfully done. In case the recording was not done successfully.
Events
start.monitor.already.monitoring success failure system.error
Attribute Events
SQL Query This node is used to execute SQL queries through the nodeflow. The outcome of the query is put in the nodeflow context for further processing in the nodeflow.
Attribute
queryString profileName
It refers to the sql string that is used for querying the database. The specified query would be executed. It refers to the profile that is configured in Ameyo to be used to create connection with the database.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 88 -
Drishti-Soft Solutions
It refers to the jdbc URL to connect to the database. It refers to the username to connect to the database. It refers to the password used to connect to the database. It specifies whether the query string is treated as a selection or an update query. It specifies whether to use Ameyo database or not. NA In case the query was successfully executed. In case the query could not be executed.
Events
sql.query.success sql.query.failure system.error
Script This node runs the TCL script specified in its script attribute.
Attribute Events
It refers to the TCL script to be executed NA In case the node was successfully processed. In case the node was not processed successfully.
Digit Collection This node is used for getting information from customer as DTMF digits. An appropriate prompt is played to customers and their feedback is stored in digitVariable, specified below, for further processing.
Attribute
It refers to the name of the variable to which the digits specified by customer are stored. It refers to the audio file that is to be played at the first instance. It refers to the voice prompt file that is to be played in case of a retry. It specifies the maximum number of acceptable digits after which the nodeflow will proceed further. It refers to the minimum number of acceptable digits for which the node will wait. It specifies the time duration after which the caller would not be able to enter the digits. It specifies the number of times the node will retry in case it was not successful. collect.digit.node.data.provider
In case the customer hung up the phone while the node processing was in progress.
Events
hungup.collect.digit success.collect.digit failure.collect.digit no-digits.collect.digit no-call.leg.collect.digit system.error In case the digits were successfully collected. In case the digits were not successfully collected.
In case there was no digit pressed as input by the customer.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 89 -
Drishti-Soft Solutions
ACD This is the most important node for calls distribution to agents. It is used to park the calls for a set of
agents. These sets could be agent queues. Then it finds out an agent who is available for taking a call and returns the agents ID. And then the call is transferred to that agent. While the ACD routes a call, it follows
intelligent routing algorithms as specified in the respective agent queues to connect customers to the most appropriate agent based different selection criterion like skill-based, LRU based etc.
Attribute
specificResourceAllowed
acdTimeout requestPriority
playSequenceNodeflow
extensionVariable
ivrDataVariables
It refers to the specific agent that has been assigned to undertake the respective call. For example in case of the some agent callback, the call is directed to that particular agent only. If the value of this value is false, then the call will be directed to the available agents of the campaign. And no specific agents queries can be requested in this ACD node. It refers to the time duration for which the ACD Node will try to get a free resource to serve the request. It refers to the priority levels for all the requests placed in an ACD node. In case there are 2-3 ACD nodes In a nodeflow, then users can assign different priority to requests of different ACD nodes. It refers to the message that is played during wait times. Cross sell and Up sell messages can be played when customers are waiting in call queues. It refers to the variable assigned to the possible extension to which the call is to be routed, this is applicable only in expert version. It refers to the variables that are used to show customer information to the agent. For example the sequence of digits that the customer has pressed during the call can be shown to the agent. default.acd.node.data.provider acd.aq.mapping.acd.node.data.provider agent.queue.based.acd.node.data.provider
dataProviderType
Events
timed.out failure hangup success system.error In case the specified time for the respective ACD node is expired. In case the node was not successfully executed. In case the calling party hungup the phone. In case the node was successfully executed.
SyncChildFlow This node is used to execute a sub-nodeflow in synchronization with the parent nodeflow i.e. parent nodeflow will wait for the child nodeflow to finish.
Attribute
childNodeflowModel timeout
It refers to the child nodeflow that is to be executed. It refers to the specified time duration until the node would be active. i.e. maximum time limit on child nodflow execution.
dataProviderType
Events
sync.child.flow.success sync.child.flow.failure sync.child.flow.timeout In case the nodeflow was successfully executed. In the nodeflow was not executed successfully. In case the nodeflow was timed out.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 90 -
Drishti-Soft Solutions
system.error
Sleep This node is used to halt the nodeflow for the specified duration.
Attribute Events
It refers to the time duration for which the nodeflow would sleep.
In case the node was successfully executed. In case the node was not successfully executed.
Hangup This node is used to hang up an active customer entity. IVR will still be running and does some tasks specified in the IVR flow.
Attribute Events
It refers to the specified time duration until the node would be active. hangup.customer.node.data.provider In case the customer was hungup successfully. In case the customer hungup had failed. In case the specified time expired. In case when customer callleg was not valid.
Customer Data If a customer is found using CustomerQuery Node then this node gets a particular attribute of the customer information into specified variable.
Attribute
dataVariable
columnName dataProviderType
It refers to the variable in which the read value of customers specified attribute will be set It refers to the column name of the customer information data.
Events
customer.data.variable.value.found customer.data.variable.value.not.found customer.data.variable.not.found customer.data.variable.failure system.error In case value is found for the specified column. In case no value is found for the specified column. In case the column was not found. In case if no customer info was set in the nodeflow context.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 91 -
Drishti-Soft Solutions
Attribute
dataProviderType amd.node.data.provider In case it a human voice, not answering machine. In case the customer hungup the call while the system was checking for AMD. In case the answering machine was successfully recognized. In case detection failed. In case the node was not successfully executed. In case the specified timeout for the node expired.
Events
human hangup.amd success.amd detection.failed.amd failure.amd timed.out system.error
DialNode This node is similar to OriginateCRTObject node only difference is that in this node one entity listens to the ring being played at other entity.
Attribute
ringTimeout
setupTimeout
It refers to the time duration after which the call will be disconnected in case it has been ringing for the specified time. It refers to the time duration after which the call will be disconnected if the specified setup time expires. Setup time is the time from the initiation of the call request till the time it starts ringing. user.dial.node.data.provider dial.node.data.provider customer.dial.node.data.provider
dataProviderType
Events
dial.failure dial.call.leg.already.there dial.verification.failed dial.failure.invalid.context dial.no.answer dial.dial.failed dial.busy In case the node was not successfully executed. In case there already existed a call leg. In case the prerequisite verification criteria were not met. In case dial is not supported on the call context. In case the dialed part did not answer. It case dial attempt failed. In case the number to be dialed was busy.
Attribute Events
It refers to the specified time duration until the node would be active.
In case the entity to which we were sending busy signal hungup the call. In case the node was not executed successfully. In case the busy signal was sent successfully.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 92 -
Drishti-Soft Solutions
In case the specified time for sending busy expired. In case call attempt has not been initiated for the entity to whom we want to send busy event.
RingingNode This node is used to send a ringing tone when the customer dials the contact center.
Attribute Events
It refers to the specified time duration until the node would be active.
In case the entity to which we were playing ringing has hungup. In case the ringing tone was not sent successfully. In case the ringing tone was sent successfully. In case the specified time for ringing expired. In case call attempt has not been initiated for the entity to whom we want to send ringing event.
TransferNode This node is used to transfer a call to other number / user ID or any other IVR number. Phone number and
IVR number can be any external number also, but they should have some appropriate outgoing entity for this.
Attribute
transferApplicationResponseRelation
keeptranferringEntityListenMode
dataProviderType
It means whether application response flag, i.e disposition is to be transferred to the target entity or not. If set to true then the agent to whom the call has been transferred will dispose the call. This parameter is added to give the option whether to keep the entity, who is transferring the call, only in listening mode. transfer.node.data.provider In case the call was successfully transferred. In case the call was not successfully transferred.
Events
success failure system.error
BargeNode This node is used to allow supervisors to forcefully barge into an interaction between the agent and a customer and making self the owner of the call. This feature is used in case the agent is not able to handle a query in an efficient manner.
Attribute
transferApplicationResponseRela tion
keepBargingEntitySpeakerMode
It means whether application response flag, i.e. disposition is to be transferred to the target entity or not. If set to true then the supervisor who is barging the call will be disposing the call. This flag is added to give the option whether to keep the entity, which has been barged, in speaking mode or not.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 93 -
Drishti-Soft Solutions
dataProviderType
barge.node.data.provider In case the supervisor was able to barge in. In case the node was not successfully executed.
Events
success failure system.error
SnoopNode This node is used to allow supervisors to snoop into an interaction between the agent and a customer without the knowledge of the agent.
Attribute
dataProviderType
Events
success failure system.error In case the node was successfully executed. In case the node was not successfully executed.
MusicOnHoldNode This node is used to play music to a call member when the call member is put on hold.
Attribute
dataProviderType music.on.hold.node.data.provider In case the music was successfully played. In case the music was not successfully played. In case the call was hungup when the music was played on hold.
Events
success.music.on.hold failure.music.on.hold hungup.music.on.hold system.error ResumeTalkNode This node is used to resume talking after the call is put on hold.
Attribute
dataProviderType resume.talk.node.data.provider In case the call was successfully resumed. In case the call was not successfully resumed. In case the call was hungup.
Events
success.resume.talk failure.resume.talk hungup.resume.talk system.error
DispositionClassRoutingNode This node is used to route the flow as per their disposition classes. Disposition classes associated with disposition codes are used in deciding the transition. There are 5 inbuilt disposition classes. User can create custom disposition classes. It will follow the transition disposition.unknown.disposition.class in that case.
Attribute
dataProviderType disposition.class.routing.node.data. provider In case the disposition class was
Events
disposition.shedule.callback
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 94 -
Drishti-Soft Solutions
disposition.add.campaign.customer.exclusion
disposition.add.process.customer.exclusion
disposition.add.campaign.media.exclusion
disposition.add.process.media.exclusion
disposition.unknown.disposition.class system.error
callback. In case the disposition class was customer exclusion from the campaign. Customer will not be called in the campaign. In case the disposition class was customer exclusion from the process. The customer will not be called in any of the campaign of the process. In case the disposition class was a media exclusion for campaign. The specified media contact will be put in the dnc list of the campaign. In case the disposition class was a media exclusion for process. The specified media contact will be put in the dnc list of the process and will not be dialed in any campaign of the proess. In case it was an unknown disposition class.
Attribute
dataProviderType disposition.call.back.node.data.provider In case a pop up was sent to the user to fill in the callback related information.
Events
success.disposition.callback system.error
DispositionCampaignCustomerDNCNodeModel This node is used to exclude a customer from a campaign. This means he will not be called in that campaign.
Attribute
dataProviderType disposition.campaign.dnc.node.data.provider In case the customer was successfully excluded from the campaign.
Events
success.disposition.campaign.exclusion system.error DispositionCampaignMediaDNCNodeModel This node is used to exclude the specified media contact from the campaign. This means that the media would not be chosen in that campaign to contact the customer.
Attribute
dataProviderType disposition.campaign.media.dnc.node.data. provider
Events
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 95 -
Drishti-Soft Solutions
DispositionProcessCustomerDNCNode This node is used to exclude the customer form all the campaigns of the process.
Attribute
dataProviderType disposition.process.dnc.node.data.provider In case the customer was excluded from all the campaigns of the process.
Events
success.disposition.process.exclus ion system.error
DispositionProcessMediaDNCNode This node is used to exclude the specified media contact from all the campaigns in the process. This means that the media would not be chosen in all the campaigns of the process to contact the customer.
Attribute
dataProviderType success.disposition.process.media. exclusion system.error disposition.process.media.dnc.node.data.prov ider In case the media was successfully excluded from the process.
DisposeAssociateNode This node is used to successfully dispose a customer, i.e. when an agent disposes a customer we check whether disposition is valid or not and if found valid then it is disposed.
Attribute
dataProviderType dispose.association.node.data.provider In case the disposition is found to be successfully valid.
Events
success.disposition.association system.error CallBackNotifierNode This node is used to notify the agent about the scheduled callback.
Attribute
dataProviderType
Events
success.callback.notifier failed.callback.notifier system.error In case the agent was notified about the Scheduled callback. In case the agent was not notified about the callback.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 96 -
Drishti-Soft Solutions
Attribute
dataProviderType listen.voice.log.node.data.provider In case the user successfully listened to the voicelog. In case the user could not listen to the voicelog. In case the entity who was listening to the voice logs hungup the call.
Events
success.listen.voice.log failure.listen.voice.log hungup.listen.voice.log system.error
Attribute
dataProviderType add.call.back.node.data.provider In case the callback was successfully scheduled.
Events
success.schedule.callback system.error
CustomerCallHistoryNode This node is used to provide the user an option to add some customized fields in the call history as per their requirement. For example a client may require the customer code to be put in call history. In that case this node would be used to make customer code a part of the customer callhistory.
Attribute
columnNames
dataProviderType
Events
customer.call.history.value.found customer.call.history.value.not.found customer.call.history.failure system.error In case respective value is found in the call history. In case no value is found in the call history. In case the node was not executed successfully.
DNCNode DNC stands for Do-not-Call. This node is to verify if the given contact exist in the DNC of either in the campaign of the process of the contact center.
Attribute
dataProviderType customer.query.node.data.provider In case dialing is allowed to the customer. In case dialing is not allowed to the customer. In case the node was not executed successfully.
Events
dial.allowed dial.not.allowed dnc.node.failure system.error
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 97 -
Drishti-Soft Solutions
TransferToPhone This node is used to transfer an active call to a third party phone number.
Attribute
transferToPhone
dataProviderType
Events
success.transfer.to.phone failed.transfer.to.phone no.phone.transfer.to.phone In case the call was successfully transferred. In case the call was not successfully transferred. In case there was no phone number mentioned to transfer the call to.
system.error AssociateUserPrompt To play customized greeting prompts to inbound calling customers, these prompts are managed by individual agents.
Attribute Events
Only unique tags needs to be specified for this parameter. associate.user.prompt.crt.object.node.data.provider In case the node was successfully executed. In case the node was not successfully executed.
RemoveCallbackNode This node is used to remove scheduled callback for a customer or a phone. This node is to be used in the disposition nodeflows, i.e. "dispose.call.back" and "dispose" nodeflows. This node should be added after the disposition has been successful, i.e it should be added after "DisposeAssociationNode".
Attribute
removeCampaignCallback removeSelfCallback
dataProviderType
It is to be set to true if campaign call back is to be removed. It is to be set to remove a user who is currently disposing the calls in case a self call back has been scheduled for him. remove.callback.node.data.provider In case the node was successfully executed. In case the node was not successfully executed.
Events
success Failure system.error
RecordToFIleNode This node is used record customer voice into an audio file. This node is to be used as a part of any nodeflow where there is a customer present (inbound/auto dial/manual dial/callback). The customer channel should be connected before reaching this node.
Attribute
filePath promptFile maxSilenceTime maxRecordTime It refers to the directory path of the file to record to. It refers to the file that is to be played back before the recording starts. This is the maximum silence time in the recorded channel after which recording is stopped. This refers to the maximum time for which the call
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 98 -
Drishti-Soft Solutions
recordingFormat dataProviderType
recording is to be done. It refers to the format of the recording file (wav, g729c etc) record.file.customer.node.data.provider In case the node was successfully executed. In case the node was not successfully executed.
Events
success Failure system.error
Failure
Name
Variables
Description
Variables are defined to store values and give inputs to nodes, they are not strongly bound, that means it contains string only, any numeric or float value will also be treated as string. Condition is to make decisions; these should also be defined in starting of IVR and are used later. This refers to defining database connection in VB or VB .Net.
Use
These are used for storing values and giving inputs to nodes, And these are also used in conditions to make decisions
Conditions
These are used to create custom events. This is used with SQL-Script node to tell this node what is the target database.
Database
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 99 -
Drishti-Soft Solutions
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 100 -
Drishti-Soft Solutions
Appendix III
Configuring Polycom Phones with DACX Ameyo - On-Phone Configuration
III.1: Setting up IP Address manually
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. Power up the Phone. Connect network cable to LAN port of Phone. Select Setup. Enter password. (Default is 456). Select DHCP Client. Select Edit. Select Disabled. Click on OK. Press the down arrow key. Select Phone IP Address. Select Edit. Enter IP Address. For eg. (010.010.001.010). Click on OK. Select Subnet Mask. Select Edit. Enter Subnet Mask. For eg. (255.255.255.000). Click on OK. Select IP Gateway. Select Edit. Enter Gateway IP Address. For eg. (010.010.001.001). Click on OK. Save Config and Reboot the Phone.
Confidential
info@drishti-soft.com; www.drishti-soft.com 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 101 -
Drishti-Soft Solutions
India | Philippines | Bangladesh | Middle East | USA Email: info@drishti-soft.com; Web: www.drishti-soft.com
2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved. Confidential info@drishti-soft.com; www.drishti-soft.com DR-180908-APUM-V14 2008 Drishti-Soft Solutions Pvt. Ltd. All rights reserved.
- 102 -