Skip to main content
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.

What Alguna sends

Each email has a type, and the type is what you customize and audit against. The full set: Reminder cadence for invoice_reminder_due and invoice_reminder_overdue is not fixed — it comes from your dunning configuration.

Who receives them

Customer-facing emails go to the customer’s billing 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: Replies do not come back to Alguna. Customer-facing emails set Reply-To to the billing support email on your 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. 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: Logo, colors and the brand shown in the email frame come from Settings → Organization → Customizations → Branding. See 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

Business details

Set the billing support address that customer replies land in.

Custom domains and addresses

Send from your own address and serve hosted pages from your own domain.

Customer contacts

Who on the customer side receives billing email.

Dunning

When overdue reminders go out and how often.