> For the complete documentation index, see [llms.txt](https://help.getweddingos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getweddingos.com/clients/client-communication.md).

# Communication & Email

WeddingOS centralizes all communication with your clients — emails you send, replies you receive, and automated follow-ups — so nothing falls through the cracks and your whole team has visibility into every conversation.

***

## Sending an email

You can send an email to a client from two places:

**From the client's email thread** — go to the Emails tab on the client detail page and click **View Email Thread**. From that page, click **Compose** — the To field pre-fills with the client's address automatically.

**From the Inbox** — click **Compose** in the nav, search for the client, and write your message. Best for sending across multiple clients without navigating to each record.

Emails go out from your connected Gmail address. If Google isn't connected, they send from the system address instead. See [Google Integration](broken://pages/J073ORMX9thKitpZ3kzL).

***

## Receiving replies

When a client replies, the message syncs into WeddingOS automatically and appears in their email thread. You don't need to check Gmail separately — replies come here.

Any email from a client whose address is in WeddingOS will sync in, not just replies to emails you sent from the app.

***

## Email threads

All communication with a client is grouped into a single thread on their Emails tab. Your whole team can see the thread — if Sammy sent an email last week and you're picking up the conversation today, the full history is right there.

The global **Inbox** in the nav shows threads across all clients in one view, sorted by most recent activity.

***

## Automated emails

WeddingOS can send automated follow-up emails on your behalf — no manual action required. These include:

* **Lead nurture sequence** — a series of follow-up emails sent to new leads over the first several days after inquiry. Stops automatically if the lead replies or their status changes.
* **Proposal follow-ups** — reminder emails sent at set intervals after a proposal is sent and hasn't been signed yet.

Automated emails are configured by your admin under **Settings → Email Templates**. You can see whether a lead is enrolled in the nurture sequence from the Leads list.

***

## Proposal signing link

When you send a proposal, the client receives a branded email with a link to review and sign electronically. This is handled automatically through the proposal flow — you don't send it manually.

If a client needs a reminder or the link has expired, you can resend it from their detail page. See [Sending a Proposal](/sales/sending-a-proposal.md).

***

## A note on sending from the right account

WeddingOS always sends from the credentials of whoever is **logged in** — not the assigned planner. If you're covering for a teammate and send an email while logged in as yourself, it goes from your address. Keep this in mind when managing clients on behalf of others.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.getweddingos.com/clients/client-communication.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.