Contact person: Business Client

Phone:Show

Email:Show

Location: Airoli, India

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"Our registration OTPs reach phones every time, yet the password-reset flow stays silent. Same Twilio account, same credentials, both endpoints live in a Node.js codebase running Express—still, only one of them delivers.

Here’s what I have done already: combed through Twilio settings, compared logs for both flows, rotated keys, tweaked the backend logic, and even ruled out obvious network issues. None of those attempts solved the problem, so I need a fresh set of expert eyes on the integration.

You’ll dive into the existing Git repository, trace the two OTP paths, inspect Twilio console callbacks, and uncover whatever subtle difference is blocking the password-reset messages. Whether it’s a Messaging Service mis-config, a Verify service mismatch, or a silent exception in the Node.js SDK, the task ends only when the reset OTPs arrive as reliably as the registration ones.

Deliverables
1. Identify the exact cause of the non-delivering password-reset OTP.
2. Apply and document the code or configuration fix.
3. Demonstrate successful delivery to test numbers (US and international).
4. Provide a brief report outlining findings, steps taken, and any recommended follow-up actions.

The stack is straightforward—Node.js, Express, Twilio Programmable Messaging/Verify—so deep familiarity with those tools, plus the usual webhook and log-tracing techniques, is essential. I’ll give you repo access and Twilio credentials in a secure channel the moment we start." (client-provided description)