List of the top 8 reasons to upgrade to Siebel 8.1:
1. Task Based UI: To help users accomplish tasks, previous versions of Siebel offered SmartScripts and iHelp, but neither were particularly intuitive or helpful. Task Based UI (user interface), however, provides a hands-on experience that guides users through each required screen. Furthermore, these screens are relatively easy to build, can offer pre-populated fields, and branch in different directions, depending on answers. As a result, this feature is particularly well-suited for complex or infrequently used sales or customer service business processes, to reduce training requirements and learning curves.
2. Templates: Pre-populate almost any entity — including accounts and activities — in Siebel and save it as a template, so users can easily launch them later. With customer service, for example, create service request entities for specific situations, to be used by a particular user or shared between all users, to save time and reduce error rates.
3. Lead entity (aka lead management): Previously, opportunities in Siebel were part of the main sales cycle — sales moved an opportunity from quote to order — and campaigns were only part of the marketing function. What was missing was a bridge between marketing and sales. The new lead entity fills that gap. Now, upload leads from external sources and let users create leads. Siebel also facilitates true lead management and qualification, meaning that a sales user can accept a lead, or reject it, which kicks it back to a lead pool managed by marketing. All in all, this is extremely useful.
4. CRM Desktop: Siebel gains a true interface to Microsoft Outlook, replacing previous, limited attempts to integrate Siebel directly with the Outlook client, or the overly complex and time-consuming Siebel Server Sync Exchange (SSSE). CRM Desktop provides true, two-way synchronization of entities that exist both in Outlook and Siebel — contacts, to-dos, and calendar items. But you can also view and create any Siebel entities in Outlook, and make them follow identical account and opportunity rules. For example, create a Siebel account in Outlook, or create and view Siebel opportunities in Outlook. Furthermore, the underlying configuration and setup is relatively easy. Finally, this meets the needs of our Siebel customers requesting “real” Outlook synchronization.
5. Search: Takes a big leap forward in Siebel 8.1, which gains brand-new search functionality, backed by a dedicated indexing database. As a result, searching is much faster. For the first time, search queries need not be case-sensitive, and you can search all Siebel entities at once, as well as external sources, such as a separate products database, or a SharePoint database. Finally, the search results get a Google-style makeover, including a hyperlink to the data, as well as a preview.
6. Territory management: Formerly known as Assignment Manager, territory management got a big upgrade with Siebel 8.0, and with 8.1 it’s been further tweaked with better functionality and capabilities for refining territories and assigning them to salespeople. For example, you can run territory management in a trial mode to show business users what the results of using different territory configurations would be.
7. Performance upgrades: On the technical side of Siebel 8.1, overall performance — including search — has improved substantially. Under the hood, this involved numerous technical changes that make the application run faster. At the same time, Oracle also made a number of enhancements to speed up productivity when using the Siebel Tools.
8. UI and functional enhancements: With Siebel 8.0, Oracle cleaned up the UI, making it look a bit nicer, and added new applications — dubbed Widgets — that run outside Siebel. One example is Mobile Sales Assistant, which makes specific Siebel functionality available via a desktop widget. With 8.0, Oracle also added a new business rules engine, which moves validation and business rules from the Siebel business layer to the administration layer. As a result, you can write business rules using more of a business language, which makes for easier and quicker configuration and rollout of business rules.
1. Task Based UI: To help users accomplish tasks, previous versions of Siebel offered SmartScripts and iHelp, but neither were particularly intuitive or helpful. Task Based UI (user interface), however, provides a hands-on experience that guides users through each required screen. Furthermore, these screens are relatively easy to build, can offer pre-populated fields, and branch in different directions, depending on answers. As a result, this feature is particularly well-suited for complex or infrequently used sales or customer service business processes, to reduce training requirements and learning curves.
2. Templates: Pre-populate almost any entity — including accounts and activities — in Siebel and save it as a template, so users can easily launch them later. With customer service, for example, create service request entities for specific situations, to be used by a particular user or shared between all users, to save time and reduce error rates.
3. Lead entity (aka lead management): Previously, opportunities in Siebel were part of the main sales cycle — sales moved an opportunity from quote to order — and campaigns were only part of the marketing function. What was missing was a bridge between marketing and sales. The new lead entity fills that gap. Now, upload leads from external sources and let users create leads. Siebel also facilitates true lead management and qualification, meaning that a sales user can accept a lead, or reject it, which kicks it back to a lead pool managed by marketing. All in all, this is extremely useful.
4. CRM Desktop: Siebel gains a true interface to Microsoft Outlook, replacing previous, limited attempts to integrate Siebel directly with the Outlook client, or the overly complex and time-consuming Siebel Server Sync Exchange (SSSE). CRM Desktop provides true, two-way synchronization of entities that exist both in Outlook and Siebel — contacts, to-dos, and calendar items. But you can also view and create any Siebel entities in Outlook, and make them follow identical account and opportunity rules. For example, create a Siebel account in Outlook, or create and view Siebel opportunities in Outlook. Furthermore, the underlying configuration and setup is relatively easy. Finally, this meets the needs of our Siebel customers requesting “real” Outlook synchronization.
5. Search: Takes a big leap forward in Siebel 8.1, which gains brand-new search functionality, backed by a dedicated indexing database. As a result, searching is much faster. For the first time, search queries need not be case-sensitive, and you can search all Siebel entities at once, as well as external sources, such as a separate products database, or a SharePoint database. Finally, the search results get a Google-style makeover, including a hyperlink to the data, as well as a preview.
6. Territory management: Formerly known as Assignment Manager, territory management got a big upgrade with Siebel 8.0, and with 8.1 it’s been further tweaked with better functionality and capabilities for refining territories and assigning them to salespeople. For example, you can run territory management in a trial mode to show business users what the results of using different territory configurations would be.
7. Performance upgrades: On the technical side of Siebel 8.1, overall performance — including search — has improved substantially. Under the hood, this involved numerous technical changes that make the application run faster. At the same time, Oracle also made a number of enhancements to speed up productivity when using the Siebel Tools.
8. UI and functional enhancements: With Siebel 8.0, Oracle cleaned up the UI, making it look a bit nicer, and added new applications — dubbed Widgets — that run outside Siebel. One example is Mobile Sales Assistant, which makes specific Siebel functionality available via a desktop widget. With 8.0, Oracle also added a new business rules engine, which moves validation and business rules from the Siebel business layer to the administration layer. As a result, you can write business rules using more of a business language, which makes for easier and quicker configuration and rollout of business rules.
No comments:
Post a Comment