-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] Test incoming texting regularly #438
Comments
… testing easier in support of #438.
@danry25 you can now use the new GET /client/test endpoint in the Swagger doc to test the functionality of any registered number. |
This is a neat endpoint, but I would like this to use a different SMS endpoint to send the SMSes so that way its coming from a different SMS network. |
Todos: @danry25 set up the actual testing hardware |
What is the problem that this feature solves?
Occasionally SMS routing disappears from a formerly active number, or is improperly set. If we send a test text message to each phone number we can detect when this happens and take corrective action (re-SMS enabling a number, reaching out to the client to let them know their SMS routing has been overridden and by who).
Describe the solution you'd like
We can hit an API to send a test text to each number, then prevent final delivery on sms.callpipe.com
How will this improve revenue or reduce our costs?
This will reduce the burden on our support team by allowing us to have accurate data on whether texting works on a phone number.
The text was updated successfully, but these errors were encountered: