> ## Documentation Index > Fetch the complete documentation index at: https://alguna.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Emails > Every email Alguna sends on your behalf: what goes out and when, who receives it, which address it comes from, and how to change the wording and the recipients. Alguna sends transactional email to your customers on your behalf — invoices, receipts, subscription notices, payment requests, dunning reminders — and a handful of internal emails to your own team. Every one of them is sent from an Alguna address by default, carries your branding, and replies to your billing support inbox. Use this page to see what goes out, decide who else should receive a copy, change the wording, or work out why a customer says nothing arrived. To send from an address at your own domain instead, see [Custom Domains and Addresses](/docs/hosted/custom-domains#sending-email-from-your-own-address). *** ## What Alguna sends Each email has a **type**, and the type is what you customize and audit against. The full set: | Type | Sent when | | --------------------------------------- | ----------------------------------------------------------------------- | | `invoice` | An invoice is issued to the customer | | `invoice_payment_link` | You send a customer a direct link to pay an invoice | | `receipt` | A payment against an invoice succeeds | | `credit_note` | A credit note is issued | | `invoice_reminder_due` | An invoice is approaching its due date | | `invoice_reminder_overdue` | An invoice has passed its due date | | `subscription_sign` | A subscription is sent to the customer for signature | | `subscription_sent_reminder` | A subscription awaiting signature is chased | | `subscription_signed` | The customer signs | | `subscription_signed_internal` | Your team is told the customer signed | | `subscription_activated` | A subscription becomes active | | `subscription_updated` | A subscription's terms change | | `subscription_cancelation_scheduled` | A cancelation is scheduled for a future date | | `subscription_canceled` | A subscription actually ends | | `subscription_autorenewal_notification` | A term is approaching auto-renewal | | `billing_information_request` | You ask a customer for billing details or a payment method | | `card_expiration_reminder` | A stored card is close to expiring | | `customer_portal_link_share` | You send a customer their [portal](/docs/hosted/customer-portal) link | | `checkout_abandoned` | A [checkout session](/docs/hosted/checkout) is started but not completed | | `wallet_topup_complete_request` | A [wallet](/docs/credits/wallets) top-up needs the customer to finish paying | | `generic` | A free-form email you compose and send from the dashboard | | `organization_invitation` | You invite a teammate to your Alguna organization | | `approval_requested` | An [approval](/docs/approvals/overview) needs a decision | | `approval_flow_approved` | An approval flow completes with an approval | | `approval_flow_rejected` | An approval flow completes with a rejection | Reminder cadence for `invoice_reminder_due` and `invoice_reminder_overdue` is not fixed — it comes from your [dunning](/docs/collections/dunning) configuration. *** ## Who receives them Customer-facing emails go to the customer's billing [contacts](/docs/customers/customer-contacts). A customer with no contact email receives nothing — Alguna has nowhere to send it, and the invoice or subscription still progresses. Check contacts first when a customer reports missing mail. On top of the recipient, you can add standing copies: * **Global CC and BCC** — addresses copied on every customer-facing email, typically a shared billing inbox so your team keeps a record without being named on each customer. * **Per-type CC and BCC** — extra addresses on one email type only, for example copying your AR team on `invoice_reminder_overdue` but nothing else. These add to the global lists rather than replacing them. Both are set under **Settings → Organization → Customizations → Email Templates**, as **Global CC Recipients** and **Global BCC Recipients** alongside the per-type fields. The last four types in the table above — `organization_invitation`, `approval_requested`, `approval_flow_approved`, `approval_flow_rejected` — are internal. They go to the people in your organization, not to customers. *** ## Which address they come from Alguna sends from its own authenticated domain. Which address depends on what the email is about: | Address | Used for | | ------------------------- | ------------------------------------------------------------------------------------------------------------------- | | `invoices@alguna.io` | Invoices, receipts, credit notes, payment links | | `subscriptions@alguna.io` | Subscription lifecycle, portal links, billing information requests, card expiry, wallet top-ups, abandoned checkout | | `cancelations@alguna.io` | Cancelation and term-ending notices | | `accounts@alguna.io` | Organization invitations to your own team | **Replies do not come back to Alguna.** Customer-facing emails set `Reply-To` to the **billing support email** on your [business details](/docs/getting-started/business-details), so a customer hitting reply reaches your team. Keep that address monitored — it is the one customers will use. To send from an address you own instead — `billing@yourcompany.com` rather than `invoices@alguna.io` — see [Custom Domains and Addresses](/docs/hosted/custom-domains#sending-email-from-your-own-address). Our team configures it, and it is the only case in which email requires DNS records on your side. *** ## Changing the wording **Settings → Organization → Customizations → Email Templates** holds the subject line, body and call-to-action text for each type, along with a live preview. Templates support variables — the customer name, invoice number, amounts and dates — so a customized template still fills in per send. A type you never edit keeps Alguna's default wording. The same screen carries the per-type settings that change what the email contains rather than how it reads: | Setting | Effect | | ------------------------ | --------------------------------------------------------------------------------------------------------------------------- | | **CC / BCC** | Standing copies for this type only, added to the global lists | | **Customer portal link** | Includes the customer's [portal](/docs/hosted/customer-portal) link. Unset means the type follows your organization-wide default | | **Line items** | Includes the invoice's line items in the email body itself. Off unless you turn it on for that type | Logo, colors and the brand shown in the email frame come from **Settings → Organization → Customizations → Branding**. See [Branding](/docs/getting-started/branding). *** ## Checking what was sent **Settings → Logs → Emails** lists what Alguna has sent for your organization, to which address, and when. Start there when a customer says an invoice never arrived: it tells you whether the email went out and to what address, which separates a missing contact from a deliverability problem. *** ## Next steps Set the billing support address that customer replies land in. Send from your own address and serve hosted pages from your own domain. Who on the customer side receives billing email. When overdue reminders go out and how often.