Report a problem without leaving the conversation
If something goes wrong while you are working with Claude, you can now report it through the same connection — you no longer have to stop, come back to the app and find the support form.
Claude drafts the ticket, then shows you the exact subject and description and waits for you to confirm before anything is filed. That step is deliberate, and it is worth knowing why: the words in a support ticket leave your organisation and reach our team, and you cannot edit or withdraw them from here afterwards. Nothing rewrites what Claude drafted, so a report written from a live working session can easily pick up a customer's name or a figure from the deal you were looking at. You get to read it first, exactly as it will be sent.
If Claude changes so much as a character between showing you the text and filing it, the filing is refused rather than sent — so what goes out is what you read.
Once filed, you get the ticket number back, along with the category, the priority, and when we are due to respond. Quote that number to us and we can pick it straight up.
Filing this way is available to owners, admins and members. Viewers can still report problems using the support form in the app, which is unchanged.
Quotes built through Claude now carry real margin
This is a fix to a real problem a customer reported. A quote whose lines Claude added had no cost recorded against them. The line totals and the quote total were exactly right — but the quote reported Total cost $0.00 and 0.00% margin. The report that found this was a twenty-line quote of hardware and support at roughly 20% blended margin, showing as break-even.
That is worse than a missing number. Pipeline reporting, the margin column on the quote list and
anyone reviewing the quote all read it as a deal with no profit in it, and a reviewer looking at
0.00% has no reason to doubt it.
Two things changed:
- A quote line can now be given its cost through the connection. Owners and admins can set a unit cost on a line, and the margin is worked out from that cost and the price. Claude cannot assert a margin directly — a cost is a fact off a supplier's price list that you can check against an invoice, a margin is arithmetic on top of it. Setting a cost is limited to owners and admins, matching who can already see cost and margin. Members can still add and edit quote lines as before.
- A quote that cannot support a margin figure now says so. If any line is missing its cost data, the quote no longer reports a made-up zero. It withholds cost and margin and instead tells you how many lines need cost data — something you can actually act on. Sections of a quote are judged on their own lines, so a fully costed section still reports its margin even when another section in the same quote does not.
Also in this release
- Margin figures on a quote were reported as empty to Claude even when they existed. Asking Claude about a quote's margin returned nothing at all for owners and admins, because the figures were being read from the wrong place. They now come from the quote's real totals.
- A support ticket now records where it came from. Tickets filed through Claude arrive tagged as such, so when we pick one up we know it came from a conversation rather than the in-app form and do not go looking for browser details that were never there.