inbox-reply

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Inbox Reply

收件箱回复

Manage and reply to lead responses in the email sequencing inbox.

管理并回复邮件序列收件箱中的潜在客户回复内容。

Environment

环境变量

Variable	Service
`INSTANTLY_API_KEY`	Instantly

Base URL:

https://api.instantly.ai/api/v2

变量	服务
`INSTANTLY_API_KEY`	Instantly

基础URL:

https://api.instantly.ai/api/v2

Inputs

输入参数

Input	Required	Source
Instantly API key	yes	env var
Context file	yes	context file (voice, product, proof points)
Campaign ID	no	user selection or list from API

输入项	是否必填	来源
Instantly API密钥	是	环境变量
上下文文件	是	上下文文件（语气、产品、佐证要点）
营销活动ID	否	用户选择或API返回列表

Workflow

工作流程

Step 1: Fetch unread replies

步骤1：获取未读回复

Fetch unread received emails from the unibox.

List unread:

GET /emails

with

is_unread=true

email_type=received

sort_order=desc

limit=50

If the user specifies a campaign, add

campaign_id

filter. If they want focused inbox only, add

mode=emode_focused

Present a summary table:

| # | From | Company | Subject | Preview | Received |

Ask the user which conversations to work on, or process all.

从Unibox中获取未读的收件邮件。

列出未读邮件： 调用

GET /emails

接口，参数为

is_unread=true

、

email_type=received

、

sort_order=desc

、

limit=50

。

如果用户指定了营销活动，添加

campaign_id

筛选条件。如果用户仅关注聚焦收件箱，添加

mode=emode_focused

参数。

展示汇总表格：

| 序号 | 发件人 | 公司 | 主题 | 预览内容 | 接收时间 |

询问用户要处理哪些对话，或者是否处理全部。

Step 2: Load full threads

步骤2：加载完整对话线程

For each selected reply, load the full conversation thread.

Get thread:

GET /emails?search=thread:{thread_id}&sort_order=asc

This returns the original outbound email(s) and all replies in chronological order, giving full context for drafting a response.

针对每个选中的回复，加载完整的对话线程。

获取对话线程： 调用

GET /emails?search=thread:{thread_id}&sort_order=asc

接口

该接口会按时间顺序返回原始外发邮件及所有回复内容，为生成回复提供完整上下文。

Step 3: Classify reply intent

步骤3：分类回复意图

Read each lead reply and classify into one of these categories:

Interested        → wants to learn more, asks questions, requests a call
Objection         → raises concern but door is not closed (pricing, timing, fit)
Not interested    → clear rejection, asks to stop
Auto-reply        → OOO, bounce, auto-responder
Meeting request   → explicitly asks to book time
Question          → asks a specific question without clear buying signal
Referral          → redirects to someone else at the company

Present classifications to the user for confirmation before drafting.

读取每条潜在客户的回复，并将其分类为以下类别之一：

感兴趣        → 想要了解更多、提出问题、请求通话
异议          → 提出顾虑但并未完全拒绝（价格、时机、适配性）
不感兴趣      → 明确拒绝、要求停止联系
自动回复      → 外出不在、邮件退回、自动回复器
会议请求      → 明确要求预约时间
问题咨询      → 提出具体问题但无明确购买信号
转介          → 转介给公司内其他人员

在生成回复草稿前，将分类结果展示给用户确认。

Step 4: Draft replies

步骤4：生成回复草稿

Read the context file for voice rules, product description, proof points, and use case framings. Draft a reply for each conversation based on intent:

Interested       → confirm interest, propose next step (call or resource)
Objection        → address concern directly, offer proof point if relevant
Question         → answer the question, bridge to value
Meeting request  → confirm availability, suggest booking link or times
Referral         → thank them, ask for intro or reach out to referral directly
Not interested   → short, respectful close; do not push
Auto-reply       → skip, no reply needed

Rules for all replies:

