Property configuration

Each property has its own settings. We set them up when a property goes live and change them when you ask. Send changes to hello@nogeek.org.

Switched on#

Whether the assistant runs for the property. When it is off, the chat shows Chat is not enabled for this destination. We can switch a property off at once if it is ever needed.

Allowed websites#

The website addresses where the assistant may run for this property. When the chat starts, it checks the address of the page it is on against this list. On any other website it shows This website is not authorised to embed this widget.

Each entry is an origin: the scheme, the host name and any port, with no path. Matching is exact, apart from upper or lower case and a trailing slash, so list every variant the property uses:

TEXT
https://www.wrenwickbay.co.uk
https://wrenwickbay.co.uk
https://book.wrenwickbay.co.uk

There are no wildcards. Add a staging website as a separate entry while you test.

Site knowledge#

Facts about the property that aren't in your platform: parking, dogs, directions, the nearest shop, hot tub rules, local tips. The assistant treats them as facts about the site and answers from them. Up to 6,000 characters.

Site knowledge can't set prices, discounts or availability. Those only ever come from your platform, at the time the guest asks. If the text contains anything that reads like an instruction to the assistant, it is ignored.

FAQs#

Questions and answers the assistant answers from. Up to 40, each question and each answer up to 800 characters. The same rules apply as for site knowledge.

Name, tone and sign-off#

SettingExampleEffect
Assistant namePoppyWhat the assistant calls itself. Without one, it is the property's booking assistant.
ToneWarm and a little playful. Use the guest's first name.How it writes.
Sign-offSee you by the sea!A line it may use when a conversation naturally ends.
Extra guidanceMention the farm shop to families.Further instructions from the property.
Header labelBooking assistantThe label under the property's name in the chat header. Defaults to AI booking assistant.

None of these can override the assistant's rules. It always says it is an AI assistant, only states prices and availability read from your platform, never takes card details in the chat, and stays on the subject of the property and booking.

Greeting and quick replies#

The first message the guest sees, and the buttons under it. By default the buttons are Check dates and prices, See the accommodation, Ask a question and Message the team. Their labels can change, but each button must do one of the things the assistant already handles.

Teaser#

The message that can appear next to the chat button in bubble mode:

SettingWhat happens
Timed (default)The teaser appears once, about four seconds after the page loads.
Button onlyJust the chat button, no teaser.
OffNo teaser.

The property can also have its own teaser text. data-launcher-label on the script tag overrides it. See Teaser text.

Measurement holdout#

To measure what the assistant adds, a property can hold back a share of visitors, up to half, who see no chat button. It is off unless you ask for it. It only applies in bubble mode, never to inline embeds or the activity widget, and never to visitors whose consent is denied.

Conversation length#

Each conversation allows up to 40 guest messages by default, which is plenty for a booking. We can change this for a property.

Book a 20-minute call