Serhat Doğan — Founder, TwoLine

GitHub LinkedIn X [email protected]

I'm a London-based software developer building SMS verification tools full-time since early 2026. I founded TwoLine (multi-country virtual phone number rental, US/UK/NL) and contribute to VerifySMS (pay-per-SMS verification at $0.42/code), a sister brand. Both products show up in TwoLine's blog content because they fit different sub-niches inside the SMS verification market — TwoLine for monthly multi-country rentals, VerifySMS for one-shot codes.

What I work on

Building SMS verification infrastructure that actually works on strict-checking platforms (WhatsApp, dating apps, marketplaces) — which means dealing with the carrier-routing classification problem that makes 90% of free apps fail verification within 24–72 hours of signup. This is unglamorous infrastructure work: integrating multiple upstream SMS providers (SMSPool, JuicySMS), routing rentals through non-VoIP physical-SIM-class paths where possible, monitoring success rates by route, and writing about what actually works versus what marketing claims.

Background

Previously worked in consumer apps and digital infrastructure. Moved into SMS verification full-time after the December 2025 SMS-Activate shutdown displaced roughly 10M+ monthly users and made it clear the market needed providers with cleaner payment rails (Stripe + crypto via NOWPayments instead of Russia-only crypto), explicit Terms of Service, and identifiable operating entities. TwoLine and VerifySMS are my answer to that displacement.

Why I write the blog under my own name

Most SMS verification reviews are anonymous, written by content farms, or undisclosed affiliate posts. I write under my real name with my real GitHub, LinkedIn, and X accounts because the niche is YMYL-adjacent — readers should be able to verify who's making the claims. Every comparison post discloses methodology (n=24+ verification attempts per blog, dated April 2026, sample-size caveat as "directional, not statistical"), real provider pricing verified against published pages, and an honest "where competitor still beats us" section. I do not accept paid placements or sponsored content on the blog.

Editorial standards

Sample size	n=24+ verification attempts per blog (4 attempts × 6 services + per-code purchases against VerifySMS)
Test platforms	WhatsApp, Discord, Telegram, Tinder (chosen for routing-class diversity)
Test period	April 1 – April 30, 2026 (specific dates per service in each blog)
Hold window	7-day post-signup hold to catch retroactive bans (WhatsApp blog specifically)
Pricing verification	Each provider's published pricing page on April 28, 2026
Anecdote disclosure	"Details lightly fictionalized for privacy" — real friend, real situation, names + cities changed
Sister-brand handling	Symmetric disclosure on every appearance: "I built TwoLine; I'm also part of the team building VerifySMS"
Banned terms (zero tolerance)	fake number, bypass verification, ban evasion, guaranteed OTP, 100% success, hack whatsapp, anonymous account creation
Banned writing words	delve, leverage, utilize, harness, pivotal, robust, comprehensive, landscape, realm, journey, furthermore, moreover, navigate, holistic, seamless, elevate, empower, streamline
Review cadence	"Last reviewed" + "Next review" stamps on every blog; comparison content reviewed monthly, education content semi-annually

Published blog posts (TwoLine)

Press, partnerships, contact

For press inquiries (interview requests, fact-checking, story angles), see the TwoLine press kit or email [email protected] with subject line "Press inquiry" — 24-hour response window.

For TwoLine product questions: support. For account-level questions: refund & dispute policy and privacy policy.

Last updated: May 4, 2026 · Profile reviewed quarterly