Actually - more on the service catalog side. (these can be fairly generic) Description: Image:
Price: Refunds: Availability: Support contact: Support hours: Support process: Policy: Security: Related items: FAQ: Manager: Maybe some internal attributes: Support group: Support priority: Risk: Owner: Related info: Those are all on the "defining" side of a service. Then you have the "actionable part" -- the "I want it" -- and then the questions for that -- but they tend to be specific to implementing the "service/item" being requested -- and they tend to not be very generic. (except) For who: On Jun 13, 2011, at 4:14 PM, Benedetto Cantatore wrote: ** What do you mean by attributes? Do mean the questions that are always asked by default? Such as "Is this request for you or for someone else?" would be an example of a question that I always ask for service items. Ben Cantatore Remedy Manager (914) 457-6209 Emerging Health IT 3 Odell Plaza Yonkers, New York 10701 >>> [email protected] 06/13/11 11:23 AM >>> ** Calling all Service Catalog builders... If you have created custom attributes for any services -- what attributes have you created? What attributes - do you always use??? -John -- John Sundberg Kinetic Data, Inc. "Building a Better Service Experience" Recipient of: WWRUG10 Best Customer Service/Support Award WWRUG09 Innovator of the Year Award [email protected] 651.556.0930 I www.kineticdata.com _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ -- John Sundberg Kinetic Data, Inc. "Building a Better Service Experience" Recipient of: WWRUG10 Best Customer Service/Support Award WWRUG09 Innovator of the Year Award [email protected] 651.556.0930 I www.kineticdata.com _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
