Skip to main content

​
Feedback Overview

The Feedback page is where you tell the Cortado team what’s working, what isn’t, and what you’d like to see next. Every submission is visible to the whole community of Cortado users, and anyone can upvote the ideas they care about most.
Feedback is shared across all Cortado users, not just your organization. This makes the page function like a lightweight public roadmap — you can see what other customers are asking for, and your upvotes help signal priority.

​
Opening the Feedback Page

Click Feedback in the page header menu, or navigate to it directly. The page is organized as a Kanban board with one column per stage, so you can see what’s been submitted, what’s planned, and what’s already shipped.

​
Submitting Feedback

Click Add Feedback in the top-right of the page to open the submission dialog.

​
Feedback Types

Choose a type that best describes what you’re submitting:
  • New Feature — a capability you’d like Cortado to add
  • Bug Fix — something isn’t working as expected
  • Improvement — an existing feature could be better
  • Question — you’re unsure how something works or why it behaves a certain way

​
Your Feedback

Describe your feedback in as much detail as you can. For feature requests, explain the problem you’re trying to solve, not just the solution you imagine. For bug reports, include what you tried, what happened, and what you expected. Click Submit Feedback to post.
Great feedback focuses on the underlying need. Instead of “add a button here,” try “I need a faster way to mark multiple leads as stale because I do this every week.” The more context you give, the easier it is for the team to design the right fix.

​
Browsing Feedback

The main Feedback view is a Kanban board with one column per stage:
  • New — recently submitted, not yet triaged
  • Planned — accepted and scheduled for future development
  • In Progress — actively being worked on
  • Complete — shipped and available in the app
  • Cancelled — won’t be addressed, with context when relevant
Each column shows a count of items, and cards within a column are sorted by upvotes (most upvoted at the top).

​
Feedback Cards

Each card shows:
  • A type badge (New Feature, Bug Fix, Improvement, or Question)
  • The feedback text, clipped to three lines by default — click See more to expand
  • The name and avatar of the submitter
  • An upvote button with the current count
  • A menu button (only on your own feedback) for editing or deleting

​
Upvoting

Click the up arrow on any feedback card to upvote it. Your upvote is added to the count and the arrow fills in to indicate you’ve voted.
  • Click again to remove your upvote — except on your own feedback
  • Click the upvote count to see a popover listing everyone who has upvoted
Your own feedback is automatically upvoted when you submit it. You can’t remove your upvote from your own feedback — it counts as your initial support for the idea.
Upvotes are one of the strongest signals we use when prioritizing the product roadmap. If you see a feature request you want, upvote it.

​
Editing Your Feedback

You can only edit feedback you submitted yourself.
  1. Find your feedback card on the board
  2. Click the three-dot menu in the top-right of the card
  3. Choose Edit
  4. Update the text in the dialog
  5. Click Save Changes
The feedback type cannot be changed after submission.

​
Deleting Your Feedback

To remove feedback you submitted:
  1. Click the three-dot menu on your card
  2. Choose Delete
  3. Confirm the deletion
Deleting feedback is permanent and removes your submission along with any upvotes it received. If you’ve changed your mind about the idea, editing is usually a better option than deleting.

​
Best Practices

  1. Search before submitting — check the board for an existing request before adding a duplicate. Upvoting an existing item is more impactful than posting another
  2. Be specific — concrete examples and the “why” behind your request make prioritization easier
  3. Use the right type — Bug Fix for broken behavior, New Feature for capabilities that don’t exist, Improvement for refining something that already works, Question when you’re unsure
  4. Upvote actively — the more you upvote, the more signal the team gets about what matters to you
  5. Check back periodically — stages shift as items get planned and shipped; look for updates on ideas you’ve upvoted
  6. Keep it constructive — feedback is public to the community, so aim for tone that’s respectful and solution-oriented

Notifications

Stay informed about activity in your organization.

Dashboard

Return to your home dashboard.