Arlo
Reads your work tools and asks approval before anything consequential goes out
Arlo is an AI agent you reach on iMessage and SMS. To start, text a number. It messages you first rather than waiting to be asked.
At a glance
| Channels | |
|---|---|
| How you start | Text a number |
| Who starts it | Messages you first |
| Is there an app | No app Nothing to install at any point |
| Categories | Personal assistants, Work, Email |
| Can do | Email,Web research,Phone calls,Persistent memory,Task management,Documents,Calls people for you |
| Connects to | Gmail, Google Calendar, Slack, Microsoft Teams, Notion, Linear, GitHub, HubSpot, Salesforce, Google Docs |
| Pricing | Unknown |
| Number type | Wireless |
| Contact number | +1 407 234 1884 |
| First message, pre-written | “hey Arlo”Composed by the product, sent by you. See why that matters. |
| Runs on | Linq (iMessage and FaceTime), Telnyx (phone calls and A2P SMS) (source) |
| Browses with | Anchor Browser, Daytona (source) |
| Number carrier | T-Mobile (Omnipoint Miami E License) block holder, before number portability |
| Status | Live |
Who is behind it
| Company | Unknown |
|---|---|
| Founders | Unknown |
| Based in | Unknown |
| Funding | Unknown |
| Investors | Unknown |
| Traction | Unknown |
Data and policy
| Trains on your conversations | Not stated in the policy |
|---|---|
| Data of people who never signed up | Not stated in the policy |
| If you cancel | Not stated in the policy |
| Model providers named | None named |
| Jurisdiction | Not stated in the policy |
| Availability | Not stated |
Read from the published policy on . Quotes are verbatim. We report what the document says and link it; we do not interpret its legal effect, and policies change.
How it works
Arlo is meant to be texted like a capable teammate. It reads Gmail, Slack, Notion, Linear and a CRM, and connects to more than 3,000 integrations.
Its stated approval model is the interesting part and the direct opposite of the act-first products in this category: it asks permission before anything consequential goes out. For anyone designing an agent that sends messages on a person's behalf, that boundary between what needs confirmation and what does not is the central design question, and Arlo answers it conservatively.
Source: arlo.sh, checked 2026-09-06. Channel support is inferred from public descriptions rather than stated by the vendor. How we source this.