Back to Details

sales-prospeo

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Prospeo Platform Help

Prospeo平台帮助

Help the user with Prospeo platform questions — from person/company enrichment and search through bulk operations, Chrome extension, API, and integrations.
为用户解答Prospeo平台相关问题——涵盖联系人/企业富集与搜索、批量操作、Chrome扩展、API、集成等全功能模块。

Step 1 — Gather context

步骤1 — 收集上下文信息

Ask the user:
  1. What area of Prospeo do you need help with?
    • A) Person enrichment — finding verified emails and phones for specific contacts
    • B) Company enrichment — firmographic data, tech stack, funding
    • C) Person search — searching 200M+ contacts with filters
    • D) Company search — searching 30M+ companies with filters
    • E) Bulk operations — enriching up to 50 records at once via API
    • F) Chrome extension — LinkedIn Sales Navigator extraction
    • G) API — authentication, endpoints, integration
    • H) Integrations — HubSpot, Salesforce, Clay, Zapier, Make, n8n
    • I) Credits & billing — understanding credit costs, managing usage
    • J) Something else — describe it
  2. What's your role?
    • A) Sales rep / AE / BDR
    • B) Sales manager / team lead
    • C) RevOps / Sales Ops
    • D) Growth / Marketing
    • E) Developer / Engineer
    • F) Founder / solo seller
    • G) Other
  3. What are you trying to accomplish? (describe your specific goal or question)
If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.
向用户询问以下信息：
  1. 你需要Prospeo哪个模块的帮助？
    • A) 联系人富集——查找指定联系人的验证邮箱和手机号
    • B) 企业富集——获取企业统计学数据、技术栈、融资信息
    • C) 联系人搜索——通过筛选条件检索2亿+联系人数据库
    • D) 企业搜索——通过筛选条件检索3000万+企业数据库
    • E) 批量操作——通过API单次最多富集50条记录
    • F) Chrome扩展——LinkedIn Sales Navigator数据提取
    • G) API——鉴权、接口、集成相关问题
    • H) 集成——HubSpot、Salesforce、Clay、Zapier、Make、n8n等集成
    • I) 点数与账单——了解点数消耗规则、管理使用量
    • J) 其他问题——请描述具体内容
  2. 你的角色是什么？
    • A) 销售代表/AE/BDR
    • B) 销售经理/团队负责人
    • C) 营收运营/销售运营
    • D) 增长/营销岗位
    • E) 开发/工程师
    • F) 创始人/独立销售
    • G) 其他
  3. 你想要实现什么目标？（请描述具体的目标或问题）
**如果用户的请求已经提供了大部分上下文信息，可以直接跳转到对应步骤。**优先基于合理假设（需明确说明假设内容）给出你能提供的最优解答，最后仅补充1-2个最关键的澄清问题即可——不要要求用户提供完整信息后才给出回复。

Step 2 — Route or answer directly

步骤2 — 路由跳转或直接解答

If the request maps to a specialized skill, route:
  • Building prospect lists from scratch → 
    /sales-prospect-list
  • Enrichment strategy across multiple tools → 
    /sales-enrich
  • Email deliverability / verification strategy → 
    /sales-deliverability
  • Buying signals / intent interpretation → 
    /sales-intent
  • Connecting tools / webhooks / Zapier → 
    /sales-integration
Otherwise, answer directly from platform knowledge using the reference below.
如果用户的请求对应其他专门技能，请跳转：
  • 从零搭建潜在客户名单 → 
    /sales-prospect-list
  • 跨多工具的富集策略制定 → 
    /sales-enrich
  • 邮箱送达率/验证策略 → 
    /sales-deliverability
  • 购买信号/意向解读 → 
    /sales-intent
  • 工具对接/webhook/Zapier配置 → 
    /sales-integration
否则，参考下方平台知识库内容直接解答。

Step 3 — Prospeo platform reference

步骤3 — Prospeo平台参考说明

Person Enrichment

联系人富集

