CRM
Report a bug from the assistant, a signup that no longer dead-ends, and error messages that name the problem
You can now report a bug or ask for a feature by telling the assistant.
You can now report a bug or ask for a feature by telling the assistant. Describe what went wrong in your own words and it files the report - with the page you were on and any errors your browser recorded already attached, so you never have to go looking for them. Anything resembling a password or key is stripped out first, and the report is saved in the CRM before it’s emailed, so it still reaches us if the emailing part is what’s broken. Signing up no longer dead-ends. Starting from a plan on the website took you to a page that could only add you to an existing workspace, so a brand-new customer submitted their email and heard nothing. One address now does both: if your company already has a workspace you join it, and if it doesn’t we start you a new one. If we can’t deliver the verification email we say so on the spot instead of showing “check your email” for an email that was never sent - and there’s a “send it again” link on the confirmation screen. Starting a signup with an address that already has an account now gets a “you already have one, here’s the sign-in link” email rather than silence. “Validation failed” now says which field. Every form error that used to be those two words now names the field as it appears on screen and what’s wrong with it. Automated social replies are labelled. Replies published by a comment rule now carry a visible automated-reply line, honouring the per-account setting that previously had no effect; replies a person writes or approves are untouched. The messaging-window warning in the inbox now matches the platform’s actual rule - a blocked Instagram or Messenger thread explains that the seven days a human agent gets have run out, instead of quoting a 24-hour limit you’d just been told didn’t apply. And the AI assistant works again on the current OpenAI models, where every tool-using request was failing; when it does hit a problem it now explains it in plain terms instead of printing the provider’s raw error.