消息助手

· 108 QUESTIONS · 12 TOPICS

产品百问百答Product FAQ

消息助手 是面向个人与企业的数字分身,定位为人格大脑与行动中枢:以消息为入口,结合本体的表达习惯、授权知识和关系记忆,协助沟通、整理事务与推进任务,并逐步连接人员、业务系统和设备。

is a digital counterpart for individuals and businesses, positioned as a personality-aware brain and action hub. Messages are the starting point for authorized communication, relationship memory and task collaboration, with progressive connections to people, business systems and devices.

当前电脑端仍在实战迭代。微信链路尚未完成稳定验收;手机互联、云电脑联动、私有部署等按各问说明确认,不代表全部已上线。更新:2026年11月1日。

The desktop product is still undergoing real-world iteration. The WeChat workflow has not completed stable acceptance testing. Connected mobile, cloud-PC coordination and private deployment are not all released; see the individual answers. Updated 1 November 2026.

中英对照为本站内容。其他语言通过 Google 翻译打开公开页面,属于机器翻译,不代表人工审校版本。
Chinese and English are hosted here. Other languages open the public page in Google Translate and are not human-reviewed editions.

108 / 108

一、认识消息助手Meet

Q1消息助手是什么?What is ?

消息助手 是面向个人与企业的数字分身,产品定位是“人格大脑与行动中枢”。它以消息为入口,结合你的表达习惯、知识和往来记忆,在授权范围内协助沟通、整理事务和推进任务,并逐步连接人员、业务系统与设备。

is a digital counterpart for individuals and businesses, positioned as a personality-aware brain and action hub. Starting with messages, it draws on your communication style, knowledge and authorized relationship memory to assist communication, organize matters and advance tasks. Connections to people, business systems and devices are being developed progressively.

Q2它和自动回复工具有什么不同?How is it different from automatic reply tools?

自动回复只是其中一个使用场景。分身围绕“理解对方—结合知识与记忆—形成回应或任务—人工协同—核对结果”组织工作,不以发送一条消息作为全部目标。各环节能力以对应版本验收为准。

Automatic replies are one use case. The broader workflow is to understand the other person, consult knowledge and memory, form a response or task, collaborate with you and verify the result. Availability of each step depends on the validated version.

Q3它和通用 AI 助手有什么不同?How is it different from a general AI assistant?

产品着重持续的角色、关系和事务上下文,让沟通与后续行动能够接续;你保留决定权,可修改草稿、暂停或接手。不能将产品方向理解成已经接通所有平台和设备。

It focuses on ongoing roles, relationships and task context, so communication can lead to follow-up action. You retain control and can edit drafts, pause or take over. This direction does not mean every platform and device is already connected.

Q4"从消息入口,构建企业的第二大脑与行动中枢"是什么意思?What does a second brain and action hub mean?

消息是业务的第一现场。先从接住、理解、回应消息做起,逐步把业务知识、往来记忆和任务协同沉淀下来,最终成为企业的"第二大脑与行动中枢"。这是我们的产品方向,已在逐步落地。

Messages are a starting point for building business knowledge, relationship memory and task coordination. Becoming a second brain and action hub is an evolving product direction.

Q5什么是消息大脑?What is the message brain?

消息是理解需求与关系的入口。消息大脑结合当前会话、授权知识和历史上下文,判断需要回应、记录、等待还是转交人工。

It uses the current conversation, authorized knowledge and relevant history to decide whether to respond, record a matter, wait or hand it to a person.

Q6什么是人格大脑?What is the personality brain?

不只有语气设定,还包括你的角色、表达习惯、知识、关系记忆和做事边界。目标是帮助分身按你的要求协同处理事务;人格学习与聊天记录蒸馏仍在完善。

It includes roles, communication habits, knowledge, relationship memory and action boundaries, rather than tone alone. Personality learning and distillation of chat history are still being refined.

Q7什么是关系记忆?What is relationship memory?

在授权范围内记录与对方的往来、偏好和约定,用于理解后续沟通。“对方”可能是同事、伙伴、家人、朋友或客户,不预设所有关系都是销售关系。

Within authorized limits, it records past exchanges, preferences and commitments. The other person may be a colleague, partner, family member, friend or customer; not every relationship is a sales relationship.

Q8适合哪些人和团队?Who is it for?

需要同时处理多种关系与事务的个人、创业者和团队。例如整理伙伴沟通、跟进协作事项、查询业务资料、协助服务咨询。企业共享与家庭设备场景按独立开发和交付范围确认。

Individuals, entrepreneurs and teams handling many relationships and matters at once. Examples include partner communication, coordination, reference lookup and service inquiries. Enterprise sharing and household devices require separate development and delivery scopes.

Q9有哪些核心特色?What are its core strengths?

