> 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/dapta-docs-es/agentes-de-voz-ia/numeros-de-telefono/como-agregar-un-numero-de-telefono-para-realizar-pruebas-en-dapta.md).

# Cómo agregar un número de teléfono para realizar pruebas en Dapta

Agrega un número de prueba gratis en Dapta —uno nuevo al mes en planes pagos— para llamar sin gastar créditos; a otros números sí se cobran.

Recientemente, lanzamos una funcionalidad que te permite realizar llamadas a números de prueba sin consumir créditos en Dapta.

{% hint style="info" %}
Los números de prueba están disponibles en los planes pagos, incluida la prueba gratuita. Solo las llamadas a un número de prueba registrado son gratis; una llamada a cualquier otro número consume créditos, aunque la estés haciendo para probar. Puedes agregar un número de prueba nuevo una vez al mes, y necesitas saldo de créditos para poder llamar.
{% endhint %}

En el siguiente tutorial, te enseńamos como hacerlo fácilmente.

{% embed url="<https://www.loom.com/share/d1afcba522654b4798385c1eaf958654?sid=68657919-25b9-4d10-874b-be972af181d7>" %}


---

# 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/dapta-docs-es/agentes-de-voz-ia/numeros-de-telefono/como-agregar-un-numero-de-telefono-para-realizar-pruebas-en-dapta.md?ask=<question>&goal=<user_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.