The core Prospeo feature — find verified emails, mobile numbers, and full B2B profiles.
Input options (any one of these):
  • First name + last name + company identifier (name, website, or LinkedIn URL)
  • Full name + company identifier
  • LinkedIn URL (standalone)
  • Email address (standalone — reverse lookup)
  • Person ID (from a previous search)
What you get back:
  • Verified email with status (VERIFIED, NOT_VERIFIED)
  • Mobile number with verification status (costs 10 credits extra)
  • Full profile: job title, job history, headline, skills, location, timezone
  • Current company data: name, domain, industry, employee count, funding, tech stack, job postings
Key settings:
  • only_verified_email: true
    — only return results with a verified email (saves credits on unmatched)
  • enrich_mobile: true
    — include mobile number lookup (costs 10 credits instead of 1)
  • only_verified_mobile: true
    — only return results with a verified mobile
Credit costs:
  • Standard enrichment (person + company + email): 1 credit
  • With mobile: 10 credits (email included free)
  • No match found: free
  • Same record enriched again: free (lifetime dedup)
Prospeo核心功能——查找验证后的邮箱、手机号以及完整的B2B个人资料。
输入选项（任选其一即可）：
  • 名 + 姓 + 企业标识符（企业名称、官网、LinkedIn地址）
  • 全名 + 企业标识符
  • LinkedIn地址（单独使用）
  • 邮箱地址（单独使用，反向查询）
  • 联系人ID（来自之前的搜索结果）
返回内容：
  • 带验证状态的邮箱（VERIFIED：已验证、NOT_VERIFIED：未验证）
  • 带验证状态的手机号（额外消耗10点数）
  • 完整资料：职位、工作经历、个人简介、技能、所在地、时区
  • 当前企业数据：名称、域名、行业、员工规模、融资情况、技术栈、招聘信息
核心配置项：
  • only_verified_email: true
    ——仅返回包含已验证邮箱的结果（未匹配时不消耗点数）
  • enrich_mobile: true
    ——包含手机号查询（消耗10点数而非1点数）
  • only_verified_mobile: true
    ——仅返回包含已验证手机号的结果
点数消耗：
  • 标准富集（联系人+企业+邮箱）：1点数
  • 包含手机号：10点数（邮箱免费包含在内）
  • 未匹配到结果：免费
  • 重复富集同一条记录：免费（终身去重）

Company Enrichment

企业富集

Firmographic data on 30M+ companies — 50+ data fields.
Input options (any one of these):
  • Company website/domain (most reliable)
  • Company LinkedIn URL
  • Company name (use with caution — less precise)
  • Company ID (from previous enrichment)
What you get back:
  • Basic info: name, website, domain, description
  • Classification: industry, type, SIC/NAICS codes
  • Size: employee count, employee range, revenue range
  • Location: HQ address, country, state, city
  • Social: LinkedIn, Twitter, Facebook, YouTube URLs
  • Financial: funding history, total funding, last funding date
  • Technology: tech stack detection
  • Engagement: job postings, B2B/B2C attributes, free trial/pricing indicators
Credit costs: 1 credit per matched company. Free for no match or duplicate.
覆盖3000万+企业的统计学数据，包含50+数据字段。
输入选项（任选其一即可）：
  • 企业官网/域名（最可靠）
  • 企业LinkedIn地址
  • 企业名称（谨慎使用，精准度较低）
  • 企业ID（来自之前的富集结果）
返回内容：
  • 基础信息：名称、官网、域名、简介
  • 分类信息：行业、类型、SIC/NAICS编码
  • 规模信息：员工数量、员工规模区间、营收区间
  • 地理位置：总部地址、国家、省份、城市
  • 社交媒体：LinkedIn、Twitter、Facebook、YouTube地址
  • 财务信息：融资历史、总融资金额、最近融资日期
  • 技术信息：技术栈检测结果
  • 运营信息：招聘信息、B2B/B2C属性、免费试用/定价标识
点数消耗：每匹配到1家企业消耗1点数，未匹配或重复查询免费。

Person Search

联系人搜索

