FAQs are listed in replies to this topic.
4 Likes
Where should I post my question?
Please see the “Welcome the the LiveKit community” post in the announcements channel.
How can I report or flag a post?
If you need to report a post, you can use the flag icon on any post, which may be hidden behind an ellipsis.
Flagged items will be raised to our community moderation team for review.
How can I get faster support? / Nobody is answering my question
Please note that the community is not a paid support channel, and responses are best-effort. Although LiveKit staff do provide support in the community, most of the responders are community members like you. For urgent or guaranteed response times, please use the official support channels, available to members on the appropriate plan.
Please note that unsolicited tagging or directly contacting other community members directly is against the community guidelines, and in extreme cases, such as direct and unsolicited contact outside of this community, can lead to removal from the community. See also the community guidelines.
Can I email support?
If you are on our ship plan or higher, you have access to email support. You can find our support email by logging into the cloud portal, cloud.livekit.io, then clicking on the “Support” button in the lower left. Your support options will be displayed, including the support email.
How can I send private messages to members?
Sometimes you may need to message other members privately, such as to provide logs or other non-public information. There is more than one way to do this, but the easiest is to find that member in the search box, then you will see a Message button on their profile. If you do not see this button, it means this member has disabled direct messaging. Please do not send unsolicited messages.
How can I share Agent insights with LiveKit Support?
By default, LiveKit support do not have access to your Agent insights data as it can contain personal information. If you are asked to share insights data for a specific room you can do so by loading the Agent insights tab for the session you want to share, then use the Share button in the top right. In the modal dialog that is displayed, please be sure to check “Allow LiveKit support to access this page”. Do NOT share this link in the public forum and remove access when it is no longer required.
I would like to report a service outage
If you experience a genuine service outage please check https://status.livekit.io/ to see if there is an ongoing incident.
If your issue is not currently listed on the status page then log into the cloud portal, cloud.livekit.io, and select the ‘Report Service Outage’ option, which is shown after you click on the “Support” button in the lower left.
The service outage reporting feature is designed for users with an existing deployment who experience a loss or prolonged degradation to their LiveKit services. For development questions, transient errors, or other technical questions, please use this support forum.
What details should I include in my question?
Providing as much information as possible when posting your question can help the community answer your question.
-
Provide a clear and specific title
-
When describing your problem also explain your goal and use case. What are you trying to achieve and what do you expect to happen?
-
Explain what is actually happening, including error messages, logs, or unexpected results. Be precise and share as much as possible whilst remembering that this is a public forum, so do not share sensitive information.
-
Include details of your environment - LiveKit is an incredibly flexible platform, but that also means there are a lot of ways it can be configured. For example, consider: Are you using LiveKit cloud, or self-hosting? Are you developing AI agents (if so, where are these agents hosted)? Do you expect a SIP participant on your calls (if so, who is your provider)? Which client SDK(s) are you using?
-
Include the version numbers of the components you are using. In general, it is best to be on the latest version of everything as each release brings new features and fewer bugs.
-
Share a minimal, reproducible code sample. We have a multitude of examples at https://github.com/livekit-examples , https://docs.livekit.io/reference/recipes/, https://github.com/livekit/agents/tree/main/examples , and https://github.com/livekit/agents-js/tree/main/examples - if you are able to reproduce your issue by modifying one of these examples, it will expedite any fix.
-
Share screenshots, or a link to a video showing your issue if appropriate.
How can I improve my agent latency?
There is no single source of latency, a turn will involve:
-
Determining when the user has finished talking, and are expecting a response from the agent
-
Speech-to-Text (STT), converting the transcribed audio into LLM tokens
-
Large Language Model (LLM), processing the tokens and replying
-
Text-to-Speech (TTS), converting the LLM response into natural-sounding audio.
For more information, please see this guide to understand and improve your agent latency: Understand and Improve Agent Latency | LiveKit
Is there an AI bot? 
Yes, you have a few options:
-
In Beta for selected users
: Our docs page has an Ask AI field in the header for logged-in users. -
Our Slack community has an
ask-aichannel with full knowledge of LiveKit -
Our docs MCP server is available for Cursor, Claude Code, Codex, Gemini CLi, and more.
-
We maintain a DeepWiki page at livekit/livekit_composite | DeepWiki where you can ask questions
How can I report a docs issue?
The quickest way to provide feedback on our docs is to click the 
emoji on the right of any of our docs pages (under the heading “Is this page helpful?”). You will then be asked to provide additional information before submitting your feedback.
All feedback will be routed to our internal docs team.
Alternatively, you can start a conversation on this form and tag it with docs-feedback.
I submitted a PR, what are the next steps? Can someone take a look?
Firstly, thank you for taking the time to submit a PR.
A few pre-requisites:
- Please read through the contributing guidelines for the project you are contributing to, this might be a separate
CONTRIBUTING.mdor the information might be contained within the ReadMe - Test your PR locally and ensure that all tests and formatting checks pass
- If this is your first contribution, please sign the contributor agreement with the same GitHub identity that raised the PR
- When you submit the PR, it will trigger an AI review, please address all the comments made by the AI bot (or bots)
Someone from the relevant team will review your PR, we get a lot of PRs so depending on the size of your request, this may take some time.
Contributing a new plugin?
We get a lot of new plugin requests, and these require extra consideration from the team as to what we officially support. Don’t block your users whilst waiting for PR approval: we encourage contributors to develop and host plugins outside of LiveKit prior to approval, along with an integration guide - that way it helps us gauge organic interest and better understand the plugin use cases. If you have hosted the plugin and integration guide yourself, please include this information in your PR.