[VoiceOps] Rephrased Question: 100+ seat MIGRATIONS to VoIP
carlos at televolve.com
Wed Feb 1 19:01:05 EST 2012
On Wed, Feb 1, 2012 at 4:51 PM, Tim Bray <tim at kooky.org> wrote:
> If the primary consideration is that the system has to be like the old
> one. Then you are lost. The correct solution is the old one. Don't
> change it. Connect some SIP trunks and keep quiet.
> If you dump the system in, they will want the key system features because
> they want the lights to find who is free in the sales department to take
> the call. You are on the back foot from day one. Trying to play catchup
> with user requirements.
Never let users drive requirements that are process oriented, force them to
give results and you drive the process.
> A proper customer requirements analysis is what is required. Most VoIP
> companies presume all phone systems are simple. They also seem scared to
> bill the customer for installation planning time.
Our business is very consultative (we don't charge for it up front), and it
results in customers who can't leave us. One said he got an offer for "the
same and more features" for a lot less money, so I said goodbye. He called
the day before porting to have us block the port since the other company
couldn't deliver half of what we did.
Be different, even if you think the customer doesn't want the hassle. Look
at the end result, not the process, as the goal.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the VoiceOps