Skip to content
Your brand

An assistant that looks like you built it.

Your customers get answers in your colours, fonts, corners and card styles, drawn inside your mobile app and website rather than in a vendor's window. Your team changes the look in Rendel's console, tries it on a test build and publishes it to every user with no app release.

Halden’s console, an invented store with Rendel running. Yours for two hours, no sign-up.

Change it once. Every answer follows.

Halden's Appearance editor, with its assistant beside it.

The problem

Your app has a design system. Most chat widgets bring their own.

Customers notice when they are handed to someone else's tool: another font, other corners, a chat bubble that looks like nothing else in your app.

It looks like someone else's product.

A separate widget arrives with its own type, its own corners and its own bubbles, so the moment a customer asks for help, they can tell they have left your app.

Every look change waits for a release.

When the look is set in the build, a new brand colour or a rounder button waits for a build and a store review, and the assistant falls behind the rest of your app.

Dark mode and contrast are left to you.

A widget that ignores your app's own theme switch can open a light panel over a dark screen, and a plain settings page takes any colour without telling you the word on your button is hard to read.

And it is one more tool to keep in step.

Another settings page to update after every rebrand, and on some chat tools a higher plan just to set your own colours or remove the vendor's badge.

How it works

From your code to every phone, with no release.

Your team works in one editor with the phone beside it, tries the draft on a test build, then publishes to everyone.

  1. Start from your code, or from a theme

    Start with the look you already have: AI setup reads your colours, dark theme, corners, font, card style and logo from your code into a draft, each value marked with its file, and never publishes. No theme to read yet? Start from one of 12 ready themes.

  2. Shape it with the phone beside you

    Change colours, type, corners and cards and see each change on a real phone size or a desktop browser, in light and dark.

  3. Try it on your test build

    Save the draft, and your app on its test key shows it on its next launch. The console's Test page shows it right away.

  4. Publish to everyone, no release

    One Publish sends Experience, Appearance and Voice live together. Devices pick it up on their next launch and keep the last good look for the first frame.

  5. Put an old look back in one step

    Every published version stays in History. Copy one into the draft, check it, and publish it again.

The look

Your look, down to the last card.

Colours, type, corners, the way cards and buttons are built, and each kind of card on its own. What a customer sees in an answer can match the rest of your app.

See every change on the phone sizes your customers hold

Catch a cramped card or a clipped label before a customer does. The preview shows every change on 11 real phone sizes and a desktop browser, in light and dark, upright or on its side, across the launcher, the welcome screen and a conversation.

Twelve themes that already read well

A look that reads well from the first tap. Each theme sets its colours, corners and message-box icons at once, checked so that no colour needs adjusting on a device. Your fonts, your logo and your words stay as they are.

Your colours, from just four

Four colours are enough to match your app. Set the background, the text, the accent and the text on it, and Rendel works out the other six roles for cards, image wells and the message box. Set any of the six yourself when your design system says otherwise.

Know what your users will see before you publish

No surprises on the device. If a colour would be hard to read, the console names the pair, shows the colour the app will draw instead and offers it in one click. A contrast problem never blocks a save: saving and publishing work either way.

Dark mode that matches how your app does it

Dark mode that looks as deliberate as your light one. Set your own dark colours, take a theme's dark version, or let Rendel work one out that keeps your accent readable on a dark ground. By default it follows the device, and on a website your page's own theme setting comes first.

  • Flutter 0.45.0 · Web 0.22.0

Your screens' own gradient behind the answers

Rendel's page can wear the gradient your screens already use: two to four colours in one of eight directions. If no text could be read on it, the device keeps a plain background.

  • Flutter 0.52.0 · Web 0.30.0

Your fonts and your type sizes

Rendel's words read like the rest of your app. Name your body and display fonts and set each text step, from Display to Caption. Fonts are named, not downloaded, so your app ships them the way it already does.

Corners that match your buttons and cards

Cards and buttons keep your app's shape. Set card corners from square to soft, and button corners from square to a full pill. Chips and the launcher follow the buttons.

Cards and buttons built the way yours are

Answer cards built the way your own are. Choose how cards sit off the page, how buttons are filled, how products are laid out, how order tracking reads and which arrows you use. Your app draws each of the five choices.

One kind of card set apart, down to its parts

Make a price stand out, or a confirm button softer, and leave the rest alone. Give product cards, info cards, lists, the order tracker or the confirmation card their own plate, image well, corner and build, then colour and size each part. In dark mode a card takes the dark theme's colours and keeps its shape.

Click the part you mean

Change the right thing the first time. Click anything in the preview to open its settings, and parts that share a colour or a corner light up together, so you see what else changes before you change it.

Around the answers

