How can we help?

Create an account at app.leadvector.app and run your first search or finder lookup. If you plan to send campaigns, connect a Google Workspace or Microsoft 365 mailbox and let warmup run first. Plans start free.

A credit is used when LeadVector returns a valid result: a found email, a found mobile number, a verification, or a reverse lookup. Empty and invalid results are not charged, and a repeat lookup on the same contact is never charged twice.

Google Workspace and Microsoft 365 mailboxes, through OAuth. No passwords are stored. LeadVector verifies each mailbox as soon as it is connected.

Yes. Invite team members, share the credit pool, and set permissions per person.

Paid plans are billed in advance, monthly or annually, to the payment method on file. Credit allocation depends on your plan, and we give 30 days notice before any change to pricing or credit allocation.

Cancel your subscription from your My Account dashboard at any time; access continues until the end of the billing period you have paid for. To close your account completely, contact support. You can export your data first, and personal data is deleted or anonymised within 30 days of termination unless the law requires us to keep it.

All personal data is stored and processed on servers in the European Union and stays there. A Data Processing Addendum is available on request for customers who need one.

No. We do not sell or share personal information for cross-context behavioral advertising. See the Privacy Policy for the full list of what we collect and why.

A full name and the company's email domain, for example lumenanalytics.com. You can look up one contact at a time or upload a file with thousands.

Yes. Every result is verified in real time before it is returned, and the verification status and MX record are saved on the contact record.

Only when LeadVector returns a valid email. Lookups that come back empty are not charged.

A LinkedIn profile URL. One at a time in the app, or a column of URLs in a bulk upload.

Valid means the server accepted the address. Invalid means it was rejected or the domain has no mail. Catch-all means the domain accepts any address. Unknown means the server did not answer conclusively.

Verification results are cached on the contact for 30 days, so re-checking the same address inside that window is free.

The LinkedIn profile behind the address, with the person's name, title, and company, saved to the contact record.

CSV and XLSX, up to 20 MB per file.

No. Results are appended to your original rows, and exports keep every column you uploaded.

Jobs are resumable. LeadVector retries failed rows and continues from where it stopped.

Campaigns import their leads from your lists, so the data you verified is exactly what gets sent to.

Google Workspace and Gmail, and Microsoft 365 and Outlook, connected through OAuth.

LeadVector ramps volume gradually and shows a health score. Most teams wait until the score is healthy before assigning the mailbox to a campaign.

Yes. Pause and resume any mailbox from the app or the API. Warmup also pauses itself with a cooldown when health drops.

As many as you need. Each step has its own delay in days and can carry variants.

Leads, sent, opens, clicks, replies, bounces, and rates, with a daily chart, per-step and per-variant breakdowns, and a searchable activity feed.

The ones you assign. LeadVector rotates across them, skips any in cooldown, and respects per-mailbox daily limits.

Every Google or Microsoft mailbox connected to your LeadVector account.

LeadVector links incoming messages to the lead and campaign that sent the original email and marks the lead as replied.

Yes. Forward with To, CC, and BCC recipients and an optional note. The sent copy is stored with the conversation.

Search contacts with natural-language filters, verify them, create and fill lists, draft campaigns and add leads to them, and answer questions about campaign performance. Each one is the same action you would run in the app.

Yes, the same way you would. It checks the credits on your account before a paid step and is charged only for valid results, so a request never stalls waiting for a click.

Responses follow a backend-controlled structure and are checked against product policy before any action runs, so the AI cannot invent an action the product does not have.

Create your access key in your account settings and send it as the x-api-key header. Each user has one key, with usage analytics in the app. The raw key is shown only once, so store it safely.

Yes. Data lookups allow 5 requests per second per key, with bursts of up to 20; campaign, lead, inbox, and mailbox endpoints allow 120 requests per minute per key; and an account is capped at 10 requests per second across all its keys. Every response carries rate-limit headers so you can back off cleanly.

Yes. API calls draw from the same credit pool as the app, including your team's shared pool.

No. Sign in with your LeadVector account. The CLI uses the same access key as the API and draws from the same credits.

Yes. Commands return structured output and exit codes, so they work in shell scripts, cron jobs, and CI pipelines.

The documentation lists every command and flag.

Add it from the Chrome Web Store, then sign in with your LeadVector account. There is no separate plan: it uses the credits, lists, and campaigns you already have.

On LinkedIn profiles, LinkedIn company pages, and company websites. Open the page, open the panel, and the contact lookup runs on the person or company the page is about.

A credit is used only when a verified email or a mobile number is returned. Every reveal searches multiple providers in real time. Contacts you have already revealed are saved to your account and are never charged twice.

Save it to your contacts, add it to a new or existing list, or add it to a campaign sequence, all from the panel. Everything you save appears in the app for your whole team.

Yes. Each client gets its own lists, mailboxes, and campaigns, and mailboxes can be tagged by account.

Forward replies with a note from Unibox, and use per-campaign analytics for reporting.

Credits are pooled on the account owner and shared with your team members.