Skip to content

Documentation

TelBuddy documentation for Twilio and Telnyx

TelBuddy is a no-code dashboard on top of a phone number you already own in your own Twilio or Telnyx account. These docs explain how to connect that account, run a shared team inbox, route voice, build phone menus, add an optional AI receptionist, and stay honest about A2P. If you want the product tour before the manuals, start at how it works.


Screenshot walkthroughs live in the Help Center.

Documentation library

🚀
Getting Started
Connect Twilio or Telnyx, sync numbers, and confirm a test call and text before you invite the team.
6 articles
 💬
Texting & Inbox
Shared threads, MMS, templates, handoffs, and AI draft or auto-reply modes.
6 articles
 👤
Contacts
Popover actions, history, notes, and files. Deliberately lightweight so it fits any industry, and not a full CRM.
2 articles
 📞
Voice & Calling
Forwarding with primary and backup plus a whisper message, voicemail in the dashboard, business-hours routing, queues, and click-to-call.
5 articles
 ☎️
IVR & Phone Menus
No-code phone menus in a form editor or a drag-and-drop flow canvas. A menu belongs to the account, so one tree can answer several numbers.
2 articles
 🤖
AI Features
The optional AI voice receptionist, knowledge base, transfer rules, appointments, and transcripts. AI has its own allowances and renews on its own date.
6 articles
 🔌
Twilio & Telnyx
Bring-your-own-carrier detail: provider is chosen per number, what connecting actually changes, and what stays yours when you disconnect.
2 articles
 🧑‍🤝‍🧑
Team & Accounts
Admin and agent roles, invitations, seat limits, and sub-accounts for more than one business under one login.
4 articles
 ✅
Compliance
A2P 10DLC stays with your carrier and your legal entity. TelBuddy does not register it for you. Plus STOP handling and what the inbox shows.
2 articles

What these docs cover

Everything here assumes the bring-your-own-carrier model: you keep the number, the carrier bill, and the compliance registration. TelBuddy is the software layer, meaning the shared inbox, forwarding, voicemail, business hours, IVR, contacts, and team roles. The AI voice receptionist is documented as an optional add-on. It is not included in core plans and it is not part of the free trial.

Pick a topic below, or follow the start-here path if you are connecting your first number today.

Start here (first hour)

  1. Connect a carrier and confirm a test call and text.
  2. Text as a team with shared SMS and MMS, templates, and AI-drafted replies.
  3. Make voice behave with forwarding, voicemail, and hours, then phone menus if callers need press 1 or press 2.
  4. Optional: turn on AI voice only after core routing already works.

Begin with Getting Started below, then work through the library in order. Carrier mixing and A2P have their own sections when you need them.

How to use this hub

Implementers should follow Getting Started, then Texting, then Voice, then IVR, and read Compliance before sending real customer traffic.

Admins should read Team and Accounts before inviting seats, and the carrier section before mixing Twilio and Telnyx inside one company.

Anyone enabling AI voice should finish knowledge base setup and place a test call before pointing a customer-facing number at the receptionist. Regulated verticals need transfer rules decided up front, not after go-live.

What these docs will not do

They will not invent features. If something is not shipping, it is not documented as though it were. They will not walk through server internals or how any protection is implemented. Public pages and product screens only.

Can't find what you're looking for?

Our team can answer directly.

Contact Support Quick Answers (FAQ)