Search through 200M+ contacts with 30+ filters. Returns up to 25 results per page, max 25,000 total (1,000 pages).
Available filters:
Filter categoryFilters
Companyindustry, location, headcount range, funding (stage, date, amount, total), websites (up to 500), names (up to 500)
Personseniority, department, location, job title, years of experience
Important: Search returns profile data but NOT emails or phones. You must use Enrich Person on results to get contact info. Search costs 1 credit per request that returns results.
通过30+筛选条件检索2亿+联系人数据库，每页最多返回25条结果，最多返回25000条（1000页）。
可用筛选条件：
筛选分类筛选项
企业维度行业、地理位置、员工规模区间、融资（阶段、日期、金额、总额）、官网（最多500个）、企业名称（最多500个）
个人维度职级、部门、地理位置、职位、工作年限
重要提示：搜索返回的是个人资料数据，不包含邮箱或手机号。你需要对搜索结果使用「联系人富集」功能获取联系方式。有返回结果的搜索请求每次消耗1点数。

Company Search

企业搜索

Search through 30M+ companies with filters. Same pagination as Person Search.
Available filters:
  • Industry, location, headcount range
  • Funding: stage, date, last amount, total amount
  • Technology stack, email provider (MX)
  • NAICS codes, SIC codes
  • Websites (up to 500), names (up to 500)
Credit cost: 1 credit per request that returns results.
通过筛选条件检索3000万+企业数据库，分页规则和联系人搜索一致。
可用筛选条件：
  • 行业、地理位置、员工规模区间
  • 融资：阶段、日期、最近融资额、总融资额
  • 技术栈、邮箱服务商（MX）
  • NAICS编码、SIC编码
  • 官网（最多500个）、企业名称（最多500个）
点数消耗：有返回结果的搜索请求每次消耗1点数。

Bulk Operations

批量操作

Enrich up to 50 records per API call for both person and company enrichment.
Bulk Enrich Person: Same input options as single enrichment, but send an array of up to 50 records. Each record needs a unique 
identifier
string for tracking. Response separates 
matched
, 
not_matched
, and 
invalid_datapoints
.
Bulk Enrich Company: Same — up to 50 companies per call with identifiers.
Credit costs: Same as single enrichment (1 per matched person/company, 10 for mobile). 
total_cost
field in response tracks total credits spent.
联系人富集和企业富集都支持单次API调用最多富集50条记录。
批量联系人富集：输入选项和单条富集一致，但需要发送最多50条记录组成的数组，每条记录需要包含唯一的
identifier
字符串用于追踪。返回结果会区分
matched
（已匹配）、
not_matched
（未匹配）、
invalid_datapoints
（无效数据）。
批量企业富集：规则同上，单次调用最多提交50家企业，每条记录需包含标识符。
点数消耗：和单条富集规则一致（每匹配1个联系人/企业消耗1点数，包含手机号则消耗10点数）。返回结果中的
total_cost
字段会统计总消耗点数。

Chrome Extension

Chrome扩展

Prospeo's Chrome extension extracts contact data from LinkedIn and LinkedIn Sales Navigator.
What it does:
  • Find verified emails from LinkedIn profiles
  • Extract contact data while browsing Sales Navigator
  • One-click enrichment without switching to the Prospeo app
Prospeo的Chrome扩展可以从LinkedIn和LinkedIn Sales Navigator提取联系人数据。
核心功能：
  • 从LinkedIn个人主页查找验证邮箱
  • 浏览Sales Navigator时提取联系人数据
  • 一键富集，无需切换到Prospeo应用

5-Step Email Verification

5步邮箱验证

Prospeo uses a 5-step verification process (built into enrichment — not a separate endpoint):
  1. Syntax check — valid email format
  2. Domain/MX check — domain exists and accepts email
  3. SMTP verification — mailbox exists
  4. Catch-all detection — identifies domains that accept all addresses
  5. Result validation — cross-references multiple signals
Verification statuses: 
VERIFIED
(safe to send), 
NOT_VERIFIED
(use with caution).
Prospeo使用5步验证流程（内置在富集功能中，没有独立接口）：
  1. 语法检查——验证邮箱格式是否有效
  2. 域名/MX检查——验证域名存在且可接收邮件
  3. SMTP验证——验证邮箱真实存在
  4. Catch-all检测——识别可接收任意地址邮件的域名
  5. 结果校验——交叉比对多维度信号
