Request a missing feature
Open Feedback, pick Feature and a topic like Integrations or Billing, describe what you need, and send it. It joins the Community Board where other users who want the same thing can upvote it instead of filing a duplicate.
Feedback Board
Submit bug reports, feature requests, improvements, and questions from inside the app, then vote on what other users have asked for. Every item lands on one Community Board visible to the whole platform, sorted by vote count, so the most-wanted ideas surface for the team automatically.
The Feedback panel opens from your profile menu in the top-right of the header, from the Feedback icon in your workspace top bar, or from the Ask a Question button in the Guide header. It also lives at its own address, /feedback, for a direct link. However you open it, you land in the same drawer: pick a type (Bug, Feature, Improvement, or Question), pick a topic (General, Chat, Integrations, Billing, Performance, Security, or a custom one you type yourself), add a title and an optional description, and send it.
Once submitted, your item posts to the Community Board, not a private queue tied to your account or tenant. Every user on the platform sees the same list, sorted by vote count first and recency second. Anyone logged in can upvote a card once, un-vote it, and open its comment thread to read or add markdown-formatted comments. The team sets a status on each item as it moves: New, Reviewing, Planned, In Progress, Done, or Won't Do, so you can track where your request stands without a separate submissions list.
What makes this different from a support inbox or a generic contact form is that the board is shared and the votes carry weight: instead of your feedback disappearing into a ticket only you and support can see, it sits next to every other user's request where anyone can find it, upvote it, and push it up the list the team actually works from. A logged-out visitor still gets a quick no-signup feedback form, but voting, commenting, and status tracking all require an account, since every item and comment is tied to a real user, just without your email shown publicly.
You do not have to keep going back to the board to find out whether anything moved. When someone comments on an item, the person who posted it, everyone who already commented on it, and everyone who voted for it get an in-app notification. Backing a card with your vote is therefore also how you subscribe to it, so a request you care about keeps you in the loop without you checking on it.
Because the board is shared, it is also a research tool before it is a submission form. Search it before you post: you will often find the thing you were about to ask for already sitting there with a status on it, which either saves you writing the request or tells you it is already Planned. Reading the board is the quickest honest answer to the question of whether something is coming.
A short, specific post travels further than a long one. For a bug, the steps that trigger it and what you expected instead are what let the team reproduce it. For a feature, describing the outcome you want rather than the screen you imagine leaves room for a better answer than the one you had in mind, and makes it easier for other users to recognise their own problem in your words and vote for it.
Submitting and Voting
Open Feedback, choose a type and a topic, give it a title and an optional longer description, and send it. It appears on the Community Board immediately, visible to every user on the platform, not just your own team.
Before posting, search the board: if your idea already exists, upvoting the existing card is more useful to the team than a duplicate. Click the up arrow on any card to vote, click again to remove it. Comment threads on each card support markdown, and you can delete your own comments at any time.
Tracking Status and Getting Help
There's no personal submissions list. To check on something you posted, find its card on the board and read its status badge: New, Reviewing, Planned, In Progress, Done, or Won't Do reflect exactly where the team has it, updated on the same card everyone else sees.
If you'd rather not use the panel, email [email protected] and it reaches the same team. The panel footer also links straight to Discord, where you can talk with other users and the team in real time alongside posting to the board.
What Happens After You Post
Your item is live on the board the moment you send it, and from then on it belongs to the conversation rather than to a queue. Anyone can upvote it, anyone can add a comment, and the team can reply in the same thread when they need a detail you did not include. Comments are yours to remove: you can delete your own at any time, and nobody else can.
When a comment lands on an item, everyone connected to it hears about it in the app: the author, the people who already commented, and the people who voted for it. That notification reaches you inside whichever workspace you are working in, so a request you filed months ago still finds you when it finally moves.
How It Works
One shared board, sorted by votes
Every submission is typed (Bug, Feature, Improvement, Question) and topic-tagged, then written to the platform-wide Community Board rather than a per-tenant list. That single board is what both users and the team look at: there is no private duplicate view.
Cards sort by vote count, then by recency, so the items with the most support rise to the top without anyone manually curating a priority list. A vote is one per user per item, toggled from the card itself, and each card shows its type, topic, status, author, and comment count at a glance.
Status changes (New through Done or Won't Do) are set by the team directly on the card. Because there's no separate ticket number or personal dashboard, checking on a request means finding its card on the board, the same view everyone else uses.
Use Cases
Report a bug with steps to reproduce
Pick Bug, write the steps that trigger it, and submit. The team tracks it on the board with a status you can check any time, and can follow up through the comment thread if they need more detail.
Push a good idea up the roadmap
Browse the Community Board before posting, find an existing request close to what you want, and upvote it. Votes sort the board directly, so backing an existing idea is often more effective than starting a new one.
Ask a question the team can answer publicly
Pick Question, add context, and submit. Other users can see the thread and comment, so the answer benefits anyone who runs into the same question later instead of staying buried in a private support ticket.
Comparison
| Before | After |
|---|---|
| A bug report disappears into a private ticket that only you and one support person can see. | It sits on a shared board where anyone hitting the same thing can find it, add the detail you missed, and vote it up. |
| Five people ask for the same capability in five separate messages, so it reads as five small unrelated requests. | They collapse onto one card with a vote count, and the board sorts by that count, so real demand rises on its own. |
| You ask for something and never learn whether it was read, turned down, or already half built. | The card carries a status, New through Done or Won't Do, in the same view everyone else is looking at. |
| Keeping track of a request means remembering to go back and check on it. | Comments notify the author, prior commenters, and voters, so the update finds you instead. |
FAQ
Where do I find the Feedback panel?
It's not in the sidebar. Click your profile avatar in the top-right of the header and choose Feedback, use the Feedback icon in the workspace top bar, click Ask a Question in the Guide header, or go straight to /feedback.
Do my votes actually influence what gets built?
Yes. The Community Board sorts by vote count first, so the most-voted requests surface at the top for the team, and that ordering is what the team works from when prioritizing.
Can I see the status of my bug report or feature request?
There's no separate submissions list. Find your card on the Community Board and its status badge, New, Reviewing, Planned, In Progress, Done, or Won't Do, shows exactly where the team has it.
Is my feedback anonymous?
No. Every item and comment is tied to your account so the team can follow up, but your email address is never shown to other users on the board.
Do I have to use the in-app panel?
No. You can email [email protected] directly instead, or join Discord from the panel footer to discuss ideas with other users and the team in real time.
Will I be told when someone replies to my feature request?
Yes. A new comment on an item notifies the person who posted it, everyone who commented on it before, and everyone who voted for it, in the app. Voting on a card is effectively how you follow it, so you hear about movement on requests you backed as well as ones you wrote.
Can I send feedback without creating an account?
Yes. A logged-out visitor to the feedback page gets a short form that reaches the team with no signup. Posting to the Community Board, voting, and commenting all need an account, because each of those is tied to a real user.
Can I take back a vote or delete a comment I left?
Yes to both. Clicking the vote arrow again removes your vote and the count drops, and you can delete any comment you wrote at any time. You can only delete your own comments, not anyone else's.
Where Feedback Board fits
Feedback Board is part of How you run the account itself.
Sign in the way your company already does, decide who can do what, and keep the money side legible. Credits, plans, invoices, referrals, and the controls that decide who reaches which part of the workspace.
- How you run the account itself: Your workspace, your money, your people.
Read the guide
More in Account & Billing
- Monthly Credits: Every paid plan comes with a pool of credits that refills automatically at the start of each billing period. Credits are the single unit that pays for everything your AI employees do: thinking, tool calls, media generation, voice, and meetings. There is nothing to top up manually each month; your allowance is just there again when the new period starts.
- Lifetime Credits (Free): Pick the Free plan and your workspace gets 2,000 credits in one grant, no card required. Those credits never reset and never expire; you spend them at your own pace across chat, tools, and media generation until they run out. It is a one-time bucket, not a monthly allowance, so it is meant for trying the platform before you commit to a paid plan.
- Buy Credits: Add credits to your workspace balance any time, on any plan, without changing your subscription. Pick from three one-time packs, pay by card through Stripe, and the credits land in your balance as soon as the payment clears.
- Upgrade & Downgrade: Move to a bigger plan the moment you need more credits or a higher employee cap, and the change takes effect immediately. Move to a smaller plan when you need less, and it takes effect at the end of your current billing period so you keep what you already paid for. Both happen from Settings, Subscription, no support ticket required.
- Promo Codes: Redeem a promotional code for a one-time, lifetime grant of bonus credits on top of your plan's monthly allowance. Enter a code at signup or any time afterward from Settings, Subscription, Get Free Credits. Each grant shows up in your Credit Grants history with its source, date, and amount, and one code can be redeemed once per workspace.
- Referrals: Share your personal referral link or invite someone by email, and you both get 1,000 free credits the moment they sign up. Track every invite from a dedicated Earn Credits page, and keep earning until you hit the 10-referral cap.
- Data Retention: Sistava deletes operational data on a fixed schedule instead of keeping it forever by default. A cleanup job runs every day and removes rows past their retention window: short-lived debug data within a week or two, working memory after 30 days of inactivity, and usage and activity history after two years. Chat messages, documents your employees write, and persistent notes are kept indefinitely unless you delete them yourself. There is no setting to change these windows; they apply the same way to every workspace.
- Google Sign-In: Sign in to Sistava with your Google account instead of creating a separate password. Choose Sign up with Google on the signup page and your workspace is ready after one approval, with your name and photo carried over automatically from Google. Because Google has already confirmed your email address, there is no verification email to chase before your AI employees can start working.
- Microsoft Sign-In: Sign up or sign in with your Microsoft account instead of creating a password. Sistava reads your Microsoft account's name, email, and profile photo to set up your account, and your Profile page shows Microsoft as your connected sign-in method. Because Microsoft has already confirmed the address belongs to you, the account counts as verified from the start and your employees can begin working straight away. Google sign-in and an ordinary email and password are the other two ways in.
- Workspace Roles: Every workspace you create has an Owner, Admin, and Collaborator role, each with a fixed set of permissions over billing, the collaborator roster, and resource access. Owners can grant a non-owner collaborator extra access, or take some away, without changing their overall role. A Roles page shows your own effective access and the full permission matrix so nobody has to guess what they can do.
- User Profile Picture: Upload a photo for your account so your teammates and AI employees see a real picture of you instead of initials. It shows up in chat, comments, and the collaborator list across every workspace you belong to. If you signed up with Google or Microsoft, your picture is pulled in automatically the first time you sign in, and you can replace it any time.
- Two-Factor Authentication: Add a second sign-in step to your Sistava account using any TOTP authenticator app, like Google Authenticator or Authy. Once enabled, a code from your app is required in addition to your password, so a leaked or guessed password alone is not enough to get in. Turning it on immediately signs out every other active session, so a session created before you enabled it cannot be used to bypass it.