Bookshelf Home | Contents | Index | PDF |
Siebel Email Response Administration Guide > Overview of Siebel Email Response > Understanding the Siebel Email Response Architecture > Managing Siebel Server Components to Process Incoming EmailOnce a customer sends an email to your company, your email server that is connected to the Siebel Server receives the email and passes it to the Communications Inbound Receiver (CIR). The Communications Inbound Receiver (CIR) resides on the Siebel Server and has a primary role in the Siebel Email Response processes. Three Communications Server components manage inbound and outbound email messages: Communications Inbound Receiver (receives email), Communications Inbound Processor (processes and routes email), and Communications Outbound Manager (sends responses to the email). Workflow Manager invokes other Siebel Server components, such as Assignment Manager and Smart Answer Manager. Communications Inbound Receiver uses the Internet SMTP/POP3 Server driver to periodically connect to your email server and check for new email messages. When Communications Inbound Receiver detects a new message, it does the following:
Processing Email in Real-Time and Nonreal-TimeDepending on your business requirements, you can process email in one of the following ways: Figure 2 provides examples of different Communications Inbound Receiver and Communications Inbound Processor configurations for your Siebel Enterprise. Processing Email in Real-TimeReal-Time email processing only uses one server component, Communications Inbound Receiver. This type of processing is best for businesses with a low volume of email customers or businesses who primarily use phone events, as these types of events always use real-time mode. Figure 3 describes the architecture for real-time email processing. For information on how to enable real-time email processing, see Enabling Real-Time Email Processing. For more detailed information on processing email in real-time, see How Real-Time Events Flow Through the Communications Inbound Receiver. Processing Email in Nonreal-TimeNonreal-Time email processing has both server components, Communications Inbound Receiver (CIR) and Communications Inbound Processor (CIP) running as separate server components. This type of processing allows you to have multiple instances of Communications Inbound Receiver (CIR) and Communications Inbound Processor (CIP) on different Siebel Servers, providing a distributed architecture which is more scalable and reliable than real-time email processing. Figure 4 describes the architecture for Nonreal-Time email processing. For information on how to enable nonreal-time email processing, see Enabling Nonreal-Time Email Processing. Processing Incoming Email with Siebel Business Process DesignerCommunications Inbound Processor uses the Workflow Process Manager in the Siebel Business Process Designer to process an email message in a number of ways, depending on the workflow process you select to handle that type of message. Oracle ships several preconfigured workflow processes that provide email processing features. For more information, see Setting Up Siebel Email Response Workflows. The Workflow Process Manager in Siebel Business Process Designer can be set up to perform the following tasks:
Determining how an Agent Replies to EmailThe agent reviews the message using the Siebel client and composes and sends a reply using templates configured for your company's needs. See Figure 1 for an illustration of this process. Understanding how the Communications Server Returns a Reply to a CustomerWhen the agent sends the message, Communications Outbound Manager, a Communications Server component, sends the replies through your email server using SMTP/POP3 communication protocols. Your email server then sends the email over the Internet to the customer's email server and the customer's email server sends it to the customer's mailbox. See Figure 1 for an illustration of this process. |
Siebel Email Response Administration Guide | Copyright © 2008, Oracle. All rights reserved. | |