Answers about 12Pilot

B2B agencies, SDR / BDR teams, founders, and GTM operators who run LinkedIn outreach for themselves or clients. It is built for multi-seat workspaces, not for personal social posting alone.

Published Solo pricing starts at $33/month, and growth is seat-based. Differentiating pieces include AI Outreach with a hard human-approval brake (AI cannot send), Google Map Extractor into the same lead database, multi-seat Unibox, Content Hub, and a public competitor matrix at 12pilot.net/compare/competitors.

No. 12Pilot is an outreach and prospecting workspace. Lead extraction from LinkedIn search / Sales Navigator and Google Maps feeds your campaign lists, but the product’s core job is safe sequences, replies, and seat management — not dumping raw scrape files.

12Pilot is built by 12Monday Technologies in Karachi, Pakistan, and sold as an English product for a global market. Payments run through Stripe. The live product is at 12pilot.net.

No. 12Pilot is an independent third-party product. You connect your own LinkedIn accounts and are responsible for using them within LinkedIn’s terms and your local laws. Safety queues and daily caps reduce risk; they do not replace judgment.

The product UI and marketing site are in English. Outreach messages can be written in whatever language your templates use — including Urdu or mixed copy — because message content is yours.

Go to 12pilot.net/auth, sign up with email, and open your workspace dashboard. No sales call is required to start on Solo.

Connect a LinkedIn account, install the Chrome extension if you use extension/cookie seats, create or import a prospect list, build a short sequence, enroll a small test batch, then watch replies in Unibox.

It depends on how the LinkedIn seat connects. Extension and cookie seats use the Chrome extension for live browser actions like lead extraction. Credential seats can run cloud worker actions without the extension. Never route a credentials action through the extension, or vice versa.

Most teams connect a seat and launch a small campaign the same day. Start with conservative daily limits while the account warms, then scale. A rushed full-blast day one is how accounts get restricted.

Check the current offer on the pricing section of 12pilot.net — plans and trials can change. Solo is published from $33/month so the barrier to a real seat is intentionally low.

Yes. Agency plans include 1-on-1 onboarding and a dedicated Slack channel. Everyone can use in-app docs, tutorials at /tutorial, and support@12pilot.net. Partners can also contact the team from the become-a-partner page.

No. Campaigns, sequences, Unibox, and lead lists are visual. API, webhooks, and MCP (Team+) are optional for teams that want automation from tools like Cursor or Claude.

Published plans: Solo from $33/month (1 seat), Team from $137/month (up to 8 seats), Agency from $292/month (up to 25 seats), and Enterprise custom. Extra LinkedIn senders have published add-on prices that drop as you move up plans. Always confirm live numbers on 12pilot.net.

Solo is built for solopreneurs: 1 LinkedIn seat, Unibox, voice notes, data enrichment, lead database, and monthly action / extraction credits. It is the cheapest published entry point versus many international tools.

Team adds more seats, more workspaces, API & webhooks, MCP server, and bring-your-own proxies. Agency adds whitelabel, 1-on-1 onboarding, a dedicated Slack channel, higher seat and credit ceilings, and is marked most popular for multi-client operators.

You pay for LinkedIn sender seats. Growth usually means adding seats rather than jumping to an opaque agency quote. Additional sender prices are published per plan so budgeting stays predictable.

Plans include monthly credits for outreach actions and for prospect extraction / enrichment. Exact pools differ by plan (for example Solo includes 800 credits per sender monthly in the published config). Unused limits and overages follow the plan rules shown in billing.

Yes. Move between Solo, Team, and Agency as your seat count grows. Enterprise is custom — talk to sales when you need contracts, advanced controls, or dedicated support beyond Agency.

Core outreach, Unibox, campaigns, and extraction are part of the plan. Optional add-ons are called out (extra seats, proxies on Team+, whitelabel on Agency). Stripe handles card billing; you see invoices in the customer portal.

The public product prices are published in USD and billed through Stripe. If you need a local invoicing arrangement for Agency or Enterprise, contact support@12pilot.net.

Solo at $33 undercuts common published starts for tools like HeyReach, Expandi, and SendPilot on our public compare page. Use 12pilot.net/compare/competitors for the live side-by-side matrix.

From LinkedIn Accounts in the dashboard, add a seat using one of the supported methods: Chrome extension (live session), cookies, or credentials for cloud worker execution. Pick the method that matches how you want actions to run.

Seats move through states such as pending, active, warming, paused, disconnected, or error. Warming and paused are intentional safety states — do not force high volume while an account is warming or paused.

Yes. Workspaces hold multiple LinkedIn seats subject to your plan’s max seats. Replies can land in a shared Unibox so the team does not juggle browser windows.

The seat moves to an error or disconnected state and queued actions stop for that seat. Reconnect via the same method (extension sync, cookies, or credentials), then resume. Failed actions are logged so you can see what did not send.

Yes — that is a primary Agency use case. Keep client workspaces isolated, assign seats carefully, and use roles so staff only see what they need.