验证状态：
VERIFIED
（可安全发送）、
NOT_VERIFIED
（谨慎使用）。

Prospeo data model

Prospeo数据模型

EntityWhat it representsKey relationships
PersonA B2B professional with contact infoHas email, mobile, job history, skills; linked to Company
CompanyAn organization with firmographic dataHas employees, funding, tech stack, job postings
SearchA filtered query across the databaseReturns Person or Company results (no contact info)
EnrichmentA lookup that returns full contact dataConsumes credits; lifetime dedup per account
实体含义核心关联
联系人（Person）带有联系方式的B2B职场人士关联邮箱、手机号、工作经历、技能；关联所属企业
企业（Company）带有统计学数据的组织机构关联员工、融资信息、技术栈、招聘信息
搜索（Search）跨数据库的筛选查询返回联系人或企业结果（不含联系方式）
富集（Enrichment）返回完整联系方式的查询操作消耗点数；同账号终身去重

API quick reference

API快速参考

  • Base URL: 
    https://api.prospeo.io
  • Auth: 
    X-KEY
    header with API key
  • Method: POST for all endpoints (GET for account-information only)
  • Content-Type: 
    application/json
  • Rate limits: Per-plan, tracked via response headers (
    x-daily-request-left
    , 
    x-minute-request-left
    , 
    x-second-rate-limit
    )
  • Active endpoints: 
    /enrich-person
    , 
    /bulk-enrich-person
    , 
    /enrich-company
    , 
    /bulk-enrich-company
    , 
    /search-person
    , 
    /search-company
    , 
    /search-suggestions
    , 
    /account-information
  • Deprecated (removed March 1, 2026): 
    /email-finder
    , 
    /mobile-finder
    , 
    /email-verifier
    , 
    /domain-search
    , 
    /social-url-enrichment
For the full endpoint catalog, request/response schemas, and rate limits, see 
references/prospeo-api-reference.md
.
  • 基础URL：
    https://api.prospeo.io
  • 鉴权方式：请求头携带
    X-KEY
    和API密钥
  • 请求方法：所有接口均使用POST（仅账户信息接口使用GET）
  • Content-Type：
    application/json
  • 速率限制：按套餐等级划分，通过响应头返回（
    x-daily-request-left
    、
    x-minute-request-left
    、
    x-second-rate-limit
    ）
  • 可用接口：
    /enrich-person
    、
    /bulk-enrich-person
    、
    /enrich-company
    、
    /bulk-enrich-company
    、
    /search-person
    、
    /search-company
    、
    /search-suggestions
    、
    /account-information
  • 已废弃接口（2026年3月1日下线）：
    /email-finder
    、
    /mobile-finder
    、
    /email-verifier
    、
    /domain-search
    、
    /social-url-enrichment
完整的接口目录、请求/响应 schema、速率限制说明请查看
references/prospeo-api-reference.md
。

Integrations

集成能力

IntegrationTypeWhat it does
HubSpotNativeEnrich CRM contacts with verified emails, phones, firmographic data
SalesforceNativeKeep CRM data clean with enriched contacts and accounts
ClayNativeAutomate data enrichment in Clay workflows, build dynamic lead lists
SmartleadNativePush enriched leads to Smartlead campaigns
InstantlyNativePush enriched leads to Instantly campaigns
LemlistNativePush enriched leads to Lemlist sequences
ZapierNativeConnect to 8,000+ apps for automated workflows
MakeNativeVisual automation workflows with Prospeo actions
n8nNative (community node)Self-hosted automation with 
@prospeo/n8n-nodes-prospeo
MCP ServerOfficial (
@prospeo/mcp-server
)		Access enrichment and search from AI agents via Model Context Protocol
集成产品类型功能
HubSpot原生集成用验证后的邮箱、手机号、企业数据丰富CRM联系人信息
Salesforce原生集成通过富集后的联系人和账户数据保持CRM数据清洁
Clay原生集成在Clay工作流中自动完成数据富集，搭建动态线索名单
Smartlead原生集成将富集后的线索推送到Smartlead营销活动
Instantly原生集成将富集后的线索推送到Instantly营销活动
Lemlist原生集成将富集后的线索推送到Lemlist触达序列
Zapier原生集成对接8000+应用实现自动化工作流
Make原生集成通过Prospeo动作搭建可视化自动化工作流
n8n原生集成（社区节点）通过
@prospeo/n8n-nodes-prospeo
实现自托管自动化
MCP Server官方提供（
@prospeo/mcp-server
）		通过模型上下文协议让AI Agent访问富集和搜索能力

