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

# Email addresses and branded phone numbers

> How your agents send email (a Lawtte address on day one, or your own Microsoft 365 or Google inbox) and how to get phone numbers that show your firm's name on caller ID and texts registered to your firm.

Your agents should look like your firm, not like a robot. This page covers where
their emails come from, and how to get numbers that show your name.

All of it lives in **Agents → Settings → Channels** and **Settings → Phone numbers**.

## Email

### Your Lawtte address, ready on day one

Every firm gets a sending address the moment it signs up, with nothing to connect:

```
yourfirm@updates.lawtte.ai
```

It's listed in your inboxes as **Your default line**. You choose the **name people
see** and where **replies go**, for example your intake inbox.

> [!NOTE]
>
> This address can send but can't read. Follow-up agents need to see whether someone
> replied, so they run in an inbox you connect (below).

### Connect your own inbox

For follow-ups that reply inside your own email threads, connect the inbox the
emails go out from:

**1. Open Agents → Settings → Channels**

Under **Email**, press **Connect an inbox**.

**2. Pick your provider**

**Connect Microsoft 365** or **Connect Google**, and sign in.

**3. Turn on Send and Listen**

**Send from** lets agents reply as that inbox. **Listen to** lets them see
replies, so they stop when someone answers.

**4. Set a default (optional)**

**Set as default** makes templates and the Agent Builder pick this inbox first.

Replies from your agents show up in that inbox's Sent folder, in the same thread,
just like you wrote them. You can disconnect an inbox at any time.

> [!TIP]
>
> Using Google Workspace or Microsoft 365 across the firm? Lawtte can connect inboxes
> for the whole firm at once, so teammates don't each sign in. Ask your Lawtte account
> team.

## Phone numbers

Open **Settings → Phone numbers** to see every number, what it's used for, whether it
can text, and what people see on caller ID.

### Branded caller ID

A branded number shows your firm's name when it calls, instead of just digits, so
people can see who's calling before they pick up.

**1. Request it**

Next to a number, press **Request branding**. Or press **Request a new number**,
choose an area code if you want one, and enter your **Caller ID name**.

**2. Choose the name**

Up to 15 characters, letters, numbers and spaces only. For example,
`OCONNOR LAW`.

**3. We set it up**

The Lawtte team sets it up, usually within a business day. The number then shows
**Branded · YOUR NAME** in the list.

> [!TIP]
>
> Connected to Claude or Grok Bot? Just ask: "Get us a new number with OUR FIRM on
> caller ID." It sends the same request.

### Texts that come from your firm

Texting numbers are either **branded** or **not branded**, and you'll see which next
to each one in **Agents → Settings → Channels**.

| | What people see |
| - | - |
| **Branded** | Texts registered to your firm with the carriers. With iMessage, they also get your contact card, with your name and logo. |
| **Not branded** | Texts sent under Lawtte's registration. The first text to each person ends with "Your Firm via Lawtte. Reply STOP to opt out." |

To get branded texting, ask your Lawtte account team. We register your firm with the
carriers (10DLC), and texting from that registration starts once it's approved.

### Getting a number

* **Studio accounts:** your receptionist's number comes with calling and texting.
  Texting from a new US number starts within minutes, once the carriers add it.
* **Firms Lawtte manages:** press **Request a new number** on **Settings → Phone
  numbers**. Call agents call from your default calling number, which you set in
  **Agents → Settings → Channels**.

Every number follows your [Do Not Call list](https://api.lawtte.ai/mcp/limits-and-safety.md) and text
opt-outs, whichever agent uses it.


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