Why does deliverability keep coming up on this page?

Because it is the part that decides whether the campaign worked, and it is the part most tools hand back to you as a support article. Mail that lands in Promotions was still delivered — it just was not read. The checks here exist so you find that out before you send, not after.

Do we need our own AWS account?

Yes, and that is deliberate. Sending through your own Amazon SES account means the reputation you build is yours, your sending limits are yours to raise, and nobody else’s bad campaign can affect your delivery. We set it up with you during handover.

Can we bring our existing contact list?

Yes, by CSV, with your own custom fields mapped on the way in. Anything already on your suppression list stays suppressed — an import cannot resurrect somebody who unsubscribed, which is the mistake that generates spam complaints.

What stops us mailing someone who opted out?

A suppression list checked on every send, and one-click unsubscribe implemented to RFC 8058 so a mail provider can honour it without the reader hunting for a link. Unsubscribes from any campaign apply everywhere.

Where do the tracking links point?

At your own tracking domain, not ours. Opens, clicks and the built-in shortener all resolve on a host you control, so the links in your mail carry your name and your reputation.

What happens if a campaign fails halfway?

Sending runs through a queue and a worker rather than a browser tab, so nothing depends on somebody keeping a page open. A campaign can be paused and resumed, and the operations screen shows what is queued, sending, throttled or failed.

Home/Products/Marketing CRM

Ucanly Marketing CRM

Email your students actually receive.

Sending mail is the easy half. The half that decides whether it worked is authentication, list hygiene and structure — and this does that work as part of the product rather than leaving it to you.

See it with sample data Compare both products

Deliverability, checked rather than assumed

This is the part we would lead with even if it were not the part we are best at, because it is the part that is usually broken.

The app reads your actual DNS and tells you what is wrong with it — SPF, DKIM and DMARC, with the record it found shown next to the record it expected. Then it scores the draft against the structural signals that push a message into Promotions, which is a different question from spam and is answered mostly by how the message is built rather than what it says. A preflight check verifies that your unsubscribe links resolve somewhere real before a campaign goes out, because a header pointing at the wrong host looks perfect and fails silently.

Screenshot to addimages/products/marketing-deliverability.pngDrop an .mp4 beside it later to make it a clip.

The records it found, beside the ones it expected.

Contacts, lists and segments

Screenshot to addimages/products/marketing-segments.pngDrop an .mp4 beside it later to make it a clip.

The count you see is the count that gets the mail.

Fields you defineAdd your own — course, intake, college, whatever you sort people by — and use them in a segment rule, a template or a report.
Segments you can see before you sendBuild from rules, preview exactly who matches, then save it to reuse. No sending to a definition you have not looked at.
A stage for each contactLead through to customer, with the history of how they moved, so a list is not just a pile of addresses.
Suppression that actually holdsChecked on every send, and an import cannot override it.

Campaigns, and what happened to them

Write it, test it against a real inbox, send it, then find out what it did.

The builder has a live preview and test sends. Reports carry opens, clicks, bounces and unsubscribes. A campaign can carry a second subject line as an A/B test, where a sample goes out first and the rest is held back until somebody picks the winner — and held means held: the remainder costs no worker time and takes no share of your send rate while it waits.

Screenshot to addimages/products/marketing-report.pngDrop an .mp4 beside it later to make it a clip.

Opens, clicks, bounces and unsubscribes per campaign.

Automations, and a queue you can watch

Screenshot to addimages/products/marketing-automation.pngDrop an .mp4 beside it later to make it a clip.

Four triggers, each a plain lookup rather than a rule engine.

Triggers that are easy to reason aboutA contact joining a list, gaining a tag, or entering a stage. Four of them, each a plain indexed lookup rather than something you have to interpret.
Switching one on does not mail everybodyActivation records a moment, and the sweep only considers what happened after it. Turning on a welcome sequence cannot blast your entire back catalogue.
Sending survives a closed laptopA queue and a worker handle throttling and retries, so a large campaign does not depend on a browser tab.
An operations screenWhat is queued, sending, throttled or failed, with an activity log behind it.

Where the mail goes out

Two delivery paths, both through your own AWS account: the Amazon SES v2 API directly, or a Lambda function if you would rather the send ran away from the web server. Open and click tracking resolve on your own tracking domain with a built-in shortener, so the links in your mail are yours rather than a third party’s — and the reputation you build belongs to you.

Your sending reputation. Your SES account, your limits, your domain. Nobody else’s campaign affects your delivery.
One-click unsubscribe. RFC 8058, required of bulk senders by Gmail and Yahoo since February 2024.
Rate limiting and throttling. Configurable per second and per batch, so you stay inside what SES will accept.
Bounces and complaints feed back. Hard bounces and spam reports land on the suppression list automatically.

Who this is for

Anyone paying per contact

Per-seat and per-contact pricing punishes you for having a big list, which is the opposite of what you want. This is a deployment, so the list size is between you and AWS.

Anyone whose mail is not landing

If open rates fell off a cliff and nobody can tell you why, the DNS checks and the spam-signal scoring are the reason to look at this.

Anyone who has to prove consent

Suppression, unsubscribe records and per-contact activity are kept in your own database, so an audit is a query rather than a support ticket.

Who it is not for. If you send a newsletter to a few hundred people once a quarter, a hosted tool is simpler and we will say so. This earns its keep when the list is large enough that per-contact pricing hurts, or when deliverability has become somebody’s actual problem.

Questions people actually ask

Next step

Click through a working one.

The demo is loaded with invented contacts, campaigns and reports, and nothing on it can reach a real address.

Book a demo See the Sales CRM