Credential seats store login secrets encrypted (AES-GCM) for the cloud worker. Extension/cookie seats rely on the browser session instead. Workspace data is isolated so one company cannot see another’s accounts.

Actions go through a queue with daily caps, retries that avoid duplicate sends, and automatic stop when an account is blocked or restricted. Human confirmation sits in front of AI Outreach launches. Safety is treated as product infrastructure, not a tip sheet.

Each seat has configurable daily ceilings for connects, messages, and related actions. Stay inside LinkedIn’s practical norms and your own warming schedule. Hitting the cap pauses further sends for that day.

12Pilot stops. A blocked seat does not keep hammering LinkedIn. Fix the restriction on LinkedIn’s side, cool down, then resume with lower limits. A person must confirm before you launch aggressive volume again.

No. AI Outreach can find matches and draft sequences from your templates, but it has no send button. Nothing goes to LinkedIn until you approve.

The system is designed to avoid duplicate sends: enrollments, action logs, and queue checks keep a prospect from getting the same action twice when status is tracked correctly. Always keep connection status updated so sequences branch on reality.

Yes. Start low, use the warming/paused states, and ramp over days or weeks. New accounts that suddenly blast hundreds of invites are the ones that get limited.

It is the prospecting surface where you pull people from LinkedIn search or Sales Navigator into your 12Pilot lead database, then enroll them into campaigns. Extraction uses plan extraction credits.

Search a local business category or area on Google Maps, import name, phone, website, and related fields into 12Pilot, then run LinkedIn outreach on that same list. It is the pipe for local businesses that are not sitting in Sales Navigator.

Yes. Bring existing prospect lists into the Prospects Database, map fields, dedupe, then enroll into a campaign. Prefer LinkedIn profile URLs when you have them so connection and messaging steps resolve cleanly.

Yes. Leads belong to the workspace that extracted or imported them. Filter, score, tag, and reuse them across campaigns without re-scraping every time.

Browsing and extracting still uses your LinkedIn session. Use the extension carefully, stay inside daily activity norms, and prefer saved searches over endless scrolling when possible.

Yes — Sales Navigator search results are a primary source for the Prospect Extractor when your LinkedIn seat has Sales Nav access.

It is the workspace CRM for LinkedIn prospects: profile data, connection status, scores, tags, and campaign enrollment history in one filterable table.

Typical statuses include none, pending, connected, and ignored. Sequences should branch on status so you do not message people who never accepted, or invite people who are already connected.

Lead Scoring ranks fit so SDRs spend time on higher-intent profiles. Use scores to prioritize AI Outreach approvals and campaign enrollment batches.

Yes. Export filtered lead lists for reporting or handoff. Data ownership stays with your workspace — exports are a feature, not a support ticket fight.

The database is designed to key on LinkedIn identity where possible. Always review import previews and merge or skip duplicates before enrolling large batches.

Yes. People who viewed your LinkedIn profile can be collected into the Profile Viewers surface and enrolled into outreach — turning inbound curiosity into a sequence.

A campaign is a sequenced outreach flow — connection requests, follow-ups, messages, profile views, and waits — attached to LinkedIn seats and a lead list. The builder uses a visual sequence graph.

Common steps include connect, message, InMail (when available), view profile, delays, and conditions based on connection or reply state. Exact available actions depend on seat method and plan.

Enrolling a lead attaches them to a campaign at step zero (or a chosen step). Status and current step advance as actions complete. Pausing a campaign pauses further queue population for that flow.

Use multiple sequence variants or template sets and compare reply rates in Unibox and campaign stats. Keep one variable changed at a time so results are readable.

Replies surface in Unibox. Best practice is to stop automated follow-ups for that lead and continue the conversation as a human. Campaign logic should not keep nudging an active conversation.

Avoid overlapping active campaigns on the same lead. Prefer one primary sequence per prospect so messaging stays coherent and duplicate-send protections stay simple.

You describe the buyer. AI finds matching prospects and drafts 2–3 sequences from your templates. You reject people, edit copy, and confirm. Only then does the system queue sends. The AI can plan; it cannot send.

Because LinkedIn accounts are real revenue assets. A hard brake keeps spam and off-brand messages from shipping. Human confirmation is the product differentiator called out as Only on 12Pilot on the compare matrix.

Planning uses Google Gemini via secure backend functions — the frontend never calls Gemini with your API key. Usage is metered inside the product so fair use stays fair.

Yes. AI drafts from your templates and tone, not a generic spam library. Review every draft before approval.

No. AI output is a proposal. You review, edit, and approve. There are no surprise overnight sends.

AI-assisted planning is part of the 12Pilot workspace experience; seat counts, credits, and advanced automation (API / MCP) still follow your plan. Check the live pricing section for the current packaging.

Unibox is the unified inbox for LinkedIn conversations across connected seats. Inbound and outbound messages live in threads so the team answers from one place instead of many LinkedIn tabs.

Yes, subject to workspace roles. Team and Agency plans are built for shared reply ownership with seat-level context still visible on each thread.

