Transactional email

Loops.so sends transactional emails like password resets and receipts triggered by product events. An agent watches for an approved event, reads the user and the event data, and issues the matching transactional email your team set up. It records the send on the contact. Events with missing data, an unverified address, or a type that maps to no template are held and raised to an operator, who checks the setup. The agent keeps to the templates and triggers your team approved, so product emails go out consistently without a person composing each one.

Marketing campaigns

Campaigns in Loops.so go to segments of your audience on a schedule. An agent reads the campaign and its target segment and, once your team approves the content, sets the campaign to send at the planned time, then notes it on the record. Segment definitions and timing stay as your team set them. Campaigns aimed at an empty segment, missing a subject, or overlapping a recent send to the same people are paused for a marketer, who resolves the conflict before release rather than risking duplicate or broken messages to subscribers.

Lifecycle loops

Loops are automated email sequences tied to a user's lifecycle stage. When a user enters a stage, such as trial start, the agent reads the profile and enrolls the person into the approved loop for that stage, recording the enrollment. It respects unsubscribe status and existing enrollments. Users who recently unsubscribed, already sit in a conflicting loop, or entered a stage from an untested source are set aside for a marketer, who confirms the path. The agent keeps enrollment tidy so no one receives two competing onboarding sequences at once.