> For the complete documentation index, see [llms.txt](https://docs.textmaddie.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.textmaddie.com/readme.md).

# Text Maddie

An iMessage agent that talks to your leads, built and run for you.

Text Maddie gives your business an agent that holds real conversations over iMessage. It answers questions, follows up, books what needs booking, and keeps notes on every contact. It works from a phone number your leads and customers text like they would text a person.

The agent is built for you by the Text Maddie team. You do not write prompts, wire up integrations, or configure models. You tell us what the agent should do, we build it, and you watch it work from your dashboard.

## What you get

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>A live dashboard</strong></td><td>Every conversation, every reply, and what the agent was thinking when it sent one.</td><td><a href="/your-dashboard/overview.md">Overview</a></td></tr><tr><td><strong>Dedicated phone lines</strong></td><td>Managed for you, never shared, and replaced before they cost you a lead.</td><td><a href="/your-dashboard/lines.md">Lines</a></td></tr><tr><td><strong>Slack notifications</strong></td><td>The agent pings your team in Slack when a human needs to step in.</td><td><a href="/your-dashboard/integrations.md">Integrations</a></td></tr><tr><td><strong>An API</strong></td><td>Trigger the agent from your own systems when something happens on your side.</td><td><a href="/working-with-us/working-with-the-team.md">Working with the Text Maddie team</a></td></tr></tbody></table>

## Start here

{% stepper %}
{% step %}

#### Understand the working relationship

We build and maintain your agent. Knowing what you control and what to ask us for saves the most time up front.

[how-it-works.md](/getting-started/how-it-works.md)
{% endstep %}

{% step %}

#### Get into your dashboard

Sign in, find your agent, and learn what the eight pages do.

[signing-in.md](/getting-started/signing-in.md)
{% endstep %}

{% step %}

#### Watch a conversation

Open Conversations, pick a thread, and read how the agent handled it.

[conversations.md](/your-dashboard/conversations.md)
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Anything you cannot do yourself, we do for you. Email your Text Maddie contact and we handle it. See [working-with-the-team.md](/working-with-us/working-with-the-team.md).
{% endhint %}


---

# 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.textmaddie.com/readme.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.