[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Reply to SimpleTexting Inbox texts with an AI agent

> Read the SimpleTexting Inbox, answer simple customer texts in your voice and hand the rest to a team member before the customer gives up waiting.

Source: https://cotlet.dev/integrations/simpletexting-api-mcp-server/reply-to-inbox-texts

A customer texts to move an appointment, the text sits in the Inbox for hours, and by the time someone answers the customer has booked somewhere else.

Cotlet does it in your own SimpleTexting account with list\_conversations, get\_conversation, send\_message and assign\_conversation, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=simpletexting) [All SimpleTexting tools](https://cotlet.dev/integrations/simpletexting-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can SimpleTexting do this on its own?

SimpleTexting has no Inbox endpoint in its API documentation (checked 23 Oct 2026), and its Zapier app has a New Incoming Message trigger but no action that reads a conversation. Templates and autoresponders send a fixed text; nothing reads the thread and answers it.

## How you do it in SimpleTexting today

1. Open Inbox. Replies to your individual texts and to campaigns both arrive there.
2. Use the filter by time waiting or time received to find who has waited longest.
3. Open a conversation, read it, then answer by hand or with a template or AI Assist.
4. For anything you cannot answer, choose a team member from the dropdown at the top of the conversation, or leave a private note.
5. Mark conversations that are done as resolved, or snooze them until later. Nothing in the Inbox answers for you.

## How to reply to SimpleTexting Inbox texts with an AI agent

Prompt

```
Go through my SimpleTexting Inbox. Reply to simple scheduling questions from my hours and open slots, and list everything else for me.
```

1. 01  
### Find who is waiting  
list\_conversations returns the Inbox. The agent keeps conversations whose last message is incoming, the customer's, and leaves out the ones where the last text is yours.
2. 02  
### Read the whole thread  
get\_conversation brings every text and private note. A note from a team member such as "refund approved, tell her Friday" changes the answer, so the agent reads it before writing.
3. 03  
### Sort into answer or hand over  
Questions about hours, slots or an address that your prompt covers are answered. Anything about money, complaints or a medical or legal matter goes to the list for you.
4. 04  
### Reply or assign  
send\_message sends the answer in the same conversation and waits for your OK by default. For the rest, assign\_conversation sets the team member you named, which sends nothing to the customer.
5. 05  
### Check before sending  
Right before sending, the agent reads the thread once more. If a team member already replied, it skips the contact.

### What you get back

Example data

```
Waiting in the Inbox: 7
Replied 4:
- Dana Whitfield: moved cleaning to Friday 10 am
- Sam Okafor: sent the address
Assigned 2 to Priya Nair (billing)
Left for you 1: "I was charged twice"
```

### Other ways to ask

- Every morning at 8, list conversations that have waited more than 2 hours and draft replies without sending them.
- Assign everything that mentions billing to Priya Nair and reply only to scheduling questions.
- Reply to anyone asking for our hours with the hours text, and skip conversations a team member already touched.

## What SimpleTexting allows, and what to know first

- SimpleTexting calls its reply tool templates and says conversations can be assigned, snoozed, marked resolved and kept with private notes.
- You can assign a conversation only to a team member who has accepted the invitation under Team.
- SimpleTexting has two roles, Admin and Team Member; a team member is a sub-account you can set up for one person, a department or a location.
- SimpleTexting lets you limit a team member to incoming texts from contacts on their own list.

send\_message asks for your OK by default. To run it daily without you, switch confirmation off for that tool in your dashboard.

Sources: [SimpleTexting: Two-way messaging and the Inbox](https://simpletexting.com/features/2-way-messaging/) · [SimpleTexting: Team members](https://simpletexting.com/features/multi-user-access/) · [SimpleTexting on Zapier MCP](https://zapier.com/mcp/simpletexting)

## Call send\_message from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/simpletexting/messages \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"contact_phone":"+12125550147","text":"Yes, Friday works. We have 10 am open. Reply YES to confirm."}'
```

Example response

```
{
"message_id": "m_77d0c4",
"conversation_id": "c_8f21a6",
"contact_phone": "+12125550147",
"direction": "outgoing",
"status": "sent",
"at": "2026-10-23T09:30:00-04:00"
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is simpletexting\_write → send\_message. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/simpletexting-api-mcp-server.md#automations)

## SimpleTexting tools this automation uses

__Cotlet SimpleTexting tools used to reply to SimpleTexting Inbox texts with an AI agent__
| Tool | Parameters |
| -------------------- | ---------------------------------- |
| list\_conversations | query, assigned\_to, limit, cursor |
| get\_conversation | conversation\_id |
| send\_message | contact\_phone, text |
| assign\_conversation | conversation\_id, assignee |

[All 12 SimpleTexting tools with descriptions](https://cotlet.dev/integrations/simpletexting-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect SimpleTexting to Cotlet?

Yes. You sign in to SimpleTexting yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get SimpleTexting once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More SimpleTexting automations

- [Schedule a SimpleTexting campaign to a list or segment](https://cotlet.dev/integrations/simpletexting-api-mcp-server/schedule-text-campaigns.md)
- [Add customers to a SimpleTexting list from a sheet or CRM](https://cotlet.dev/integrations/simpletexting-api-mcp-server/add-customers-to-a-text-list.md)
- [SimpleTexting API and MCP server: every tool](https://cotlet.dev/integrations/simpletexting-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to SimpleTexting.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with SimpleTexting.

[Sign up free](https://cotlet.dev/app/signup?app=simpletexting)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.