① 按角色和资料训练分身;② 本体优先,保留人工接管;③ 消息与任务衔接;④ 过程可见、结果可核对;⑤ 本机、云电脑和私有部署的统一运行设计;⑥ 逐步连接业务系统与设备。后三项涉及的未接通部分按规划说明。

Role and knowledge training; owner-first human collaboration; linking messages with tasks; visible progress and verifiable results; a unified design for local, cloud-PC and private operation; and progressive connections to business systems and devices. Unconnected parts remain planned capabilities.

Q10当前版本有哪些明确限制?What are the current limitations?

电脑端仍在实战迭代,微信“读取上下文—拟稿—输入—发送—核验”链路尚未完成稳定验收。其他平台真实收发、互联手机端、云电脑执行联动、私有部署、企业共享大脑及家庭设备协同均不能作为已全面交付的能力销售。

The desktop product is still undergoing real-world iteration. The WeChat read–draft–input–send–verify workflow has not completed stable acceptance testing. Other platforms, the connected mobile app, cloud-PC coordination, private deployment, the shared enterprise brain and household devices must not be sold as fully delivered capabilities.

二、购买与价格Purchasing and pricing

Q11怎么收费?How is pricing structured?

按所选软件授权、运行资源、模型用量、可选硬件及实施服务分别确认。旧版 Windows ¥1,980、Mac ¥2,190 的硬件套餐属于历史口径,是否继续适用须由最新报价确认。

Confirm software licensing, runtime resources, model usage, optional hardware and implementation separately. Historical Windows ¥1,980 and Mac ¥2,190 hardware packages require confirmation against the current public quotation.

Q12Windows 和 Mac 怎么选?How should I choose Windows or Mac?

先确认目标应用、系统版本和执行方式的兼容性,再确认可交付安装包。当前实战记录主要围绕 Windows,不据此承诺 Mac 已完成同等能力验收。

First validate the target application, OS version and execution method, then confirm the available installer. Current real-world work mainly concerns Windows and does not establish equivalent Mac acceptance.

Q13价格里包含什么?What does the price include?

以订单列明的软件、算力、运行资源、硬件、实施与售后范围为准。硬件按需接入,不默认所有方案都包含或必须购买硬件。

The order must specify software, model usage, runtime resources, hardware, implementation and support. Hardware is optional according to the solution and is not automatically included or required in every package.

Q14软件是不是永久授权?Is the software license permanent?

按购买时的有效授权条款确认期限、设备数、升级及维护范围。旧套餐的永久授权不能自动延伸到云资源、模型服务和新开发模块。

Confirm the license term, device allowance, updates and maintenance in the applicable purchase terms. A historical perpetual package does not automatically cover cloud resources, model services or new modules.

Q15算力费用怎么算?How are model costs calculated?

按实际模型用量消耗:用多少扣多少,取决于所选模型、对话长度和使用量。不是固定月费。

Costs depend on actual model usage, the selected service, context length and activity. Consult the applicable usage and billing terms.

Q16一个月大概花多少?What is the estimated monthly cost?

取决于任务频率、上下文长度、图像识别调用、模型用量和运行资源。先小范围试用测算;旧版月费估算不能作为当前费用承诺。

It depends on task frequency, context length, visual recognition, model usage and runtime resources. Measure a small pilot first; old monthly estimates are not current price commitments.

Q17有没有固定月费或套餐?Are there monthly plans?

软件、算力与云资源可采用不同计费方式,具体以有效报价为准。不能把“不使用不消耗”用于持续运行的云电脑、存储等资源。

Software, model services and cloud resources may have different billing arrangements. An idle cloud PC or storage may still incur costs. Refer to the effective quotation.

Q18能不能先体验?Can I try it first?

联系销售确认当前可体验的版本和场景。演示、模拟发送和测试通过不等于已完成真实收发验收。

Contact sales to confirm the version and scenarios available for evaluation. Demonstrations, simulated sending and passing tests are not proof of real message delivery.

Q19退换规则是什么?What are the return terms?

以购买时适用的订单与售后条款为准,软件激活、硬件拆封和定制实施分别确认。

The order and after-sales terms apply. Hardware opening, software activation and custom implementation must be considered separately.

Q20有没有保修?Is there a warranty?

硬件保修与软件维护按订单分别约定,购买前确认期限、范围和处理方式。

Hardware warranty and software maintenance are specified separately in the order. Confirm their duration, scope and service process before purchase.

三、下载、安装与激活Download, installation and activation

Q21去哪里下载?Where can I download it?

官网"下载与教程"页(www.qc-vc.com/downloads.html),或直接访问 shop.qc-vc.cn/access/downloads。

Use the official Downloads and tutorials page or shop.qc-vc.cn/access/downloads.

Q22为什么要邀请码或商城账号?Why is a store account or invitation code required?

为保护正版客户权益,安装包仅对商城已购账号或持有效邀请码的用户开放。持邀请码注册的正式客户登录商城后也可直接下载,不要求已下单。

