Resources
Community
Builders solving the same problems you are, in public. The community is where prompt patterns, flow templates, and hard-won carrier lore get shared before they ever reach the docs.
Discord
The fastest place to get unstuck. Katexs engineers are in the server daily, and most questions get a useful answer from another builder before we get to them.
#build-help
Prompt, flow, and tool problems. Paste your config and a transcript for the fastest answer.
#telephony
Numbers, SIP, carriers, registration, and answer-rate war stories.
#integrations
CRM mappings, n8n recipes, and custom tool schemas people are willing to share.
#showcase
Working agents with numbers you can call. The best way to learn what good sounds like.
#changelog
Every release, mirrored from What's New, with the team on hand for follow-ups.
Forum
For longer-lived material: architecture write-ups, prompt-engineering deep dives, and searchable answers to questions that recur. Threads stay indexed, which makes the forum the better home for anything you would want to find again in six months.
- Patterns — Reusable approaches to routing, escalation, verification, and confirmation.
- Templates — Exportable Flow and Agent definitions you can import straight into Creator.
- Feature requests — Public, votable, and read by the product team every week.
Showcase
A directory of live agents built by the community, each with a short write-up covering the use case, the stack, and one thing that was harder than expected. Submissions are reviewed for quality rather than volume — we would rather have thirty excellent entries than three hundred demos.
- 1
Build something real
Showcase entries must be agents handling actual traffic, not sandbox toys.
- 2
Write the honest version
Include what you tried first and why it did not work. That is the part everyone learns from.
- 3
Submit in #showcase
Tag a moderator. Reviewed entries are published within a week and featured in the newsletter.
Ground rules
- Be specific — "It doesn't work" gets sympathy; a config, a transcript, and a call ID get a fix.
- Share back — If the community solved your problem, post the solution. That is the entire mechanism.
- No recruiting or spam — Hiring and services go in the dedicated channel, once.
- Respect confidentiality — Your customers did not agree to appear in a Discord thread.