> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/ai-voice-agents/phone-numbers/inbound-calls-and-how-to-activate-them.md). # Inbound Calls and How to Activate Them An inbound line lets customers reach an AI Agent through a Dapta-activated number; US numbers are bought directly, other countries through Support. ### What is an Inbound Line and How Does It Work? An inbound line allows you to receive incoming calls through a phone number activated via Dapta. This means your customers can call you directly and be attended by an AI Agent or redirected according to the configuration you choose. To activate this feature, Dapta handles the purchase of the phone number, which involves an additional monthly credit cost. ### Associated Costs US numbers are bought directly in **Voice Agents → Phone Numbers** and show their monthly price in credits before you confirm. Numbers in other countries are set up by Support and quoted in credits. Every current rate is on the credits page: {% content-ref url="/pages/GXYct6Ze1oeIlY1toPVo" %} [Billing and credits](/my-account/how-credits-work-in-dapta.md) {% endcontent-ref %} ### Validation and Activation Process 1. Send your request to or to the tech person supporting you with the implementation. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.dapta.ai/ai-voice-agents/phone-numbers/inbound-calls-and-how-to-activate-them.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.