What Firsay does, and where the limits are.
Short answers about evidence, repeated candidates, provider costs, Telegram coverage, and outreach.
Why did Firsay return fewer leads than requested?
The requested count is a target. Firsay does not pad the list when profiles lack role, project, category, recency, or contact proof.
Will another account see the same candidates?
It can on the first run. Candidate history and rotation are isolated per account and search scope, so each account develops its own exclusion history.
Why can a run cost money when LLM tokens are zero?
Discovery and profile-verification providers charge separately from language models. Canonical BIO hydration, recent-post checks, project graph expansion, and web verification can consume provider credits.
What happens on error 429?
The current provider or account has reached a request, daily usage, or configured cost limit. Wait for the shown retry period, narrow the task, or contact support for a higher limit.
Does Firsay search all of Telegram?
No. Telegram has no complete global public BIO index. Coverage depends on accessible public entities, configured sources, indexed messages, and canonical profile checks.
Why is a public contact missing?
Firsay does not guess private contact information. If a person has no public email, Telegram, website, or open contact path, the field remains missing.
Can Firsay send outreach automatically?
Firsay currently supports review-first drafting, approval, queues, and a mock sender. A real sender is not represented as active until platform-specific controls are configured and verified.
How do I report a bad result?
Send the task, filters, run ID, result link, expected behavior, and screenshot to support. Never include passwords, API keys, session strings, or private invite links.