Why you can trust it
What the assistant promises
Answers are generated by AI
A visible label in the conversation always shows clearly that you're talking to an automated assistant, not a person.
Answers only from verified sources
Information comes from the destination's official knowledge base, curated by OMD Țara Dornelor — never guessed and never pulled from other sites.
Doesn't ask for personal data
Ask anything without an account, a form or signing up — the assistant doesn't need your data to help you.
Never invents prices or schedules
It never makes up prices, schedules or availability — when it doesn't know, it says so plainly and points you to the tourist information point or the destination's channels.
How it answers
A real conversation
A real conversation example — an illustration, not a working chat on this page.
What it knows
What you can ask
Attractions
What to see, what to visit, how long a trail takes.
Events
What's happening in the destination, with real dates.
Accommodation
Properties and real availability, not a static list.
Restaurants
Where to eat, what kind of kitchen, hours.
Ski slopes
Snow conditions, whenever the operator has published a report.
Transport
Train and bus — from the schedules entered by OMD Țara Dornelor.
Weather
The forecast for the coming days.
Where it knows it from
The sources, in the order they matter
When two sources disagree about the same thing, the one on top wins.
- 1
The destination's operational base
Accommodation, events, ski slopes and transport, entered directly by OMD Țara Dornelor. When anything else disagrees, this has the final word.
- 2
The assistant's wiki
Pages written or generated specifically for the conversation, based on the facts above.
- 2b
The destination's editorial site
Story and context from the Țara Dornelor tourism site — it complements, not replaces, the operational data.
- 3
Uploaded documents
Materials added by OMD Țara Dornelor, with an expiry date — they drop out of answers on their own once expired.
- 4
Weather
The forecast queried live, straight from the weather service, separately from the other sources.
What it doesn't do
Where it stops, on purpose
Doesn't estimate schedules
It doesn't make up departure times, durations or route numbers. When it doesn't have the exact data, it says so plainly and points to the official source — never a search link it made up.
Doesn't book anything itself
It never completes a booking inside the conversation. For accommodation, events or packages, it gives you the direct link to the real booking mechanism.
Doesn't ask for personal data to answer
You can ask anything without an account and without leaving an e-mail. An e-mail is requested ONLY if you choose to receive a follow-up, never to get a simple answer.
Doesn't make legally binding decisions
It doesn't approve, reject or decide anything with consequences for you — it's an informational guide, not an authority. Any decision that legally affects you stays with the operator or the competent institution.
The widget, on your site
The same assistant, mounted on the member's site
Ecosystem members can put the assistant on their own site in a few lines — it's not a separate integration, it's the same brain, the same knowledge base.
What you get
A script
A <script> tag you paste into the page — or the npm package, if the site is React/Next.
Your own key
Issued from the admin panel, tied to your account — the plaintext is shown once, at creation.
Verified origin
The key only works from the domain added to the allowlist — a request from another origin is refused.
The key's domain
A destination key sees the whole catalog; an accommodation-unit key sees everything except other accommodation units.
Issuing the key
Keys are issued from the assistant's admin panel, in the configuration section — by the OMD Țara Dornelor operator or the platform administrator.
What it looks like, in practice
<script
src="https://chatbot.omd-taradornelor.ro/chatbot-widget.iife.js"
data-api-url="https://chatbot.omd-taradornelor.ro"
data-api-key="tdc_••••••••••"
data-position="bottom-right"
data-language="ro"
defer
></script>The key in the example is truncated — yours is generated from the admin panel and shown only once.
