We'll see how it goes. I have 30 days to try it out and if I don't like it, I get my $99 back. I don't think I'll be sending it back! 
She did the plugging in & such, set up the software activation on the phone, did a test call, showed me the settings and how to access, etc., and we were actually done in a short amount of time. Chatted about the phone the rest of the hour, LOL! 
I am keeping a log. Besides sometimes the captioning not kicking in & having to hang up & redial. Sometimes captions has also failed for incoming calls and I've had to ask people to hang up & call again. 
Also, one message so far did not have captions w/ voice so faint even w/ maxed out volume (on both hearing aids & phone) I could not hear speaker. Fortunately my DH (husband) was able to hear enough to get name + phone #. Other times message is fine and incoming & outgoing are fine. I have 30 days so will see how it goes...will email them my log to see what they may suggest, if the problems continue. When it works, it's awesome. When it's not... 
So, I put my hearing DH (hubby) on and the upshot was that we can't do it wirelessly, even just across the room. Not enough signal strength. So phone is on the computer table next to the computer. DH connected the phone with an Ethernet cable. So now it appears to have solved the problem and the phone is showing full reception instead of 3 marks. I have a couple more weeks to continue evaluating. I'll get my $99 back and send them their phone if the service isn't better. I can always go back to never answering the phone, using my IP-Relay phone number for call backs, and use the free state Captel phone to call out. I'm thinking this technology, while totally worthy if we can actually answer our phones and not worry about incoming captioning or that people calling us are idiots who don't call the special access # to give us captioning. But it's useless if it's going to be erratic service... 
Today I finally got ticked off at the phone... I had to dial a number EIGHT times before the dang captioning kicked in before the call connected & I would get a stupid message the captioning had failed. No kidding, CapTel! :roll: So I hit the customer service button -- and even *that* captioning failed!
. So that is why this technology is so appealing to me. But if it's not going to work consistently, it's not worth it. I never have had to redial because captioning did not kick in with the old freebie CapTel. Only with this new internet version.
I hope it works for you!!!
We did talk to them and ended up hooking the phone directly with an Ethernet cable. No go with operating wirelessly across the room from our computer setup. It works consistently now, but having it on the network *does* slow down our Internet feed. Found out our DSL is the 3.0 Mbps variety and that is just not enough "oomph" to handle both the phone and the Internet. However, the good news is I found out in our area DSL 6.0 Mbps is available at the same cost to use by our ISP. I am in the midst of working with them to get it set up. While these captioning phones just say "DSL" they should caution about the 3.0 Mbps DSL slower feed vs. faster speed, IMO. It can make a huge difference. We didn't have this download slowdown when online before we had the phone, so I know it's the addition of the phone that is causing the slowdown. Hopefully we'll get around that, though. 
So we rehooked everything into different ports as some techie online friends suggested, who were familiar with our Mac setup. That didn't help either. So we call the CapTel customer service tech back that helped us before and we are now conducting a new "experiment:" 
we now turn off the captioning button on the phone whenever we are online, which disconnects the phone from the internet. We can still get captioning when the phone rings by first pushing the caption button on before lifting the handset. Then incoming/outgoing is captioned. When we're done with the internet, then we turn caption button back on, on the phone.