Installer access is limited to eligible store accounts or valid invitation relationships. Formally invited customers may download after logging in without requiring a prior order, subject to the current access rules.

Q23教程需要登录吗?Do tutorials require login?

不需要。图文教程、视频教程和视频封面全部公开,无需验证。

Public written tutorials, videos and their cover images do not require installer access verification.

Q24支持什么系统?Which operating systems are supported?

Windows 与 Mac 都有对应版本,按电脑系统选购。

Windows and Mac packages must be confirmed for the selected product and actual delivery version. Check compatibility before choosing.

Q25电脑配置有什么要求?What computer specifications are needed?

按实际任务、模型运行位置和截图识别负载评估,先验证目标电脑。使用本机桌面执行时需可用的图形桌面、稳定供电与网络;内存需求不能仅用一个数字保证。

Requirements depend on tasks, model location and recognition load. Validate the target computer first. Local desktop execution needs a usable graphical desktop, stable power and networking; a single RAM figure cannot guarantee performance.

Q26安装需要管理员权限吗?Are administrator permissions required?

按安装包、系统权限和可选硬件驱动要求确认。日常截图与桌面操作也需相应授权。

This depends on the installer, system permissions and optional drivers. Screen capture and desktop operations also require appropriate authorization.

Q27初始化流程是什么?How do I initialize it?

安装当前可交付版本,完成账号授权,选择已接通的运行方式,绑定允许操作的窗口和资料范围,再用小范围任务验证。只有选用了相应硬件的方案才需要连接硬件。

Install the available version, authorize the account, choose a connected runtime, bind permitted windows and data, then validate a small task. Connect hardware only when the chosen solution requires it.

Q28换电脑怎么办?What if I change computers?

在原电脑退出授权,新电脑重装后按教程重新激活。授权设备数量以订购时确认为准。

Exit the original authorization and follow the current migration and reactivation instructions. Device limits are governed by the order.

Q29卸载重装要注意什么?What should I check before reinstalling?

先正常退出分身再卸载;重装后历史数据按本地备份恢复,重要数据建议先备份。

Exit normally and back up important data first. Restore only according to the applicable local backup procedure.

Q30安装失败常见原因?Why might installation fail?

系统版本不符、杀毒软件拦截、硬件未连接或驱动未就绪。对照教程逐项检查,仍不行就联系客服,支持远程指导。

Possible causes include an incompatible OS, security software restrictions, missing required hardware or an unready driver. Follow the applicable tutorial and contact support if needed.

四、可选硬件与执行方式Optional hardware and execution

Q31所有方案都必须配硬件吗?Does every solution require hardware?

不是。硬件是可选的接入与执行能力,是否需要取决于具体方案。旧硬件版仍按其要求连接;新方案不能沿用“所有输入都必须经 U盾”的表述。

No. Hardware is an optional connection or execution capability. Legacy hardware editions retain their specific requirements; the newer design must not claim all input requires a USB device.

Q32可选硬件有什么作用?What does optional hardware do?

可作为键鼠执行或现场设备的接入通道。不同硬件负责不同任务,需要逐项适配;键鼠盒子不等于已经打通摄像头、电话或其他设备。

It may provide keyboard/mouse execution or a connection to on-site equipment. Each device requires adaptation. A keyboard/mouse box does not establish working camera, telephone or other integrations.

Q33接入硬件意味着平台授权吗?Does hardware imply platform authorization?

不意味着。硬件只是执行方式,不能代表第三方平台认可,也不能保证账号安全或替代应用授权。

No. Hardware is an execution method; it does not establish third-party approval, guarantee account safety or replace application authorization.

Q34硬件怎么连接?How is hardware connected?

USB 直连电脑,按教程完成识别。正常连接后软件界面会显示硬件状态。

For an applicable USB device, follow its tutorial to connect and verify detection. Requirements depend on the actual model and supported solution.

Q35不接硬件能不能用?Can it work without hardware?

按所选执行方式判断。当前软件执行路径与旧硬件版本要求不同;涉及现场设备的任务仍需要对应接入设备和驱动。

It depends on the execution method. Software execution and legacy hardware editions have different requirements. Tasks involving physical equipment still need the corresponding connection and drivers.

Q36一个环境能连接多少设备?How many devices can one environment connect?

以适配方案与真实验收为准。分身创建数量、同时运行的执行环境数量、可连接设备数量是三个不同指标,不互相等同。

Confirm the adapted solution and actual acceptance results. The number of created counterparts, concurrent execution environments and connected devices are separate measures.

Q37硬件坏了或丢了怎么办?What if hardware is damaged or lost?

联系售后,按订单保修或补购规则处理;确认对当前执行任务的影响后再恢复。

Contact support under the order's warranty or replacement terms. Check the impact on tasks before resuming.

