Weekly Newsletter Signup

• Upcoming
  Live Online Workshops

  • Excel and SharePoint: I didn’t know you could do that!
  • Easy Tabs Interface - Simple SharePoint Navigation for Complex Information
  • Train the Trainer: Materials and Resources for in-house SharePoint Training
  • Become Your Company’s SharePoint SuperStar!
  • Hack SharePoint Web Part Displays with XSLT
  • Business Solution: Health Care Case Management
  • Killer Calendars in SharePoint
  • The Basics of Content Types
  • Business Solution: Create a Compliance Report Intake System in SharePoint
  • Business Solution: Manage Input with Dynamic Feedback Forms
  • Live Blogging at SharePoint Conference 2009

• Ongoing Series

  • Article Archives (1000+)
    All Authors
  • This Week in SharePoint with Joel
    Joel Oleson
  • jQuery for Everyone
    Paul Grenier
  • The Calculated Column
    Dessie Lunsford
  • The Data View Web Part
    Laura Rogers
  • Stump the Panel: Q&A
  • Subscribe to the Weekly Newsletter

• Authors

  • Dessie Lunsford
  • Laura Rogers
  • Lee Reed
  • Mark Miller
  • Jim Bob Howard
  • Paul Galvin
  • Paul Grenier
  • Toni Frankola
  • Woody Windischman

• SharePoint Resources

  • Bits of SharePoint
  • Codeless Solutions for SharePoint
  • Get the Point
  • Innovation Matters
  • Path to SharePoint
  • Paul Galvin
  • SharePoint 911
  • SharePoint Blank
  • SharePoint Blogs at SharePointU
  • SharePoint for Non-Developers
  • SharePoint Forums at SharePointU
  • SharePoint Screencasts
  • SharePoint Use Cases
  • Social Media Talk Tweets
  • The Sanity Point
  • The Weekly Newsletter  

Scenario

Let’s consider the following scenario: Your company is working with a partner. All support requests are being submitted via email.

You have a a team of people submitting requests:

Furthermore, sometimes you need to include additional people on your side. The communication channels might get even more complicated (the more employees you have working on this, the more complicated it gets ).

The real problem here is using email as communication channel. Email is a great tool, easy to use and everything. But the problem is that knowledge from each conversation is lost in a personal inbox. If the receiver does not forward the email to other team members he will be the only one able to solve the problem.

This is where SharePoint kicks-in; in this article I am going to describe a simple procedure to automate the knowledge capture with SharePoint (WSS included ).

We are going to configure SharePoint to receive emails, store them to a document library, and configure Outlook clients to forward all emails coming from Partner directly to SharePoint.

Step by step guide to set it up: SharePoint configuration

I will try to explain how to setup this solution using Microsoft as my partner but you can adjust this solution to match your settings.

• Create a document library (e.g. Microsoft Support – Knowledge Base), we are going to use this it as knowledge repository for this partner.
• Enable incoming e-mail integration (learn more about Enabling and configuring e-mail support for a list or library) for it.
  I am using the following e-mail integration settings:

• Create an email alert for all members in your team to be alerted when a new item is created (use Alert me functionality or a workflow)

Outlook configuration

The next step is to configure a rule in Outlook to forward all the emails to your Knowledge base library, I created the following rule:

Apply this rule after the message arrives
from Microsoft Support
 and contains Re: in the subject
forward to [email protected]

My Outlook is going to forward each email sent by Microsoft support and containing “Re:” (sometimes we get other emails and I do not want these to be forwarded). Each email will be received by SharePoint and stored to your online knowledge base.

Conclusion

Benefits of this solution:

• Everything is automated. Once you set it up, you do not need to do anything else
• Every team member is being alerted when there is new information in the Knowledge base
• You can benefit from SharePoint search capabilities to search it:
• New team members can use your Knowledge base to learn more about previous support requests. This is very important!
• Other people from your company can also check the knowledge base periodically

Potential problems:

• Although Outlook rules can be Exported/Imported this procedure is not so trivial. So you will probably need to instruct each team member on how to create rule
• Maintaining rules might also be problematic
• Sometimes support requests cannot be solved with just one email. When you have multiple emails going back and forth between you and your partner (all being part of one support request) under proposed incoming email settings, SharePoint will create one folder for each reply. Change the incoming email setting to match your needs. Configuration options are limited, but it is something we can live with.

 

Author: Toni Frankola SharePoint Use Cases Toni started his Web adventure in late 90’s and has been working with various web technologies ever since.

Toni is leading project engagements and managing a team of consultants specializing in Microsoft technologies. His primary focus is on Microsoft Office SharePoint and Dynamics CRM. He works at Perpetuum Mobile, a Microsoft Gold Partner from Croatia.

---

Notify me of comments to this article:
E-Mail:

---

Comments