Appearance and copy
Colours, avatar, launcher, every visitor-facing string, and branding removal. All of it is dashboard configuration, no code.
Appearance
| Setting | Applies to |
|---|---|
| Primary colour | Buttons, accents and the send control. |
| Header colour | The chat panel header. |
| Background colour | The message area. |
| Visitor bubble colour | The visitor's own messages. |
| Avatar | The chatbot's picture in the header and next to its messages. Upload an image or use a generated orb. |
| Launcher label | The text on the floating button, e.g. "Have Questions?". |
| Launcher icon | The image on the floating button. |
Palette suggestions. If you trained from a website, OyeChats samples that site's colours and offers them as one-click suggestions, so the widget can match your brand without you fetching hex codes.
Every visitor-facing string
All of these are editable per chatbot from Experience → Messages. Defaults are shown so you can see what you are replacing.
| String | Default |
|---|---|
| Welcome greeting | "Hi There, How can I help you today?" |
| Welcome title | "Hi there 👋" |
| Suggested questions | "Our Services", "About us", "Contact us" |
| Input placeholder | "Write a message..." |
| Proactive greeting | "Hi! Let us know if you have any questions." |
| Live chat label | "Live chat" |
| Waiting message | Shown while a visitor waits for an operator. |
| Offline message | "We'll be right back! Leave a message and we'll follow up shortly." |
| Rating prompt | "How was your experience?" |
| End-chat label | "End chat and return to AI" |
Writing for another language. There is no automatic translation layer for widget chrome. To run the widget in another language, replace these strings with that language and instruct the chatbot to reply in it via the system prompt.
Optional widget features
| Feature | Default | What it does |
|---|---|---|
| Post-chat rating | On | Asks the visitor to rate the conversation when it ends. Feeds Analytics → Ratings. |
| Typing preview | On | Shows the visitor that an operator is typing during live chat. |
| Show branding | On | The "Powered by OyeChats" badge inside the widget. |
| Queue position | Off | Tells a waiting visitor their place in the live-chat queue. |
| File sharing | Off | Lets a visitor attach a file during a live chat with an operator. |
| Email transcript | Off | Offers the visitor a copy of the conversation by email. |
On Free these are all forced off. The defaults above apply on paid plans. A Free workspace has file sharing, post-chat rating, queue position, typing preview and email transcript forced off, and the branding badge forced on, no matter what is stored against the chatbot. The lock is applied server-side when the widget fetches its configuration, so it holds even for settings left over from a previous paid tier.
Removing OyeChats branding
White-label branding is a plan entitlement. On plans that include it you can turn off the in-widget badge and edit the branding text and link, and the dashboard emits an embed snippet without the attribution anchor.
Two separate things. The in-widget badge and the attribution
<a> in your page HTML are distinct. The badge is inside the shadow root and only visible after a visitor opens the chat; the anchor is in your served HTML, which is the only version search engines and AI assistants can read. Removing branding removes both.Something here wrong or missing? Tell us and name this page. We will fix it.