How to use VibeGuard as a Telegram horoscope bot

Horoscope is part of VibeGuard’s community engagement layer. It is meant to give members a simple daily ritual after the group is already protected, moderated, and easy to follow.

Like other VibeGuard features, horoscope behavior is scoped to the Telegram group. Each group keeps its own enabled features, member context, Mini App context, recaps, AI usage, music settings, relationship settings, and engagement preferences.

Admins should treat horoscope as social content, not advice. It is there to create a recurring community moment, not to replace moderation, support, or serious decision-making.

The main command is simple: use horoscope followed by a zodiac sign.

Members can also use direct zodiac sign names where supported. VibeGuard can recognize English sign aliases, Russian sign aliases where localized, and zodiac symbol aliases. All 12 zodiac signs are supported.

Examples:

• horoscope aries
• horoscope leo
• horoscope scorpio
• horoscope ♓

The exact aliases available may depend on localization and group settings. On the English docs page, keep English examples primary. Russian aliases should live mostly in the Russian docs page.

When a member asks for a horoscope, VibeGuard parses the command and sign, determines the current service day, checks whether that sign has already been cached for the day, and returns the daily result.

If the result is not cached yet, VibeGuard fetches the raw horoscope from the configured source, parses the response, optionally applies AI styling when enabled, caches the final result, and sends it back in Telegram.

Caching matters. It keeps the experience fast for repeat requests, reduces unnecessary source calls, and helps control AI usage when styling is enabled.

Horoscope can optionally style the daily text through VibeGuard’s AI layer. That can make the response feel more natural for the community, while still keeping the feature lightweight.

AI styling is not required for horoscope to work. If AI styling is unavailable, VibeGuard should fall back to the raw source text instead of failing the user. If the source itself is unavailable, the bot should return a friendly error and avoid confusing silence.

AI usage remains controlled through backend settings and quotas. Each group member can use up to 10 AI help/prompts for free, but horoscope styling and interactive AI prompts should be treated as separate product surfaces where the implementation controls them.

Admins should keep horoscope enabled only where it fits the group culture. A creator fan chat may enjoy daily zodiac posts. A serious marketplace or support group may prefer to keep engagement features quieter.

The horoscope service can use a configured source URL template, a horoscope AI model alias, a service timezone, cache settings, and Telegram delivery mode. These are operational settings, not things regular members should edit from chat.

Responses should stay localized for the group where localization is available. On English pages and English groups, use English examples. On Russian pages and Russian groups, use natural Russian command and sign examples.

Expected result: members can request a daily horoscope by sign, VibeGuard returns the cached result when available, AI styling improves the text only when enabled and available, and the bot gives a friendly fallback when something goes wrong.

Troubleshooting:

Problem: The bot does not recognize a sign. Fix: Try the full English sign name, a common alias, or a zodiac symbol. Check whether the group’s language/localization supports the alias being used.

Problem: The same result appears more than once. Fix: That is expected for the same sign and service day. VibeGuard caches daily output.

Problem: The response looks plain instead of styled. Fix: AI styling may be disabled or temporarily unavailable. The bot should still return raw horoscope text when possible.

Problem: Horoscope is not responding in this group. Fix: Check whether horoscope is enabled for the group and whether VibeGuard is still active in the chat.

Problem: The daily timing feels off. Fix: Check the service timezone or group expectation for “today.” Horoscope content is tied to a service day.