> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nuphos.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# iMessage

> Pair a phone to talk to the agent over iMessage.

Once your phone is paired, the agent becomes a contact you can text — handy for
getting paged and replying on the go. Setup requires the **Administrator** role.

## Connect

<Steps>
  <Step title="Generate a pairing code">
    In **Settings → Workspace → iMessage**, generate a pairing code. It's 8
    characters (using an unambiguous alphabet — no `0`/`O` or `1`/`I`) and expires
    in 15 minutes.
  </Step>

  <Step title="Text the code">
    From the phone you want to link, send `pair <CODE>` to the Nuphos iMessage
    number. The code is single-use.
  </Step>

  <Step title="Confirm">
    Once verified, the phone is linked to your team and can talk to the agent.
  </Step>
</Steps>

## In the Nuphos app

iMessage conversations are real [agent sessions](/agent/sessions) — they show up
in the team's workspace with their full transcript. Linked devices are managed
in **Settings → Workspace → iMessage**: admins map phones to users (numbers in
**E.164** format — a leading `+`, country code, then the number, e.g.
`+15551234567`), remove devices, and can reset a conversation thread to start
fresh.

## What the agent can do for you

Everything it can do in the app, from your Messages thread:

* Text a question — *"is prod healthy?"* — and the agent checks your
  [connectors](/connectors/overview) and replies, splitting long answers into
  readable chunks. See [Chat with the agent](/collaboration/chat-agent).
* Get paged by a [trigger](/agent/triggers), then steer the investigation by
  replying — without opening a laptop.
* Approve or decline a proposed [plan](/agent/plans) from wherever you are.

## Permissions & authorization

iMessage is an **entry point**, not an escape hatch — the same boundaries apply
as in the app:

* **Hard boundary — who is acting.** The phone-to-user mapping decides which
  Nuphos user a text acts as, and that user's
  [access control](/security/access-control) applies: their role, the member
  allow-lists on each account, and the credentials selected for the session. A
  phone is only linked after the pairing handshake above, and admins can unlink
  it at any time.
* **Soft boundary — what may run.** Changes still require
  [plan approval](/security/approvals), and
  [Auto-authorization](/security/auto-mode) still governs each command — your
  standing rules apply identically to sessions started over iMessage.

## Good to know

* Pairing codes are **single-use and expire in 15 minutes** — generate a fresh
  one per device.
* If a phone changes hands, unlink it in Settings; the new owner would otherwise
  be texting as the mapped user.