Pricing

定价

As of March 2026 — verify current pricing at prospeo.io/pricing
PlanPrice/moCredits/moKey features
Free$075Core enrichment, Chrome extension
Starter$391,000Full API access
Growth$995,000Team sharing
Pro$19920,000Priority support
Business$36950,000High-volume enrichment
All plans include person + company enrichment, search, Chrome extension, and API access. Mobile enrichment costs 10 credits per lookup on all plans.
2026年3月版本——最新定价请查看prospeo.io/pricing
套餐月费每月点数核心权益
免费版$075核心富集功能、Chrome扩展
入门版$391000完整API访问权限
成长版$995000团队共享
专业版$19920000优先支持
企业版$36950000高吞吐富集能力
所有套餐都包含联系人+企业富集、搜索、Chrome扩展、API访问权限。所有套餐的手机号富集均按每次查询10点数消耗。

Step 4 — Actionable guidance

步骤4 — 可落地的指导建议

Based on the user's specific question:
  1. Step-by-step instructions — numbered steps to accomplish their goal in Prospeo
  2. Configuration recommendations — specific settings, with navigation paths
  3. Common pitfalls — what can go wrong and how to avoid it
  4. Verification — how to confirm the change worked
  5. For API questions — always include: "For the full endpoint catalog, request/response schemas, and rate limits, see 
    references/prospeo-api-reference.md
    ."
根据用户的具体问题提供以下内容：
  1. 分步操作指引——用编号步骤说明在Prospeo中完成目标的操作流程
  2. 配置建议——具体的配置项，附带操作路径
  3. 常见误区——容易出错的点以及规避方法
  4. 结果验证——如何确认操作生效
  5. API相关问题——必须补充：「完整的接口目录、请求/响应 schema、速率限制说明请查看
    references/prospeo-api-reference.md
    。」

Gotchas

注意事项

Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.
  • Don't confuse Search with Enrichment. Person Search and Company Search return profile data but NOT emails or phones. You must call Enrich Person/Company separately to get contact info. This is a two-step process and each step costs credits.
  • Don't forget mobile enrichment costs 10x. A standard enrichment is 1 credit, but adding 
    enrich_mobile: true
    makes it 10 credits. At scale this adds up fast. Only enable mobile for contacts you'll actually call.
  • Don't use deprecated endpoints. The old Email Finder, Mobile Finder, Email Verifier, Domain Search, and Social URL Enrichment endpoints were removed March 1, 2026. Use the new Enrich Person/Company endpoints instead.
  • Don't ignore the lifetime dedup. Prospeo doesn't charge for re-enriching the same record. If you need updated data on someone you've already enriched, re-run the enrichment for free. But note this is per-account, not per-team-member.
  • Don't search by company name alone. Company name matching is fuzzy and can return wrong results. Always use website/domain or LinkedIn URL as the company identifier when possible.
