Ways to describe location bandwidth requirements
-
Well, I would see it as you have two ways you can go about it, depending on your reasoning for finding out this information.
"How fast is your internet?" coupled with "Do you find yourself waiting for pages to load or items to download more than you'd like?" may be a good starting point without getting into detail. It will at least tell you their level of satisfaction with their current speeds.
Or
"What internet speed does your company pay for?"
This should at the very least prompt them to ask the right people. If they were tasked with taking interest in your services, they should be at least partially invested in getting you the information you need.
-
@FiyaFly said in Ways to describe location bandwidth requirements:
@DustinB3403 Fair enough. My mistake for assuming on that one. I apologize. Though, still in my mind, as a decision maker they should, in theory, have at least some knowledge on that purchase, or be able to find it. Maybe not via speed test, but via billing, IT, C-level execs. I feel like in this day and age quite a few departments have an idea of that.
Oh man - this is a problem I have around here - people just decide that they need a new website to make something work. be damned that the website needs a 4 year old version of Java and only runs on XP - they gotta have it.
-
I think you might have failed long before you come to this point.
Why not back this whole thing up.
On your website that talks about your services, have a button that says - test my connection to make sure this service will work for you. have you web team install their own speed test - thing - and you can do a test directly from your own system to make sure they won't have any issues because they even look any further.
-
@Dashrender said in Ways to describe location bandwidth requirements:
I think you might have failed long before you come to this point.
Why not back this whole thing up.
On your website that talks about your services, have a button that says - test my connection to make sure this service will work for you. have you web team install their own speed test - thing - and you can do a test directly from your own system to make sure they won't have any issues because they even look any further.
The issue with this is that we could potentially loose clients without even knowing about them. And we can still provide our service, just a less bandwidth intense variety of it.
-
@DustinB3403 said in Ways to describe location bandwidth requirements:
@Dashrender said in Ways to describe location bandwidth requirements:
I think you might have failed long before you come to this point.
Why not back this whole thing up.
On your website that talks about your services, have a button that says - test my connection to make sure this service will work for you. have you web team install their own speed test - thing - and you can do a test directly from your own system to make sure they won't have any issues because they even look any further.
The issue with this is that we could potentially loose clients without even knowing about them. And we can still provide our service, just a less bandwidth intense variety of it.
Then make your website give the options - or don't do the test until after they click through. But make the running of the test a requirement when someone calls you - Hey before I can talk about pricing for whatever, you need to visit our website and click this button. The questionnaire seems just weird.
-
@Dashrender And what if the buyer isn't at the facility where the bulk of the participants are joining from? Or what if there are participants joining from a starbucks or mc.d's etc. . .
Then we'd have misleading information and the supposed promise of a successful product delivery.
-
@DustinB3403 said in Ways to describe location bandwidth requirements:
@Dashrender And what if the buyer isn't at the facility where the bulk of the participants are joining from? Or what if there are participants joining from a starbucks or mc.d's etc. . .
Then we'd have misleading information and the supposed promise of a successful product delivery.
LOL like you can ever get away from that! Then you list in HUGE letters - these tests need to be done from any locatoin that will be used for this training to ensure compatibility.
-
@Dashrender said in Ways to describe location bandwidth requirements:
@DustinB3403 said in Ways to describe location bandwidth requirements:
@Dashrender And what if the buyer isn't at the facility where the bulk of the participants are joining from? Or what if there are participants joining from a starbucks or mc.d's etc. . .
Then we'd have misleading information and the supposed promise of a successful product delivery.
LOL like you can ever get away from that! Then you list in HUGE letters - these tests need to be done from any locatoin that will be used for this training to ensure compatibility.
Eh.... "conditions apply dial-up internet not supported. TWC $14.99 not supported"
I see the customers running already...
-
@DustinB3403 said in Ways to describe location bandwidth requirements:
@Dashrender said in Ways to describe location bandwidth requirements:
@DustinB3403 said in Ways to describe location bandwidth requirements:
@Dashrender And what if the buyer isn't at the facility where the bulk of the participants are joining from? Or what if there are participants joining from a starbucks or mc.d's etc. . .
Then we'd have misleading information and the supposed promise of a successful product delivery.
LOL like you can ever get away from that! Then you list in HUGE letters - these tests need to be done from any locatoin that will be used for this training to ensure compatibility.
Eh.... "conditions apply dial-up internet not supported. TWC $14.99 not supported"
I see the customers running already...
running away...
-
@DustinB3403 said in Ways to describe location bandwidth requirements:
@Dashrender said in Ways to describe location bandwidth requirements:
I think you might have failed long before you come to this point.
Why not back this whole thing up.
On your website that talks about your services, have a button that says - test my connection to make sure this service will work for you. have you web team install their own speed test - thing - and you can do a test directly from your own system to make sure they won't have any issues because they even look any further.
The issue with this is that we could potentially loose clients without even knowing about them. And we can still provide our service, just a less bandwidth intense variety of it.
Maybe just detect the speed and adapt accordingly.
-
@scottalanmiller said in Ways to describe location bandwidth requirements:
@DustinB3403 said in Ways to describe location bandwidth requirements:
@Dashrender said in Ways to describe location bandwidth requirements:
I think you might have failed long before you come to this point.
Why not back this whole thing up.
On your website that talks about your services, have a button that says - test my connection to make sure this service will work for you. have you web team install their own speed test - thing - and you can do a test directly from your own system to make sure they won't have any issues because they even look any further.
The issue with this is that we could potentially loose clients without even knowing about them. And we can still provide our service, just a less bandwidth intense variety of it.
Maybe just detect the speed and adapt accordingly.
Our system does this already, and the result is an unacceptable live product. There are other solutions, but others put the cart before the horse here and bought expensive software and are determined to "make it work".
-
@DustinB3403 said in Ways to describe location bandwidth requirements:
@scottalanmiller said in Ways to describe location bandwidth requirements:
@DustinB3403 said in Ways to describe location bandwidth requirements:
@Dashrender said in Ways to describe location bandwidth requirements:
I think you might have failed long before you come to this point.
Why not back this whole thing up.
On your website that talks about your services, have a button that says - test my connection to make sure this service will work for you. have you web team install their own speed test - thing - and you can do a test directly from your own system to make sure they won't have any issues because they even look any further.
The issue with this is that we could potentially loose clients without even knowing about them. And we can still provide our service, just a less bandwidth intense variety of it.
Maybe just detect the speed and adapt accordingly.
Our system does this already, and the result is an unacceptable live product. There are other solutions, but others put the cart before the horse here and bought expensive software and are determined to "make it work".
LOL - sunk cost fallacy
-
@Dashrender said in Ways to describe location bandwidth requirements:
@DustinB3403 said in Ways to describe location bandwidth requirements:
@Dashrender And what if the buyer isn't at the facility where the bulk of the participants are joining from? Or what if there are participants joining from a starbucks or mc.d's etc. . .
Then we'd have misleading information and the supposed promise of a successful product delivery.
LOL like you can ever get away from that! Then you list in HUGE letters - these tests need to be done from any locatoin that will be used for this training to ensure compatibility.
This happens all the time - and internet connections change, you the resller can't control that.
-
@Dashrender said in Ways to describe location bandwidth requirements:
@DustinB3403 said in Ways to describe location bandwidth requirements:
@scottalanmiller said in Ways to describe location bandwidth requirements:
@DustinB3403 said in Ways to describe location bandwidth requirements:
@Dashrender said in Ways to describe location bandwidth requirements:
I think you might have failed long before you come to this point.
Why not back this whole thing up.
On your website that talks about your services, have a button that says - test my connection to make sure this service will work for you. have you web team install their own speed test - thing - and you can do a test directly from your own system to make sure they won't have any issues because they even look any further.
The issue with this is that we could potentially loose clients without even knowing about them. And we can still provide our service, just a less bandwidth intense variety of it.
Maybe just detect the speed and adapt accordingly.
Our system does this already, and the result is an unacceptable live product. There are other solutions, but others put the cart before the horse here and bought expensive software and are determined to "make it work".
LOL - sunk cost fallacy
Yes it really is... I had a solid solution, explained why, and for 1 minuscule reason it was veto'd. Yet it offers us the best option, without the need to worry about the clients internet bandwidth....
so... just ask "how fast is your internet?"
