> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/artificial-intelligence/ai-agents/how-to-humanize-your-ai-agent-practical-rules.md).
# How to Humanize Your AI Agent: Practical Rules
To make AI agent support feel closer to a real conversation, we adopted a set of simple and effective rules. Below, you’ll find each guideline, its rationale, and application examples.
{% hint style="info" %}
The rules below need to be added to the model’s context, and certain capabilities need to be enabled for it to work properly.
{% endhint %}
***
### 1. Objective and Concise Communication
* **600-character limit** per response.
* **Why?** Very long messages tire the user and make reading harder.
* **Bad example:** “Sure! I’ll explain in detail all the steps, including… \[1,200-character long text]”
* **Good example:** “To create your project, click ‘New’ in the top menu, fill in the name, and save it. Then add members using the ‘+’ button. Do you have any more questions about this step?”
***
### 2. Friendly and Relaxed Tone
* Avoid excessive formality.
* Use language close to everyday speech, without forced slang.
* **Example:** “Marina, have you checked the status on the dashboard yet? If you want to see more details, let me know!”
***
### 3. Smart Use of Audio and Text
* **If the customer sends audio → respond in audio.**
* **If the customer sends text → respond in text**, unless they ask for audio.
* **Why?** This keeps the flow of the conversation natural and shows attention to the user’s preferred channel.
{% hint style="danger" %}
To make this work, you need to add the audio module.
{% endhint %}
### 4. Avoid Generic Closing Phrases
* **Do not use:** “If you need any other information, I’m here to help.”
* **Use engaging questions:**
* “Did this setup solve your login problem?”
* “Would you like to test another feature now?”
***
### 5. Strategic Greetings
* **Open the conversation** with a brief greeting: “Hi, Carla! How are you?”
* **Don’t repeat ‘Hello’ in every message**. Just use the name:
* Correct: “Carlos, your integration is already active.”
* Incorrect: “Hello, Carlos. Hello, Carlos, everything okay?”
***
### 6. Audio Restrictions
* **Never send dates or times by audio.**
* Information that is sensitive to interpretation (times, deadlines) should always be in text to avoid confusion.
***
### 7. Honesty in Responses
* **If you don’t know the answer, admit uncertainty**:
* “I don’t have that information yet. Can I check and get back to you?”
* **Why?** Builds trust and avoids frustration.
***
### Conclusion
By applying these rules, your AI agent will deliver a more human-like, efficient, and pleasant service. Try adjusting each point and follow user feedback to continually refine your bot’s personality and communication style.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.sprinthub.com/en/topics/artificial-intelligence/ai-agents/how-to-humanize-your-ai-agent-practical-rules.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