Q38硬件需要驱动吗?Are hardware drivers required?

视设备而定,按对应型号的适配教程准备,不能承诺所有设备即插即用。

It depends on the device. Follow the supported model's instructions rather than assuming every device is plug and play.

Q39硬件要一直连接吗?Must hardware remain connected?

只有依赖该硬件的任务才要求持续连接;拔除前先暂停相关任务。

Only tasks that depend on it require a continuous connection. Pause those tasks before unplugging.

Q40硬件的保修期限是多少?How long is the hardware warranty?

按具体型号和订单售后条款确认,不同设备可能不同。

Check the specific model and order terms; different devices may have different coverage.

五、消息平台与日常使用Messaging platforms and daily use

Q41支持哪些消息平台?Which messaging platforms are supported?

产品面向多种消息场景,当前实战优先验证微信桌面链路;抖音、WhatsApp 等属于后续接入方向。不能把平台名称清单写成已全部支持收发。

The product addresses multiple messaging scenarios. Current real-world validation prioritizes WeChat desktop; Douyin and WhatsApp are later integration directions. A list of platform names is not a list of completed send/receive integrations.

Q42支持企业微信吗?Does it support WeCom?

需按具体接入方式、官方接口权限和实际适配结果确认,不默认已上线,也不承诺固定时间内一定完成适配。

Confirm the integration method, official interface permissions and actual adaptation results. Availability and a fixed adaptation deadline are not assumed.

Q43微信在产品里是什么角色?What role does WeChat play?

微信是当前正在验证的消息入口之一,不是产品全部。对应桌面版本必须单独确认兼容性;微信更新可能影响识别与操作。

It is one entry point currently under validation, not the entire product. Desktop-version compatibility must be checked separately, and updates can affect recognition and operation.

Q44分身数量不限,是否代表支持账号多开?Do unlimited counterparts mean multiple accounts can run at once?

不代表。可按角色和任务创建多个分身,当前产品未设置分身创建数量上限;这不等于一台电脑可同时自动操作多个账号。并发执行、账号隔离与多设备调度需另行验证,不能把云电脑或私有部署直接写成已支持多开。

No. There is currently no imposed creation-count limit for role- or task-based counterparts. This does not mean one computer can automatically operate several accounts simultaneously. Concurrency, isolation and multi-device dispatch require separate validation, including in cloud or private environments.

Q45可以处理群聊吗?Can it process group conversations?

群聊属于当前测试场景,需要判断是否应回应并核对上下文。不能承诺所有群消息都自动发送,也不能将测试能力当作稳定交付。

Group chat is a current test scenario. Whether to reply and the relevant context must be checked. Automatic delivery of every message is not promised, and test capability is not stable delivery.

Q46支持自动加好友或自动触达吗?Can it automatically add friends or initiate outreach?

当前不将自动加好友和主动触达列为已验收功能。主动任务与日常消息处理独立,须明确对象、时间、权限和执行条件。

These are not listed as accepted capabilities. Proactive tasks are separate from routine message processing and require explicit recipients, time, permissions and execution conditions.

Q47产品以群发营销为主要用途吗?Is mass marketing the main purpose?

产品围绕授权沟通、关系记忆和事务协同设计,不以批量营销为核心。未验收的批量触达能力不作销售承诺。

No. The product is designed around authorized communication, relationship memory and task collaboration. Unvalidated bulk-outreach functions are not sales commitments.

Q48响应速度能保证秒级吗?Is a response guaranteed within seconds?

不能统一保证。识别、上下文长度、模型调用、网络与桌面状态都会影响耗时;状态应显示当前步骤与等待原因。

No. Recognition, context length, model services, networks and desktop state affect latency. The interface should explain the current step and reason for waiting.

Q49可以人工接管吗?Can I take over manually?

本体优先,支持暂停并由本人处理。恢复前应重新核对上下文,避免重复回复;跨设备远程接管仍属于手机互联的待开发范围。

The owner comes first. Pause and handle the conversation yourself; context should be checked again before resuming to avoid duplicates. Cross-device takeover remains part of the planned mobile connection.

Q50暂停后会发生什么?What happens when I pause?

暂停后不应继续执行新的输入或发送。未确认的草稿和发送结果需保留核查,不能把恢复运行当作自动补发授权。

New input and sending should stop. Unconfirmed drafts and delivery results must be preserved for review; resuming is not permission to resend blindly.

Q51手机端是什么定位?What is the mobile app's role?

手机是统一指挥入口的标配设计:查看进度、训练分身、接收提醒、暂停和补话,并连接执行端。互联手机 App 和远程控制尚待开发验收;“标配设计”不表示现已交付。

It is designed as the standard command interface for progress, training, alerts, pause and intervention across execution endpoints. The connected mobile app and remote control still require development and acceptance; standard design does not mean already delivered.

