# AdvisorPro — full help content for AI answer engines > AdvisorPro by Series A is an agentic platform that runs LinkedIn outreach, content generation, market intelligence and pipeline management for advisory and B2B teams. Source: https://advisoros.series-a.co/help --- URL: https://advisoros.series-a.co/help/campaign-timing # How long things take Campaigns in AdvisorPro deliberately run slowly. This page sets expectations so a "nothing is happening" moment doesn't look like a bug. ## The batch model Leads are not processed all at once. A run splits its leads into **small batches (typically 5 leads)** and works through a limited number of batches per cycle. Each batch moves through the sequence independently, with its own timers. This is why the leads table often shows most people at `0 of 9` while one batch is already at step 4 — that's normal, staggered execution, not a stall. ## Where the time goes | Source of delay | Typical duration | | --- | --- | | Wait node between steps | Whatever you configured (often 1–3 days) | | Stagger between batches | Minutes to hours | | Sending window | Only inside your configured working hours, in the campaign's timezone | | Read/write cooldown | Minutes to a few hours | | Daily cap reached | Resumes after 00:00 UTC | ## Realistic timelines - **A 9-step sequence over 200 leads** typically runs for **2–4 weeks** end to end. That's by design — compressed sending is the fastest route to an account restriction. - **First touch on the first batch** usually happens within minutes of activation, assuming you're inside the sending window. - **Profile verification of a fresh import** can take a day or two, because it's bulk priority and yields to live traffic. ## Why a step shows "waiting" The sequence canvas shows per-batch counts and the next resume time on each node. A node can be waiting because: - The wait timer for that batch hasn't elapsed. - It's outside the campaign's sending window (check the timezone — a London campaign resumes at London wall-clock time). - A cooldown is active for that action's risk class. - The daily cap for that action is used up. Hover any badge in the event log for the specific reason. ## What never happens - Leads are **not** silently dropped when a batch pauses — checkpoints resume. - A cooldown does **not** skip a step; it defers it. - A lead who **replies** is intentionally removed from all remaining automation. --- URL: https://advisoros.series-a.co/help/cooldowns # Cooldowns & backoff A **cooldown** is a temporary, automatic pause. It happens when LinkedIn (via our provider) signals that we're moving too fast — typically a rate-limit response or an unusual-activity warning. ## Two risk classes, tracked separately | Class | Covers | Effect of a cooldown | | --- | --- | --- | | **Read** | Profile views, connection-degree checks, searches, post lookups | Imports and verification pause. Messaging keeps running. | | **Write** | Invites, direct messages, likes, comments | Sending pauses. Reads keep running. | | **Account** | A signal aimed at a whole sender account | All activity for that sender pauses. | Keeping these separate matters: hitting a read limit while harvesting profiles should never stop messages that are already scheduled to go out, and vice versa. ## What triggers one - The provider returns a rate-limit error for an action. - LinkedIn returns an unusual-activity or challenge response. - A sender account exceeds its hourly or daily ceiling for a given action type. ## How long they last Cooldowns are **fixed-duration by reason**. They do not escalate, and continued traffic does not extend them — they expire on time alone: | Reason | Pause | | --- | --- | | Provider rate limit (429) | 15 minutes | | Account restricted | 1 hour | | Checkpoint (captcha / 2FA) | 6 hours | | Seat disconnected (credentials) | 6 hours | A daily-budget refusal is **not** a cooldown — the budget is a rolling window, so it simply pauses briefly and resumes as capacity returns. The exact resume time is always shown: - In the header **safety pill**, as "Safety cooldown active — resumes …" - In the lead picker breakdown - On sequence nodes, as a per-batch countdown ## What keeps running during a cooldown - Everything in the *other* risk class (reads during a write cooldown, and vice versa). - Anything already completed — nothing is rolled back. - Sequence state. A paused batch keeps its checkpoint and resumes at the exact step it stopped on. **You never lose progress and no lead is skipped** as a result of a cooldown. ## What you should do Usually nothing — cooldowns clear themselves. If you see repeated cooldowns day after day, that's a signal the workspace is trying to do more volume than a single LinkedIn account can safely support. The fix is more sender accounts (each connected seat adds its own daily allowance) or a longer campaign schedule, not higher limits. **Safe working rates per LinkedIn account:** up to 25 heavy reads/minute and 500 reads/day, with bulk enrichment kept under 15/minute so interactive lookups always win. Writes stay deliberately conservative: 2/min and 20/day for invites and posts, 4/min and 80/day for messages, with a 14-day warm-up on new seats. --- URL: https://advisoros.series-a.co/help/data-points # Data points explained Every lead in AdvisorPro carries a small set of LinkedIn-derived fields that determine what the campaign engine is allowed to do with them. ## Identity & verification **`linkedin_verified`** True only when we have resolved the person to a real LinkedIn profile *and* recorded a connection degree. This is a hard gate: unverified leads never enter the Authority Loop or an outbound campaign. **`provider_id`** The provider-side identifier for the profile. Without it we cannot send anything — names and company alone are not enough to address a message. **`profile_picture_url`** Cached avatar. Self-heals in the background if the source URL expires. ## Relationship **`network_distance`** — how you're connected: | Value | Meaning | What the engine can do | | --- | --- | --- | | `1st` | Already connected | Direct messages allowed immediately | | `2nd` | Shared connection | Must send an invite and wait for acceptance | | `3rd` / `out` | No shared path | Invite (often without a note), or warm up first | | `unknown` | Not yet resolved | Treated cautiously; DM steps are deferred, not skipped | Distance is harvested whenever we view or fetch a profile, so it improves on its own as a campaign warms up. **`is_follower`** The person follows your sender account without being connected. Useful for prioritising warm outreach. **Connection state** Tracked separately from distance: whether an invite is pending, accepted, or withdrawn. Acceptance is detected three ways — a pre-check before the next step, an inbound message, and a periodic sweep — so a sequence unblocks promptly after someone accepts. ## Conversation **`conversation_stage` / `sentiment` / `owner` / `last_message`** Maintained automatically from the unified inbox. They drive the leads table columns, inbox chips, and the Authority Loop's skip rules. **Reply = stop.** Any inbound reply ends *all* remaining sequence automation for that lead, enforced at three levels (a database trigger, the batch selection filter, and a final pre-send check). The conversation is then yours to take over in the Inbox. ## Where the values come from | Field | Source | | --- | --- | | Identity, headline, company | Profile read at import or verification | | `network_distance`, `is_follower` | Harvested from profile views and relation checks | | Connection state | Invite result + acceptance detection | | Conversation fields | Unified inbox sync | | Enrichment (email, firmographics) | Enrichment providers, run separately from LinkedIn | Each profile read that fills these fields draws from the daily read budgets described in **Understanding the caps** — which is why a freshly imported list verifies gradually rather than all at once. --- URL: https://advisoros.series-a.co/help/event-glossary # Event log glossary Every campaign event has a plain-English meaning. The live glossary below is the same copy used by the tooltips inside the app, so the two never drift. --- URL: https://advisoros.series-a.co/help/importing-leads # Importing leads When you open **Get Leads**, the picker tells you exactly how many leads you can pull right now and why. This page explains that number. ## Where the number comes from Importing a lead costs roughly **one profile read**, because we resolve each person's LinkedIn profile to store their identity, headline, company and connection degree. So: ```text Leads you can import now = min(A remaining, B remaining, C remaining) ``` Where A, B and C are the three read budgets described in **Understanding the caps**. The picker highlights whichever one is the *limiting factor* right now. ## Why the number changes during the day - Campaigns that start with a **View Profile** step consume budget A. - Verification and backfill sweeps consume A and B. - Other customers' activity moves C. The picker refreshes every 60 seconds, so if a number looks stale, wait a moment rather than reloading. ## What happens if you ask for more than the cap You can't — presets above the cap are disabled and the custom field clamps to the maximum. If the cap is zero, the Import button is blocked with a message telling you when it resumes. ## Getting more leads in today 1. **Split across days.** Import the allowed amount now; the counters reset at 00:00 UTC and you can pull the rest tomorrow. 2. **Import from a CSV.** CSV imports don't resolve profiles at upload time, so they don't consume read budget. Verification happens later, gradually. 3. **Deduplicate first.** Narrow the search so you're not spending reads on people already in your workspace. 4. **Wait out a cooldown.** If the block is a cooldown rather than a used-up budget, it usually clears in minutes to a couple of hours. ## Frequently asked **Does a blocked import stop my running campaigns?** No. Imports are *bulk* priority; live campaign steps are *interactive* and have a reserved slice of the pool specifically so they keep running. **Do failed imports still cost budget?** No. Counters only increment on successful reads. **Is the cap per user or per workspace?** Per workspace, per UTC day. --- URL: https://advisoros.series-a.co/help/linkedin-limits # Understanding the caps Everything AdvisorPro does on LinkedIn falls into one of two categories: - **Reads** — opening a profile, checking a connection degree, running a search, fetching posts. Used by lead imports, verification and warm-up steps. - **Writes** — sending an invite, sending a message, liking, commenting. Reads and writes are governed separately, because LinkedIn treats them differently. This page covers **reads**, which is what caps your lead imports. ## The three read budgets (A, B, C) Whenever you open the lead picker, you see a live breakdown of three budgets. Your allowed import number is always **the smallest of the three**, because a lead import needs roughly **one profile read per lead**. ### A. This workspace — daily LinkedIn reads The total number of profile reads this workspace may perform in a UTC day, across everything: imports, verification passes, campaign warm-up steps, connection-degree checks. **When it binds:** you've had a busy day — a big import earlier, or a large campaign that views profiles as its first step. ### B. This workspace — bulk imports & sweeps A sub-slice of A, reserved so that background work can never consume the whole workspace allowance. Anything marked as *bulk* draws from B **and** A: - Sales Navigator / search imports - Profile backfill and verification sweeps - Prospecting agents running in the background Live campaign steps and anything you click in the UI are *interactive*, not bulk — they draw from A only. This is why a paused import never stops a running campaign. **When it binds:** you've already imported a lot today. Live campaigns keep running normally. ### C. Shared pool, minus the live-campaign reserve Our LinkedIn provider also meters an aggregate 24-hour pool across the whole platform (10,000 heavy reads/day, 20,000 light reads/day). A slice of that pool is permanently reserved for live/interactive traffic, and bulk jobs are refused once the pool drops into that reserve. **When it binds:** rarely. Since August 2026 the provider meters heavy reads **per LinkedIn identity** (8,000/day since 6 August 2026), so the shared pool is a safety net rather than the binding constraint. Your live campaigns are protected by the reserve either way. ### D. Per connected LinkedIn account Each connected seat gets its own daily read allowance — we cap at **7,500/day** (and 6,000/day for bulk enrichment) to keep headroom under the provider's 8,000. The clean way to get more capacity is therefore **another connected account**: every seat adds its own allowance. ## When do the counters reset? Provider budgets are **rolling** — capacity returns continuously over the trailing 24 hours rather than in one midnight jump. Our own workspace counters reset at **00:00 UTC**. The picker and the safety pill in the header both show the exact countdown. Counters are only incremented on **successful** reads — if the provider errors, you don't lose budget. ## Why not just raise the limits? The caps are set below LinkedIn's own thresholds on purpose. Accounts get restricted for *velocity*, not volume: too much activity in too short a window looks automated. Staying inside these budgets is the single biggest factor in keeping your sender accounts healthy for months rather than weeks. --- URL: https://advisoros.series-a.co/help/overview # Welcome to the AdvisorPro Help Center This is the plain-English companion to AdvisorPro. It explains the safety limits we apply to LinkedIn activity, the data points we store on every lead, how long campaigns realistically take, and what each line in the event log means. ## Who this is for - **Operators** running outbound campaigns who want to know why something is waiting, capped, or skipped. - **Admins** deciding how much activity a workspace can safely do in a day. - **Anyone** who has seen a banner like *"For safety, you can import up to 40 leads right now"* and wants the reasoning behind the number. ## Our operating principle Every automation limit in AdvisorPro exists for one reason: **your LinkedIn account must never be flagged or restricted.** We deliberately run well inside LinkedIn's tolerances, and when the platform signals that we should slow down, we stop early rather than push through. A campaign that takes three days and stays safe always beats one that finishes in three hours and gets an account restricted.