sundance-communications.com/forum Forums TDM Business Telephone Systems Toshiba Telephones & Systems List of features that can be put on buttons

We are getting ready to do a big install (CIX 670). We ant to give each of the employees a list of how we can program their buttons. Along with a template. Does anyone have a list like this already made up?

Also has anyone figured out how to program a greeting key on the phone so you can switch between greetings easily?

Come on now. You are about to do a big install and you do not have a manual or a trained installer. I feel for this future unhappy client.

We have both of those. I didn't want to give the CEO a manual and tell him, What buttons do you want on your phone. I was looking to see if anyone had created a quick reference list so I didn't have to reinvent the wheel.

autochange.

I have not seen a Toshiba "Feature" cheat sheet that explains buttons. There are the horrible sales brochures, uck, ouch, no.

I do have just such a list for Samsung, but didn't make one up for Toshiba, just so few hours I am not sleeping now.

Here is a sample of what I made for Samsung:

OHVA – if this is an assigned button on your phone, you can “flip” the call in order to deliver a short message “Peter is on line three,” then the call flips back to normal.

(You can also have an OHVA Reject button, so you can kill that announcement)

(You can also have an OHVA Block button, so all OHVA announcements are blocked while that button is in the “ON” position.

Directory – Look through all speed dial entries on your phone or in the system

Save # - The number you called is busy and you press this button and make other calls. Press this button any time later and your call is dialed. (Like a last number redial stuck away in a pocket for later use.)

Redial # - Redials your number up to 15 times trying to get through a busy line.

Call forward – transfers your calls to another extension for until you change the transfer.


If anyone would like to do this for the pre-CIX systems (DK 16 to DK424i) and CIX systems, that would be a really nice thing to do.

Personally, I would just give them a normal DKT template and that's it. Only if they wish for a feature, would I think for a while before giving them the solution.

This was because years ago, I did the same thing and after the installation, the customer (using the Toshiba Strata DK280's back page brochure) made me sit with him and list down all the features one by one. Yeah, after three hours, I started not to like Program 39. For the next few weeks, we had to go back and forth to implement/disable features as the customer got confused/preferred other reafures.

So now, the most I would do would be DSS assignments, Account Codes, Door Locks and the occasional one touch dials via System Speed Dials.

Phew.

I have what I call a system design worksheet that I send to every new customer prior to the install along with a list of questions and sample keymaps. i then have a meeting to "design" their system. By giving then the worksheet, they can read about the most popular features and I deal with questions and requests in the meeting. After the meeting, I program the system in the office and then install it. This does a few things: 1. The tech isn't programming while the customer is watching. 2. The system can be tested before being installed so it makes the installers look better. 3. The overall installation goes much better!!!

If anyone wants my documents, please e-mail me. I will be happy to share!!

Amy

I've only been programing telephone systems a less then 3 years (as a primary fuction) and see how customers can be so frustrating with setting up AA, ringing, buttons, etc, which are always last minute decisions, while my company is calling me to see why I'm not at my next job yet.

I often make the mistake of asking the customer at the end of an install how he wants it configured, which can take hours, while they have a with others. Then change there minds after they see how it works.

I always offer suggestions. I know some installers will set up a system the way they think it should be set up, then tell the customer that this is how it works, with out discussing options. Here ya go, see ya later.

I usually don't have the option of having a meeting with the end user, but I have been thinking about putting together a questionaire to be filled out by them while the system is being installed by me.

have the sales people take care of the features requests.. besides, they would have had to discuss features if they got the sale - they promise it, we just try to make it happen. about the greetings change, try myphonemanager for end users.

Ya, like the time the customer was told that with his brand new Stratgy ES he could record his calls with a push of the button, except that he had a DK system that didn't support it...

But these guys here are usually pretty good. Owner was a tech, and is active in most quotes/proposals (I hate it when a non-technical sales person try to run a project). Sometimes it says on the work order if there is a feature they definately want.

And to be honest, I can be my own worst enemy, like when I try to sell them a system they already own, by telling them all the great things it does, and then hear "Oh, we want it to do that" after I already packed up my Laptop..

I feel like I'm always learning, and not just the technical issues.

I think myPhoneManager would work in some situations. I have not installed it yet in a new site. Usually, without a MAS, too many network issues, with PC securtiy etc. Some sites have no admin rights on their PCs. Emanager won't run on server 2003, so I'd guess MyPhoneManager won't either.