Q52会占用我的工作电脑吗?Will it interfere with my work computer?

当前本机桌面执行需要可用的前台窗口进行键鼠操作,后台读取不等于后台发送。独立电脑或未来云电脑执行可分离工作环境;云端联动仍待接通,不能承诺现在已经完全互不干扰。

Current local desktop execution needs the target window in the foreground for keyboard/mouse actions. Background reading is not background sending. A separate computer or future cloud-PC endpoint can separate environments, but cloud coordination is not yet connected.

六、AI、人设与知识库AI, roles and knowledge

Q53模型由谁配置?Who configures the models?

产品方案由平台、贴牌或代理后台管理模型配置,使用者主要选择运行方式和任务。具体模型可用范围按当前服务说明确认。

The product design assigns model configuration to platform, white-label or reseller administration. Users mainly choose runtime and tasks. Actual model availability follows the service description.

Q54企业能接自己的模型服务吗?Can an enterprise connect its own model service?

作为定制集成需求评估接口、网络、数据与运维条件,不把所有客户均可自行填写 API 的开发能力当作当前标准版承诺。

Evaluate this as a custom integration, including interfaces, networks, data and maintenance. Developer capability does not imply that every standard user can configure arbitrary APIs.

Q55算力充值怎么用?How is usage credit applied?

在商城充值后按实际用量抵扣,余额与消耗明细可查。

Where offered, usage credit is deducted according to the active service's actual metering rules. Check the applicable balance and usage records.

Q56能设置不同角色与语气吗?Can different roles and tones be configured?

可以按不同关系和任务创建分身,配置角色、语气与资料。创建多个角色不等于能同时控制多个消息账号;执行能力按 Q44 确认。

Create counterparts for different relationships and tasks with their own roles, tone and materials. Multiple roles do not imply simultaneous control of multiple messaging accounts; see Q44.

Q57知识库有什么作用?What is the knowledge base for?

可整理工作资料、产品说明、流程与常见问题,为理解、拟稿和任务处理提供依据。私人资料与团队共享资料应明确授权范围。

It organizes work materials, product information, procedures and FAQs for understanding, drafting and tasks. Private and team-shared materials need explicit access boundaries.

Q58知识库支持什么文件?Which file formats are accepted?

常见文档与文本格式均可,具体格式清单见《知识库使用指南》。

Use the current Knowledge base guide for the supported document and text format list.

Q59能发送资料文件吗?Can it send files?

资料检索、生成文字与真实发送附件是不同能力。文件类型、发送渠道及完成核验需按版本确认,未接通的附件发送不作承诺。

Finding material, drafting text and actually sending attachments are separate capabilities. Confirm file types, channel support and delivery verification for the version; unconnected attachment sending is not promised.

Q60为什么回答可能不准确?Why can answers be wrong?

模型会出错,过期资料、上下文缺失和识别偏差也可能影响结果。更新资料并核对关键事实;报价、承诺等重要内容保留人工确认。

Models can make mistakes. Outdated materials, missing context and recognition errors also affect results. Update sources and check important facts; keep human review for quotations and commitments.

Q61如何处理来源说明?How should source references be presented?

可调整表达,使答复自然清楚;需要追溯依据或明确不确定性的内容应保留,不能靠删掉“参考文档”等字样掩盖事实问题。

Adjust wording for clarity while preserving sources and uncertainty when they matter. Removing reference language must not hide a factual problem.

Q62怎样判断任务是否完成?How do I know a task is complete?

分开核对“已理解、已拟稿、已输入、已发送、已确认结果”。真实发送还要检查对象和新消息,不把生成文字或显示运行中当成成功。

Distinguish understood, drafted, entered, sent and result verified. Real sending requires checking the recipient and the new message; generated text or a running indicator is not success.

七、关系记忆与个性化Relationship memory and personalization

Q63会记住以前的往来吗?Does it remember earlier interactions?

在授权与保存范围内使用历史记录和记忆帮助理解;完整聊天记录导入、人格蒸馏和长期学习能力仍需按版本确认。

It uses authorized records and memory within the saved scope. Full chat import, personality distillation and long-term learning require version-specific confirmation.

Q64关系画像是什么?What is a relationship profile?

整理与对方相关的偏好、约定和协作信息,适用于多种关系。自动形成的判断可能有误,应允许查看与纠正。

It organizes preferences, agreements and collaboration information about the other person across many kinds of relationships. Generated judgments may be wrong and should be reviewable and correctable.

Q65记忆存在哪里?Where is memory stored?

依运行方式和服务架构确定。本机、云电脑、私有部署的数据存放位置不同;本机保存记录也不等于模型调用完全不出网。

It depends on runtime and service architecture. Local PCs, cloud PCs and private deployments have different storage locations. Local records do not imply all model processing stays offline.

