WhatsApp bot — chat with RESILAND from your phone

Half the project's audience is in the field with intermittent data, no laptop, and a phone that already has WhatsApp open. So we wired RESILAND Intelligence to it.

Save the number, send a message

Add +90 535 374 99 71 to your contacts. Open WhatsApp, send "hi" or anything in EN/TR/RU/UZ. The bot replies within seconds.

Voice calls are disabled — this is a chat-only contact. SMS, voice, and WhatsApp voice will route to a placeholder. Don't be surprised by the silence.

What you can ask

• Lookups. "List nurseries within 30 km of Andijan." "How many parcels in Surxondaryo?" "What's the NDVI trend for parcel 12345?"
• Verdicts. "Is parcel 12345 suitable for Pistacia vera?" "Score this 200-ha block for almond restoration."
• Reports. "Generate a feasibility brief for the polygon I sent." "Translate report e0b37e1b to Russian." (PDF + share link sent back as a WhatsApp message.)
• Status. "What's my demo-allowance balance?" "When does my translation finish?"

Background routing

Each WhatsApp message hits a stateless webhook on our backend, which:

1. Resolves the sender phone to an app_user row (or creates one for first-time users with a default org).
2. Sends the message to P1 Main Orchestrator (Haiku 4.5) — same agent the web chat uses.
3. P1 classifies and dispatches to Haiku for lookups, Sonnet 4.6 for translations / mid-size synthesis, Opus 4.7 for reasoning-heavy verdicts and Vision.
4. The reply streams back to WhatsApp as a single message (or multiple, if the result is long enough to need pagination).

Why this matters

A field officer in a Tashkent oblast doesn't need a custom app to consult the platform. They need an answer to "should I plant Juniperus seravschanica here?" — and they need it on the device they already use. WhatsApp is that device.

Privacy

WhatsApp messages and replies are logged in the same agent_invocations table as web requests, with the same retention policy. Your phone number is hashed; raw numbers never leave the backend.