> 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-text-agents/setting-up-your-text-agent.md).

# Setting Up your Text Agent

- [Text Agent Settings Overview](https://docs.dapta.ai/ai-text-agents/setting-up-your-text-agent/text-agent-settings-overview.md): See what each text agent setting controls, Language, Identity Name, Purpose, Model and Temperature, and why editing the prompt actually changes behavior.
- [Dapta Auto](https://docs.dapta.ai/ai-text-agents/setting-up-your-text-agent/dapta-auto.md): Dapta Auto is the model Dapta chooses and keeps up to date for your Text Agent. New agents start on it, it reads images and voice notes, and it costs 40 credits per answer.
- [Conversation behavior](https://docs.dapta.ai/ai-text-agents/setting-up-your-text-agent/conversation-behavior.md): Set your Text Agent's inactivity timeout, reply delay, split replies and WhatsApp typing indicator. Check follow-up timing before publishing changes.
- [Text Agent Actions](https://docs.dapta.ai/ai-text-agents/setting-up-your-text-agent/text-agent-actions.md): Create API actions that call another webhook, or Transfer to a human actions that hand a conversation to a person or a team inside Dapta and set the message the customer receives at that moment.
- [Schedule Appointments with dCal](https://docs.dapta.ai/ai-text-agents/setting-up-your-text-agent/schedule-appointments-with-dapta-calendars.md): Let your Text Agent offer your real open times and book the appointment inside the chat. Add the Schedule appointments action, pick the meeting, and every booking lands in your dCal account.
- [Brains for Text Agents](https://docs.dapta.ai/ai-text-agents/setting-up-your-text-agent/brains-for-text-agents.md): Create a Brain from the Settings tab, add up to 25 sources, web pages, files, or text, and track it through Pending, In Process, and Completed states.
- [Playground: Testing your Text AI Agents](https://docs.dapta.ai/ai-text-agents/setting-up-your-text-agent/playground-testing-your-text-ai-agents.md): Save a Text Agent draft, test it in Playground with a fresh conversation, and publish only after checking its responses and actions.
- [Post-Conversation Analysis](https://docs.dapta.ai/ai-text-agents/setting-up-your-text-agent/post-conversation-analysis.md): Automatically extract structured data from every conversation and send results to external systems via webhook when a conversation ends.
- [CRM Pipeline Sync](https://docs.dapta.ai/ai-text-agents/setting-up-your-text-agent/crm-pipeline-sync.md): Automatically move contacts to the right stage in your CRM pipeline after every conversation. Connect GoHighLevel or HubSpot, choose eligible stages, and let the agent handle the rest.
- [Follow-ups](https://docs.dapta.ai/ai-text-agents/setting-up-your-text-agent/follow-ups.md): Automatically re-engage users who go silent mid-conversation by sending scheduled follow-up messages after periods of inactivity.


---

# 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-text-agents/setting-up-your-text-agent.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.