CCS Service Request ...Deployment and System Requirements

Unlike traditional stand-alone service request software, CCS Service Request is built into Outlook, eliminating the need to manage multiple contact databases or toggle between separate applications. CCS Service Request works entirely inside Outlook and easily deploys across the entire organization. User acceptance is the highest in the market, because users create new tickets from within Outlook, which they usually have open on their desktop already.

No new hardware or software investment needed!

Get more return on your investment in the Microsoft software you already own, like Exchange Server, Office and Outlook. You can deploy Crow Canyon applications to every division, department, and location without being forced to buy additional hardware or software.

CCS Service Request is built upon Microsoft Outlook and leverages the Microsoft Exchange environment. It supports:

Quick Setup Fast Deployment and High User Acceptance

Because we take advantage of your existing infrastructure, installation and setup typically takes minutes, with full deployment to all users available across your network. Execute our setup files and load the folders into your public folders and you are up and running.

Most or all of your users probably already have Microsoft Outlook installed on their desktops or laptops, and CCS Service Request clients are installed as a simple Outlook add-in. They do not have to sign-in to a separate application, or fill in redundant contact information. CCS Service Request leverages the organizational information in Active Directory, Contact manager, task and calendar tools built within Outlook. Not even web-based systems have this high of user acceptance.

No New Maintenance, Synchronization or Backup/archiving Work Required!

Because tickets are stored in Public folders, CCS Service Request leverages your existing procedures for archiving, back-up and security settings in Outlook. Application maintenance is minimal and does not require your IT department to add more resources to maintain the application.

Storage Requirements for CCS Service Request and Impact on Your Exchange Server

The storage effect of mplementing CCS Service Request in your Exchange/public folders environment is similar to adding 1-2 additional mailboxes. Each ticket is equivalent to a simple email, thus if you are getting 100 tickets per day, that is like adding one new email user to your system. Like email, old tickets are archived and compressed automatically by Outlook. Additionally, you should see no impact on overall email performance for your organization.

If you are running CCS Service Request Standard version and using the Email Converter function (which uses the Exchange Event Sink function), a small module is added to the Exchange Server to process emails. This is a very low-impact function and does not affect the performance of the Exchange Server.

Scalability for Large Implementations

Since CCS Service Request installs on top of Exchange and Outlook, it will scale across your organization just like Outlook itself does today. If you have 500 users on your email system today it will scale to support them. If you have 10,000 email users, it will scale to support them also.