Channels

From AgileApps Support Wiki
Revision as of 02:17, 15 May 2013 by imported>Aeric (→‎Email)

Channels are avenues through which cases comes in, and through which case communications occur. In the early days of support systems, the Phone channel was pretty much the only channel there was. But there has been a tremedous expansion in the number of ways we connect with each other and do business. ServiceDesk is on top of that trend, providing a wide array of case communication channels.

Email

When customers send a message to an Email Channel:

  1. If the message is in reply to an existing case, their comments are automatically recorded in the case history.
  2. If it is a new message and you have configured the channel to allow it, a new case can be created automatically.
  3. You can choose to restrict that privilege to known customers, or open it to anyone
  4. You can also choose to create a new Contact record on the spot, when someone new creates a case, so you have them in your system.
    The initial Email Channel that comes with ServiceDesk can be used for experimentation, and for internal use. But for your external customers, you’ll want a channel that includes your brand--something like support@MyCompany.com. You can set up as many email channels as you need for that purpose. For example: product1-support@MyCompany.com and product2-support@MyCompany.com.

Learn more:

  1. Email_10_Customizing.html--Customizing Your Email Channel to Minimize Spam and Maximize Results
  2. Email_30_Mailbox.html--Adding a Mailbox to Handle Messages from an External Email Address

Service Portal

The Service Portal (also known as the Web Portal) is a place for registered customers to add and view cases. In addition to tracking their cases, you can also set things up to provide your customers with:

  1. A Knowledge Base that contains a collection of articles you have categorized and published,

with some articles reserved for internal use.

  1. A Community that allows your customers to interact with each other, and which allows a Case

Agent to convert a question to a case with the click of a button. You can configure the portal so that only contacts in your database can use it, or you can open it to the public. If open, you can restrict access to registered users, or allow unregistered "guests" to take advantage of its features. Learn more:

  1. Start_10_ServicePortal.html--Configuring and Using the Service Portal
  2. HowTo_10_PortalInvitation.html--Invite a Contact to the Service Portal

Twitter

You can create cases when messages are posted to a selected account, when messages mention a selected account, or you can use a Twitter account to carry on communications. You can also set up a search to look for Tweets that mention your brand. Learn more: Channel_30_Twitter.html--Setting Up Twitter and Twitter Search

Facebook

Your customers can create a case by posting to your Facebook page, by sending you a private message (or both) depending on your configuration. You can automatically create new Contact records. And you can choose to create cases selectively, based on the number of followers and the "mood" of the message (happy, sad, angry, etc.). Learn more: Channel_10_Facebook.html--Setting Up a Facebook Channel

Web Forms

You can generate code to embed in your website, so customers can create a case by filling out a form. That form can include a Captcha segment, where the user types the characters displayed on the screen, to ensure that it is a person who is filling out the form, rather than a computer program. You can let the platform handle the form processing, specifing which fields to display and which are required. You insert a small link into your web page, and that\’s it. The platform handles the rest. Or you can take greater control of the form by generating HTML. You can then customize the HTML in any number of ways before adding it to your website. Learn more: Channel_40_WebForm.html--Embedding a Record-Creation Form in Your Web Site