When Kuwait ops need an archive agent

The job is a question about rooms you already keep. “What did that Telegram group say about the tender.” “Who posted the new SKU.” Someone still scrolls three apps because search in the store is a dump.

Teams ask for “social listening.” That is a dashboard. This agent answers from messages you already fetched, cites the row, and stops when the pile is silent.

What the agent actually does

It knows which X accounts, Discord channels, and Telegram groups you already collect. A person asks in one sentence. It searches the store, returns a short answer with a link or a timestamp, and refuses when nothing matches. It does not add a source. It does not reply in the room.

AI agents can sit on that ask. The X / Discord / Telegram fetcher is how the pile got into one place. We will not treat one desk’s rooms as yours.

This is not the fetch-or-not decision. Fetching is coverage. Asking starts after the row exists. It is also not a mention ping. A ping fires when a keyword appears. This job waits for a person. And it is not a comment reply on your own posts. A reply writes back in public. This search stays inside the desk.

When we leave the search with a person

If legal has not named which rooms the agent may quote into Slack, keep the person on every paste. If a private Discord and a public Telegram share a topic, do not let the answer mix them as one voice.

Kuwait desks often mix Gulf Arabic voice notes with English text in the same group. Name which of those the agent may read. Do not transcribe a three-minute rant and call it a decision.

Bring one question someone still answered by scrolling, and the room it came from. Book thirty minutes or write hello@jamilglobal.com.