Deliverability at Hober

Last updated 2026-07-26

This page is only available in English.

Deliverability is the marketer's problem but the platform's infrastructure. This page explains how Hober's sending actually works, what protects your reputation from other tenants, and how to warm up a new sending domain — stated plainly, including the limits of where we are today.

How Hober sends email

Hober delivers email through SendGrid, authenticated as your sending domain — SPF, DKIM, and DMARC belong to you, not to a shared Hober identity. The per-channel deliverability panel in the dashboard checks your domain authentication status directly and shows the exact DNS records to verify, and our own transactional domains run the same SPF/DKIM/DMARC setup we ask of you.

Responsibility splits cleanly:

  • You own domain authentication and list quality — who you import and how you got their consent.
  • Hober owns everything after the send button: suppression enforcement, consent checks, bounce and complaint processing, one-click List-Unsubscribe headers, and the feedback loops into your dashboard.

What protects your reputation

  • A per-tenant suppression ledger. Bounces, spam complaints, and unsubscribes are recorded per tenant and enforced on every subsequent send. A suppressed address is not "less likely" to be contacted — it is structurally excluded at dispatch.
  • Consent enforced at send time. Every message — including ones an AI agent proposes — passes the consent, quiet-hours, and frequency-cap guardrail before delivery. Withdrawn consent suppresses immediately.
  • Standards-compliant unsubscribes. RFC 8058 one-click List-Unsubscribe headers and human-readable preference links ship on every marketing email, which is what mailbox providers now expect from senders.
  • Visible health. The deliverability dashboard shows your per-channel delivery rate, bounce and complaint rates, and trend — the same numbers we watch, with warning thresholds at 2% bounces and 0.1% complaints.

The honest limit: Hober tenants currently send from SendGrid's shared IP pools. Your domain reputation is yours alone; IP reputation is shared with the pool. Dedicated IP options and inbox-placement testing are on the roadmap — until then, the suppression and consent enforcement above is what keeps the pool healthy, and it applies to every tenant equally.

Warming up a new sending domain

  1. Authenticate before anything. Verify SPF and DKIM in the channel's deliverability panel first. Sending unauthenticated mail is the fastest way to teach providers to distrust the domain.
  2. Start with your most engaged segment. First sends should go to recent openers/clickers or fresh signups — recipients likely to engage, which is the signal providers read.
  3. Ramp volume gradually. A practical schedule: hundreds per day in week one, doubling every few days as metrics hold. Avoid a first-week blast to a cold, imported list — that pattern looks identical to spam.
  4. Watch the dashboard thresholds. If bounces exceed 2% or complaints exceed 0.1%, pause the ramp, clean the segment, and let the metrics recover before resuming.
  5. Keep suppression on. Never re-import or work around suppressed addresses; the ledger is protecting the domain you are warming.

Other channels, briefly

Push reputation is token hygiene, not IPs: invalid tokens are detected and fed back into deliverability automatically. SMS reputation is carrier filtering: STOP replies are recorded as opt-outs the moment they arrive. WhatsApp is template approval and the 24-hour window, both enforced at send creation. The per-channel details live on the channels page.