Newsletter software for member organizations

Campaigns are built from widget blocks dropped into the layout: text, images, buttons, and dividers. Styling is set in the editor rather than in code, and a default button style is configured once and applied across campaigns.

Orgo ships 18 predefined templates. Any campaign design can be saved into your organization's own library, and templates duplicate, so a monthly digest or an event announcement is rebuilt from an existing layout instead of from scratch.

Placeholders insert per-recipient values into the campaign:

• First name
• Last name
• Preferences URL
• Unsubscribe URL

Campaigns send from an address your organization chooses, such as info@yourorganization.org, rather than an Orgo address. The DNS setup behind this sits under deliverability below.

Every campaign previews in desktop and mobile layouts before sending. Sending happens immediately or on a schedule, with time zone support, so a send timed for a Tuesday morning lands on a Tuesday morning.

Campaign content can be edited as HTML directly, for designs produced outside the builder. A sent campaign can also be published as a public link, for sharing the same content outside email.

Recipients are chosen at campaign level from:

• All members
• All contacts
• Members and contacts together
• A specific group
• A specific chapter
• Registrants of a specific event
• A static list
• A dynamic segment

A segment is a set of chained criteria rather than a saved list of people:

• Account status
• Tags
• Membership fee status
• Date joined
• Age
• Recurring payment status
• Attended or did not attend a given event
• Subscription status

The criteria are evaluated at the moment of sending. A member who lapses, joins, or ages past a bracket moves in or out of the segment without anyone editing it.

Audiences that need manual control, such as a board list or a press list, are built by adding and removing people directly. Static and dynamic lists coexist in the same organization.

The target audience can be described in plain language, and the matching criteria are generated from that description. The generated criteria stay editable, so the segment is refined by hand afterwards.

A campaign can target everyone registered for a given event. Because contacts do not need a login account, this reaches non-member attendees alongside members in the same send.

A local communication manager building an audience sees only their own chapter's members and contacts. National campaigns target the whole organization, one chapter, a region, a role-based group, or a saved segment.

Members hold login accounts. Contacts, including newsletter subscribers, donors, event registrants, and form respondents, are tracked without one. Campaigns target either group or both.

Newsletter subscription forms embed into any external website through an iframe, with no Orgo branding. Submissions create contact records directly, and each widget tracks the subscribers it produced.

Converting a contact into a member carries their history across:

• Donation and payment history
• Event attendance
• Signed documents
• Newsletter subscriptions
• The full log of emails already sent to them

Contacts are matched by email or phone as a unique identifier, and duplicate records are detected and merged rather than accumulating.

Each person controls their own notification and subscription settings from their profile, and unsubscribes are handled automatically through the placeholder link carried in every campaign.

Registration and signup forms carry configurable consent checkboxes with linked documents, so permission to email is recorded on the record itself rather than tracked separately.

Each campaign reports:

• Delivered
• Opened
• Clicked
• Bounced
• Unsubscribed
• Complaints

Every metric opens into the list of people behind it. Finding which addresses bounced, who unsubscribed, or who marked a campaign as spam takes one click rather than a support request.

A per-campaign breakdown ranks every link by click volume, which shows whether the donation button, the event page, or the article drove the response.

A campaign can be resent to the recipients who did not open it, without rebuilding the audience or the content.

Every email sent to a person is recorded on their member or contact record, alongside profile changes, payments, and event history. Answering what a given member has already been sent does not require opening the campaign tool.

Organization-level analytics track emails sent, logins, discussions, and newsletter subscribers over any period, filterable by chapter. Chapter admins see the same dashboards restricted to their own chapter.

Campaigns send through Amazon SES, with capacity in the range of 1.5 million emails a month. That covers a weekly newsletter to a six-figure contact base plus the transactional and campaign traffic around it.

Orgo supplies the DNS records, including DKIM and SPF, for the sender identity your organization chooses. Campaigns then authenticate as your own domain instead of a shared one.

Dedicated IPs are available as an option. A shared pool carries the reputation of every organization sending from it, while a dedicated pool carries only yours, with sending balanced across the pool.

Soft bounces are retried automatically. Hard bounces are unsubscribed automatically, so a dead address is not repeatedly retried at the cost of sender reputation.

Inbox placement also depends on work outside the platform, such as warming up a new sender address or a new IP before high-volume sending. Orgo provides guidance on this rather than presenting deliverability as automatic.

A dedicated communication manager permission covers newsletters and moderation. It exists at organization, parent-chapter, and local-chapter level, isolated to that level's people, so delegating email does not mean handing over the member database.

Email sends, profile changes, data exports, and report generation are logged with the user, the timestamp, and the IP address.

Member and contact data is hosted on AWS in Frankfurt and does not leave the European Union. Deployment to a specific country or region is possible where regulation requires it.

Your organization owns its contact data. CSV export is available per module and through the API, every export is logged, and large exports of sensitive data prompt a warning before they run.