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

# Connecting your inbox

> Turning an approved Apple Business Register account into a working Tied inbox.

Once Apple approves your registration and you have linked Tied as your MSP, this part is short. The slow work was [registration](/channels/apple-messages/registration).

## What you should have in hand

<ResponseField name="Apple Business Register approval" type="required">
  Your account is approved and your brand assets are live.
</ResponseField>

<ResponseField name="Tied linked as your MSP" type="required">
  Nominated inside Apple Business Register. Without this, messages have nowhere to route.
</ResponseField>

<ResponseField name="Your Apple credentials" type="required">
  The identifiers Apple issues on approval.
</ResponseField>

<ResponseField name="An Advanced or Enterprise plan" type="required">
  AMB is not available on Starter or Business. See [Plans](/pricing/plans).
</ResponseField>

## Connect it

<Steps>
  <Step title="Create the inbox" icon="inbox">
    Create an Apple Messages for Business inbox and supply the credentials Apple issued. The inbox is the
    configured surface — channel plus team, hours and agent.
  </Step>

  <Step title="Attach your AI agent" icon="bot">
    Point the inbox at the agent that should handle it. Without one, every conversation waits for a human.
  </Step>

  <Step title="Set routing and hours" icon="users-round">
    Which team owns it, how conversations are assigned, and what happens outside business hours. These
    are per-inbox — your AMB inbox can behave differently from your web chat inbox.
  </Step>

  <Step title="Send a test message" icon="send">
    Message your own business from an iPhone through one of your [entry points](/channels/apple-messages/entry-points).
    Confirm it arrives in the right inbox, routes to the right team, and that the agent responds.
  </Step>

  <Step title="Test a rich primitive" icon="sparkles">
    Send a List Picker or a Rich Link and confirm it renders correctly on the device. Rich primitives are
    the reason you are on this channel — verify one before you call it live.
  </Step>
</Steps>

<Warning>
  **Test on a real iPhone, not a simulator.** Apple Pay, Face ID authorisation and iMessage Extensions
  behave differently in simulation, and those are precisely the features worth having AMB for.
</Warning>

## Verify before you publish entry points

Once your Maps listing carries a Message button, customers will use it. Before that goes live, confirm:

* A conversation reaches the intended inbox
* The AI agent responds, and its knowledge covers what people will actually ask
* Handoff to a human works, and someone is watching
* At least one rich primitive renders correctly on a real device
* Out-of-hours behaviour is set to something you would be happy for a customer to receive at 2am

## Running more than one brand

Each AMB agent is one verified Apple business sender, typically one per brand. Multi-brand operations provision multiple agents, each with its own inbox, and there are no agent fees however many you run. See [Apple Messages fees](/pricing/channel-fees/apple-messages).

## Next

<CardGroup cols={2}>
  <Card title="Rich Feature Messages" icon="sparkles" href="/channels/apple-messages/rich-feature-messages">
    The eight primitives, now that you can send them.
  </Card>

  <Card title="Known limitations" icon="triangle-alert" href="/channels/apple-messages/limitations">
    Read before designing a flow around this channel.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.