Guide

1. 1

   Add the bot to your server

   Use the Add to Discord button and approve the permissions. Vyach needs to join voice channels and post in the channel where summaries will appear.

2. 2

   Run /settings setup

   Vyach finds or creates the forum where summaries are published. You can point it at an existing channel any time with /settings channels.

3. 3

   Start a meeting with /meeting start

   Join a voice channel first, then run the command. Vyach joins, plays a short sound and asks each participant for recording consent. Title, tag and template are optional.

4. 4

   Finish with /meeting end

   Vyach stops recording, transcribes the speech, writes the summary and posts it to your forum or channel. Longer meetings take a little longer to process.

• When a meeting starts or someone joins and has not made a choice on this server yet, they get a private message asking whether they agree to be recorded. The message links to the voice channel Vyach joined.
• After any choice, agree or decline, Vyach sends a short private confirmation that the choice is saved and how to change it with /privacy consent.
• The answer is saved per server and applies to future meetings too, so nobody is asked again every time.
• Until someone agrees, their audio is not recorded. Declining does not mute or disconnect them, they can keep talking.
• The person who started the meeting is told privately who is not being recorded, because missing voices can hurt the quality of the summary. Someone who declines or cannot receive messages is reported right away. For someone who has not answered, it happens 5 minutes after they were asked by default, and you can change that with /settings recording.
• A sound plays in the voice channel when recording starts and ends.

• /privacy consentCheck your current choice on this server.
• /privacy consent record:trueAllow recording your voice.
• /privacy consent record:falseStop being recorded from now on.

A summary covers what was discussed, decisions that were actually made, action items, blockers, open questions and next steps. Each point can point back to who said it and when.

• Language. Summaries use the bot language of your server by default. Override it for a single meeting with the summary_language option of /meeting start.
• Templates. General is built in and shapes a balanced report. Community and Pro servers can create their own templates with /template create and pick one with the template option of /meeting start. General itself cannot be overridden.
• Personality. Community and Pro servers can set a writing style for summaries, answers and catch-up messages with /settings personality.
• On Free, custom settings are inactive, kept for 30 days to restore the subscription, then removed.
• AI can make mistakes. Check important details in summaries, answers, catch-ups and tasks; generated messages include a reminder.

• Usage limit reached. The recording ends and the summary is posted as it is, with a note at the end saying the recording was interrupted because the usage limit ran out.
• Listening was lost. If Vyach is deafened for more than 10 minutes, or loses its voice connection for more than 30 seconds, the recording ends, the summary is still created and ends with a note that something may be missing.
• Vyach was removed from the call. If it is kicked or moved out of the voice channel, the summary is still created and the note at the end gives that reason.
• Vyach was restarted. If the bot is shut down during a call, the part already recorded is summarized and the note at the end says so.
• Everyone left. After 10 minutes with nobody in the voice channel, Vyach ends the recording and publishes the summary as usual.

Whatever the reason, a summary of an interrupted call ends with a short note explaining why the recording stopped.

Add a tag when you start a meeting, for example backend or design. Meetings with the same tag form one history with their own numbering, and summaries in a forum are labeled with it. Meetings without a tag go to general.

Questions are answered from a single tag at a time. A tag never leaks into another one.

For example: @Vyach #backend what did we decide about the release?

• Add #tag when your server has several histories. If you leave it out and it is ambiguous, Vyach asks which one you mean.
• Reply to one of the bot's answers to ask a follow-up, for example about a specific meeting.
• Use first person freely. “What do I need to do?” is resolved to you.
• Answers cite the meetings they came from. If the records do not contain the answer, Vyach says so instead of guessing.
• Your plan sets the monthly question allowance. Vyach answers questions about meeting data that is still retained.
• Each person can ask one question every 30 seconds. Requests blocked by this cooldown do not consume the monthly allowance.
• Everyone can ask by default. Once asking is granted to specific users or roles with /settings access-grant, only they and server managers can, and everyone else gets a short refusal that costs no allowance.

If a person joins after the meeting has started and something important happened before they arrived, they receive a short private message with the key points. Small talk and filler never trigger a message.

• /settings catchup enabled:falseTurn catch-up messages off.
• /settings catchup grace_seconds:120Only send a catch-up if the person missed at least this long (30 to 3600 seconds).

When a summary contains action items, Vyach can create one post per item in a tasks forum. The owner, deadline and priority are included, and the owner is mentioned when they can be matched to a participant.

/settings setup does not create a tasks forum. Create one yourself and choose it with /settings channels, then switch automatic creation on or off with /settings tasks.

