Most CRM buyers never think about how their emails get sent. That’s fair — it’s plumbing. But plumbing is what breaks on Monday morning when your automated reminders don’t reach customers and your sales team walks into a bad week.
We shipped something this month that makes that breakage very unlikely for HARi customers. It’s worth explaining, because it’s the kind of quiet architectural decision that separates a CRM that works on day 900 from one that only works on day 1.
The problem, in SME terms
Picture this. You run a 15-person sales team in Hong Kong. Between daily follow-ups, appointment reminders, and invoice notifications, your CRM sends around 200 emails a day on your team’s behalf. Everything hums along.
Meanwhile, somewhere else on the same CRM platform, another company accidentally publishes a broken workflow — one that tries to send 50,000 emails in an hour. The shared email provider notices the spike, assumes someone’s been compromised, and throttles the entire account.
Now your Monday morning reminders don’t go out. Your customers don’t show up to appointments. Your sales team misses quota for the week. And you — quite reasonably — blame the CRM.
This is not hypothetical. It is a well-documented failure mode in CRMs that share customer infrastructure without guardrails. We built HARi specifically so it cannot happen to you.
What “shared platform” actually means
HARi is a shared platform. That means many customers run on the same underlying servers and services. This is normal and it is how we keep the price at one flat fee rather than charging you per user.
The problem with shared platforms is not sharing — it’s sharing without isolation. Imagine an apartment building where everyone shares one water meter. If your neighbour leaves the tap running, your bill spikes. Now imagine the same building where every flat has its own meter and its own valve. Everyone still shares the same pipes to the street, but one person’s mistake stays contained.
Good shared-platform design is about adding the meters and valves. That’s what we’ve done.
The three things we built
Per-tenant email rate limits
Every HARi customer gets their own hourly email budget. Paid accounts send up to 500 emails per hour. Free trial accounts send up to 100. The budget resets automatically every hour.
The important word is “their own.” If another customer on HARi accidentally triggers a runaway send, their budget hits zero and they stop. Your budget is not touched. Your Monday reminders go out. Your sales team does not find out anything happened.
For most HARi customers, 500 per hour is more headroom than they’ll ever use. If you run a larger operation and need more, we can raise the ceiling from the admin panel.
A from-domain allowlist
When you set up HARi, you tell us which email domains you’re allowed to send from — typically your company domain, such as yourcompany.hk, plus the subdomain we assign you.
Every outgoing email now passes through a checkpoint. If the sending address doesn’t match a domain you’ve registered, the email is refused before it leaves our network. It never reaches your recipient. It never hits the email provider’s servers.
This matters for two reasons. First, it protects your brand — no one else on the platform can accidentally or deliberately send email claiming to be “sales@yourcompany.hk”. Second, it keeps billing attribution clean: if something looks wrong in your send logs, you know it was genuinely from your workspace.
A per-send audit trail
Every single email HARi sends on your behalf is logged — who sent it, when, to whom, what the subject was, and whether it was accepted by the email provider. You can search this log from within the app. It’s retained for 13 months, long enough to cover a full audit cycle.
This matters for Hong Kong PDPO compliance (you can show a regulator exactly what was sent to a data subject), for billing disputes (you can prove delivery attempts), and for your own diagnostic sanity when a customer says “I never got your email.”
Why this matters for Hong Kong specifically
Hong Kong’s PDPO requires meaningful separation of customer data between organisations using shared systems. Many CRMs tick that box in the database layer but leave email as a muddy shared resource — emails from dozens of customers going out through the same sending account, tangled reputations, shared throttling.
HARi’s approach keeps the separation clean all the way through. Your sends go out under your allowlisted domains. Your rate limit is yours. Your audit log is yours. Another customer’s spam complaints cannot affect your deliverability. Another customer’s runaway workflow cannot steal your sending capacity.
For customer-facing workflows — appointment confirmations, quote follow-ups, invoice reminders — predictable email delivery is not a nice-to-have. It’s the whole point.
What this costs you
Nothing extra. HARi’s pricing is a flat HK$1,990 per month for unlimited users and unlimited workflows. The email relay ships as part of the platform — you’re already using it if you’re already a customer.
There’s no setup required. The defaults work for the vast majority of businesses. If you want to tune rate limits or register additional sending domains, it’s all in the admin panel.
What’s still coming
Being honest: seven of the eight pieces of this work are live in production as of today. The eighth is a small internal cleanup that removes some legacy fallback paths we no longer need. We’re leaving those in place for a week so we can confirm nothing in the system is quietly relying on them. Normal platform engineering caution — ship the user-visible value first, clean up the scaffolding once we know it’s safe.
You won’t notice when the eighth piece ships. It’s purely housekeeping.
Closing
You picked a CRM so that your team could reach your customers reliably. That reliability is earned in the plumbing — the rate limits, the audit trails, the domain checks that most customers will never see but that protect every email you send.
We built the plumbing right so you don’t have to think about it. If you’re still evaluating HARi, have a look at the pricing page and the features overview, or read Why Hong Kong SMEs Need a CRM in 2026 for the broader context.