Match the lead's tone and length — short replies get short responses
Reference specifics from their message to show it is not a template
Reference the original outbound context when relevant
Never start with "I" as the first word
No generic openers ("Thanks for getting back to me", "Great to hear from you")
One clear call to action per reply, never two
No attachments unless the user explicitly provides one
Plain text unless the original thread was HTML-formatted

Present each draft alongside the original thread for the user to review and edit.

读取上下文文件中的语气规则、产品描述、佐证要点和用例框架。根据回复意图为每个对话生成回复草稿：

感兴趣       → 确认对方兴趣，提出下一步建议（通话或资料）
异议        → 直接回应顾虑，如有相关佐证要点则提供
问题咨询      → 回答问题，衔接产品价值
会议请求      → 确认可预约时间，建议预约链接或具体时段
转介          → 表示感谢，请求引荐或直接联系被转介人
不感兴趣      → 简短、礼貌地结束对话；不要过度推销
自动回复      → 跳过，无需回复

所有回复需遵循以下规则：

匹配潜在客户的语气和篇幅——简短回复对应简短的回应
引用对方消息中的具体内容，表明回复并非模板
相关时引用原始外发邮件的上下文
永远不要以“我”作为回复的第一个词
避免通用开场白（如“感谢您的回复”、“很高兴收到您的消息”）
每条回复仅包含一个明确的行动召唤，不要有多个
除非用户明确要求，否则不要添加附件
除非原始对话是HTML格式，否则使用纯文本格式

将每个回复草稿与原始对话线程一同展示给用户审核和编辑。

Step 5: Confirm and send

步骤5：确认并发送

Before sending, present a final checklist for each reply:

| # | To | Via Account | Subject | Intent | Action |

The user must confirm before any reply is sent.

Send reply:

POST /emails/reply

with:

```
eaccount
```
: the same email account that sent the original outbound
```
reply_to_uuid
```
: the ID of the lead's most recent message
```
subject
```
: keep the existing thread subject (Re: ...)
```
body
```
: the approved reply in
```
{ "text": "...", "html": "..." }
```

Send one at a time. Report success or failure for each.

发送前，为每条回复展示最终检查清单：

| 序号 | 收件人 | 发送账户 | 主题 | 意图 | 行动 |

所有回复必须经用户确认后才能发送。

发送回复： 调用

POST /emails/reply

接口，参数包括：

```
eaccount
```
: 与原始外发邮件相同的发件账户
```
reply_to_uuid
```
: 潜在客户最新消息的ID
```
subject
```
: 保留现有对话主题（Re: ...）
```
body
```
: 已获批的回复内容，格式为
```
{ "text": "...", "html": "..." }
```

逐个发送回复，并报告每条的成功或失败状态。

Step 6: Post-reply housekeeping

步骤6：回复后整理

After sending:

Mark thread as read:

POST /emails/threads/{thread_id}/mark-as-read

Update lead interest status if the classification warrants it:
```
POST /leads/update-interest-status
```
with
```
lead_email
```
and appropriate
```
interest_value
```
Report final summary:

| # | Lead | Intent | Reply Sent | Status Updated |

发送完成后：

标记对话为已读： 调用

POST /emails/threads/{thread_id}/mark-as-read

接口

更新潜在客户兴趣状态（如果分类结果需要）：调用
```
POST /leads/update-interest-status
```
接口，传入
```
lead_email
```
和对应的
```
interest_value
```
展示最终汇总：

| 序号 | 潜在客户 | 意图 | 是否已发送回复 | 是否已更新状态 |

Step 7: Skip and defer handling

步骤7：跳过和延迟处理

For replies the user wants to skip or defer:

Skip (not interested / auto-reply): mark as read, optionally update interest status
Defer: leave unread, note for next session

Never send a reply the user has not explicitly approved.

对于用户想要跳过或延迟处理的回复：

跳过（不感兴趣/自动回复）： 标记为已读，可选择性更新兴趣状态
延迟： 保持未读状态，记录到下次处理会话

绝不发送未经用户明确批准的回复。

Reference

参考文档

See references/instantly-inbox-api.md for full Instantly Unibox and Reply API documentation.

查看references/instantly-inbox-api.md获取完整的Instantly Unibox和回复API文档。