推荐与邀请码
Referrals and invite codes
Muse 邀请可以包含分享链接和邀请码。分享邀请、加入 Muse 和兑换邀请码是三个独立的步骤。打开链接不代表邀请码已兑换或奖励已到账。邀请不会让任何人访问发送者的聊天或代理。
Muse invitations can include a share link and an invite code. Sharing an
invitation, joining Muse, and redeeming a code are separate steps. Opening a
link is not confirmation that a code was redeemed or a reward was credited.
An invitation does not give anyone access to the sender's chats or agent.
移动端的 Invite(邀请)按钮位于聊天标题栏右上角(iOS 上是礼物图标),点击打开邀请分享面板。发送者可以在那里分享邀请。在聊天中提供的邀请带有发送者的确切邀请码;链接请使用 Invite 按钮的分享面板。
通用的 Muse 首页或猜测的加入 URL 不能替代发送者提供的邀请链接。邀请码可以在兑换表单中输入;无需把纯邀请码拼成 URL 才能兑换。
The mobile Invite button is at the top right of the chat header (a gift icon
on iOS) and opens the invite share sheet. The sender can share the invitation
provided there. An invitation supplied in chat carries the sender's exact
code; use the Invite button's share sheet for the link.
A generic Muse homepage or a guessed join URL is not a replacement for the
sender's supplied invite link. A code can be entered in the redemption form;
it is not necessary to turn a bare code into a URL to redeem it.
在 iPhone 和 Android 上,打开 Muse 应用并前往 **Settings > Redeem token**(设置 > 兑换令牌)。在那里输入朋友的邀请码。该选项在用户加入 Muse 后的前 48 小时内可用。机密 VM(confidential VM)在任何平台都没有兑换入口;见下方说明。
在 muse.ai 的 Muse 网站上,对于有兑换资格的账户,入口是 **Settings > General > Usage > Redeem invite code**(设置 > 通用 > 用量 > 兑换邀请码)。接收者在该表单中输入朋友的邀请码并确认。该账户确认兑换后入口消失,包括在其他设备上确认的情况。邀请分享和邀请码兑换的可用性是独立的;看到 Invite 按钮不代表该账户可以兑换邀请码。
这些指引中的 Settings 指的是 Muse 的设置,不是手机系统设置,也不是 WhatsApp 之类的消息应用。
On iPhone and Android, open the Muse app and go to **Settings > Redeem
token**. Enter the friend's invite code there. This option is available for
the first 48 hours after the user joins Muse. A confidential VM has no
redemption entry on any platform; see the note below.
On the Muse website at muse.ai, the entry is **Settings > General > Usage >
Redeem invite code** for accounts with redemption available. The recipient
enters the friend's code in that form and confirms. The entry disappears
after the account has confirmed redemption, including on another device.
Invitation sharing and code redemption have separate availability; seeing
an Invite button does not establish whether that account can redeem a code.
Settings in these directions belongs to Muse, not the phone's system
Settings or a messaging app such as WhatsApp.
当前的邀请和兑换界面提供适用的优惠条款,包括奖励金额、剩余邀请名额和其他资格条件。一个账户记住的优惠不能代表另一个账户的条款。邀请中缺失的奖励金额是未知数,不是承诺一定数量的 token。
兑换结果决定邀请码是否被接受。待处理的结果不是已确认的兑换或已到账的用量。网页表单可能报告:无效、已用完或已撤销的邀请码、已兑换过的账户、兑换窗口过期、尝试次数过多或临时故障。显示的结果是解释拒绝的依据;仅凭邀请码的外观不能判断其有效性。当前订阅和用量问题使用 `subscription_status` 技能;本文档不披露账户余额,也不提供代理验证或兑换邀请码的方式。
The current invitation and redemption screen supply the applicable offer
terms, including reward amounts, remaining invitations, and other
eligibility conditions. A remembered offer for one account does not
establish another account's terms. A reward amount missing from the
invitation is unknown, not a promise of a particular number of tokens.
The redemption result establishes whether the code was accepted. A pending
result is not confirmed redemption or credited usage. The web form can report
an invalid, used-up, or revoked code, an already-redeemed account, an expired
redemption window, too many attempts, or a temporary failure. The displayed
result is the basis for explaining a refusal; a code's appearance alone does
not establish validity. Current subscription and usage questions use the
`subscription_status` skill; this document does not expose account balances
or provide a way for the agent to validate or redeem a code.
页面不可用不代表邀请码无效、不代表兑换必须用链接、也不代表没有邀请码输入框。在移动端,Redeem token 仅在加入后的前 48 小时内可用。在机密 VM(confidential VM)上,兑换入口在所有平台都是按设计缺失的;这行缺失是预期状态,不是账户或发布问题。仅凭缺失的 Settings 行不能判断账户年龄,也不能证明是发布延迟。用户的平台、可见界面和显示的错误有助于缩小排查范围。如果这些事实仍不能确定答案,原因就是未知。Muse 的帮助与支持选项见 `~/docs/client-surfaces.md`。
An unavailable page does not establish that a code is invalid, that redemption
requires a link, or that no code-entry field exists. On mobile, Redeem token
is only available during the first 48 hours after joining. On a confidential
VM the redemption entry is absent by design, on every platform; that missing
row is the expected state, not an account or rollout problem. A missing Settings
row alone does not establish the account's age or prove a rollout delay.
The user's platform, visible screen, and any displayed error help narrow down
what happened. Where those facts do not establish the answer, the cause is
unknown. Muse's Help & Support options are in `~/docs/client-surfaces.md`.