«wa.me के बाद number paste करो» - आधी site buttons «Invalid phone number»। Format issue: extra +, bracket, unencoded text। Working formats, encoding, conversion/ban context।
Article के बाद Click to Chat बिना error; site/signature/QR format choice।
पहले: wa.me/919876543210 और api.whatsapp.com/send/ equal; ?text= as typed।
बाद: wa.me modern recommended; api older। ?text= URL-encoded mandatory। Click send नहीं - chat open + prefill; user Send tap।
| Format | Use | Note |
|---|---|---|
wa.me/<number> |
Basic button | Modern |
wa.me/<number>?text=<text> |
Prefill | URL-encoded |
api.whatsapp.com/send/?phone=... |
Old WebView | Legacy; some in-app browsers stable |
wa.me/?text=... |
Share no number | Pick contact |
Mobile deeplink; desktop intermediate page।
International without +, spaces, brackets: 919876543210। Wrong → invalid number error।
?text= encoded: space %20, ? %3F। Unencoded breaks।
~2000–4000 chars possible; 150–200 readable on phone।
Prefill only; user must Send। Click vs real inquiry - drop-off।
Mobile click→send ~60–85%; desktop ~25–40%। Forum benchmarks।
Three buttons, different ?text= (header, calculator, contacts)। Handling speed +35%। Inbound funnel overlap।
Different ?text= = free attribution।
User-initiated via wa.me - «whitest» practice; not Meta doc। Antispam। Aggressive prefill - report still possible। Report metrics।
wa.me to official WABA - first inbound opens free 24h window।
Test api format if WebView flaky। Own redirect: mobile whatsapp://, desktop web.whatsapp.com।
Audit buttons: clean number, encoded text, per-block different prefill।
Practical rule:
Link opens chat; human sends - दो events; analytics में मत मिलाओ।