• The server owner always has full control: server settings, data export and deletion, retention and delegating access. Paying for a subscription grants billing access only; independent administrator and delegated permissions still apply.
• Members with the Manage Server permission can manage settings and templates.
• Only the server owner can delegate manage, meetings and questions to users or roles with /settings access-grant, and revoke them with /settings access-revoke. Review current access with /settings access-list; payers need separate Manage access to view server settings and access lists.
• Settings, templates, personality and channels. Includes running meetings and asking questions.
• meetings and questions are open to everyone until the first grant. After that only the people and roles you chose, plus server managers, have them. Revoking the last grant opens the permission to everyone again.

• /settings access-grant permission:meetings role:@HostsOnly the Hosts role and managers can run meetings.
• /settings access-revoke permission:meetings role:@HostsTake the permission back. When the last grant is revoked, everyone can run meetings again.

The payer is whoever completes the checkout. The server owner can also hand the subscription to another member: /billing payer-add, or the Billing page of the dashboard, creates a checkout link for the member you choose.

1. 1

   Run /billing payer-add

   Pick the member and the plan, Community or Pro. Only the server owner can do this, and bots cannot be chosen.

2. 2

   The member receives the link

   Vyach sends the checkout link to the invited member in a private message. You only get a private confirmation. If their private messages are closed, the invitation is cancelled: ask them to allow messages from Vyach and try again.

3. 3

   They pay in Polar

   Once Polar confirms the subscription, the member becomes the payer. Until then they get no extra rights. The link expires after about a day, and only one invitation can be open at a time.

• /billing payer-add user:@Member tier:proInvite a member to pay for the Pro plan. The checkout link goes to them privately.
• /billing subscribe tier:communityPay for the plan yourself. If the previous payer has left, the owner can take over this way.

• An invitation is possible when the server has no active subscription, or when the previous payer has left the server. While the current payer is still on the server, they keep the subscription.
• If the payer leaves the server, renewal is cancelled and the paid plan stays active until the end of the period already paid for. The owner and the payer are notified.
• A new payer, whether the owner or an invited member, is charged for the first time only after that paid period ends, so there is no gap in the plan and no double payment.
• The payer can manage or cancel the subscription with /billing portal. Only the server owner can delete server data with /privacy delete-server.

• Free. 2 recording hours and 10 questions per month, shared across the Free servers of one owner. Each server retains transcripts and stored summaries for its 5 latest meetings. Published Discord summaries remain.
• Community. 30 hours of recording and 100 questions per month, unlimited meeting history, plus custom templates and personality.
• Pro. 60 hours of recording and 500 questions per month, unlimited meeting history, plus catch-ups for late joiners and task posts.
• Paid quotas renew with the subscription’s monthly billing period. On Free, monthly periods start when the bot is added or the server switches to Free.
• Recording time counts the whole call, from the moment recording starts with /meeting start until it ends, including pauses and silence.
• Vyach posts a warning 30 minutes before the limit is reached and pings the person who started the call. Change the time with /settings recording.
• When the limit is reached, the recording ends and the summary is posted with a note that the recording was interrupted.
• Running low? Community and Pro servers can buy add-on packs with /billing addon: a pack of meeting hours or a pack of questions, each equal to the monthly allowance of your plan. Packs expire at the end of the current billing period.
• On Free, paid features are disabled immediately. Custom templates and personality settings remain for 30 days so you can restore the subscription, then are removed. After this grace period, stored meeting history is reduced to the latest 5 meetings. Published Discord summaries remain.

• Raw audio is deleted after successful transcription. Audio left by a transcription failure is deleted after 24 hours.
• After the chosen period without activity, recordings, transcripts, stored summaries, consent metadata and request metadata are deleted. Server settings and billing remain. If the bot has left the server, the subscription is cancelled before all server data is deleted after retention expires.
• Question and answer texts are never stored. Only user ID, time and request status are kept for 30 days for quotas and the dashboard.
• Your data is not used to train AI models.
• We count public page views, bot/community invitation redirects and shared UTM campaign labels for 90 days. No visitor identifiers, IP addresses, analytics cookies or visitor journeys.

• /privacy delete-my-dataAny member can delete their own recordings, transcript segments and meeting metadata, with confirmation. Recording consent becomes declined; affected stored summaries are removed. Published Discord summaries remain. Cleanup waits for ongoing meeting processing to finish.
• /privacy exportThe server owner can request an archive. Its private link is valid for 24 hours after the archive is ready. Downloading requires Discord sign-in and current Owner access.
• /privacy delete-dataOwner only, with confirmation. Deletes recordings, transcripts, stored summaries, consent metadata and request metadata. Revokes archive links. Published Discord messages, settings, the subscription and quota usage remain.
• /privacy delete-serverOwner only, with confirmation. Cancels the subscription before deleting all server data, then sends the payer a private notification. Published Discord messages remain. Purchased paid time is not refunded.