The first thing almost every business does after installing AIVA's widget is change how it looks. Not the logic, not the triggers — the color. It's the fastest edit available and, it turns out, the one that matters most for whether a widget feels like it belongs on a site or feels like a third-party tool someone dropped in.
That instinct is correct, and it's worth explaining why a chat bubble's color carries more weight than its size or its position ever will.
Trust is visual before it's functional
A customer who opens a support widget makes a snap judgment about whether they're still talking to the business before they've read a single word — the same way you trust a storefront more when the signage matches the brand you expected to walk into. A widget in AIVA's default styling, dropped unmodified onto a business's site, reads as exactly what it is: a plugged-in third-party tool. The same widget in the business's own colors, with their own tone in the greeting, reads as part of the business. The underlying software hasn't changed at all. The trust signal has.
This isn't unique to chat widgets — it's the same reasoning behind why a payment page that suddenly looks unfamiliar makes people hesitate at checkout, or why a phone call that opens with the wrong company name gets hung up on before the first real sentence. Visual consistency is a trust shortcut people use constantly and mostly unconsciously, and a widget that skips it is quietly spending down trust it didn't need to spend.
What actually gets changed, roughly in order
Color, almost universally. Matching the primary brand color is the change every business makes, usually within minutes of going live — often before they've finished the rest of setup. It's the highest-leverage, lowest-effort edit there is.
The opening message, by industry. A clinic's greeting tends to be direct and reassuring. A salon's is warmer and more casual. A professional services firm's is terser. Businesses spend real time getting this line right, because it's the first thing a visitor reads, and it sets the register for the whole conversation that follows.
Position and icon, less often. Most businesses leave the widget in its default corner with a simple icon. The ones who touch this tend to have a specific reason — an existing floating button already in that corner, or a mascot they want represented instead of a generic chat symbol.
The pattern we see across customers: color and greeting get changed by nearly everyone in the first week. Position and icon get changed by a minority, usually to solve a specific conflict rather than out of general preference. Design effort should go where businesses actually spend their time, and that's what shaped which controls we prioritized building.
What "branding" actually covers under the hood
Color isn't a single toggle — a business setting one brand color needs it applied consistently across a button background, a hover state, an active state, and enough contrast against whatever text sits on top of it that the widget stays readable rather than just on-brand. Set only the base color and leave the rest to guess, and you end up with a widget that matches the brand in screenshots and looks slightly wrong the moment someone actually hovers over a button or taps it on a phone. The dashboard derives the supporting states from the one color a business picks, rather than asking a salon owner to understand what a hover state even is.
Typography is handled differently, deliberately. The widget doesn't let a business swap in an arbitrary web font, because a mismatched or poorly-hinted font can make text render unevenly across devices in ways that are hard for a non-designer to catch before it ships. What's configurable is color, the greeting, an icon or small logo upload, and position — the widget's actual shape, like corner radius and spacing, stays consistent across every deployment, the same way AIVA's own product interface does. That consistency is deliberate: businesses get to make it theirs without accidentally making it worse.
Where a business could get this wrong, and the guardrails
The most common way self-service branding goes wrong elsewhere is a color choice that looks fine in isolation and fails once it's actually load-bearing — a light brand yellow, say, used as a background behind white text that was never going to be legible on it. AIVA's dashboard checks basic contrast when a color is set and flags the combination before it goes live, rather than letting a business discover the problem from a customer who can't read their own chat window. It's a small guardrail, but it's the difference between "on-brand" and "on-brand and still usable."
The other place businesses occasionally misjudge is the icon. A detailed logo that reads clearly at full size can turn into an unrecognizable smudge at the small size a widget bubble actually renders at. We recommend a simple mark over a full logo for exactly this reason, and the dashboard preview shows the icon at its actual rendered size, not an enlarged version, so what a business sees while configuring it is what a visitor will actually see.
Branding has to survive contexts a business didn't think about
A color picked while looking at the widget on a plain white background doesn't automatically work everywhere that widget renders. A site with a dark-themed homepage, a busy image-heavy hero section behind the bubble, or a high-contrast accessibility mode a visitor has enabled in their own browser are all real rendering contexts a business isn't thinking about when they pick one brand color in a dashboard. The widget's own container carries enough separation — a shadow, a border, sufficient contrast against whatever's behind it — that it stays legible regardless of what's on the page underneath it, rather than assuming every host site is a plain white background like the one in a settings preview.
The same logic applies to loading and error states, which a business never explicitly designs but which still have to look intentional. A widget that's mid-load, or that's briefly lost its connection to AIVA's servers, still renders in the business's chosen color rather than snapping back to a generic default that would look like a glitch. Small detail, but it's the difference between a widget that reads as reliably "yours" and one that occasionally reminds a visitor it's someone else's software.
Why we didn't make this a design project
None of these are things a business should need a designer or developer for. Branding controls live in plain settings — pick a color, write a greeting, choose a position — not in a codebase. That matters because the businesses running AIVA are clinics, salons, coaching centers, and service providers, not engineering teams. If matching their own brand required a dev ticket, most of them simply wouldn't do it, and the widget would sit there looking like what it technically is instead of looking like what it's actually meant to be: their own front desk, online.
This sits alongside the other two widget decisions we've written about — how the widget embeds in three lines of code in the first place, and when it should actually appear once it's installed. Branding, install, and triggers are three separate settings, not three separate projects, and none of them require touching a line of code after the initial paste. See the widget as it ships by default on the platform page, read about adding it without hiring a developer if the whole process still sounds like more work than it actually is, or start free and rebrand your own widget in about the time it takes to read this sentence twice.