基于调研整理的最优实践——请重点查看，尤其是套餐限制功能、集成相关的注意事项可能会更新过时。
  • 不要混淆搜索和富集功能。联系人搜索和企业搜索返回的是资料数据，不包含邮箱或手机号，你需要单独调用联系人/企业富集接口获取联系方式。这是两个独立步骤，每一步都会消耗点数。
  • 不要忽略手机号富集10倍的点数消耗。标准富集仅消耗1点数，但开启
    enrich_mobile: true
    后会消耗10点数，大规模使用时成本增长很快，仅对你实际需要电话联系的联系人开启该功能即可。
  • 不要使用已废弃接口。旧的邮箱查找、手机号查找、邮箱验证、域名搜索、社交地址富集接口已于2026年3月1日下线，请使用新的联系人/企业富集接口替代。
  • 不要浪费终身去重权益。Prospeo不会对重复富集同一条记录收费，如果你需要获取之前已经富集过的联系人的最新数据，可以免费重新执行富集。注意该规则是账号维度的，不是团队成员维度。
  • 不要仅使用企业名称搜索。企业名称匹配是模糊匹配，可能返回错误结果，尽可能使用官网/域名或者LinkedIn地址作为企业标识符。

Step 5 — Related skills

步骤5 — 相关技能

  • /sales-enrich
    — Enrichment strategy across multiple tools (waterfall, CRM hygiene, credit optimization)
  • /sales-prospect-list
    — Build prospect lists to enrich with Prospeo
  • /sales-deliverability
    — Email deliverability — verify emails before sending
  • /sales-intent
    — Layer buying signals on enriched contacts to prioritize outreach
  • /sales-cadence
    — Design outbound sequences for enriched contacts
  • /sales-integration
    — Connect Prospeo to other tools via API, Zapier, Make, n8n
  • /sales-do
    — Not sure which skill to use? The router matches any sales objective to the right skill. Install: 
    npx skills add sales-skills/sales --skills sales-do
  • /sales-enrich
    —— 跨多工具的富集策略（瀑布流富集、CRM数据 hygiene、点数优化）
  • /sales-prospect-list
    —— 搭建可用于Prospeo富集的潜在客户名单
  • /sales-deliverability
    —— 邮箱送达率——发送前验证邮箱有效性
  • /sales-intent
    —— 给富集后的联系人叠加购买信号，优先触达高意向客户
  • /sales-cadence
    —— 为富集后的联系人设计外触达序列
  • /sales-integration
    —— 通过API、Zapier、Make、n8n将Prospeo和其他工具对接
  • /sales-do
    —— 不知道该用哪个技能？该路由可以匹配任意销售目标到对应技能。安装命令：
    npx skills add sales-skills/sales --skills sales-do

Examples

示例

Example 1: Enrich a list of prospects

示例1：富集潜在客户名单

User says: "I have 200 LinkedIn URLs from Sales Navigator. How do I enrich them all with emails in Prospeo?" Skill does:
  1. Recommends using the Bulk Enrich Person API endpoint with LinkedIn URLs
  2. Explains batching into groups of 50 (API limit per call)
  3. Shows the API request format with 
    linkedin_url
    as the data field
  4. Recommends setting 
    only_verified_email: true
    to save credits
  5. Calculates credit cost: 200 credits max (1 per match, free for no-match) Result: User has a batched enrichment plan with API examples and credit estimate
用户提问：「我从Sales Navigator导出了200条LinkedIn地址，怎么用Prospeo批量富集获取所有人的邮箱？」 技能响应：
  1. 推荐使用批量联系人富集API接口，传入LinkedIn地址
  2. 说明需要分成50条一组的批次（API单次调用上限）
  3. 展示以
    linkedin_url
    为入参的API请求格式
  4. 建议设置
    only_verified_email: true
    节省点数
  5. 计算点数消耗：最多200点数（每条匹配成功消耗1点数，未匹配免费） 结果：用户获得分批次富集方案，包含API示例和点数预估。

Example 2: Find decision-makers at target companies

示例2：查找目标企业的决策人

User says: "I need to find VP-level contacts at 50 SaaS companies with 100-500 employees" Skill does:
  1. Recommends using Search Person with company filters (headcount_range, industry) and person filters (seniority: VP)
  2. Shows how to use 
    company.websites
    filter with a list of target domains
  3. Explains that search results need separate enrichment to get emails
  4. Suggests a workflow: Search → filter results → Bulk Enrich top matches Result: Two-step search-then-enrich workflow with filter configuration