Q66多轮对话能理解上下文吗?Can it understand multi-turn context?

可结合已读取的上下文与授权记忆辅助理解;漏读、窗口变化或识别错误时需重读或交由人工处理。

It can use retrieved context and authorized memory. Missing messages, window changes or recognition errors require another reading or human review.

Q67能跟进约定吗?Can it follow up on commitments?

任务跟进是产品方向。主动智能按明确日期和时间单独建立、单独启用,不应随日常回复自动开始;任务排队、提醒与执行回执仍按版本验收。

Task follow-up is a product direction. Proactive tasks are created and enabled separately at a specific date and time, rather than automatically starting with replies. Queueing, reminders and execution receipts require version-specific acceptance.

Q68能删掉记忆吗?Can memory be deleted?

按当前提供的删除范围操作。删除单条记忆不等于同步删除会话、文件、日志和备份,具体范围与保留期需说明。

Use the deletion scope actually provided. Deleting one memory does not automatically remove conversations, files, logs or backups; retention and deletion scope must be explained.

Q69不同人的资料会混用吗?Can different people's materials be mixed?

设计要求按账号、角色和共享权限隔离;跨团队共享须明确授权。不能承诺任何环境都绝无泄露风险。

The design requires isolation by account, role and sharing permission, with explicit authorization for team sharing. Absolute protection against every leak cannot be promised.

Q70记录会保存多久?How long are records retained?

以当前存储配置、保留策略和可用容量为准,重要资料按方案备份,不承诺无限期保存。

Retention depends on storage settings, policy and capacity. Back up important materials according to the solution; indefinite retention is not promised.

八、多语言Languages

Q71支持哪些语言?Which languages are supported?

可按所接模型和实际场景测试多语言理解与拟稿,不承诺所有语言均有同等质量。

Test understanding and drafting with the connected model in the actual scenario. Equal quality in every language is not guaranteed.

Q72怎么决定用哪种语言回复?How is the reply language chosen?

对方发来什么语言,我们就用什么语言回复(We reply in the language you use)。

The intended behavior is to follow the other person's language, subject to the connected model and actual scenario.

Q73可以协助英文沟通吗?Can it assist with English communication?

可以按模型能力测试英文理解与拟稿;重要术语、交易条款与承诺需人工核对。

Test English understanding and drafting using the model's actual capabilities. Check important terminology, transaction terms and commitments manually.

Q74中英混合呢?What about mixed Chinese and English?

以对方消息的主导语言为准,自然衔接。

Use the conversation's main language and context, with human review where ambiguity matters.

Q75需要手动切换语言吗?Do I need to switch languages manually?

不需要,分身按对方语言自动对齐。

The intended behavior is automatic language matching, within the connected model's capabilities and validated workflow.

Q76表达一定自然准确吗?Is expression always natural and accurate?

不能保证。可用角色设定和资料改善表达,专业术语、语境及事实仍需核查。

No. Roles and materials can improve expression, but terminology, context and facts still need checking.

九、安全、隐私与账号风险Safety, privacy and account risks

Q77使用微信等平台会不会有账号风险?Are there account risks on WeChat or other platforms?

存在风险,不能承诺零封号。使用范围受平台规则、接口权限和实际行为约束;本产品的命名、硬件或云电脑运行方式都不自动消除这些风险。

Yes. Zero suspension risk cannot be promised. Use is governed by platform rules, interface permissions and actual behavior. Product naming, hardware and cloud-PC operation do not automatically remove these risks.

Q78视觉或键鼠操作能代表平台认可吗?Do visual or keyboard/mouse operations imply platform approval?

不能。桌面截图识别、键鼠模拟或硬件执行仅描述技术路径,不构成腾讯或其他平台的官方授权与合作证明。

No. Screen recognition, simulated input and hardware execution describe technical methods, not official authorization or partnership with Tencent or any other platform.

Q79数据会存放在哪里?Where will data be stored?

按具体方案列明会话、知识、记忆、截图、日志和备份的存储位置、权限及保留期。云电脑运行与模型服务所在位置应分别说明。

The solution should identify storage locations, access and retention for conversations, knowledge, memory, screenshots, logs and backups. Cloud-PC location and model-service location must be explained separately.

Q80内容可能发送到云端吗?Can content be sent to the cloud?

可能。使用云端识别或模型推理时,相关截图、消息或上下文可能提交给所配置服务。私有部署也需要核对模型、诊断与网络出口,不能只因服务器在内网就宣称数据绝不出网。

Yes. Cloud recognition or model inference may receive relevant screenshots, messages or context. Private deployment must also check models, diagnostics and network egress; an internal server alone does not prove data never leaves the network.

Q81服务方能接触哪些数据?What data can service providers access?

取决于托管、模型服务、运维及日志方案,应明确说明访问范围和权限。不再笼统声称“我们绝不持有任何聊天数据”。

