Archives
All the articles I've archived.
-
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.
-
Tools, workflows, skills, agents: the words everyone uses differently
"Just give the agent some tools" hides four distinct layers that get built separately, tested separately, and fail separately. A call-center analogy for the terminology every AI vendor uses, but rarely defines the same way twice.