Defining Optional Agent Characteristics

Select another agent with whom this agent can have a chat session or can ask to conference into another chat.

Each agent buddy must be logged in a physical queue on the same cluster to be able to chat. If two agents must be able to chat but they do not share a cluster, use the Physical Queue Move Agent page to move the agents into physical queues on the same MCF cluster.

Agent buddies are listed with their login status in the buddy list on the multichannel console.

Displays the buddy agent's nickname.

Select the window to which the specified configuration applies.

Select from:

• Agent to Agent Chat

• Agent to Customer Chat

• E-mail

• Generic Alert

• Grab URL

• MultiChannel Console

Enter the distance in pixels from the top and left edges of the screen when the window first appears.

Enter the width and height, in pixels, of the window when it first appears.

Select from:

Automatic: The window appears automatically. For customer-initiated chat or tasks that are initiated from the EnQueue() built-in function, the task is automatically accepted as well. For agent-initiated chat, the agent can elect not to accept the task; in effect, the agent can preview the task. If this is the desired behavior, select Manual from the Accept Mode drop-down list box. If you want agent-to-agent tasks to function like customer-initiated tasks, select Automatic from the Accept Mode drop-down list box.

Manual: The window does not appear until the agent clicks the task on the agent MultiChannel Console. For customer-initiated chat or tasks that are initiated from the EnQueue() built-in function, clicking the task means that the task is automatically accepted as well. For agent-initiated chat, the behavior depends on the setting for the Accept Mode field.

Select from:

Automatic: Agent-to-agent chats are automatically accepted without requiring the agent to click the icon.

Manual: Agent-to-agent chats require the agent to click the icon.

Accept mode affects only collaborative chat.

Responses, except those that are identified by Other, are linked to specific events. These responses are always sent on these events from this agent. If an agent does not have a customized response for a specific event, the response is read from a default value that is set in the Message Catalog. The response text that is set here overrides the default text that is set in the Message Catalog.

Select from:

• Abandon: A chat is abandoned when a chat initiator closes the chat window before the chat is accepted by an agent. This message appears when the agent accepts the abandoned chat.

• Accept: This response is automatically sent to the chat initiator when an agent accepts a chat in response to a chat request that does not include a question.

  If the chat request includes a question, the agent's Answer Question text is sent in response instead of the Accept response.

• Answer Question: This response is automatically sent to the chat initiator when an agent accepts a chat in response to a chat request that includes a question.

• Deny: This response applies only to collaborative chat. If an agent elects not to accept a chat, this message is automatically sent to the chat initiator.

• End: If either party quits a chat after the chat is accepted, this message is displayed from the agent.

• Forward: If the agent forwards a chat session to another queue, this message is sent to the customer.

• Other: These messages are never automatically sent in a chat session. Their message names appear in the Template Messages drop-down list box on the agent chat page. These messages are appended to the template messages (chat responses) that are defined for the queue.

This name appears in the agent's template response drop-down list box.

Enter the response text to appear in the chat window.

The URL name appears in the agent's static URL drop-down list box.

This description appears only on this page, to further describe this URL or, for example, its reason for inclusion.

Enter the queue push URL.

The URL must include the opening http:// and any required parameters.

All static URLs that are defined for the agent are downloaded when the agent launches the agent chat console by accepting a customer chat. Static URLs are not available in collaborative chat.

If you send a PeopleSoft Pure Internet Architecture URL, be sure that the recipient has permissions to access that portal , node, or page.

Select from the following values the action that occurs when a task that is assigned to an agent is unassigned:

• Prompt whether to close window (default).

• Close the task window.

• Do not close the task window.

Select from the following log trace levels:

• 0 - None

• 1 - Information

• 2 - Debug

If a value other than 0 is selected, a tracer window appears to display activities and events on the chat or MultiChannel Console for debugging purposes.

Specify the number of communications to the Real-time Event Notification (REN) server before a refresh occurs for a browser-based client. Default refresh frequency is 10000. You can configure the field depending on the memory available to the client.  A higher value will use more memory, but will allow a longer time between refreshes.

This check box is enabled when the value entered for Trace Level is not 0. Select this check box to enable the agent to clear the tracer log based on Number of messages to save and Number of messages to allow.

If the check box is deselected, the tracer log will not be cleared and the Number of messages to save and Number of messages to allow will be disabled.

Specify the minimum number of recent tracer log messages that should be maintained in the tracer window.

Specify the maximum number of tracer log messages that will be maintained in the tracer window.