Recently active
test cover photo
It would be good if we could standardize this column, just like how we should standardize internal notes on CS. Yes, I understand that when a case is closed, this information should be just the solution to the issue, however during the life of the case, this needs to be a historical chain of events. Cases get transferred, run on for long periods of time, switch queues, escalated, severity, incidents, etc.. this information needs to be tracked at a glance, and if this is not the section to do it in, Advisory board needs to work with Management on Process Documentation to suggest where we can put it if this is not the right spot.
In today's society, we've accepted the cell phone as an allowable addiction. Simon Sinek, a thought leader in the industry has this to say on what this is doing to relationships and trust.... We need to put away our phones... What do you think?? If you agree, VOTE for Culture: Ban cell phones from Conference Rooms. If you don't agree or have other thoughts, let's have a discussion here...
Hello Advisory Board, We need automation for Engineers to be able to succeed in the requirements for the CLQR (SRQR, or whatever it wants to be called next year). Two things about this are. 1. Engineers are required to put a Case Comment of "Case Assessment summary" which tells the reviewer that, yes i've reviewed the materials, yes, i've reviewed the attachments, yes, ive reviewed customer session data, along with what the TSE is going to do with the information provided. This needs to be split into something significantly more easier for the engineer. If taking the word of the engineer is not sufficient enough, then we should provide checkboxes that Engineers can use to say, Yes, I've viewed all those things, along with an area where they can type all their pre-contact the customer information. Then at least if a customer suggests that he or she already saw an article, or already provided an attachment, that can be checked against the checkbox and then be done.&nb
Go to "My Settings" and check your subscriptions:
Please be sure to subscribe to discussions, ideas, and blog.
We currently have two global distribution lists which can only be owned by one person TS-NA-AdvisoryBoard = Board Members Owner: Glenn Williams TS-NA-AdvisoryMembers = Members Owner: Jennifer Sledz Distribution List - How to manager members
See this Discussion on instruction on How to Register on PTC Community 1) Employee goes to PTC Community and submits their normal PTC credentials (laptop login) 2) Complete screen name 3) Review the Terms and Conditions of being on the Community THAT'S ALL FOLKS!!...you are now a general user! If you need special group or further access, contact community@ptc.com mailbox with group name/group leader
This is a test of Lithium functionality with respect to posting. Animated image: A mememnto for the old community. A video: Text colours (no background setting OotB), size changes and formatting. Yay strikethrough! Spoiler (Highlight to read)The only problems I've noticed are:1) That it jumps the text window to the wrong spot on an undo, probably because of the image and video embedded above. Slightly annoying, but not critical. 2) You can't do bulletted lists inside spoilers.3) The spell check doesn't use the browser spell check functionality (and hence dictionary). Team Creo will be annoyed by that!The only problems I've noticed are:1) That it jumps the text window to the wrong spot on an undo, probably because of the image and video embedded above. Slightly annoying, but not critical. 2) You can't do bulletted lists inside spoilers.3) The spell check doesn't use the browser spell check functionality (and hence d
Taking another look. Monitoring the following report Articles with topics without AF on a monthly basis displays articles which have been Unsuccessfully flagged gives me insight as to the hang-ups with this process. I know we can make this easier for all. Let's put on our thinking caps and give this a try.Current process:Click 'Show Feed' on an article in KCS modeFreeform text in the following format: #feedback #<flag_type> <Comment>#feedback #improve#feedback #rework #feedback #duplicate#feedback #archiveSuggestions:Make flagging case insensitive -Open 3 years, only 280 points, not very popular??Remove "#feedback" tag since it is redundantOpen 4 months, only 10 votes, not very popular?Add #translate as a tagOpen 8 days, only 3 votes Do these help? Should we take it one step further? What do you think??
!!46 VOTES!! Please read, vote and give feedback I’m writing to you about Thot Idea --[SEARCH] Support multi-language search for warning/error messages in KCS search engineWe have got 46 votes on this idea, LOVE to hear from the Western Engineers. Currently, customer is using Dylan system when he opens a case. As I know that the search engine of Dylan will understand the meaning of customer’s word first, and then Dylan finds out the suitable articles basing on the meaning instead of keywords. Under this logic, Dylan is hard to recognize an error message from PTC product when customer just want to search some articles regarding a specific error message.So is it possible to add a logic in Dylan? For example, if customer enters some words with quotation marks, then Dylan can recognize this is an error message and find out relevant articles with this message.Combine the previous Thot idea, if we have an error message library with multi-language, Dylan can support the error message s
Hey everyone,I've been thinking about how people might use Case Status in Salesforce in different ways and that it would be nice to understand what the practical uses are for each status and develop some best practices for us as TSEs to follow. Below is what I have come up with so far. I'd love to get your feedback regarding it!New:Cases exist in this status for the short time between the creation of the case and the time cs_ptc sends the “Thank you for submitting your question to us” emailCases remain in this status when it has been created by the TSE using the New TS Case or Clone action in SalesforceA TSE would have no practical reason to set a case to this statusAs a best practice, TSEs should not be owning any case in “New” status for an extended period of timeAssigned:Cases are not given this status in any automated use caseOnly practical use of this status might be when someone QB’ing a queue assigns a case to a particular TSE who will own itCases should not be in “Assigned” sta
Hi all,I received some feedback about the email best practices already, so I figured we could start a thread here. Assuming we end up adding all the TSEs to the group, it will also be a good place we can all discuss it.I would be interested in hearing an opinion from you folks.I have not yet heard a case where the TSAM is against (or in fact hasn’t requested) being included on all communicationssince this allows them to speak more intelligently on conference calls regarding a customer andhaving up to the minute case progress info (without referring back to the maybe current/maybe notStatus Details on the case).Shouldn’t the Outlook template automatically include the TSAM on the CC line for Premium cases?Likewise, shouldn’t the template automatically populate the Subject with case number and contact? Surely this isn’t any major amount of work to fix, and would result in making the template a usable time saver as opposed to a non-issue.I prefer “Greetings” to “Hi” or “Hello”. It is more
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.