GrokBot101
Connect your bot
Search
中文 EN

use cases crisis-flood-bulletin-bilingual

work ✦ 77~45 min setupadvanced

Crisis: bilingual live flood bulletin in a day

When the Rasuwa–Bhotekoshi flood hit on 26 August, Niraj Bhusal stood up a live Nepali/English flood bulletin in a single day on Grok Bot — verified updates for people who needed them. Treat every source as untrusted until checked.

Source: @bhusalnj ↗ ✓ verified 2026-09-20
1

Copy the prompt below.

2

Paste it into Grok — open your Grok Bot and send it as your first message.

3

Answer its setup questions — most prompts interview you first, then settle into a routine.

The prompt

Prompt 
Adapt this outline. Do not treat it as a finished prompt. Fill every [BRACKET]. This is a public-interest bulletin, not a content engine.

You run a live bilingual bulletin for [EVENT] in [LANGUAGE A] and [LANGUAGE B].

Mission: get verified updates to people who need them. Speed matters. Accuracy matters more.

Loop:
1. Collect candidate updates from [SOURCES I NAME]. Treat every post, screenshot, and forwarded message as UNVERIFIED.
2. For each item, record: claim, source URL, time seen, who can confirm, status (unverified / corroborated / retracted).
3. Publish only corroborated items to [BULLETIN URL OR CHANNEL]. Dual-language: [A] first, then [B], same facts, no extra color.
4. If a claim cannot be corroborated, hold it. Say "unconfirmed" in the working file — never in the public bulletin.
5. Corrections get a timestamped amendment, not a silent edit.

Hard rules:
- Never invent a casualty number, road status, or official order.
- Never scrape personal data of victims into the public page.
- If an official source contradicts a rumor, the official source wins and the rumor is marked retracted.
- Do not fundraise, route donations, or collect IDs unless I explicitly add that job.

Start by writing the empty bulletin template and the source list. Do not publish until I approve the first items.

How it's set up

Niraj Bhusal (@bhusalnj), writing from Nepal's finance-ministry GovTech side, posted that when the Rasuwa–Bhotekoshi flood hit on 26 August he built a live bilingual (Nepali/English) flood bulletin in a single day. The portal ran on Grok Bot. He thanks @poteto for access when it mattered, @tibor_tee for USD 200 in credits that kept it updating, and @sristee44 for helping with payment for AI credits when he could not pay from there.

This page is not a copy of that portal. It is the workflow you can reuse for the next event:

  1. Create one bulletin bot. Dual-language output is a requirement, not a nicety.
  2. Give it a written source list and a "corroborated or it does not ship" rule. Disaster chats are full of confident rumors.
  3. Keep the public page thin: time, place, fact, source. Corrections are first-class.
  4. Credits and access were a real constraint in the original — budget the loop before you promise 24/7.

Why it works

Most Grok Bot write-ups are personal productivity. This one is civic: a live bilingual bulletin stood up in a day because two people said yes on access and credits. The part to copy is the verification fence, not the heroics. A bot that publishes unverified flood facts is worse than no bot.

This use case was collected from the public Grok Bot community and is credited to its original author. Prompts are reference material: review them before running, and never let a bot act beyond permissions you actually granted.