Blog
Analogies and real architecture behind building AI agents with Wetel.
-
Chatbot, assistant or AI employee: what is the difference?
Three terms that get used as if they meant the same thing. A plain guide for managers: what each one can do, what a chatbot is missing, and the parts that make an AI employee, with what is live in Wetel today and what is still being built.
-
Supervised or autonomous? What an AI employee should be allowed to do on its own
Two promises hide behind 'AI employee': one acts alone, the other checks with you. A practical way to decide what an AI employee may do on its own, before you hand over the keys.
-
Building a front desk agent that delegates to specialists, entirely from the dashboard
Updated:A click-through walkthrough of Wetel's SUB_AGENT dispatch node and the certified operation picker — how to build one coordinator agent that hands a conversation off to three specialist agents at once, each pulling real, live data out of a connected partner system, without writing a partner integration by hand.
-
Concurrent sub-agents and a certified GraphQL catalog: building a multi-partner AI front desk without writing three integrations
Updated:How Wetel's SUB_AGENT v2 concurrent dispatch and its certified operation catalog combine to let one AI agent reach into multiple partner APIs (OmniChat, Nortia, aisCRM) at once, all three firing concurrently with real data — verified live with real overlapping timestamps and an honest account of what it took to get there.
-
How to connect Lark to a Wetel AI agent, step by step
A complete, reproducible walkthrough — from creating a Lark app in the developer console to a working AI agent that answers real questions about your Lark Base. No code required for most of it, and the one real bug we hit along the way (with the fix) is worth reading even if you're not touching Lark.
-
Why your AI agent needs to interrupt you back
Updated:Most voice AI platforms call themselves 'interruptible' when they really mean turn-taking. Real barge-in needs voice-activity detection, frame-level audio handling, and a workflow engine that can cancel itself mid-thought — here's what that actually takes to build, and how Wetel does it.