Link to home
Start Free TrialLog in
Avatar of JesusFreak42
JesusFreak42

asked on

Sharepoint for Ticketing System

Hello,
    I am running a small IT company that is growing and finds itself needs a ticketing system in order to keep work orders from being forgotten. Right now I am beta testing bluefolder.com. I have also tested zendesk. My question is basically that I also have a small hosted 2010 Sharepoint Site that I am learning Sharepoint on. As I have delved into it a bit, I find that this may be a more integrated solution for a ticketing system, especially as I am looking at MS Dynamics as well for CMS. I wanted some opinions on the following questions
1) Is this even worth considering?
2) Is this something difficult to design, or something I could probably figure out myself?
3) How much would it cost to have somene design it?

Thanks!
Avatar of typerracer
typerracer

As with most decisions, the answer is "It depends"

SharePoint is great for managing lists and, when combined with SharePoint Designer workflow tools, can solve many of the basic problems you need to solve.  If your need is to quickly build a bare bones solution where you are able to track version history, attach files, route status updates as they appear and keep track of who is working on what, a SharePoint solution can be stood up out of the box very quickly through learning on the fly or hiring someone to build it.

If you need a more robust and polished solution that offers true call center management capabilities, then you should be looking at dedicated solutions that are built for the help desk industry.

Without more detail on what you need to track, what your workflows are, etc, it's tough to go much further than that.  However, I can confirm that SharePoint does provide a lot of the essential tools that would enable you to get up and running quickly if you choose to go the custom route.
Avatar of JesusFreak42

ASKER

We need to track the following
1) Work Orders
   a) Their nature (priority) and department (VOIP, Tech Support, Etc.)
   b) Time Worked
   c) Notes/emails
   d) Technicians
   e) Materials Used (expenses)
   f) Multiple Tasks (if work order is a Project rather than an incident)
   g) Status
2) Customer Files
   a) Netowrk Diagrams, etc.
   b) Contracts
3) Inventories
   a) Software/equipment the customer has and the waranntee/serial numbers of them

Obviously customer contact information

The reason I am even thinking about Sharepoint is not that I am unhappy with bluefolder. I actually like it quite a bit. It more has to do with integration. I would love to be able to pull up a person in ms Dynamics and immediately see their ticket history. Maybe this is not the right way to go about it, but integration is probably the main reason I am considering this.
ASKER CERTIFIED SOLUTION
Avatar of typerracer
typerracer

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks for all that! This is something that is needed soon, but there is no absolute due date yet. We simply recognize it as something that will be helpful now, but absolutely necessary as our business is growing. To give a rough idea of timeframe, I would say 1 month would be great, 3 months would be the longest wait (seeing as I am leaving for vacation then).
I just signed up for a demo dynamics site to see how these two work together. Thanks for all your help. Any additional advice would be great.