Your name on the header, your words in the box.

The header, the welcome screen and the message box are part of the look too, and so is the switch that hides Rendel.

Your logo in the header

Customers can see whose assistant they are talking to: your logo sits before its name once a conversation starts. Upload it and crop it square; a new logo reaches users only when you publish.

  • PNG, JPEG, WebP or SVG, up to 2 MB
  • Uploads are off in the demo console
  • Flutter 0.46.1 · Web 0.23.2

Your assistant's name and welcome, in your look

The first screen a customer sees speaks in your voice. The name, the welcome headline, the line under it and up to four suggestions come from Experience, and Appearance shows them in your look. One link takes you to edit the words.

A message box that matches your inputs

The box people type in looks like your own inputs. Colour the box, the words people type and the prompt, write your own prompt of up to 60 characters, and pick the glyph for attach, voice and send. Leave the prompt blank and people get the SDK's own, in their language.

Ask whether an answer helped

Learn which answers land. Turn on a thumbs up and down under each answer, and every vote is counted in Analytics.

  • Off by default
  • Flutter 0.49.0 · Web 0.26.0

Hide Rendel without a release

Pause Rendel without shipping anything. Switch off Available in this app and, from each device's next launch, the button is gone and Rendel stops opening, while calls from your own code still work. Switch it back on the same way.

The way in

A way in that fits your screens.

Rendel's button in your label, icon and style, placed where your app needs it, or no button at all and your own buttons instead.

A launcher with your word and your icon

People find help under a word they know. Write the launcher's label in up to 24 characters, show it with its icon or the icon alone, and pick one of 20 icons. Icon only still reads the label to screen readers.

  • Flutter 0.66.0 · Web 0.44.0

Your own icon, made sharp at launcher size

Your own mark stays sharp at launcher size. Upload it and the console turns it into one clean shape in the launcher's text colour, and warns you about thin lines or a wordmark that would look tiny. You see it on a light and a dark screen before anything is stored.

  • Uploads are off in the demo console
  • Flutter 0.66.0 · Web 0.44.0

Let people move the launcher out of their way

Nobody has to read around the launcher. Turn on dragging and people can push it aside: it settles on the nearer edge and keeps that place on every page, even after a restart, on that device.

  • Off by default
  • Flutter 0.66.0 · Web 0.44.0

A launcher in your own button style

Your way in can look like your own buttons. Give the launcher a gradient, a ring, a glow, a soft light and a size from 40 to 72, all published from the console. If the icon can't be read on your gradient, the button keeps the accent and the console tells you.

  • Flutter 0.79.0 · Web 0.55.0
  • Light and icon size: 0.80.0 · 0.56.0

Draw the launcher yourself, keep Rendel's behaviour

Keep your own button design and still get Rendel's behaviour. Draw the button as your own Flutter widget, and Rendel handles the tap, the label read to screen readers, the unread count, stepping aside and dragging. Appearance notices your own button and says which of its settings still apply.

  • Mobile SDK only
  • Mobile SDK 0.81.1 or later

A way in where your app needs one

The way in sits where your customers already look. In your mobile app you put Rendel's button in a corner, a bar or a settings row, and on a website it sits in a corner. Or turn it off and open Rendel from your own buttons, with one way in on screen at a time.

  • Badges: Flutter 0.73.0 · Web 0.50.0

Opens like one of your own screens

Rendel moves like one of your screens, not a pop-up. In your mobile app it opens as a sheet over the screen, and while a screen it opened is in front it shrinks to a bubble, then grows back as it was left. On a website it opens as a panel, and on a phone as a sheet with the page dimmed behind.

Every device

From the console to every device, with a way back.

What you publish is drawn by your app itself, reaches devices on their next launch, and falls back to your code's own look if anything goes wrong.

Drawn by your app, not in a web view

Answers feel native because your app draws them. On iOS and Android your app's own Flutter widgets draw every answer, and on a website Rendel draws in the page with its styles kept apart from yours. The same colour arithmetic runs in the console and both SDKs, so the colours you preview are the colours that ship.

  • All 37 component types take your look

Every look kept by name, with a fast way back

Find a look again by its name, and take one back off quickly. Name a publish, such as Autumn brand refresh, and History keeps it under that name. Owners and Admins can roll the live version back from Experience's Published versions in one confirmed step.

  • Roll back: Owners and Admins

If anything goes wrong, your app keeps its own look

If the look can't arrive, customers still see a finished assistant. Never published, offline, timed out, an error or a value out of range: in each case the app draws the look its own code sets. Settings from a newer server version are ignored, not fatal.

Your messages arrive in the same look

