AI agent vs chatbot
A chatbot talks. Trelinx AI Agent gets it done.
Most “AI” on Singapore SME websites is a text widget that answers FAQs and then says “let me get a human to assist.” That human already has hands full answering calls and WhatsApp while attending to walk-ins. Trelinx AI Agent books the appointment, takes the deposit, routes the caller to the right outlet, and picks up the phone in Singlish at 2am. Human escalation only when needed.
The difference between a generic chatbot and your Trelinx AI Agent? Tooling integrations. It plugs into the tools you already run — calendar, payments, telephony, CRM and more. It's not just talking, it gets the right things done.
Side-by-side
4 axes that actually matter.
Answers questions, then escalates to a human for anything real
Books, reschedules, takes the deposit, pulls the record, runs your workflow — mid-conversation, through your own tools
Scripted flows + canned replies · goes blank off-script
Your real data — your menus, prices, policies, FAQs. Answers accurately, no making things up
A text box on your website. Misses every phone call
Voice + WhatsApp. Answers the call in under a second, in Singlish + 14 other languages (WhatsApp in 4)
One widget, one site, no idea you run 7 outlets
Multi-outlet native — routes each caller to the right branch, one dashboard across every outlet
Why “just talks” costs you
A chatbot that can't book is a missed booking. It collects the enquiry, says “our team will get back to you,” and your front desk finds 40 messages on Monday morning — half of them already booked with someone who picked up.
captures the lead → waits for a human → the caller calls your competitor who answered.
captures the lead → books it on the spot → confirmation lands on the customer's WhatsApp before they've put the phone down.
No CPF. No MC. No “let me check and get back to you.”
“But I already have a chatbot”
You probably do — a widget that handles “what are your opening hours.” Keep it if you like. But the calls it can't take, the bookings it can't close, and the after-hours messages it leaves on read are the gap an AI Agent fills. The question isn't chatbot or not — it's who's actually closing the booking when your team's busy.
What “acts” looks like
Books + collects payment through your provider (Google Calendar · HitPay · Stripe · Shopify bundled) — not a parallel system you reconcile later.
Custom tool execution mid-conversation pulls a customer record, checks stock, triggers your workflow.
Connects to what you already run your POS, booking system, CRM. Anything beyond the standard list is built per-need, from S$888.
Routes to the right brain hands between specialised agents (sales · support · bookings), or to a human with full context so the customer never repeats themselves.
See the full breakdown on /features · see the price on /pricing
Questions operators ask
What's the actual difference between a chatbot and an AI agent?
A chatbot answers questions from a script. An AI agent acts — it books, takes payment, pulls records and runs your workflows mid-conversation, on voice and WhatsApp, grounded in your own data.
Can it really take a booking and payment on its own?
Yes. It books into your calendar and collects payment through your own provider (HitPay, Stripe), then confirms on WhatsApp — no human in the loop unless you want one.
Will it make things up like some chatbots do?
No. It answers only from your own content (menus, prices, policies). Off-topic or unsure → it says so or routes to a human.
Does it work on the phone, or just website chat?
Both. Voice (answers calls in under a second, Singlish + 14 other languages) and WhatsApp (4 languages). A chatbot is text-only.
I run multiple outlets — can it handle that?
Yes. It routes each caller to the right branch and shows every outlet in one dashboard. Most chat widgets are single-site.
Do I have to throw out my current chatbot?
No. Trelinx covers the calls and bookings a text widget can't — keep what works, fill the gap.