# Look, wording and language

> Match Tamr's AI waiter to your app at runtime: colours, fonts, corners, the waiter's name and labels, starters, diet and allergen restrictions, theme, language and context.

Source: https://tamr.link/docs/sdks/appearance

The restaurant sets how the waiter looks and talks in **Settings > Waiter in your app**. Your app can change some of it at runtime, field by field, while the restaurant leaves **Allow the app to customise** on (the default).

**Who wins, lowest to highest:** Tamr's defaults, the restaurant's brand, the menu's brand, the restaurant's "Waiter in your app" settings, then your app's values.

## The setters

| Setter | Fields | Notes |
| --- | --- | --- |
| `setAppearance` | `scheme` (`light`, `dark`, `auto`), `accent`, `accentSecondary`, `paper`, `text` (colours as `#RRGGBB`), `displayFont`, `uiFont`, `corners` (`round`, `soft`, `square`), `showHeader`, `showLogo`, `showStarters`, `showBack`, `hideVoice`, and the [chat's parts](#the-chats-parts) | `null` resets one field to the restaurant's. Pass `appearance` when you create the controller so the first frame is already styled. "Powered by Tamr" always shows. |
| `setText` | `waiterName` (40 characters), `welcomeTitle` (80), `welcomeSubtitle` (140), `placeholder` (60), `labels`: `newChat`, `tryAgain`, `addToCart`, `checkout`, `callWaiter`, `thinking` (40 each) | Wording travels over the bridge only, never in a URL. |
| `setStarters` | Up to 6 suggestions, each a `label` (60) and an optional `prompt` (300) | An empty list brings back the restaurant's. |
| `setRestrictions` | `avoidAllergens`: `gluten`, `dairy`, `egg`, `nuts`, `sesame`, `soy`, `fish`, `shellfish`, `peanut`, `mustard`. `keepDiets`: `vegan`, `vegetarian`, `gluten_free`, `halal`, `kosher`, `dairy_free`, `nut_free`, `keto` | Only ever adds to the diner's own; it can't lift one. The waiter checks these in code before it proposes a dish. |
| `setTheme` | `light` or `dark` | Your app's mode. |
| `setLocale` | A language tag, such as `ar`, `fr` or `en-GB` | The chat's own wording and the reply language. Arabic is right to left. |
| `setContext` | `branch`, `mode` (`dine_in`, `pickup`, `delivery`), `table` (a hint), `tableScan`, `currency` | Where and how the diner is served. |

Every setter's value is kept and sent again whenever the page reloads, so set it once.

## The chat's parts

From Web, Flutter, iOS and Android 1.2.0 and React Native 1.3.0, `setAppearance` also styles each part of the chat. Every field is optional, and one left out keeps the restaurant's choice, then the page's own.

| Field | Values | What it changes |
| --- | --- | --- |
| `headerColor` | `#RRGGBB` | The bar at the top. Its words take black or white, whichever reads. |
| `bubbleColor` | `#RRGGBB` | The diner's own messages, with black or white words. |
| `buttonColor` | `#RRGGBB` | Send, Checkout and the other main buttons. |
| `cardColor` | `#RRGGBB` | Dish cards and the cart card; the words on them follow. |
| `mutedColor` | `#RRGGBB` | Quieter words: notes and details. Nudged until it reads on your `paper`. |
| `lineColor` | `#RRGGBB` | The thin lines between parts. |
| `positiveColor` | `#RRGGBB` | "Added" and "In your cart". Nudged until it reads on your `paper`. |
| `header` | `plain`, `brand` | `brand` fills the bar with your accent. A `headerColor` wins over it. |
| `bubble` | `soft`, `brand` | `brand` fills the diner's messages with your accent. A `bubbleColor` wins over it. |
| `buttons` | `pill`, `rounded`, `square` | The shape of the buttons and chips. |
| `starterStyle` | `chips`, `cards` | The welcome's starters. Left unset: cards for up to four, else chips. |
| `showWaiterName` | `true`, `false` | The waiter's name in the bar. |
| `showWelcome` | `true`, `false` | The waiter's greeting when the chat opens. |
| `showQuickReplies` | `true`, `false` | The short replies the waiter suggests under an answer. |
| `showNewChat` | `true`, `false` | "New chat" under the conversation. |
| `showCheckout` | `true`, `false` | Checkout on the card of dishes the waiter put in your app's cart. Hide it when your app has its own. |

The restaurant can set every one of these in **Settings > Waiter in your app**, and its dashboard preview shows them. `showPoweredBy` is still accepted but ignored.

## An appearance message

What `setAppearance` sends, as the contract's fixtures hold it:

appearance:

```json
{
  "v": 1,
  "id": "msg_0089",
  "type": "appearance",
  "ts": 1792310489000,
  "data": {
    "scheme": "auto",
    "accent": "#1F7A4D",
    "accentSecondary": "#C8C8C4",
    "paper": "#FFFFFF",
    "text": "#131313",
    "displayFont": "Avenir Next",
    "uiFont": "Roboto",
    "corners": "soft",
    "showHeader": false,
    "showLogo": true,
    "showStarters": true,
    "showBack": true,
    "showPoweredBy": false,
    "hideVoice": true,
    "hideReviews": true,
    "hideRetailSuggestions": true,
    "hideLoyalty": true
  }
}
```

## What your app can't do

Turn on a feature the restaurant turned off, show voice notes once the restaurant hid them, change prices or menu content, lift an allergen or diet restriction, or hide "Powered by Tamr". With **Allow the app to customise** off, the page ignores your appearance, wording and starters. To hide Tamr's own reviews, take-home suggestions or treats, see [Hiding features](https://tamr.link/docs/guides/hiding-features).

## Languages

The restaurant writes wording and starters per language. A diner in a language the restaurant didn't set sees Tamr's translated words and the waiter's own greeting.

## In debug builds

From each SDK's next release, a value Tamr would refuse (a colour that isn't `#RRGGBB`, seven starters, a 41-character table) stops at the call in a debug build, naming the message, the field and the rule. A release build still sends a bad look or wording field, and the page drops that field alone, with one warning line such as `[tamr] shell: appearance: dropped accent (format)`.
