Publishing an application is a decision, and it comes with a chat

Featurekamo-internal
Shipped
September 5, 2026 at 8:32 PM UTC
Author
Kamo
Commit
7ef024e

**Vendors & Products no longer prints a link for every product it has.** It printed one for every mortgage product the moment that product existed, which meant every one of them had a live public form nobody had agreed to publish — and a printed link for a page that answers 404 is worse than no link, because somebody sends it. There is now a Publish button, and the address appears only once the page is actually live. **Publishing asks one real question: which web chat answers questions on it.** Someone filling in a mortgage application will have a question, and a form with no way to ask one is where they stop. "Create a new web chat instead" is offered whether or not they already have one — an org running a chat on its marketing site usually wants a separate one for a lender's application, routed and worded differently, and making them go and find the other screen is how that turns into reusing the wrong one. It deep-links into the creator with the dialog already open and brings them back to the product they were publishing. **A chat set up for the org's own site needs a new key to work here**, because a page Kamo hosts resolves the key server-side and that one was shown once and never stored. Reissuing rotates it, so the dialog says so before the button is pressed rather than after. **The new-integration dialog is rebuilt.** Two columns — the decisions on the left, a live preview on the right — and it starts in the org's own brand colours instead of the stock green-on-near-black that belonged to nobody. The preview is here rather than behind "Custom design" because the point of seeding from the brand is that most orgs never need to open the customizer, and they can only know that if they can see it. Surface and text colours are derived by luminance, so a lender with a pale primary gets dark type on it rather than white on yellow. Seeded, never locked: an existing integration is never repainted, since an org that rebrands has already chosen its widget's colours. `npm test` green: 448 files, 5532 tests, all guards, and check-i18n-keys against a fresh clone of the dictionary.

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free ForeverView Pricing