Select relevant sources
Start with groups where customers ask questions or your topic is discussed. Dozens of unrelated chats add noise. Choose known groups from the Zuvi catalog or add a public URL. A connected account or the bot must actually be allowed to read each source.
Define the event
One filter can look for requests to buy a product; another can find questions about a service. State the location, whose need counts and what to exclude. This turns simple mention monitoring into an intent-based search.
Check working status
After selecting sources and a filter, use /status. It distinguishes incomplete setup, pending access, active search, a pause and queue delay. An empty /leads feed alone cannot prove that every group is connected.
Choose alert delivery
Urgent requests suit immediate alerts. A broad topic may be easier as an hourly batch or after quiet hours in your time zone. Delivery settings change timing, not the saved filter or continued processing.
Know the limits
Zuvi cannot monitor a group a connected account cannot read. Queue or Telegram delays can postpone an alert. Open the original message and check context before acting on an important result.
Try it with your groups
Open Zuvi, choose an accessible source and test the rule on a real example before monitoring starts.
Open bot