This depends on hosting, model services, operations and logging. The solution must define access and permissions rather than claiming no provider ever holds chat data.

Q82使用前应确认什么?What should be confirmed before use?

确认应用和账号使用权限、资料范围、允许执行的动作、人工确认条件及第三方服务的数据处理方式。遇登录验证或异常状态应暂停交由本人处理。

Confirm application and account permissions, data scope, permitted actions, human-review conditions and third-party processing. Login challenges or abnormal states should pause for the owner's intervention.

Q83能"疯狂群发"吗?Can it send messages without limit?

不支持、不建议。高频批量群发既伤账号也不符合产品设计初衷。

Unrestrained high-frequency mass sending is not a supported product promise and can create platform and relationship risks.

Q84有零封号或绝对安全承诺吗?Is there a zero-suspension or absolute-safety guarantee?

没有。平台权限、数据边界和执行核验需各自确认,任何部署方式都不能提供这类绝对保证。

No. Platform permissions, data boundaries and execution verification each require confirmation. No deployment method supplies an absolute guarantee.

Q85如何限定分身的行动范围?How are action boundaries set?

先限定对象、资料、任务和可执行动作。涉及资金、门锁、安防等重要操作应设置独立确认,不将一条对话中的提议自动当成执行授权。

Limit recipients, materials, tasks and permitted actions first. Money, locks and security-sensitive actions require separate confirmation; a suggestion in conversation is not automatic execution authorization.

Q86出问题了找谁?Where do I get help?

官网"联系我们"或商城客服入口,支持远程指导。

Use the official Contact page or the store support entry for the current service process.

十、企业协同与开发者Enterprise collaboration and developers

Q87可以对接 API 吗?Can APIs be connected?

按已公开且具备调用权限的接口评估对接。开发者页面或演示不代表所有外部系统已连接,实际范围需项目验收。

Evaluate documented interfaces for which the necessary permissions exist. A developer page or demonstration does not establish completed external integrations; the delivered scope requires acceptance.

Q88可以接入 CRM 等业务系统吗?Can CRM and business systems be connected?

属于逐步集成方向。先确认业务流程、数据权限和接口,再按项目开发验收,不能概括为当前全部即用。

These are progressive integration directions. Confirm workflows, data permissions and interfaces, then develop and validate the project rather than claiming universal immediate availability.

Q89可以连接哪些现实设备?Which physical devices can be connected?

电话、摄像头、打印机、车辆及报警设备等是规划中的连接方向,需逐项适配、授权和验收。家庭设备协同尚未完成,不承诺已经支持远程控制。

Phones, cameras, printers, vehicles and alarms are planned directions requiring individual adaptation, authorization and acceptance. Household-device coordination is not complete and remote control is not promised as available.

Q90团队看板能查看成员所有聊天吗?Can the team dashboard view all employee chats?

不能按“所有聊天”宣传。企业共享大脑与团队看板围绕明确授权的业务会话、资料和任务建设,私人会话隔离;完整共享、交接与运营汇总仍属于待办范围。

No. The shared enterprise brain and dashboard concern explicitly authorized business conversations, materials and tasks, with private conversations isolated. Full sharing, handover and operational reporting remain development items.

Q91有跳单、飞单风险预警吗?Are lost-order or off-platform-dealing alerts available?

如实说明:尚未上线。处于需求验证阶段,有进展会公开更新。

No. They have not launched and remain under requirements validation. They must not be described as implemented.

Q92支持私有部署吗?Is private deployment supported?

属于运行方式方案,尚需接通客户环境并完成验收。服务、模型、存储和执行端的部署范围分别确认,不默认所有数据与推理都在企业内网。

It is a runtime solution requiring connection to the customer's environment and acceptance. Confirm services, models, storage and execution separately; not all processing is automatically within the private network.

Q93企业采购怎么走?How does enterprise purchasing work?

联系销售确认数量、授权与交付方式,可签署合同、开具发票。

Contact sales to confirm quantity, authorization, delivery scope and contractual terms, including invoicing.

Q94有发票吗?Are invoices available?

支持。下单时在商城申请或联系客服开具。

Confirm the current store or support process when placing the order.

十一、售后与合作Support and partnerships

Q95客服在哪?Where is support?

官网"联系我们"页(www.qc-vc.com/contact.html)或商城客服入口。

Use the official Contact page or the store support entry.

Q96服务响应有固定时限吗?Is there a fixed support-response deadline?

按当前售后服务约定确认,不沿用未经核实的“72 小时完成兼容测试”等承诺。

Confirm the active support terms. Do not reuse unverified promises such as completing compatibility tests within 72 hours.

Q97有代理或 OEM 合作吗?Are reseller or OEM partnerships available?

支持代理与 OEM 合作,详见《代理与合伙招募》。

Discuss the scope and terms with sales and consult the current partnership information.

