Support gets saved views, a shareable help page, and answers from your boards

Support works like an inbox now

The conversation list filters. Status, mood, language, visitor email, a date range or the last seven days, star rating: pick what you need in the filter dialog and the list narrows to it. Search reads the title, the summary, the last message, and the visitor's name or email, so the thread you half-remember from Tuesday takes one search instead of a scroll.

Keep landing on the same combination? Save it as a view and name it. Views sit as tabs above the list and belong to the whole organization, so "unhappy this week" is one click for everyone on the team. Anyone who can read Support can apply a view. Changing one takes configure access.

Feedback moved into the thread. A star rating arrives as a message in the conversation instead of a tray stuck to the composer, and each star tells you what it means as you hover it.

A support page you can hand out, no website needed

A widget used to need a website to sit on. Turn on the hosted page for one, pick a handle, and Support answers at /help/<your-handle>. It's a public page, so it can go in an email signature or a bio link. For a client who has a business but no site, that's the whole feature.

The page stays off until a manager turns it on. Choosing a handle is part of that, and the Widget tab shows your daily AI budget while you do it, because every conversation on a public page spends your organization's own usage.

Your boards can answer for you

Connect a board column, Blog → Published for instance, and every client-visible card in it becomes something the assistant can answer from. Cards get picked up as they're written, dropped when they leave the column, and refreshed when their body changes. Answers track the board rather than a copy of it taken the day you set it up. The picker counts the cards in each column and marks the ones already in use.

Everything the assistant draws on sits in one list now: the Q&A you wrote, pages you imported, URLs you crawled, cards from your boards. Each one says where it came from and how often it has actually grounded a reply. Open a source for its health, its coverage, its last sync, and whatever went wrong if something did. One level deeper is the exact text being indexed.

Long tables load as you scroll

Prev and Next are gone. Customers, the Boards table view, the Media Center grid and its picker, your API keys and their activity, audit pages and runs, ads campaigns, Trash, and the Support knowledge base all keep loading as you reach the bottom. A long table opens about as fast as a short one.

Which columns you show and how you sort them survive leaving the page. Rows answer to the keyboard, and sorted columns announce themselves to a screen reader. Loading placeholders match the shape of the rows they stand in for.

Cal.com bookings, all the way through

Connect Cal.com from Integrations and your calendar joins the rest of SharpOS. Read bookable slots, list and open bookings, book one, cancel it, move it. That works from an automation, over the API, or from an AI tool you've connected.

Bookings start automations too. Booking created, rescheduled, cancelled, and meeting ended each fire as a trigger, so a new booking can add the customer and send the confirmation while you're doing something else. A booking SharpOS made itself won't fire the trigger, so an automation can't chase its own output.

Your brand carries into the widget

The support widget takes its look from the Brand Kit. Bind a color slot to a kit color and it follows the kit from then on, dark colorway included, along with the kit's font and theme mode. Change the brand color once and the widget changes with it.

The Brand Kit gained a theme scope of its own: Light, Dark, or Both. Colors and assets follow the scope, color tiles split into their light and dark halves, and narrowing the scope tells you what it would discard before you commit.

Connected AI tools can read your workspace

A client connected to SharpOS over MCP could already run tools. Now it can read as well: your Playbook, your Brand Kit, any page as markdown, asked for by name. It sees exactly what its key is allowed to see and nothing else. The newest clients connect with no special handling, and the ones you set up months ago carry on.

Also in this release

Videos preview at their own shape. A portrait video no longer spills out of the preview and hides its own controls.

Publishing a Studio project to Instagram checks that the image it's about to post is the one you'd see in the editor. When it can't confirm that, it asks you to open the project instead of posting.