Leads, competitor posts and media that are publicly visible on 6 platforms, collected on a schedule against the keywords and scope you set, then cleaned and deduped into your contact list or media library. What comes back depends on what each platform makes public at the time, and that limit is written into the workflow.
I'm going platform by platform for leads and end up with a few dozen a day
Jobs run on a schedule against your keywords and scope, and results land in the library. Your team reviews filtered output instead of paging through feeds.
Everyone exports their own spreadsheet, and half of the merged file is duplicates
Records are cleaned and deduped on the way in using identifier fields. Duplicates across jobs and across platforms merge into one entry, with every source kept.
The only way to see what competitors post is to scroll their feeds myself
Name the competitor accounts and their public posts get collected on a schedule, ordered by account and date, so shifts in cadence and topic show up.
The data we pull piles up in a spreadsheet and nobody follows up on it
Leads enter the contact list with their tags, so the Conversation agent can queue follow-up straight away. No exporting between tools.
Two steps need you: the collection scope, and what the data is for. Scope sets the compliance boundary; purpose decides which library the data enters and who can see it. AI makes neither call.
You name the platforms, keywords, competitor accounts, regions and fields, and state what this batch of data is for.
Jobs run on schedule inside a cloud browser environment or cloud phone, over a proxy in the matching region, at a rate the platform will tolerate.
Invalid entries drop out, duplicates across platforms merge into one record with sources kept, and tags are applied automatically by platform, region and keyword.
Whether leads go to the contact list or stay in the warehouse, and whether media is cleared for publishing, is yours to review before anything moves.
Leads go to the contact list for the Conversation agent to work, media goes to the media library for the Publisher, and the full dataset stays in the warehouse for export.
Scope is yours to set. The same keyword is collectable to a different degree on each platform and in each region, and local rules on handling personal data differ too. What to collect, and what to use it for, is your compliance call — not something AI should make for you.
6 platforms covered. Collection is limited to what a platform makes publicly visible at the time, and the available fields differ by platform.
Collect public accounts and contact details by keyword, region and topic, recording the source of every entry.
Name an account and its public posts are collected on a schedule, ordered by account and date, showing topic choices and frequency.
Invalid entries are dropped before storage, and duplicates across jobs and platforms merge into a single record that keeps all its sources.
Tags are applied automatically by platform, region and keyword, and you can add your own. Tags follow the lead into the contact list.
Approved leads enter the contact list with their source and tags, ready to assign to the Conversation agent.
Publicly visible images and video can be stored in the media library for the Publisher to draw on.
Every collected record stays in the warehouse. Filter and export it, or connect through the API and webhooks.
The Collector is software. The accounts, environments and network it works through are separate. We spell that out so you don't plan against the wrong cost.
Approved leads arrive tagged in the contact list, where the Conversation agent queues follow-up and automatic replies.
Collected competitor content and media land in the media library as raw material for topics and posts.
When breaking down the goal it decides which platforms, how wide a scope and how often to run, then brings the open items to you.
Collection runs in an isolated environment with its own fingerprint and route, so it never implicates your publishing or conversation accounts.
No, and nobody should promise otherwise. Two limits apply. First, only what a platform currently makes publicly visible: content behind a login, behind a friend connection, or already restricted by the platform is out of scope. Second, local rules on handling personal data — collecting and using personal information requires a lawful basis on your side. Visibility rules also change, so a field that's collectable today may not be tomorrow. When something can't be collected, the log records the reason; we don't pad the results with stale data. Before you sign, a consultant walks through what's actually collectable for your target platforms and regions.
The data is what the platform page showed, so accuracy depends on the source. Information on a platform can be out of date or simply false, and collection does not verify it. Cleaning only handles malformed entries and duplicates; it makes no judgement about whether content is true. So work a small batch of leads first, confirm the quality, then widen the scope.
6 platforms: WhatsApp, Telegram, Reddit, X, YouTube and Facebook. What you can collect, and which fields, varies a lot between them — the options shown during setup are what actually applies.
It can, which is why both rate and concurrency are capped and requests are spread across the day instead of bunched together. Keep collection accounts separate from your publishing and conversation accounts, with their own environments and proxies, so the risk stays in one place. If captchas or access restrictions appear, the job slows down or pauses and logs it.
Records are matched on identifier fields, and duplicates across jobs and platforms merge into one entry with every source retained. The same person collected on two platforms becomes a single record marked with both sources, which makes the outreach channel easier to choose.
Yes. Filter the results and export them, or push them to your own CRM or data platform through the API and webhooks. The warehouse keeps the full record set, and exporting doesn't change the status of leads already stored.
A consultant will tell you what is and isn't collectable for your target platforms and regions first, then quote the resources.