Yes — voice notes are included on Solo and higher as part of the messaging toolkit for warmer follow-ups.

Yes. Personalize with prospect fields (name, company, title, and custom data) so sequences stay human. Always spot-check a few renders before launching a big batch.

Yes. Open the thread in Unibox or from the lead record. History plus campaign context should be enough to reply without interrogating the prospect.

Failed actions are logged with reason codes when available (session expired, restriction, timeout). Fix the seat or copy, then retry from the queue — retries are designed not to double-send a success.

Content Hub is where you plan and manage LinkedIn content alongside outreach so posting and prospecting live in one workspace instead of separate tools.

Yes. The Inbound Invitations surface helps you review and act on people requesting to connect with you, so inbound demand does not sit unread in LinkedIn alone.

Someone who viewed your profile already showed interest. Collect them, score fit, and enroll high-fit viewers into a short, polite sequence.

Content Hub covers LinkedIn-centric content workflows tied to outreach. If you need multi-network scheduling (Instagram, TikTok, etc.), keep a dedicated social tool and use 12Pilot for LinkedIn GTM.

Yes — engagement and outreach should reinforce each other. Tag leads who engage with content so SDRs prioritize warm conversations in Unibox.

Workspace members use roles such as owner, admin, member, and viewer. Give staff the least access they need — viewers should not change billing or delete campaigns.

Solo includes 1 workspace. Team publishes multiple workspaces (3 in the standard config). Agency and Enterprise lift those ceilings for multi-client operations.

Invite from Team Seats with their email. They create their own login — never share the owner password. Revoke access when someone leaves the company or client project.

Yes. Use separate workspaces per client or brand. Workspace isolation is a hard rule: queries and seats stay scoped to the active workspace.

Completed actions write to an immutable actions log used for stats and debugging. Admin surfaces expose health and audit views for operators who need them.

Yes. Agency is built for multi-seat, multi-client delivery: up to 25 seats in the published config, whitelabel, 1-on-1 onboarding, dedicated Slack, and higher credit ceilings.

Agency packaging includes whitelabel options so client-facing surfaces can carry your brand instead of only 12Pilot chrome. Ask onboarding which surfaces are covered on your contract.

Visit 12pilot.net/become-a-partner and use the contact form. Partners help distribute 12Pilot to agencies and GTM teams; commercial details are handled case by case.

A member community for agencies, SDRs, and GTM operators — separate from a paid SaaS subscription. Apply at /join-our-community. After approval you land in Communitor for XP, rank, and referrals.

No. Community joins Communitor. You still sign up separately for SaaS seats, campaigns, and Unibox.

Communitor is the member dashboard for XP, rank, referral stats, and your personal referral link. It lives at /communitor and uses a community login cookie separate from the product dashboard.

If someone invited you, paste their code (for example 12PL-001) or use a link with ?ref=. When you join, they earn XP. You receive your own referral link inside Communitor after approval.

It bridges LinkedIn in the browser with your 12Pilot workspace: syncs session/workspace context, supports lead extraction, and executes extension-routed actions. After updates to the interceptor, reload the extension at chrome://extensions.

Credential seats can run cloud Playwright worker actions without the extension. Extension/cookie seats need the extension. Lead scraping from LinkedIn pages is extension-only.

Yes on Team and above. Use API & webhooks to push events into your CRM or internal tools. MCP server support on Team+ lets agentic tools like Cursor or Claude work with the same plans — still without giving AI a send button.

Yes on Team+. Bring-your-own proxies is for operators who need tighter network control across seats.

Stripe for SaaS billing. Connect a card in checkout; invoices and customer portal follow Stripe’s standard flows.

Yes via Google Map Extractor — import local businesses into the same database you use for LinkedIn campaigns.

Prefer native webhooks and API on Team+ for reliable event delivery. If you need Zapier-style glue, webhook into Zapier or Make from your workspace events.

Email support@12pilot.net. Agency customers with a dedicated Slack channel should use that channel for faster operational help. Partners can also reach out from the become-a-partner contact form.

Privacy Policy, Terms of Service, and Cookie Policy live under /policy on 12pilot.net. Read them before connecting LinkedIn accounts that hold customer data.

Every query is scoped by workspace. One company cannot read another company’s leads, seats, or messages. That isolation is a hard platform rule.

LinkedIn credential seats use AES-GCM encryption for stored secrets, with encryption handled in backend services — not in the browser.

Yes. Completed actions write to an immutable log used for daily stats, debugging, and proving what sent. Queued work retries carefully to avoid duplicate sends.

Yes. Contact support@12pilot.net to exercise access, correction, export, or deletion rights. We may need to verify identity before fulfilling a request.

Yes — web app, workers, queues, daily caps, encrypted logins, and live billing are in production at 12pilot.net. We do not claim ISO certifications we have not earned; the safety checks above are already live.

Search this library again with keywords like Unibox, seats, Maps, or AI, or email support@12pilot.net with your workspace name and a screenshot of the error.