Find answers to your technical questions and learn how to use our products
Search suggestions:
Find answers to your technical questions and learn how to use our products
Search suggestions:
Use the SMS node to send SMS. The SMS node has 5 children nodes; Restrictions, Address, Sender's address, Applications, and ResultProcessors.
Ensure that the value of "Next State" property of the Result Processor node is set to "wait" and you have a Result handler for SMS Delivered with the value of "Next State" property set to "done”. The notifications and delivery receipts are considered as inbound traffic. For more information about capacity and pacing on Avaya Experience Portal, see Avaya Experience Portal documentation.
The following table lists the properties of the node and their descriptions:
Property Name |
Description |
Name |
Use this as a display name in the campaign strategy editor. If you do not specify a name, then the default name is SMS. |
Description |
Use to specify the description for SMS node. |
Sender's Address |
Use to specify the sender's address to be displayed to the recipient of the SMS message. If the Sender's Address node is not added, POM uses the sender's address value defined in this parameter. |
Restrict On No Suitable Address |
If you set this property to Yes and if POM cannot attempt a record because of guard time restrictions, or minimum and maximum contact time restrictions, POM marks the record as temporary restricted. POM queues the record to the predefined POM queue for a retry. Set this property to No if you want POM to mark the records that cannot be attempted because of guard time restrictions, or minimum and maximum contact time restrictions as completed. POM assigns the Sys_No_Callable_Address completion code to such records. The default value is Yes. |
Min Contact Time |
MinContactTime defines the earliest time when POM can send the SMS. So from 00:00 to Min Contact Time, you cannot send any SMS. You can send the SMS from Min Contact Time to either Max Contact Time, if set, or till 23:59.
Note:
If the Min Contact Time is greater than the Max Contact Time then the condition is reverse, that is, you can send SMS from Max Contact Time till 23:59 from the earlier day, and from 00:00 to Min Contact Time, the next day. For example, Min Contact Time is 23:00 and Max Contact Time is 05:00. Then you can send SMS from 23:00 to 23:59 on the earlier day and from 00:00 to 05:00 on the next day. Date and Time based comparisons use the date and time format specified in Global Date Format field. Min Contact Time must not be equal to Max Contact Time. |
Max Contact Time |
Max Contact Time defines the time till when you can make calls. So from Max Contact Time to 23:59, you cannot send any SMS. You can send SMS, either from 00:00 or Min Contact Time, if set, till Max Contact Time. For example, if you are running a campaign and you do not want to send SMS after 8pm, you can set the Max Contact Time to 20:00:00. |
Re-check Interval (min) |
Use this to specify a time interval after which when a contact attempt is restricted because it matched some restriction of type 'temporary' it will be again checked for all the restrictions defined in that handler. If no value is specified for this parameter then it will be considered as 1 minute. |
On Media Server Failure |
On Media Server Failure has two values in the drop-down; retry or no_retry. If you choose retry, you can keep on trying to establish a connection with the media server. If you choose no_retry, then you can mark the disposition as Media_Server_Failure and move to the next contact. |
Edit Description |
Use to edit the description for the SMS node. |
Applications |
|
SMS Application |
The application to be used for inbound SMS and delivery receipts. This field displays the shipped POM SMS applications and custom SMS applications. |
Pacing Parameters |
|
SMS Pacing Type |
Use to select the pacing type as None, Time-based, or Skill-based.
Note:
The Skill Based Call Pacing Type is not visible if you have installed POM in Oceana mode. |
If you select the SMS Pacing Type as Time-based, you see the following additional fields: |
|
Pace |
Use to specify the number of SMSs to send. |
SMS Pace Time Unit |
Use to specify the number of SMS to send for the selected time unit. You can specify the time unit in seconds, minutes, and hour. For example, 5 SMSs to be sent per minute. |
If you select the SMS Pacing Type as skill-based, you see the following additional fields: |
|
Skill |
Use to specify the inbound skill to monitor. If you disable the skill for pacing, while the skill-based campaign is running, the changes do not take effect immediately on the running campaign. You must stop the skill-based campaign manually and change the skill being monitored from the campaign strategy. |
Parameter |
Use to select a parameter for the skill-based pacing. The options are: Avg. Speed of Answer, Expected Wait Time, Queue Length, and Service Level. |
Expected Wait Time |
You can edit this property only when you select value Expected Wait Time in the Parameter property. You can select either High, Med, Low, or a combination of these values. When you click SHOW SOURCE button to view the XML file, the “ewtLevels” key value pair with selected levels is displayed on the screen. |
Desired Value |
Depending on the parameter you select, specify different values. For Expected Wait Time, specify a valid integer value between 1 to 7200. For Service Level, specify a valid integer value between 1 to 100 .For Avg Speed of Answer, specify a valid integer value between 1 to 1000 .For Queue Length, specify a valid integer value between 1 to 7200. |
Initial Pace |
Use to specify the number of SMSs POM can send in the Pace Interval. |
Pace Interval |
Use to specify the time unit for pacing. The options are: Hour, Minute, and Second. |
Pacing Variation (%) |
Use to specify the % value of pace using which the actual pacing is varied to match the maximum pace. POM also uses the value you specify to match or reduce the pacing to match to the initial pace. |
Max Pace |
Use to specify a maximum pace value with which the campaign can run. The value must be between 1 and 500000. |
Edit Description |
Use to change the description of the node. |