What your team sends looks like the rest of Rendel. Follow-ups, and an open conversation with your team, sit at the top as cards in your card colour, corners and accent: up to three at a time, from the last seven days.

  • Flutter 0.59.7 · Web 0.38.7
How Engage sends them

Your developers keep a floor in code

Your app looks right before anything is published. Your developers set a theme in code from four colours and choose light, dark or the device's setting, and the console's look sits on top of it. On Flutter they can also redraw a catalog component with your own widget.

In the demo

Halden, from draft to phone.

Halden is an invented shoe store that has had Rendel in its app for five weeks. This is the walk its demo console lets you take, with nothing to set up.

Publish a new look and watch Halden's phone pick it up

Every step is a real control in your own two-hour copy.

  1. Open the demo console. Your own copy of Halden opens straight on Appearance.
  2. The draft is waiting: v2 is live in forest green, and v3, a warmer terracotta, has never been published.
  3. Round it off. Set Card corners to 16 and Button corners to 999, and the preview follows as you type.
  4. Press Publish and confirm. The badge reads v3 live.
  5. Open the Halden app from the demo bar. It reloads in the look you published and opens Rendel on it.
  6. Changed your mind? In History, copy v2 into the draft and publish it again as v4, and Halden is green again.

Try it in the demo console

Halden's Appearance, yours for two hours with no sign-up. Publish a look and watch Halden's own phone show it.

Try the console
Compared

Part of your app, not a window on top of it.

What changes when the assistant is part of your app rather than a tool on top of it.

WhatRendelA separate chat widget
Where it is drawnInside your app: your mobile app's own widgets, no web view, and in the page on a website, with its styles kept apartOften the vendor's own messenger screen, opened over your app
How far the look goesTen colour roles, corners, six type steps, five build choices, each kind of card down to its parts, and a page gradientUsually a brand colour, a logo and a launcher image; some add a header image or a few fonts
FontsAny family your app already ships, named for body text and headingsA short list of web fonts on some tools, none on colour-only settings
Light and darkYour own dark colours, a theme's dark version or one worked out from your light ones; follows the device, or your page's own setting on the webA palette per theme, where offered
ContrastChecked as you edit, with the colour the device will draw and a one-click fixUsually left to you
Changing the lookA draft on your test build, then one Publish with no app release, and any published version back in a stepOne live settings page; some mobile SDKs take a theme file and a new build
The way inA launcher in your label, icon and button style that people can drag, or your own button with Rendel's badges and behaviourA launcher in the vendor's shape, with a position and an image to choose
Who sets it upYour coding agent reads your theme from your code into a draft, each value marked with its fileSomeone copies hex codes into a settings page

And what your team sends from Engage arrives at the top of Rendel in the same look.

Where a separate tool can be ahead: native Swift, Kotlin and React Native SDKs. Rendel's Mobile SDK is for Flutter apps today, and its Web SDK for websites.

Controls and privacy

Who can change it, and what it reveals.

The look holds nothing about your users, and only the people who set up your assistant can change it.

Who can change the look

Every save, publish and upload is checked against the person's role.

RoleEdit, save, publish, restore, uploadRoll back live
OwnerYesYes
AdminYesYes
DeveloperYesNo
AnalystSees it, read onlyNo
Conversation reviewerSees it, read onlyNo
Customer supportNo access: this role sees Support onlyNo

Nothing about your users

The look is colours, sizes, font names, your words on screen, your logo and your launcher icon. Your assistant's instructions, knowledge and actions never travel with it.

Public by design, so keep drafts plain

What you publish is served to every copy of your app. A draft is not private either: the test key ships inside test builds and can be read out of one, so keep unannounced names out of a draft.

Stored in Frankfurt

Your look, your logo and your launcher icon are kept in Frankfurt (eu-central-1). The logo and icon sit in a private store and are served only to a copy of your app that holds its key, and a draft logo only to the test key.

Nothing to download, nothing linked

Fonts are named, never linked or downloaded, and the logo and icon travel as ids, never as addresses.

What is kept, and where

Every published version stays in History, and every save and restore is in the audit log with its version. Each device keeps the last good look for its next launch, and the place a person dragged the launcher to.

What the app's call records

When your app asks for its look, Rendel notes the SDK version and platform, at most every five minutes, and which launcher it draws. On a live key it counts the device toward your plan's users, at most once a day, for 90 days after it was last seen.

What your users switch, and what you do

Your users have nothing to switch off here: their device's light or dark setting picks the theme unless your app sets one. Your team can hide Rendel for everyone with Available in this app, which hides it on screen and is not a security control.

Turn it on

Nothing extra to install or pay.

Appearance comes with the SDK your app already runs and with every plan, so turning it on is a few steps in the console.

Your app runs the SDK

