10 Best Practices for a Successful Customer Solution Engagement


 
Thread Tools Search this Thread
Operating Systems Solaris Solaris BigAdmin RSS 10 Best Practices for a Successful Customer Solution Engagement
# 1  
Old 03-17-2010
10 Best Practices for a Successful Customer Solution Engagement

This paper discusses 10 key areas that frequently are not handled correctly and lead to customer dissatisfaction during customer solution engagements, and it provides recommendations for successfully handling them.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Shell Script to prompt customer for name etc

reposting How do I create a shell script called 'custinfo' to prompt a customer to enter and display back the following: name, age, address, phone number, product, price range. Thanks (1 Reply)
Discussion started by: SQLScript
1 Replies

2. UNIX for Dummies Questions & Answers

identify a customer under a UNIX server

Like many UNIX users, there is a small team that is connected to UNIX (under the same UNIX user) via putty from a Windows PC. Is there a way, once under UNIX, to know the address of the originating computer or anything that can differentiate initial users ? (7 Replies)
Discussion started by: popescu1954
7 Replies

3. HP-UX

Customer support engineer

Hi All, I need the help to deploy or implement HP MC service guard 2 node cluster step by step procedure is any1 who can help me to send me the step by step procedure. Thanks and Regards Jahangir (12 Replies)
Discussion started by: Jahangir
12 Replies
Login or Register to Ask a Question
moniker(3pm)						User Contributed Perl Documentation					      moniker(3pm)

NAME
UNIVERSAL::moniker - Nicer names for your Perl modules/classes SYNOPSIS
use UNIVERSAL::moniker; DESCRIPTION
Class names in Perl often don't sound great when spoken, or look good when written in prose. For this reason, we tend to say things like "customer" or "basket" when we are referring to "My::Site::User::Customer" or "My::Site::Shop::Basket". We thought it would be nice if our classes knew what we would prefer to call them. This module will add a "moniker" (and "plural_moniker") method to "UNIVERSAL", and so to every class or module. moniker $ob->moniker; Returns the moniker for $ob. So, if $ob->isa("Big::Scary::Animal"), "moniker" will return "animal". plural_moniker $ob->plural_moniker; Returns the plural moniker for $ob. So, if $ob->isa("Cephalopod::Octopus"), "plural_moniker" will return "octopuses". (You need to install Lingua::EN::Inflect for this to work.) AUTHORS
Marty Pauley <marty+perl@kasei.com>, Tony Bowden <tony@kasei.com>, Elizabeth Mattijsen <liz@dijkmat.nl> (Yes, 3 authors for such a small module!) COPYRIGHT
Copyright (C) 2004 Kasei This program is free software; you can redistribute it under the same terms as Perl. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. perl v5.10.0 2009-06-09 moniker(3pm)