[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference ilbbak::us_sales_service

Title:US_SALES_SERVICE
Notice:Please register in note 2; DVNs in note 31
Moderator:MCIS3::JDAIGNEAULT
Created:Thu May 16 1991
Last Modified:Tue Sep 03 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:226
Total number of notes:1486

189.0. "How can we improve communication with the sales force?" by SMAUG::GARROD (From VMS -> NT; Unix a mere page from history) Thu Apr 22 1993 20:32

        
    What is the best way to make information easily retreivable by the
    sales force? In these days of people downsizing I think it is key to
    have information available in the right format.
    
    As you can see from the attached I have made a lot of information
    available on the product set I'm responsible for right from a high
    level presentation for sales reps to give to a customer and its
    scripted version, right down to much more detailed information
    on the product set.
    
    I regularly get calls from sales reps looking for information. But
    after sending them this file when they call back the conversation
    often goes like this:
    
    Sales Rep: "Thanks for all the information you sent me. Unfortunately
    	I haven't been able to look at it yet. I've asked Joe Blow our
    	last remaining sales support person in this office (the rest got
        TSFOed) to copy the files to the one workstation we have in this
    	office and print them off. I should get them in the next few days.
    	Us sales reps only have access to ALL-IN-1 and can't easily get
    	information off the net.
    
    	But meanwhile I have the following questions, I'm meeting with
    	the customer this afternoon..."
    
    Now the reason I put all this information together was to make the
    process more efficient. I am deliberately after getting the information
    into the hands of the sales reps. I'm not at all interested in getting
    the information into the hands of the sales support people. That comes
    after the sales rep has got a good lead. But it seems that the system
    is not set up for sales reps to easily get the information that I have.
    Hence I have to answer the same questions over and over again that
    are already answered in the material referenced below. I'm quite happy
    to do that because it means sales of our products and I have found that
    sales reps will actually go out and push products where they feel there
    is some solid support behind them. But I'd like to save myself and my
    team for the questions that aren't answered in the written material.
    
    Yes we'll get the presentation into OPAL. But my question is what is
    the best way of making the .PS files available?
    
    Dave
    
    
00SALES_KIT.LIS		22-Apr-1993

This directory (SMAUG::GWYS:[3270_TO_VAX]) contains information on products
that address 3270 connectivity to DEC application needs. 3270s include real
3270 terminals, SNA networked PCs and SNA LAN networked PCs.

All products in this product set are shipping in volume. If you need further
information please contact SMAUG::GARROD.

The following files are in this directory. All of these files are world
readable and may be copied. The contents of these files are intended to be
used as sales tools and may be shared with customers except where marked
"Digital Internal Use Only" or "Digital Confidential". At the end of this
file is a set of COPY commands to copy these files to your system.

00SALES_KIT.LIS		- This file.

SALES_KIT_MEMO.TXT	- Overview information about the products
			  and this Sales Kit.

DOMAIN_CUSTOMER_PRESENTATION.PS
			- High level customer presentation designed for use
			  by sales representatives seeking out Computer
			  Downsizing opportunities in accounts with a large
			  IBM presence. 

DOMAIN_CUSTOMER_PRESENTATION_SCRIPTED.PS
			- Scripted version of DOMAIN_CUSTOMER_PRESENTATION.PS

DOMAINCP.PPT		- Powerpoint version of DOMAIN_CUSTOMER_PRESENTATION.PS

DOMAIN_SALES_FLYER.PS	- Two page (or one page double sided) flyer covering
			  MEP VT and Domain Gateway for handing out to potential
			  customers.

DOMAIN_PROMOTION_SALES_FLASH.TXT
			- Q4 FY93 Sales Flash announcing 15% off promotion
			  program for a 3270 Connectivity / Domain Gateway
			  solution.

DOMAIN_FACT_SHEET.PS	- Fact sheet on the DEC SNA Domain Gateway-CT.

MEP_VT_FACT_SHEET.PS	- Fact sheet on MEP VT for DEC SNA 3270 Application 
			  Services.

QUESTIONS.TXT           - Questions and answers about this product set

ORDERING_STEPS.TXT	- Step by step instructions on the part numbers to quote
			  when ordering MEP VT, 3270 Application Services and
			  the Domain Gateway.

DOMAIN_INSTALLATION_SERVICE.TXT
			- Description of policies around how to get installation
			  services (QSF08-SZ or QSF06-SZ) delivered.


DOMAIN_GWY_SPD.PS	- DEC SNA Domain Gateway, V1.0 SPD 38.69.xx

3270_SERVICES_SPD.PS	- DEC SNA 3270 Application Services, V1.0 SPD 38.70.xx

MEP_VT_SPD.PS		- MEP VT for DEC SNA 3270 Application Services, V2.3
			  SPD 44.00.xx

NEW_VAX_TIMES_ARTICLE.TXT
			- November "New VAX Times" article on 3270 Connectivity
			  and the Domain Gateway

SALES_UPDATE.TXT	- *CORRECTED* DEC SNA Domain Gateway, DEC SNA 3270
			  Application Services Sales Update announcement
			  article.	  Volume 23 No.15, May 4. 1992.
			  (pricing error has been corrected).

MEP-VT220_SALES_UPDATE.TXT
			- MEP-VT220 for 3270 Application Services
			  sales update article.

DECUS_DEC92_OVERVIEW.PS - DECUS Presentation, IBM Interconnect Product
			  Set Overview includes slides on Domain Gateway.

DECUS_DEC92_SNAPU5.PS	- DECUS Presentation, Digital's DEC SNA Domain Gateway.
			  Technical overview.

DECUS_DEC92_3270.PS	- DECUS Presentation, 3270 Connectivity to
			  VMS Applications. Technical overview.

$COPY SMAUG::GWYS:[3270_TO_VAX]00SALES_KIT.LIS * 
$COPY SMAUG::GWYS:[3270_TO_VAX]SALES_KIT_MEMO.TXT *
$COPY SMAUG::GWYS:[3270_TO_VAX]DOMAIN_CUSTOMER_PRESENTATION.PS *
$COPY SMAUG::GWYS:[3270_TO_VAX]DOMAIN_CUSTOMER_PRESENTATION_SCRIPTED.PS *
$COPY SMAUG::GWYS:[3270_TO_VAX]DOMAINCP.PPT *
$COPY SMAUG::GWYS:[3270_TO_VAX]DOMAIN_SALES_FLYER.PS *
$COPY SMAUG::GWYS:[3270_TO_VAX]DOMAIN_PROMOTION_SALES_FLASH.TXT *
$COPY SMAUG::GWYS:[3270_TO_VAX]DOMAIN_FACT_SHEET.PS *
$COPY SMAUG::GWYS:[3270_TO_VAX]MEP_VT_FACT_SHEET.PS *
$COPY SMAUG::GWYS:[3270_TO_VAX]QUESTIONS.TXT *
$COPY SMAUG::GWYS:[3270_TO_VAX]ORDERING_STEPS.TXT *
$COPY SMAUG::GWYS:[3270_TO_VAX]DOMAIN_INSTALLATION_SERVICE.TXT *
$COPY SMAUG::GWYS:[3270_TO_VAX]DOMAIN_GWY_SPD.PS *
$COPY SMAUG::GWYS:[3270_TO_VAX]3270_SERVICES_SPD.PS *
$COPY SMAUG::GWYS:[3270_TO_VAX]MEP_VT_SPD.PS *
$COPY SMAUG::GWYS:[3270_TO_VAX]NEW_VAX_TIMES_ARTICLE.TXT *
$COPY SMAUG::GWYS:[3270_TO_VAX]SALES_UPDATE.TXT *
$COPY SMAUG::GWYS:[3270_TO_VAX]MEP-VT220_SALES_UPDATE.TXT *
$COPY SMAUG::GWYS:[3270_TO_VAX]DECUS_DEC92_OVERVIEW.PS *
$COPY SMAUG::GWYS:[3270_TO_VAX]DECUS_DEC92_SNAPU5.PS *
$COPY SMAUG::GWYS:[3270_TO_VAX]DECUS_DEC92_3270.PS *
T.RTitleUserPersonal
Name
DateLines
189.1Since you askedGUCCI::HERBAl is the *first* nameThu Apr 22 1993 23:2933
    I'm a little technical and work within a sales team so that I see/hear
    the frustrations that they voice. The simplist answer from my
    observation is TRAINING....once we've made our minds up with WHAT tools
    we want to train the rep on.
    
    I've personally been through the Sales Training (5 years ago) and they
    taught little on tools and how to get information (even VTX). There's
    been some attempts to help with publications such as the Yellow Pages.
    Unfortunately, management simultaneously began restricting access for
    Reps that went beyond All-In-1. Recently, for example, the capability
    to get to the infamous $ thru a UDK was blocked.
    
    We should not dump on the sales force for the simple reason that our
    Corporation has done everything possible over the years to prevent the
    Rep from being computer literate. On the brighter side though, I'm
    hearing of efforts from within IM&T and EDU that are aimed at
    correcting some of this. Some of it is automation. Some of it is as
    simple as having a SINGLE repository for online information such as
    OPAL. Let's face it, when we have to tell the field multiple ways to
    obtain information ("From Unix/VMS/Pathworks, etc, etc") what does one
    expect?
    
    Check out VTX lately. Under the Access/Sales Updae Menu, there's the
    banner that Sales Update has been merged with Business Partner update.
    I searched all over for a "Business Partner Update" section on VTX
    (there isn't any). Strangely enough though, the latest (printed) Sales
    Update is no where to be found online under any category. All the
    while, VOGON announces the "new look of VTX"....and of course,
    interesting services such as Order Status go off the air for several
    says.
    
    I'm sure you are doing your best but there's more fixin to the system
    that needs to be done first.
189.2RCOCER::MICKOLAlmost 'Falling Down'Fri Apr 23 1993 00:4440
This is a dilemma. I'm the lone Sales Support Consultant in the U.S. for the 
Xerox Account Team, so I'm the one who has to go get the .PS files printed.
A few months ago, when all of the reps were bound to their character-cell 
terminals and ALL-IN-1, I would have said, forget it.

Now, all of the reps I support have 325p notebook PCs with Microsoft Office 
and docking stations. They have done things with them you'd be amazed at 
(considering their lack of computer literacy a few months ago). All of the PCs 
are networked to a Pathworks server when connected to the docking stations, so 
we have file and print services.

Here is what I suggest:

	- Utilize VTX to disseminate as much information as possible, either 
	  through Sales Update or specific product/technology infobases.

	- Setup a mechanism to allow the reps to get access to powerpoint 
	  (.PPT) versions of your presentations/slides. This can be either
	  through a pointer to a directory or via an automated copy that
	  moves the file to the rep's local system.

	- Continue to utilize the notes files. Most reps dont access them now,
	  but I'm seeing more and more start to get into notes and check things 
	  out themselves.

The task of copying a .PS file from some remote directory to a local system 
and printing it is still out of the technical grasp of some of the reps I 
support, but clear instructions from your end and mine can solve that problem.

That is what I suggest based on our account team. I think we're somewhat 
unique, but hopefully the suggestion I listed above will have some universal 
appeal.

regards,

Jim Mickol
Sales Support
Xerox Account Team
Rochester, NY
DTN 252-7106
189.3Thabks so far, more info still welcomeSMAUG::GARRODFrom VMS -> NT; Unix a mere page from historyFri Apr 23 1993 10:4913
    Thanks for the suggestions so far. Please could somebody who
    understands the tools from the sales reps end tell me how to clarify
    the instructions in .0. I give the DCL COPY commands. How do I say how
    to print the docs, I've no idea of queue setup on the sales reps
    systems of course. Not to mention of course that what I posted in .0
    involves editing the received mail message and extracting the COPY
    commands from the end.
    
    As you see here is a .PPT filer for one of the presentations. We'll get
    that into OPAL but is just having it in a directory like I've done OK
    as well?
    
    Dave
189.4PostScript Printing Instructions May Help.MCIS3::RISTMon May 03 1993 18:14122
    The following PostScript Printing Guide was created last year for the 
    PostScript Printer Project and distributed to all field personnel 
    throughout the U.S. via ALL-IN-1.  This guide was created by U.S. 
    Education and Training.  If needed it could be updated.
    
    Let me know if you have any questions.
    
    Holly Rist
    U.S. Sales IM&T 
    
    =======================================================================
       POSTSCRIPT PRINTING WITH ALL-IN-1 V3.0
    =======================================================================

       SECTION I - INTRODUCTION
       The purpose of this guide is to help you print PostScript 
       documents in your ALL-IN-1 environment. The three areas 
       covered are:
    
       - Printing PostScript documents you have obtained from OPAL 
         (Online Presentation Access Library); Section II.

       - Printing PostScript documents mailed to you as attachments to 
         ALL-IN-1 mail messages; Section III.

       - Importing PostScript files from VMS to ALL-IN-1; Section IV.
    
    
       SECTION II - PRINTING DOCUMENTS FROM OPAL (ONLINE PRESENTATION 
       ACCESS LIBRARY)
       There are two types of documents you can mail to your ALL-IN-1 
       account from OPAL and print:
 
       - Text-only documents: These documents, such as descriptions 
         and scripts for slide presentations, do not require the use 
         of a PostScript printer.
       
       - Text and graphics documents: These documents, such as slide 
         presentations, contain text and graphics and require a 
         PostScript printer to be printed. NOTE: These documents tend 
         to be very large and can possibly exceed the ALL-IN-1 account 
         quotas. If the document is too large to mail, contact your 
         Help Desk for assistance.    
    
       STEP 1: Obtaining the Document from OPAL
       	         	  					          
       A. Select the documents you want mailed to your ALL-IN-1 mail 
          account.
       B. Be sure that the mail address you specify in OPAL is your 
          ALL-IN-1 address, for example: Jane Brown @TTB.

       STEP 2: Printing to a PostScript Printer

       A. In the current item block, display the document to be printed. 
          Alternately, you can place the pointer next to the document in 
          an index.
       B. Enter P (Print) and press <RETURN>.
       C. Enter the name of the print queue in the Document Destination 
          field and press <TAB> to move the cursor in the Print Style 
          field. NOTE: To view the available print queues, clear the 
          Document Destination field and press GOLD/L or the <FIND> key.  
       D. If printing to a PostScript printer, enter PS in the Print Style 
          field and press <RETURN>. NOTE: This field can be left blank If 
          you are printing to a non-PostScript printer.
    
       SECTION III - PRINTING POSTSCRIPT ATTACHMENTS RECEIVED IN 
       ALL-IN-1 MAIL       
       The following steps describe how to print a PostScript document 
       received as an attachment to an ALL-IN-1 mail message.
    
       STEP 1: Filing the PostScript Attachment
       When you receive an ALL-IN-1 mail message with a PostScript 
       attachment, file the attachment and assign it folder and title 
       names that are meaningful to you as follows:
    
       A. In the current item block, display the document you received that 
          contains the PostScript attachment. Alternately, you can place 
          the pointer next to the document in an index.
       B. Enter FA (File Attachment) and press <RETURN>.   	
       C. Enter a folder name (e.g. PostScript Documents) and press <TAB> 
          to move the cursor to the Title field.  	
       D. Enter a Title name (e.g. Filed Document) and press <RETURN>.	  
                    
       STEP 2: Printing to a PostScript Printer
       Once the PostScript attachment has been filed, print it as 
       follows:   
       	         
       A. In the current item block, display the document to be 
          printed. Alternately, you can place the pointer next to the 
          document in an index.      	
       B. Enter P (Print) and press <RETURN>	
       C. Enter the name of a PostScript print queue in the Document 
          Destination field and Press <RETURN>. NOTE: To view the 
          available print queues, clear the Document Destination field 
          and press GOLD/L or the <FIND> key.
       D. Enter PS in the Print Style field and press <RETURN>.
       
       SECTION IV - IMPORTING POSTSCRIPT FILES FROM VMS to ALL-IN-1
       When importing PostScript files from VMS to ALL-IN-1, use the 
       following steps:

       A. Select DT (Document Transfer)
       B. From the Document Transfer menu, select RVC (Receive without 
          Conversion). NOTE: If you select RV instead of RVC, you will 
          get an error message indicating that a PostScript file cannot 
          be converted to WPS-PLUS format.	
       C. Enter the file specification of the VMS PostScript file to be 
          imported and press <RETURN>.
       D. Enter a Title and use the <UP ARROW> to move the cursor to 
          the Folder field.
       E. Enter a Folder name and press <RETURN>
       F. The message DOCUMENT CREATED indicates that the PostScript 
          file now resides in your ALL-IN-1 account. NOTE: You can now 
          attach this file to an ALL-IN-1 mail message.

    





    
189.5Needs more workGUCCI::HERBAl is the *first* nameMon May 03 1993 20:487
    To be honest, 100 lines of instructions is too complex for the average
    sales rep who's focused on getting answers quick and selling. For an
    ASCII file, the way to print is a simple "p". Can't this process be
    automated in some fashion?
    
    The instructions may be clear and seem simple but too lengthy tobe
    filed in the bag of a rep for "quick reference".
189.6Thanks for the follow upSMAUG::GARRODFrom VMS -&gt; NT; Unix a mere page from historyWed May 05 1993 10:5262
    
    First of all I'd like to thank Curtis Martin and Holly Rist of US Sales
    IM&T for following up on .0 to me offline and also for the reply in
    this file. Attached is the response I sent to their offline followup.
    
    Apparently for the future there is a great system of Powerpoint being
    put in place so that we will no longer have to leave postscript files
    around. But of course the problem there will that few in engineering/PM
    will have access to powerpoint. I'm still trying to get my VP's
    signature for getting the $50 Powerpoint software through the SSB (see
    my story in DIGITAL.NOTE if interested under a "A tale of two
    companies").
    
    Re .-1 I agree this procedure does seem overly complex to just
    remember. Also as you can see from my response below it is missing the
    step to actually get the .PS file to the local system.
    
    Dave
    
From:	SMAUG::GARROD "An Englishman's mind works best when it is almost too late  05-May-1993 0946 -0400"  5-MAY-1993 09:46:47.04
To:	GARROD
CC:	
Subj:	Follow up message

I'd like to thank you both for your phone messages and mail replies. I
tried to call you back but only got voicemail so didn't leave a message,
hence this message.

I like the approach you are taking for the future around Powerpoint. Of
course my only disappointment is that it is not in place now. Some suggestions
on making sure people know about it in the future. Key thing is to make sure
that both information providers and information eaters both know. Since one
of the problems is that sales and engineering tend to run in parallel universes
sometimes you need to make sure that you publish clearly how to put information
into the system. Also don't make it hard to get info into the system. Ie don't
put too many gatekeepers in front of it. Ie things like call xxx to get access
to system yyy and then register with person zzz if you can get hold of them.

Holly, regarding the ALL-IN-1 instructions for getting postscript files
across the network into ALL-IN-1. I think you're missing an important
step. You say how to get the postscript files into ALL-IN-1 from VMS but
that assumes they are local. You leave it unsaid how to move the postscript
files from wherever they are on the network to the local sales rep's system.
This is key. Not knowing what their ALL-IN-1 environment looks like I
can't give instructions. What they really need is FTSV installed on their
ststem so that from DCL they can issue the command:

SPOOL COPY remote::interesting-file.PS local-file.PS
or even just:
COPY remote::interesting-file.PS local-file.PS

Then they can do the ALL-In-1 magic that you detail in your instructions.
But without that first bit I think they're still out of luck. And also I 
understand that for some reason I totally don't understand they're not allowed
to getr a DCL prompt. Given that how are they meant to transfer the .PS files?

Again I thank you for the fact that you followed up on this and obviously
recognize the problem.

Thanks,

Dave
189.7Plans for improvementUSSAIL::MARTINWed May 05 1993 19:3971
Dave was too quick for me, but here's the reply I sent him via mail:



Dave:  

Obviously, this problem is not new & is complicated by the current
business practice (on most systems) to prevent All-in-1 users from
getting DCL access.  

However, there is good news.  With the deployment of notebook PCs to the
US Sales Force last year, we began work on a PC infrastructure that would
simplify the process of taping into information such as yours.

Based on our pilot experiences with EPSS (Electronic Performance Support
Systems), we are creating a "core" PC utility called the Catalog
Librarian.  This tool, combined with a world-wide initiative to create
corss-database catalogs & indexes (focusing on VTX infobases first, but
expanding beyond that), will allow a Sales PC user to point and click to
browse the information that's available (using keywords, categories,
etc.).  They can then request the information.  If the user is connected
to the network, a request will go out over Pathworks.  If not, the modem
will be used to dial into a central server and make the request.  

The user can "queue up" a request for several information sources and,
whenever it's convenient, connect to the network.  At that time, the
requests will be submitted to the supplier sources, wherever they are
located on the EasyNet.  The user can wait online or, if the request is
expected to take a while to build, hang up and reconnect at a later time.

As a "information publisher", all you'll have to do is "register" your
information in the central catalog.  We've deployed MS Word, Excel, &
Powerpoint as the primary tools, so that's what you'd want to "publish"
your information in (shifting away from Postscript).

We hope to build the entire Sales PC application portfolio around this
architecture.  (It will be critical for product managers like yourself to
support this approach for information delivery by "publishing" in the
catalog.  If not, we'll end up with a nice looking tool that's
"content-free".)

That's the good news.  The not-so-good news is that we're still several
months away from being able to deploy and there are still a couple key
operational infrastructure prerequisites, but we're moving.  We'll be
piloting this with the HealthCare CBU in Q1.  If all goes well, we should
then be able to begin deployment in Q2.

In the meantime, we're pretty much stuck with All-in-1 as the least
common denominator for information dissemination.  Although you and many
others have experienced frustrations, things have actually gotten better
there as well.

Last year, we surveyed the field and provided many additional Postscript
printers to ensure everyone had access to one.  In addition, Kermit is
now available on all All-in-1 systems so that users can download to their
PCs.  Although technically possible, we still need to provide
direction and training.

At this stage, I'd recommend that you provide a "cheat sheet" that can
walk sales users through the copy & print (or download) process in a
step-by-step fashion.  

I've already asked one of my team members, Holly Rist, to contact you to
help develop a set of directions that will work on the field production
All-in-1 systems.

Please call me if you have any questions or suggestions.

Curtis Martin
Selling Productivity Tools Portfolio Manger
US Sales IM&T