Most people have had a bad experience with a chatbot. The little pop-up that ignores what you typed and tries to push you into a contact form. The bullet-list menu that doesn't have the option you actually need. The one that confidently makes up an answer and sends you down a wrong path.
When we started building Tuqlas, we made a short list of things we never wanted to do. Here's what's on it — and how it shapes the product.
It only answers from what you've taught it
The single biggest reason chatbots feel untrustworthy is that they hallucinate. They fill in gaps with plausible-sounding fiction. We refuse to do that.
A Tuqlas bot answers from your own content — the files, FAQs, and pages you uploaded. If it doesn't know the answer, it says so. Clearly. No guessing.
A chatbot that admits it doesn't know is infinitely more useful than one that fakes confidence. Visitors trust honesty.
It doesn't make people wait
Answers stream as they're generated, so visitors see the reply forming in real time. There's no spinning cursor, no "thinking…" delay. It feels like a fast typist on the other end, not a load screen.
The difference seems small, but it changes how people use the bot. They actually have a conversation, instead of clicking off after waiting eight seconds.
It speaks the visitor's language naturally
No rigid menus. No "please choose option 1." People type the way they actually talk, and the bot meets them there — whether they're asking in English, Filipino, or mixing both within the same sentence.
It captures leads when it makes sense — not by interrupting
A lot of chatbots open with "What's your email?" before the visitor has any reason to give it. That's the fastest way to get ignored.
Tuqlas waits for the actual signal — someone asking for a quote, wanting a callback, sharing their email naturally as part of the conversation. Then it captures the lead and tells you. Visitors don't feel cornered, and the leads you do get are actually qualified.
It gets out of the way
The single best feature of a chatbot is that the visitor stops noticing it's a bot. They asked a question, they got a good answer, they kept moving toward whatever they came to do.
The goal isn't to make people talk to the bot. It's to remove the friction between them and the thing they actually want.
A short list, lived honestly
That's it. There's no secret formula. We made a few design choices, took them seriously, and built around them:
- Answer from your real content
- Stream replies instantly
- Speak naturally, in any language the visitor brings
- Capture leads only when the signal is real
- Disappear when you've done your job
It turns out that's most of what makes a chatbot useful.
Try Tuqlas on your site — free to start, works on any website with one script tag.