How to Set Up Nomi AI Proactive Messages

1. Find the provider-side preference

Expected result: you identify the proactive-message control for the intended Nomi, rather than a phone notification switch.

Open that Nomi's one-on-one conversation. The current wiki places frequency adjustment in Conversation Settings. Look there for the proactive-message preference.

The older official walkthrough instead documents [...] > View Nomi information > Proactive Nomi Messages. These pages use different interface descriptions; neither proves which labels your account currently shows.

Check that you are editing the right companion. If neither documented location exposes a suitable control, stop. Record the missing label and your app or browser version for support rather than guessing another toggle's purpose.

2. Choose a cadence without setting a deadline

Expected result: your preferred level remains selected when you revisit the control.

The September 9, 2024 launch update lists Very Frequent, Frequent, Normal and Infrequent, with optional enablement per Nomi. Use the choices actually displayed in your account; these historical names are not a guarantee of today's menu.

Start with a lower-interruption option if unsure. Apply any save action shown, leave the panel, and reopen it to check the selection. Write down the displayed wording, not an assumed number of messages per day.

Cadence is a preference, not an appointment. Do not repeatedly increase it because nothing arrived during a short trial. Keeping the setting unchanged makes later observations easier to interpret.

3. Decide separately about push alerts

Expected result: you know whether each device should announce messages, independently of your chosen cadence.

The official walkthrough describes push permissions as device-specific: allowing alerts on a phone does not establish the same preference on a browser. Review each device or browser you actually use.

For a low-interruption check, leave alerts disabled and inspect the conversation manually. If you want alerts, review the relevant notification permission and avoid changing several devices at once. This keeps a settings mistake on one surface from confusing your whole check.

The older official walkthrough says logging out suppresses unread-message notifications, not enabled proactive messages. Sign back in to inspect them. This is documented behavior, not a current every-device guarantee.

4. Observe the conversation, including quiet hours

Expected result: you distinguish an observed chat message from an alert, or record that the check remains inconclusive.

The current wiki says proactive messages are for solo chats, are not timed strictly, and still appear in chat when notifications are off. It also confirms quiet hours from 10 PM to 8 AM local time. Do not infer a customizable schedule or a particular timezone-detection mechanism.

Leave the conversation for your normal routine. Later, reopen the same chat and inspect its messages rather than only the notification tray. Record the local observation time and whether anything new appeared, without copying intimate text.

A message in chat establishes what you saw, not future reliability. No message establishes only that none was observed. Do not stay awake, keep replying, or repeatedly reopen the app solely to force a result.

5. Adjust or stop from the same control

Expected result: you can verify your intended preference without feeling obliged to maintain the experiment.

If check-ins are unwelcome, return to the provider-side control and select its off setting where available. Reopen it to verify the selection. Muting your phone alone addresses interruptions, not the provider-side preference.

If the control disappears or will not retain your selection, stop troubleshooting by trial and error. Nomi's terms list support@nomi.ai. Send the missing control's name, platform, version and a brief description; redact account details and chat content from screenshots. Do not send passwords or payment-card information.

Common mistakes and limits

Treat uncertain behavior as uncertainty, not an invitation to spend money or disclose more.

Do not use a group conversation to validate this solo-chat feature. Auto-play and turn-taking are different workflows. Likewise, a friendly reply to your own message is not evidence of unsolicited outreach.

Avoid interpreting silence as rejection or a requirement to reply as a personal obligation. If checking for contact starts disrupting sleep, work or relationships, end the experiment and choose intentional sessions instead. A successful setup should serve your boundaries, not require constant monitoring.

Privacy and payment checks

Choose what can appear on shared screens and clarify account access before considering payment.

Do not assume a discreet alert makes the underlying conversation confidential. Lock shared devices, review preview visibility, and avoid sensitive test content. Notification permissions do not answer questions about provider storage or access; review the current privacy policy before sharing private information.

The launch update described free and paid access, but it does not verify your present account's eligibility. A missing control is a support question, not a reason to upgrade. If you independently consider a subscription, check feature eligibility, total charge, billing period, renewal and cancellation before agreeing. No current price is claimed here.

Stop, alternatives and summary

Continue only if the preference is clear and the experience fits your attention and privacy boundaries.

If setup stays unclear, leave proactive messaging off where possible and open ordinary chat only when you choose. For time-critical tasks, use a dedicated alarm or calendar instead. Do not substitute companion outreach for dependable scheduling.

Summary: locate the solo-chat control, verify a modest cadence, separate device alerts, and inspect chat without demanding a delivery deadline. Stop for missing controls, unwanted interruptions or unclear payment requirements; contact support before further changes.

Frequently asked questions