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

# Texts

> Read and send customer texts, handle website-form leads, and book from a thread.

Texts is the shared inbox for customer text messages and website-form leads. Open it from **Desk → Texts** (`/desk/texts`).

> [!NOTE]
>
> Texting is on, including automatic texts. If an admin ever pauses sending, you'll see: **"Texting is turned off for now. You can read messages, but sending is paused."** You can still read every thread.

## Find a conversation

* The page opens on the thread list with nothing selected. Pick a thread to read it.
* Use the **Leads** and **Chats** tabs to switch between new leads and ongoing conversations.
* Filter chips sit in one row: **Open**, **Unattended**, **Mine**, **All**, **ServiceTitan sync**, and **Texts only**. **ServiceTitan sync** shows only chats imported from ServiceTitan. **Mine** shows threads assigned to you. Turn on **Texts only** to keep SMS threads and hide call, voice, and email rows in the list. Counts and the list follow that filter.
* **Mine** / **Assign to me** starts **off** for every role. The inbox opens on all threads. Turn on **Mine** when you only want threads assigned to you. Nothing is deleted when the filter changes.
* When a thread is linked to a customer, the contact name in the list and in the thread header opens that customer's profile the same way a name does on the Calls desk (customer flyout when it's available, otherwise the Customers page). Names that aren't matched stay plain text.
* Each thread has a colored **source tag**: Website form, Phone call, Text message, ServiceTitan sync, Sales app, Added by staff, Referral, or Imported/Other. For website leads, the tag names the form the lead came from instead of just saying "Website form" (see [Website-form leads](#website-form-leads)). The source tag, line, campaign and assignee are shown in the thread header and the details column on the right, not on the rows of the list.
* A new text from a customer goes into their most recently active thread.

### What each row in the list shows

The thread list reads like a running feed of texts in and out, newest first. Each row shows:

* **Who it's with.** The customer's name, or their phone number when the thread isn't linked to a customer.
* **The latest message.** A text the customer sent has no label in front of it, so you read their words as they wrote them. A text we sent starts with **You:** when you sent it, or the sender's first name (like **Sam:**) when a teammate did.
* **Texts we sent on a website lead.** When the latest message on a website-form lead is a text from you or a teammate, like a proposal link, the row shows that text as it was sent. The form summary only shows when the customer's form is the latest message.
* **Photos and failed sends.** A message that's only a photo shows a small picture icon and **Photo**. A text that didn't go through shows **Not delivered** in red. The preview is never blank.
* **When it happened.** Under an hour shows minutes, like **9m**. Earlier today shows a clock time, like **3:42 PM**. Then **Yesterday**, then a short date. Times use the timezone in your profile, and the zone is named once at the top of the list instead of on every row. **Yesterday** means the previous calendar day in your timezone, not "24 hours ago."
* **Unread.** Unread rows show the name and preview in bold, plus a blue dot on the left. The blue dot means a new text from the customer that nobody has answered yet. A text we send never adds it. It follows the same rule as the red dot on Texts in the side menu (see [What the counts and dots mean](#what-the-counts-and-dots-mean)).

On a phone, each row is at least a thumb's height and the preview stays on one line.

> [!NOTE]
>
> The preview shows the newest text with that customer from any of our lines, not just yours. If a teammate texted the customer after you did, you'll see their message, with their first name in front. You still get one row per thread. This applies to everyone who can text, including office staff and installers. It only fills in the preview on threads you already have; a customer you've never texted doesn't show up as a new row because a teammate texted them.

When a customer has a website-form lead that isn't on anyone's line yet and also a thread you own, the list shows them once, as your thread. Your thread already includes the form, so you don't get two rows with the same message. The form lead isn't closed or changed, and a link straight to it still opens it. If the form lead was assigned to someone, your thread also shows under **Mine** for that person, so it doesn't drop out of their list. The chip counts and the Texts badge count the customer once.

Sending, how threads are grouped, and STOP opt-outs work the same as before.

## See the whole conversation with a customer

When you open a thread you own, you see every text with that customer from all of our lines, not only the ones on your own line. A teammate's texts to the customer show in order with the rest, and messages a teammate sent are labeled **Sent by** with their name. Replies from the customer to a teammate show up too.

This is how Texts works for everyone who can text, including office staff and installers.

* You only see the conversation for customers you can already reach through one of your own threads. Texts with other customers stay hidden.
* On an unowned website-form lead, office and sales staff still see texts from other lines. Installers do not.
* When you reply, the text still goes out from your own line.

### Customer details on the right

When you open a thread, the details column on the right lists the customer's **Name**, **Phone**, our number, **Property** and **Source**:

* **Name** is a link to the customer's page when the thread is linked to a customer. Unmatched names stay plain text. Customer names link to the customer page across Field Ops; see [Getting to the customer page](https://help.yournewdoor.com/customers/open-a-customer.md).
* **Property** shows the customer's service address. Field Ops uses the customer's own property address first, then the address on the job linked to the thread, then the address on the customer's most recent job. If none of those has an address, the **Property** row is left out instead of showing a dash.

### What the counts and dots mean

The numbers in Texts match what you see:

* The number on each filter chip (**Open**, **All**, **Mine**, **Unattended**, **ServiceTitan sync**) and the **N threads** line above the list count exactly the rows that filter shows. Threads without a phone number still appear in the list and are counted.
* The **Open** filter shows only conversations that are still open. A thread that's been closed, archived or resolved leaves **Open** but stays under **All**.
* The cyan badge on **Texts** in the side menu, and the Texts badge on mobile, show a number: how many open text conversations you can see. It's the same number as the **Open** chip on the Texts page. The badge is a light blue pill with the count in it, and it hides when the count is zero.
* The red dot on Texts is separate and has no number. It lights up when a customer has texted and nobody has answered yet, and you haven't read it. The blue dot on a row in the list follows the same rule.
* Only a new text from the customer lights the dots. Texts we send never do: your own, a teammate's, automatic form replies, booking confirmations and chats synced from ServiceTitan. When someone replies, the blue dot clears as soon as the list refreshes, even if that thread is open, and a new customer text shows the dot without reopening the thread.
* Once anyone on the team replies to the customer, from any line, that text counts as answered and the thread isn't unread for anyone. A new text from the customer after the reply makes it unread again.
* When you send a text, that thread is marked read for you.
* Automatic texts don't count as an answer. That includes the automatic reply a website-form lead gets, [booking confirmation texts](https://help.yournewdoor.com/bookings/confirmation-texts.md), and any other text the system sends. If one of these goes out after the customer's text, the thread stays unread until a person replies or opens it.
* If you haven't opened Texts yet in this browser, the badge and the dot stay off until it loads. Opening a customer's Texts panel on the customer page doesn't change the badge.

> [!NOTE]
>
> Reading a thread is tracked per person, in your own browser. Opening a thread on one computer doesn't clear it on another. A reply from anyone on the team clears it everywhere.

## ServiceTitan chats

Chats imported from ServiceTitan are tagged **ServiceTitan sync** instead of **Text message**. You'll see the tag in the thread header, on the thread's **Source** row, and on each imported message in the customer's timeline. Use the **ServiceTitan sync** filter chip to see only these chats.

* **View in ServiceTitan** opens the original conversation in ServiceTitan in a new tab. It's in the thread header and on each imported message.
* Photos from a ServiceTitan chat show as a **View photo in ServiceTitan** link instead of a picture, because those photos need a ServiceTitan login.
* One ServiceTitan chat can cover more than one job. When the job changes between messages, the thread shows a divider with the job name and a small **inferred** label. Field Ops guesses these dividers from the imported data, so treat them as a guide, not a record. Messages without a job get no divider.
* If an imported chat is missing a phone number, that spot is just left blank.

> [!NOTE]
>
> The customer's lead source isn't changed by this. Customers who came in from ServiceTitan still show **Office import** in reporting.

## Link straight to a thread

A Texts link that names a specific thread opens that thread directly, as long as you're allowed to see it. If you aren't, the thread doesn't open, and Texts doesn't start a new message in its place.

## Assign a thread

Use **Assign to me** or **Unassign** on a thread. Door Experts, Design Concierges, office and sales staff can assign. Installers, assessors and technicians can't. Assigning works the same in every view.

## Website-form leads

The globe source tag on a website lead shows which form it came from, such as **Repair form**, **Project upload**, **Services**, **Warranty claim** or **Contact survey**. You'll see the same name in the thread header and on the thread's **Source** row. Field Ops picks the name in this order:

1. The form on the customer's most recent website message.
2. If that's missing, the first form the customer ever filled out.
3. If neither is known, it just says **Website form**.

Customers imported from the old Sales Center show **Project upload (legacy)**. A form the app doesn't recognize shows its name cleaned up into plain words. Long names are cut off with "…"; hover over the tag to see the full name. The tag looks the same for every role.

A website-form card shows a short summary. Click **Show details** for the full form, including the **Submitted from** row. Website-form leads show for everyone with access to Texts.

### When the customer already has a thread

A website form from someone you already text with lands in the conversation they already have, instead of starting a second one. This covers every website form, including **Project upload**. The form shows up as a new incoming message with the same form card, so you see it right after their last text.

Field Ops finds the thread like this:

1. The thread with the phone number on the form that had the most recent activity, whoever owns it, including the shared company line. This only counts when that thread isn't linked to anyone yet, or is already linked to the customer the form matches.
2. Otherwise, if the form matches a customer, that customer's most recent text thread.
3. If neither is found, a new form thread opens for that customer, or a new unassigned form thread when the form doesn't match anyone.

The existing thread keeps its owner, status, subject and customer. Nothing is merged or closed, and a closed thread stays closed even when a new form lands in it. If the website sends the same form twice, it only shows once.

> [!NOTE]
>
> A form never lands in a different customer's thread. If the form's email matches one customer but its phone number belongs to a thread linked to someone else, the form goes on the matched customer's own latest thread (or a new one) instead. That phone number isn't copied onto the matched customer, and the other customer's thread and record don't change.

### Customer photos on a website form

When a customer uploads door photos on a website form (like **Project upload**), the card shows them as small thumbnails right in the summary, so you don't need to open **Show details** to see them.

* Photos are grouped by door, with one labeled row each, like **Door 1 photos** and **Door 2 photos**. Photos for the same door always land in one row, even if the form labeled them a little differently.
* Photos that aren't tied to a door, like the ones on a **Warranty claim** form, show together in a single **Photos** row instead of one row per photo.
* Click a thumbnail to open the full-size photo in a new tab.
* If a photo can't load, you'll see a small bordered box with its label instead.

> [!NOTE]
>
> Only photos stored by our website form show as thumbnails. A link from anywhere else stays as plain text you can still read, and Field Ops won't load it automatically.

These photos are shown on the card only. They aren't saved to the job or customer record yet.

Above the summary, a small grey **Form** line tells you which website form the lead filled out and the page they sent it from, for example **Form · warranty\_claim** followed by the page address. If the website didn't send a form name or page, the line doesn't show.

### Address from a website form

When a website form includes a full street address, Field Ops looks it up and saves it as the customer's property. The address then shows on the customer page and in the **Property** row in Texts, so you don't have to type it in.

* The form needs a house number, a street and a ZIP. Without them, Field Ops doesn't look the address up.
* The address is saved only when the lookup is a confident match: the house number, ZIP and state are the same as on the form, and the street name matches. If the lookup isn't sure, no address is saved.
* A customer who already has a property keeps it. A form never changes their address or adds a second one.
* Whatever happens with the address, the lead still comes in, and the address the customer typed stays on the form under **Show details**. When nothing was saved, add the address yourself in [Edit customer details](https://help.yournewdoor.com/customers/edit-details.md).

### Text a website-form lead

You can text a website-form lead from Texts the same way you text any other thread you can see. When you send on an unowned form thread, Field Ops claims it to the shared company line so the send goes through. If the customer first submitted without a phone and later fills out a form that includes one, that number is added to their customer record when it was missing. This is skipped when the number already belongs to a different customer or to a thread linked to a different customer. Opening Texts from a customer link prefers a sibling thread that already has a phone you can text when the same customer has more than one thread.

## Open Texts from a customer

Most **Text** buttons (customer page, **+** menu, appointment flyouts, bookings, the consult schedule and jobs) open the customer page with its [Texts rail](https://help.yournewdoor.com/customers/add-menu.md#texts-rail-on-the-customer-page) open, so you text right next to the customer's file. The rail uses the same thread and composer as this desk. The **Message** button on the Sales Kanban, and links straight to `/desk/texts`, still open this desk.

When Texts opens for a customer, here's what you get:

* If the customer already has a thread, that thread opens. When they have more than one, a thread you can actually text wins over an empty website-form thread.
* If there's no thread yet, a new message opens with the customer's name in the header and their phone already in **To**.
* If the customer has no phone, you'll see the usual **No phone on file** message.
* If another customer has the same phone number, their thread doesn't open. A thread with that number is only reused when it isn't linked to a customer yet or is already this customer's. Otherwise Field Ops starts a new thread for this customer, and the other customer's thread stays with them.

## Send a text

**1. Start or open a thread**

Open an existing thread, or click **+ New text**. New text searches your existing contacts first.

**2. Write the message**

The composer has emoji, 5 saved templates, and photo attach.

**3. Attach photos (optional)**

Up to 3 photos per text: jpg, png, gif, webp or heic, max 5 MB each. If one fails, you'll see **"Photo didn't send. Tap to retry."**

You can also drag photos onto the composer of an open thread and they're added the same way as photo attach. A brand-new message (**+ New text**, or a new compose from a customer link) doesn't take dropped photos yet, so send the first text, then add photos in the thread. Dropping photos works the same way on the [Texts rail](https://help.yournewdoor.com/customers/add-menu.md#texts-rail-on-the-customer-page) on a customer page.

When the thread is linked to a customer, photos you send and photos the customer sends also show in **Photos** on their customer page and job, captioned **From Text**. See [Photos from texts](https://help.yournewdoor.com/customers/photos-and-files.md#photos-from-texts).

**4. Send**

The first text to a customer automatically includes a STOP opt-out line. Quiet hours apply.

> [!WARNING]
>
> If you see **"We can't tell if this text went out. Don't resend yet. Close this and check the thread."**, don't send it again. Check the thread first so the customer doesn't get two texts.

### When the number is already a customer

If you type a number in **+ New text** that belongs to a customer, you'll see **"This number is already"** followed by the customer's name. Click **Use this customer** to text them.

* If that customer has a text thread, you'll see **already has a text thread** with **Open existing thread** and **Start a new thread anyway**.
* **Open existing thread** opens that customer's own thread. A thread with the number counts only when it isn't linked to any customer yet or is already this customer's, and their own thread comes first.
* When another customer has the same number, their thread never opens under this customer's name. If this customer has no thread of their own, a new message opens instead.

## Automatic booking confirmation texts

Field Ops can text a customer when their appointment is booked, or when their consult moves to a new time. Changing a booked site assessment, install, repair or warranty visit doesn't text; the office can send the booked text again with **Resend confirmation**. These texts are switched off until an admin turns them on. When they're on, the text lands in the customer's thread like any other message, sent by the system with no staff signature. Customers who replied STOP are skipped, quiet hours apply, and canceling an appointment doesn't text. See [Booking confirmation texts](https://help.yournewdoor.com/bookings/confirmation-texts.md) for the exact wording and rules.

## Shared company line

A shared company texting line is available.

## Book a job from a thread

Click **Book job** in a thread. It opens a new booking (`/bookings/new`) with the customer's name, phone and customer record already filled in. See [Bookings and consults](https://help.yournewdoor.com/guides/bookings.md).


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