Send feedback
Tell Basemodo what is wrong or missing, from anywhere in basemodo.com while you are signed in. Every message is read, and answered by email.
Sending it
- In the sidebar, under Docs, choose Send feedback. On a phone, open the menu first.
- Write what happened, or what you wish Basemodo did. Up to 5,000 characters.
- If you like, mark it Bug, Idea or Other.
- Choose Send. The dialog says when it has been sent.
Anyone signed in can send feedback: an Owner, a Member who was only invited to one App, an Admin of a Workspace.
From the terminal or your agent
The CLI sends it as the person it is signed in as (basemodo feedback):
basemodo feedback "The Logs stay empty after a Deploy" --category bug--category is bug, idea or other, and can be left out. Your agent sends it the same way, or with the MCP tool feedback on the local or the remote MCP, as you: ask it to tell Basemodo when something gets in your way. Feedback from an agent carries its MCP client's name and version (claude-code 2.1.0), so we know which agent it came through.
What goes with it
You only write the message. Basemodo adds where you were, so you don't have to explain it:
- the page you were on (
/apps/lunch-rota/logs); - the App you were in, by name, and the Workspace, if any;
- your browser, as it names itself.
Nothing else is attached: no screenshot, and nothing from inside your Apps.
What happens to it
Your feedback is kept first, then emailed to support@basemodo.com with your email as Reply-To, so the answer comes straight back to your inbox. If that email fails to leave, your feedback is still kept: nothing you send is lost.
Basemodo's Operators read every message, newest first, with who sent it and where they were, and mark each one read once they have dealt with it, so none is left unread.
To keep the inbox readable, one person can send up to 10 messages an hour and 20 a day. Past that, the dialog says so (too_many_feedback): send it again later, or write to support@basemodo.com. The same message sent twice within a day is kept once.