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.

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

SetterFieldsNotes
setAppearancescheme (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 partsnull 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.
setTextwaiterName (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.
setStartersUp to 6 suggestions, each a label (60) and an optional prompt (300)An empty list brings back the restaurant's.
setRestrictionsavoidAllergens: gluten, dairy, egg, nuts, sesame, soy, fish, shellfish, peanut, mustard. keepDiets: vegan, vegetarian, gluten_free, halal, kosher, dairy_free, nut_free, ketoOnly ever adds to the diner's own; it can't lift one. The waiter checks these in code before it proposes a dish.
setThemelight or darkYour app's mode.
setLocaleA language tag, such as ar, fr or en-GBThe chat's own wording and the reply language. Arabic is right to left.
setContextbranch, mode (dine_in, pickup, delivery), table (a hint), tableScan, currencyWhere 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.

FieldValuesWhat it changes
headerColor#RRGGBBThe bar at the top. Its words take black or white, whichever reads.
bubbleColor#RRGGBBThe diner's own messages, with black or white words.
buttonColor#RRGGBBSend, Checkout and the other main buttons.
cardColor#RRGGBBDish cards and the cart card; the words on them follow.
mutedColor#RRGGBBQuieter words: notes and details. Nudged until it reads on your paper.
lineColor#RRGGBBThe thin lines between parts.
positiveColor#RRGGBB"Added" and "In your cart". Nudged until it reads on your paper.
headerplain, brandbrand fills the bar with your accent. A headerColor wins over it.
bubblesoft, brandbrand fills the diner's messages with your accent. A bubbleColor wins over it.
buttonspill, rounded, squareThe shape of the buttons and chips.
starterStylechips, cardsThe welcome's starters. Left unset: cards for up to four, else chips.
showWaiterNametrue, falseThe waiter's name in the bar.
showWelcometrue, falseThe waiter's greeting when the chat opens.
showQuickRepliestrue, falseThe short replies the waiter suggests under an answer.
showNewChattrue, false"New chat" under the conversation.
showCheckouttrue, falseCheckout 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
{
  "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.

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).