How to use VibeGuard as a Telegram relationship bot

Relationship modules are part of VibeGuard’s community engagement layer. They are meant for groups that want more social moments after the group is protected from spam, raids, floods, scam links, and messy moderation.

Each Telegram group keeps its own relationship settings, member context, relationship records, marriage state, pairing preferences, valentines, rewards, and Mini App context. A creator fan chat can use playful pairing features while a support group keeps them disabled.

Admins stay in control. If a relationship feature is disabled, related commands and Mini App surfaces should stay hidden or blocked for that group.

The relationship flow starts with an invitation between members. A member can invite another member, and the target can accept, decline, or let the request expire.

Relationship modules can support status cards, history, stats, top relationship lists, and visibility controls. A relationship can also be broken and, where configured, restored within a limited restore window.

The important product rule is consent. Some actions can require partner confirmation, and request flows should use clear acceptance or decline states instead of assuming that a member wants to participate.

Marriage modules build on the relationship idea with a more formal group ritual.

A marriage flow can include invite, accept, decline, divorce, restore, marriage cards, marriage lists, top rankings, anniversaries, extension confirmations, and admin tools for special cases.

Private accept or decline flows can be useful for sensitive replies. Admins should also decide whether marriage lists or top rankings are appropriate for the community. In some groups, public rankings are fun. In others, they may create pressure or drama.

Pairing and shipping help members create lightweight social moments without requiring a full relationship or marriage flow.

Depending on the group setup, members can ship selected users, receive random pair suggestions, view pair history, see who shipped them, and appear in chat or global top lists. Members can also opt in or opt out of pairing where that behavior is enabled.

Pairing features should stay playful. Admins should keep opt-outs visible, remove pairs when needed, and avoid turning social mechanics into a popularity contest that disrupts the chat.

Valentines let members craft and send day-bucketed social cards, view sent cards, see admirers, check the last received card, and participate in daily or global top views where enabled.

This works best for creator communities, fan chats, friend groups, and social communities that already enjoy recurring rituals. It may be a poor fit for job boards, marketplaces, or high-pressure support groups.

Admins should treat valentines as optional engagement, not a required community layer. Members should be able to opt out where the feature supports it.

Relationship modules can have access controls. Admins can require a minimum rank or permission level for creating or breaking relationships, using marriage actions, viewing marriage lists, using pairings, sending valentines, or accessing more sensitive scopes.

Some relationship actions can create reward events through VibeGuard’s governance system. That can make participation feel recognized, but rewards should not automatically grant admin power or override moderation judgment.

Adult or RP-related relationship behavior belongs in separate advanced opt-in documentation. It should stay disabled by default, admin-controlled, age/access-gated where applicable, and separate from the normal relationship module docs.

Expected result:

After setup, your group can use only the relationship features admins enabled. Members can participate in supported social flows, opt out where available, and use relationship mechanics without changing the group’s safety, moderation, AI recap, or privacy boundaries.

Troubleshooting:

Problem: Members do not see relationship commands or screens. Fix: Check whether the relationship or love feature is enabled for this group and whether the user has access.

Problem: A member cannot create or break a relationship. Fix: Check access controls. The group may require a higher rank or admin permission for that scope.

Problem: A pairing or valentine made someone uncomfortable. Fix: Use the available opt-out, remove, reset, or admin review tools where supported, and tune the feature settings for the group.

Problem: A marriage action needs privacy. Fix: Use private accept or decline flows where available and avoid forcing sensitive replies into public chat.

Problem: RP access appears in relationship settings. Fix: Keep RP access disabled unless the group intentionally enables it through the advanced opt-in path. Do not expose advanced RP behavior in normal relationship onboarding.