> ## Documentation Index > Fetch the complete documentation index at: https://docs.firetone.com.au/llms.txt > Use this file to discover all available pages before exploring further. # FireTone > A multi-tenant cloud phone system: inbound services, outbound campaigns, and AI that answers, assists and is billed for. FireTone runs phone calls for more than one organisation on shared infrastructure. It answers inbound numbers, places outbound campaigns, gives agents a console, and puts AI on the call — answering it, helping the person who answers it, or writing what it should say. Your numbers, your campaigns, your agents and your AI. For the people taking calls. Short, and worth reading once. Tenants, carriers, rates and the machines it all runs on. Everything the panel does, the panel does through this. ## Two ideas that explain most of the product **Inbound is a process. Outbound is a campaign.** A *process* is one named service — its numbers, its opening hours, the workflow it runs and where a caller lands when the workflow does not take them. A *campaign* is orchestrated outbound: a list of people, a reason for calling them, and a pace. Dialling a number by hand is deliberately neither, which is why it lives on an agent's desk rather than in either menu. **The API is the authority, and the panel only reflects it.** Every screen is gated on a named permission the server grants; the panel keeps no second copy of who may do what. If a screen is missing, the grant is. **Reading the money.** Where you are not permitted to see a cost or a margin, FireTone shows it as *withheld* — never as zero. A zero is a claim that something cost nothing, and that claim is almost always false. The same principle runs through the product: absent and zero are different facts.