用户提问：「我需要找50家员工规模100-500人的SaaS企业的VP级联系人」 技能响应：
  1. 推荐使用联系人搜索功能，配置企业筛选条件（员工规模区间、行业）和个人筛选条件（职级：VP）
  2. 展示如何使用
    company.websites
    筛选器传入目标域名列表
  3. 说明搜索结果需要单独富集才能获取邮箱
  4. 建议工作流：搜索→筛选结果→批量富集高匹配度联系人 结果：用户获得「先搜索后富集」的两步工作流，包含筛选配置方法。

Example 3: API integration with CRM

示例3：和CRM的API集成

User says: "How do I set up auto-enrichment of new HubSpot contacts with Prospeo?" Skill does:
  1. Checks if the user wants native HubSpot integration or custom API pipeline
  2. For native: walks through connecting HubSpot in Prospeo settings
  3. For custom: designs a Zapier/Make workflow — HubSpot "New Contact" trigger → Prospeo Enrich Person action → HubSpot "Update Contact" with enriched fields
  4. Addresses credit budgeting for ongoing auto-enrichment Result: Auto-enrichment pipeline with credit management strategy
用户提问：「怎么配置Prospeo自动富集新的HubSpot联系人？」 技能响应：
  1. 询问用户需要原生HubSpot集成还是自定义API流程
  2. 原生集成：指导用户在Prospeo设置中绑定HubSpot账号
  3. 自定义流程：设计Zapier/Make工作流——HubSpot「新联系人」触发→Prospeo联系人富集动作→HubSpot「更新联系人」写入富集字段
  4. 说明持续自动富集的点数预算管理方法 结果：用户获得自动富集流程方案，包含点数管理策略。

Troubleshooting

故障排查

Low match rate on enrichments

富集匹配率低

Symptom: Many records return NO_MATCH Cause: Insufficient identifying data, or contacts are in niche industries with low database coverage Solution: Provide multiple data points (name + company website + LinkedIn URL) for best matching. Use 
only_verified_email: false
to see unverified results. For low-coverage segments, consider waterfall enrichment with multiple providers — see 
/sales-enrich
.
症状：很多记录返回NO_MATCH 原因：标识数据不足，或者联系人所属细分行业数据库覆盖率低 解决方案：提供多维度标识数据（姓名+企业官网+LinkedIn地址）获得最佳匹配效果。设置
only_verified_email: false
查看未验证结果。对于低覆盖率的细分领域，可考虑多供应商瀑布流富集方案，参考
/sales-enrich
。

API returning 429 errors

API返回429错误

Symptom: Rate limit exceeded errors on API calls Cause: Sending too many requests per minute/second for your plan tier Solution: Check response headers (
x-minute-request-left
, 
x-second-rate-limit
) to understand your limits. Implement exponential backoff on 429 responses. Use bulk endpoints (50 records per call) instead of single enrichments to reduce request count.
症状：API调用返回速率超限错误 原因：每秒/每分钟请求量超过你的套餐等级限制 解决方案：查看响应头（
x-minute-request-left
、
x-second-rate-limit
）了解你的速率限制。收到429响应时实现指数退避逻辑。使用批量接口（单次调用最多50条记录）替代单条富集减少请求量。

Credits running out mid-month

月中点数耗尽

Symptom: INSUFFICIENT_CREDITS error before billing cycle resets Cause: Mobile enrichment consuming 10x credits, or bulk operations enriching unqualified records Solution: Check usage via the Account Information endpoint or dashboard. Disable 
enrich_mobile
for contacts you won't call. Use 
only_verified_email: true
to skip unverifiable records. Apply ICP filters before enriching — don't enrich contacts you'll never reach out to.
症状：账单周期重置前返回INSUFFICIENT_CREDITS错误 原因：手机号富集消耗10倍点数，或者批量操作富集了大量不符合要求的记录 解决方案：通过账户信息接口或后台查看使用情况。对不需要电话联系的联系人关闭
enrich_mobile
。设置
only_verified_email: true
跳过无法验证的记录。富集前先应用ICP筛选——不要对你永远不会触达的联系人执行富集。