> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/using-peakcommerce/system-communications.md).

# System Communications

PeakCommerce sends transactional emails and in-app notifications as customers move through your storefront and account portal — account activation, subscription-change confirmations, and payment receipts. These messages carry your brand and reach customers at high-trust moments, so PeakCommerce gives you control over both **what they say** and **how they're delivered**.

Two settings work together:

* **Notification Templates** (**Settings → Notification Templates**) — choose which events trigger a message, and edit each message's channel, subject, and body. Use `{{variable}}` placeholders to pull in order, customer, and subscription details.
* **Email delivery** — PeakCommerce's built-in sender is fine for testing, but for production you connect your own email provider so mail comes from your domain, reputation, and deliverability tooling.

In this section:

* [Notification Templates](/product/using-peakcommerce/system-communications/email-templates.md)
* [Using Your Own Email Provider](/product/using-peakcommerce/system-communications/using-your-own-smtp-email-provider.md)


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.peakcommerce.com/product/using-peakcommerce/system-communications.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.