# Transactional Targeted Mailouts Transactional Targeted Mailouts allow you to trigger emails based on records in a transactional database rather than using your contacts database as the source. This makes it possible to send a separate, personalised email for each transaction a contact has — not just one email per contact. A common use case is keeping customers informed as a request moves through an internal process. For example, as a customer's application for power, phone, insurance, or internet moves through stages — *received*, *allocated*, *actioned*, *completed* — a transactional record can be added at each stage, triggering a personalised update email at each step. This kind of proactive communication reduces unnecessary contact centre load. > **Note:** Transactional Targeted Mailouts require setup by the UbiQuity team before use. Contact UbiQuity if you are interested in this feature. *** ### Setting up a Transactional Targeted Mailout A Transactional Targeted Mailout can be used as part of either a one-off or automated email campaign. To enable it, you must have a transactional database set up within your UbiQuity account. 1. Create a mailout in the usual way — see Mailouts or Automated Mailouts 2. On the Mailout Details screen, toggle **Do you want to send emails for every transaction?** to active 3. Select the transactional database you want to use as the source *** ### Filtering The filtering screen for a Transactional Targeted Mailout works differently to a standard mailout filter. Instead of showing one row per contact, it shows one row per transactional record — so a single contact may appear multiple times if they have multiple records. When building a filter, the first available fields are those specific to the selected transactional table. You can still filter on other areas of UbiQuity, but transactional fields are shown first to make it clear you are working with a transactional source. This structure allows you to filter on a specific status or stage, or to use dynamic content within a single email that adapts based on the transactional record. *** ### Dedupe Deduplication is not available for Transactional Targeted Mailouts. This is intentional — a single contact may legitimately receive multiple emails, one for each transactional record that matches the filter. *** *** ## Service Messaging *Send critical service communications to contacts even if they have opted out of marketing emails.* Service messaging — sometimes called transactional messaging — allows you to send essential communications to your customers in real time, regardless of their marketing opt-out status. These are messages your customers need to receive, such as: * Order or application confirmations * Appointment reminders * Password resets * Status updates on a request or application * Insurance notifications * Dispatched documents or tickets Unlike marketing emails, service messages are triggered by a customer action or business event rather than a campaign schedule. > **Note:** Service Messaging requires setup by the UbiQuity team. Contact UbiQuity to discuss your requirements. *** ### How it works Service messages in UbiQuity are triggered from your transactional or relational database. As a customer record updates — for example, as an application moves through stages — UbiQuity can trigger the relevant service email at each step. Because these are service communications rather than marketing messages, they are sent even if the contact has opted out of marketing emails. This is consistent with the intent of opt-out legislation, which is designed to protect consumers from unwanted marketing rather than from service-critical communications. *** ### Use cases **Customer-facing:** * Application, payment, or order confirmations * Password resets and account notifications * Status updates on an application, order, or payment **Operational:** * Service call or appointment confirmations * Notifications for dispatched documents or tickets * Progress updates as requests move through internal workflows *** ### Sending service messages via other channels Service messages are typically sent by email, but UbiQuity also supports sending them via TXT or push notification if those channels are more appropriate for your audience. --- # Agent Instructions: 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://docs.ubiquity.co.nz/documentation/channels/email/transactional-targeted-mailouts.md?ask= ``` 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.