Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix Issue 1: 咨询链路整改 + 约拍表单大幅简化 [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#14760•Fetched 2026-04-24 06:14:53
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
0
Author
xingye19931215-opsxingye19931215-ops
Participants
xingye19931215-opsxingye19931215-ops
Timeline (top)
cross-referenced ×3labeled ×2
RAW_BUFFERClick to expand / collapse

目标

重构咨询入口与表单，对齐新产品逻辑：用户不直接联系摄影师，所有咨询先由平台承接。

具体改动

1. 机器人欢迎气泡层（前置于表单）

  • 用户点击「发起咨询」后，先展示机器人欢迎语气泡
  • 气泡文案：「你好，我是约拍助理！请留下简要信息，我们会尽快联系你 💬」
  • 代码结构预留 bot_config 接口（url/token/enabled），当前 enabled=false，后续真实接入时只需开关
  • 点击「填写信息」展开表单

2. 约拍表单字段大幅简化（已拍板）

保留字段：

  • 拍摄城市（多选 + 每个城市可选多个日期时间段）
  • 微信号（推荐必填）/ 手机号（二选一）
  • 备注（选填）

删除字段：

  • 姓名
  • 预算范围
  • 风格偏好
  • 拍摄类型多选

3. 表单提交后的状态承接

  • 提交成功页文案更新，明确「助理会在xx小时内通过微信/手机联系你」
  • me/inquiries 咨询状态承接文案对齐

涉及文件

  • src/app/(user)/inquire/page.tsx
  • src/app/(user)/inquire/success/page.tsx

验收标准

  • /inquire 页面：先见机器人气泡，再展开表单
  • 表单只含已拍板字段
  • 微信/手机二选一逻辑正确
  • 城市可多选，每个城市可选多个日期
  • 提交成功页文案正确承接
  • 禁止 auto merge

extent analysis

TL;DR

Update the inquire page to display a robot welcome bubble before the form, simplify the form fields, and modify the submission success page to reflect the new product logic.

Guidance

  • Review the src/app/(user)/inquire/page.tsx file to ensure the robot welcome bubble is correctly implemented and the form fields are simplified as specified.
  • Verify that the bot_config interface is properly configured with the correct URL, token, and enabled status.
  • Check the src/app/(user)/inquire/success/page.tsx file to confirm the submission success page text is updated to reflect the new product logic.
  • Test the form submission process to ensure the correct fields are required and the submission success page is displayed with the correct text.

Example

No code example is provided as the issue does not contain specific code snippets.

Notes

The issue appears to be a product requirement change, and the guidance provided is based on the assumption that the development team is familiar with the existing codebase and can implement the changes accordingly.

Recommendation

Apply the workaround by updating the inquire page and form fields as specified, and modifying the submission success page to reflect the new product logic, as this is a deliberate product change rather than a bug fix.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#latency issue#model loading#dependency error#configuration error#environment variable

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING