Pressing the '1' key is the golden rule of collecting a ResponseiQ callback. No matter which call setting you're on, you will need to press 1 to tell our system you're ready and raring to go.

But what happens if you press it and the voice keeps repeating on a loop, or there's silence and the call disconnects?

Firstly, check your handset, switch it on and off again, and restart your system. It sounds obvious but 9/10 it's a handset glitch where our system hasn't recognised yours.

Secondly, don't panic - call the person back via the email you received so you don't lose them. Unless the problem happens consistently (twice in a row, more than three times in the same hour) it is likely to be due to the following known concerns:

VoIP phones systems sometimes run into DTMF issues because the system uses non-standard DTMF tones by default. These problems can usually be resolved by altering the settings on the VoIP system itself. If a VoIP system provides multiple DTMF options, try testing each of these options to see which one works the best.

The browser-based version of Google Voice has known issues with DTMF.

Any issue which causes sound to be lost or altered, such as poor reception, poor audio quality or significant background noise, can also make it difficult for carriers to distinguish between DTMF and other noise.

If you're worried about this error and it keeps happening, drop us a message on Intercom or email support@responseiq.com with the following info:

Call ID

We really appreciate as much info as possible, otherwise we're going in blind. You can find this in Call Reports.

We'll take a look for you as soon as we can. Let us know if it's happened more than once in the same day as this helps us to escalate the issue.

If you were interested in this article, we also have an article about our Voice-to-Claim feature here: http://knowledge.responseiq.com/en/articles/3992977-voice-to-claim