Integration
Course enquiry funnel with OTP verification
A Flask lead-capture flow: dependent dropdowns, OTP-verified contact details, and a brochure released only to verified enquiries.
Own buildProduction build
01The problem
What it had to solve.
Education enquiry forms fill up with junk numbers, and the brochure gets downloaded by people who never intended to enrol. Both problems come from collecting contact details nobody ever verifies.
02The build
How it was put together.
- Enquiry form with dependent dropdowns — country drives state, course type drives course name — served from the database rather than hardcoded
- OTP generation and verification before an enquiry is accepted, so the phone number is real
- Brochure download gated behind successful verification, with a separate path when none is available
- Payment integration wired in for paid course flows
- Deployed as a WSGI application against SQL Server
Stack
FlaskPythonSQL ServerWSGIJavaScript
What it demonstrates
- Treating lead quality as an engineering problem, not a marketing one
- Multi-step server-side flows where each step validates the one before it
- Integrating third-party OTP and payment providers end to end
Next step
Tell us what you are trying to build.
A first call is thirty minutes, costs nothing, and ends with a straight answer about whether we are the right group for it — plus the names of the specialists who would actually do the work.