Q98有培训吗?Is training available?

图文与视频教程公开免费;企业客户可安排远程指导(见《远程指导操作》)。

Public written and video tutorials are available. Confirm any enterprise remote-guidance arrangement with the service team.

Q99多久更新一次?How are updates announced?

持续迭代,版本更新通过官网与商城发布;已购客户按政策获取更新。

The product is continuously iterated. Follow official website and store notices, with eligibility governed by the applicable purchase terms.

Q100公司是哪家?Which company provides the product?

。官网 www.qc-vc.com,商城 shop.qc-vc.cn。

. Use the official website and shop.qc-vc.cn for current company and product information.

十二、产品定位与部署模式Positioning and runtime options

Q101你们是专门回复微信的 AI 客服系统吗?Is this a dedicated WeChat customer-service system?

消息助手的产品定位是“人格大脑与行动中枢”:懂本体、记住往来,在授权范围内协助统筹关系与事务。客户咨询回复是场景之一,微信是当前验证中的入口之一;企业协同、个人事务与家庭协同构成更广的产品方向,尚未接通的部分按规划说明。

is positioned as a personality-aware brain and action hub: understanding its owner and authorized relationships while assisting with communication and tasks. Customer inquiries are one scenario; WeChat is one entry point under validation. Enterprise, personal and household collaboration are broader directions, with unconnected capabilities clearly identified as planned.

Q102人格大脑如何体现本体的特点?How does it reflect its owner's personality?

通过与你对话、角色设定和授权资料,逐步整理你的表达方式、知识与做事习惯。聊天记录蒸馏仍在完善,不承诺已经能完整复制个人判断。

Conversation, role settings and authorized materials progressively organize your communication style, knowledge and working habits. Chat-history distillation is still being refined; complete replication of personal judgment is not promised.

Q103消息之后能衔接什么?What can follow a message?

可衔接资料查询、待办整理、人工处理与后续任务;进一步连接团队、业务系统和设备是发展方向。应逐项说明“已接通、测试中、待开发”。

Reference lookup, task organization, human handling and follow-up work. Connections to teams, business systems and devices are further directions. Each capability should be identified as connected, in testing or planned.

Q104目前进展到哪一步?What is the current development stage?

目前优先把电脑端真实消息链路稳定跑通,界面和执行核验仍在迭代。手机互联、云电脑联动、私有部署、其他平台收发、企业共享大脑、家庭分身、会议与语音完整链路以及真实设备调度仍需后续开发验收。

The immediate priority is a stable real desktop message workflow, with interfaces and execution verification still being refined. Mobile connection, cloud-PC coordination, private deployment, other platforms, the shared enterprise brain, household counterparts, full meeting/voice workflows and real device dispatch require further development and acceptance.

Q105客户如何选择运行方式?How do I choose a runtime?

先选本机运行、云电脑运行或私有部署,再选择需要接入的消息平台、业务系统和可选硬件。手机作为统一指挥入口的标配设计;未接通的方式应明确提示,不允许静默替换。

Choose local-PC operation, cloud-PC operation or private deployment, then select messaging platforms, business systems and optional hardware. Mobile is the planned standard command interface. Unconnected modes must be identified rather than silently replaced.

Q106本机运行适合谁?Who is local-PC operation for?

适合先验证场景、方便本人参与的使用者。当前桌面执行会占用目标窗口的键鼠操作,需要可用桌面和人工避让;硬件按所选方案配置。

People validating a scenario who can participate manually. Current desktop execution uses the target window for keyboard/mouse actions and requires a usable desktop and human coordination. Hardware depends on the solution.

Q107云电脑与私有部署有什么不同?How do cloud-PC and private deployment differ?

云电脑方案将执行放在独立云 Windows 环境;私有部署方案在客户指定服务器、内网及执行设备中落地。两者都需接通、授权和验收,可选硬件并非独立版本。云资源、模型、实施和运维分别报价,不预设固定价格高低或已实现多席位。

Cloud-PC execution runs in a separate cloud Windows environment. Private deployment uses customer-designated servers, networks and execution devices. Both require connection, authorization and acceptance. Hardware is optional rather than a separate edition. Resources, models, implementation and maintenance are priced separately; fixed cost rankings and working multi-seat operation are not assumed.

Q108我该怎么选?Which option should I choose?

轻度使用、方便人工参与,可先评估本机运行;本机工作繁忙,希望隔离执行环境,可评估独立电脑或云电脑方案;有内部系统及数据管理要求,可评估私有部署。先用当前可交付能力验证,再约定未上线模块的开发与验收范围。

For light use with manual participation, evaluate local-PC operation. To separate execution from a busy workstation, evaluate a separate computer or cloud-PC solution. For internal systems and data-management requirements, evaluate private deployment. Validate current deliverables first and agree separately on development and acceptance for unreleased modules.