Appearance needs no code of its own. When your app starts, the Mobile and Web SDK fetches the published look. Current versions: Flutter 0.82.0, Web 0.57.0.

Your team opens Assistant › Appearance

Pick a theme or set your colours, then Save draft to try it and Publish to send it. Owners, Admins and Developers can publish.

Every plan, no messages used

Appearance is on every plan, the free Pilot included, and editing or publishing it uses none of your messages.

What your developers decide in code

Light, dark or the device's setting; where Rendel's button sits, or opening Rendel from your own buttons; your own launcher widget; bundling the fonts you name; and remoteConfig: false to pin a build to its code.

The SDK version each part needs

An older SDK simply ignores settings it does not know yet.

Part of the lookMobile SDK (Flutter)Web SDK
Colours, fonts, sizes, corners, published from the consoleEvery versionEvery version
Header logo0.46.10.23.2
Dark mode0.45.00.22.0
Helpful? under answers0.49.00.26.0
Background gradient0.52.00.30.0
Cards at the top of Rendel0.59.70.38.7
Launcher label style, 20 icons, your own icon, dragging0.66.00.44.0
Unread count and dot on the launcher0.73.00.50.0
Launcher gradient, ring, glow and size0.79.00.55.0
Launcher light, icon size and glow strength0.80.00.56.0
Your own launcher widget0.81.1 or laterNot on the web: launcher: false and your own button

What teams ask before they start.

  • No. In your mobile app, your app's own Flutter widgets draw every answer, with no web view. On a website, Rendel draws in your page with its styles kept apart from yours. Either way it uses your colours, fonts, corners and card styles, set in Assistant › Appearance.

  • Yes. Name a body font and, if you like, a display font for headings. Fonts are named, never downloaded, so your app has to include the font, as it does for its own screens. On a website with no font named, Rendel takes your page's own body font.

  • Yes. By default it follows the device. On a website it reads your page's data-theme first, then the browser's setting, and watches both. In a mobile app your developers choose light, dark or the device's setting in code. Set your own dark colours, take a theme's dark version, or let Rendel work one out.

  • Yes. Every published version stays in History: copy one into the draft, check it on your test build and publish it again. Owners and Admins can also roll the live version back from Experience's Published versions.

  • The console tells you while you edit: which pair falls under 4.5:1 for text or 3:1 for a control's edge, the colour the device will draw instead, and a button to take it. It never blocks a save. On the device, a colour that cannot be read is deepened so the words stay readable.

  • Yes. On a website, turn the launcher off and open Rendel from your own button, or show the launcher only on some pages. In a mobile app you place Rendel's button where you want it, or open Rendel from any button of yours. Rendel keeps one way in on screen at a time.

  • Its label, up to 24 characters, or the icon alone; one of 20 icons or your own; a gradient, ring, glow, soft light and a size from 40 to 72; and whether people can drag it. All of it is published from the console. In a Flutter app you can also draw the button yourself and keep Rendel's badges.

  • Yes. Choose shadow, outline or flat cards, filled or outlined buttons, product tiles, lists or photos, and three order-tracking styles. Then give each kind of card its own colours, corners and part sizes, such as a larger price or a softer confirm button.

  • Yes. AI setup reads your light and dark colours, corners, font, card style and logo from your code and writes them into the Appearance draft, each marked with the file it came from. It never publishes. On a live app, a later code sync waits in Sync review on Home.

  • The look holds nothing about your users: it is colours, sizes, font names, your words on screen, your logo and your launcher icon. It never carries your instructions, knowledge or actions. It is stored in Frankfurt (eu-central-1), with the logo and icon in a private store served only to your app's key.

  • No extra cost. Appearance is on every plan, the free Pilot included, and editing or publishing uses no messages. Owners, Admins and Developers can edit, save, publish and restore it, and Owners and Admins can also roll the live version back. Analysts and conversation reviewers see it read only.

  • Not yet. Rendel's Mobile SDK is for Flutter apps on iOS and Android, and its Web SDK is for websites. There is no native Swift, Kotlin or React Native SDK today; Platform support in the docs says where each one stands.

Put it in your app this week.

Start free on your own, or tell us what your customers do most and we’ll show you that exact workflow, working, in a tailored demo.

  • PilotFree400 messages a month
  • Starter$199 / month4,000 messages a month
  • Growth$799 / month20,000 messages a month
Every plan, and the estimatorOr try a live store’s console first, yours for two hours

Prefer email?

sales@rendel.ai

Prefer to write first?

Tell us about your app and we’ll show the right workflow in a tailored demo.

Help us tailor the demoOptional

We use this to get in touch about the demo and, if a partner introduced you, to credit them. We never sell it. See the privacy policy.