Kayako logo
Will Implement (V4) Feature requests in this forum will be implemented in Version 4 of the product line (the current version).

Reply
 
LinkBack Thread Tools Search this Thread Rate Thread Display Modes
  (#1) Old
AKL-MFCU Offline
Member
 
Posts: 102
Join Date: Feb 2006
Location: Lakeland, Florida - USA
System -> Integrate Ticket<->Tasks<->Appointments etc - 18-07-2006, 07:23 PM

I think it would be a really cool option if there was an export ticket to task option. The ticket would export it's data to the teamwork task section, and prompt you for any necessary additional information (due dates, etc.). Reason i say this is i spend around 15-20 minutes a day moving some of the tickets that i get that are task related (could be a long project) and I'd rather not have them build up in the ticket system. So i spend time copying and pasting when im sure it wouldn't be too hard to port the sql tables over. Let me know if anyone else finds this as a good idea.
   
Reply With Quote
  (#2) Old
jamesM Offline
Member
 
Posts: 35
Join Date: Jun 2006
19-07-2006, 12:18 AM

Thats funny we do the same thing at the moment :-) as some tickets move in to project that we track through tasks.
   
Reply With Quote
  (#3) Old
superiorit Offline
New Member
 
Posts: 4
Join Date: Jul 2006
Suggestion: Ticket Scheduling - 24-07-2006, 06:13 PM

Other then online support, our company provides on-site support for our clients. We would like to see a way to schedule a ticket and for it to show up on selected calendars.
   
Reply With Quote
  (#4) Old
superiorit Offline
New Member
 
Posts: 4
Join Date: Jul 2006
26-07-2006, 02:41 PM

Anyone else have a need for this?
   
Reply With Quote
  (#5) Old
Bconsulting Offline
Member
 
Bconsulting's Avatar
 
Posts: 86
Join Date: Sep 2005
Location: Earth Most Of The Time
27-07-2006, 02:12 AM

I would love to see this also.
   
Reply With Quote
  (#6) Old
rrnworks Offline
Member
 
Posts: 44
Join Date: Oct 2005
29-07-2006, 07:51 PM

Ticket scheduling seems like a long overdue feature. I would simply request for Varun to provide some basic integration between the ticket and teamwork modules. This would include contacts and events. I don't understand why this hasn't been designed from the start though.
   
Reply With Quote
  (#7) Old
rrnworks Offline
Member
 
Posts: 44
Join Date: Oct 2005
29-07-2006, 07:54 PM

This just goes along with our previous requests for better (any?) integration between the ticket and teamwork modules. Seems like common sense?
   
Reply With Quote
  (#8) Old
rrnworks Offline
Member
 
Posts: 44
Join Date: Oct 2005
Module Integration and Reporting - 29-07-2006, 08:04 PM

I would encourage you to include better (any?) integration between the ticketing and teamwork/syncworks modules (ie. events/scheduling and contact/company information inside each ticket - schedule tickets - move tickets to tasks, group tickets by projects, etc.)

Are you planning on letting fieldfetch talk between the different kayako modules?

Finally, reporting is still very important. Creating a flexible interface to allow us to create our own reports with Crystal or Access would be very powerful. In the least, simply supplying us with a complete DDF for mysql would be very helpful.

Thanks!
Chris
   
Reply With Quote
  (#9) Old
logicway Offline
Member
 
Posts: 64
Join Date: Jul 2006
Users and Contacts Integration - 30-07-2006, 02:49 AM

Just started using eSupport, looks really great.

But there is something that should be improved, the integration of Users and Contacts (Teamwork).

From Contacts there should be an easy way to mark them also as Users.
Marking a Contact as User, should create also a User. Creating a User should also create a Contact.

When viewing a ticket, some Contact-information must be displayed, like phonenumber, companyname, fullname. This displayable-information must be configurable and all information must be available to configure. Even in the current ticket view it is hard to find which client the ticket concerns. The owner of the ticket should never be the staff-member where it doesn't matter if the staff-member created the ticket manually. The owner is always the client or company. If you want a staff-member to be the person who handles the ticket and store that in the ticket, you should give that another name, something like "Assigned to".

Tasks should be integrated too. From a ticket a task should be created, and some contact information should also be stored in the task. There should be actually a new module called Bugs available.

I hope these features get implemented asap. I read that there are many forum members who also want this feature. I hereby ask these members to post in this thread.

Last edited by logicway; 30-07-2006 at 03:13 AM..
   
Reply With Quote
  (#10) Old
superiorit Offline
New Member
 
Posts: 4
Join Date: Jul 2006
31-07-2006, 01:02 AM

Well, BUMP for a VERY important feature IMO.
   
Reply With Quote
  (#11) Old
PaulV Offline
New Member
 
Posts: 19
Join Date: Jun 2006
Location: Canada
31-07-2006, 01:58 PM

Hi,

This has crossed my mind aswell. If somehow the user's database could be cross referenced with the 'contacts' DB, I think that would be a really useable feature.
   
Reply With Quote
  (#12) Old
LittleBandit Offline
New Member
 
Posts: 1
Join Date: Aug 2006
Much Wanted Feature - 02-08-2006, 03:41 PM

We were just asking Kayako support about this feature only a few days ago.

We're a PC repair business, so we provide online support to our clients for simple issues but also On-Site support aswell for hardware problems.

We want to use the Task list in the TeamWorks area as sort of a booking engine where we can assign callouts to technicians but we would need to be able to have the ability to assign a Contacts details to the ticket, such as Name, Address, Phone Number and brief description of the problem, sort of a more advanced Ticket really.

We would also like to see it work with the KayakoMobile so we could elimate all paper work and wriet ups could be completed on site, this would save us hours in the office in the evening.

I'd really like to see this as a new feature soon

Last edited by LittleBandit; 02-08-2006 at 03:44 PM..
   
Reply With Quote
  (#13) Old
AKL-MFCU Offline
Member
 
Posts: 102
Join Date: Feb 2006
Location: Lakeland, Florida - USA
Once i get - 05-08-2006, 06:05 PM

once i get the hello world figured out on building the module, im going to crack open the database and create a manual option to export between the two. However, since the ticket system doesn't seemed to have an "assigned' start and due date, im going to export those tables blank to the task. You'll probabbly have to go manually change those if you want. Let me know if anyone is interested in the porting code.
   
Reply With Quote
  (#14) Old
jamesM Offline
Member
 
Posts: 35
Join Date: Jun 2006
07-08-2006, 12:31 AM

Very nice AKL keep us updated :-)
   
Reply With Quote
  (#15) Old
rrnworks Offline
Member
 
Posts: 44
Join Date: Oct 2005
07-08-2006, 02:32 PM

We're very interested as well....
   
Reply With Quote
Reply

Tags
>, integrate

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On

Similar Threads
Thread Thread Starter Forum Replies Last Post
The SLA system explained with example implementation Matthew SupportSuite, eSupport and LiveResponse 29 27-08-2008 02:39 PM
Ticket Purchaser (Pay-Per-Ticket System) greengiant Developers & Code 24 23-05-2007 05:14 PM
New Build: 3.10.02 STABLE Ryan Lederman News and Announcements 0 05-03-2007 09:53 PM
New Pay per ticket system jc11 Developers & Code 12 23-08-2006 03:45 PM



Powered by vBulletin® Version 3.7.5
Copyright ©2000 - 2009, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.2.0
Help desk software by Kayako.


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48