Make your support replies land in the inbox.

To stop support email landing in spam, send it from your own verified domain rather than a free address, publish the three authentication records for that domain (SPF, DKIM and DMARC), keep replies threaded so they read as part of a real conversation, and test to a few real inboxes before you go live. Get those right and most spam-folder problems disappear.

That is exactly the path Solves walks you down. Replies go out from your own brand domain, sent through Postmark (an established transactional email provider), with the correct headers and standards-based threading so a reply lands in the same conversation the customer started, not as a cold, disconnected message. We do not run our own outbound mail servers; using a proven provider gives you well-managed sending infrastructure and reputation from day one.

During guided mailbox setup, Solves checks your SPF, DKIM and DMARC and gives you copyable DNS records to publish. The checks are aligned with the principles in the NCSC Mail Check guidance for UK organisations. Crucially, live sending for a mailbox stays blocked until those checks pass, so your very first reply is correctly authenticated rather than a guess. If you must start before DNS has fully propagated, a founder override can be recorded against the mailbox, so the decision is explicit and audited.

After you are live, Solves keeps deliverability visible. Bounces, spam complaints and suppressed addresses are surfaced rather than buried in a log somewhere, and abuse and loop controls stop your desk replying to an auto-responder forever or amplifying a mail loop. A good sending reputation is something you maintain, not set once, and the desk gives you the signals to maintain it.

SPF: who is allowed to send for your domain

SPF (Sender Policy Framework) is a record in your DNS that lists which servers are allowed to send email on behalf of your domain. When a receiving server gets a message claiming to be from you, it checks whether the sending server is on that list. If your sending provider is not authorised in SPF, the message looks suspicious. Solves gives you the exact SPF entry to publish so your authorised sender is recognised.

DKIM: a tamper-evident signature

DKIM (DomainKeys Identified Mail) adds a cryptographic signature to each message, using a key published in your DNS. The receiving server uses that key to confirm the message genuinely came from your domain and was not altered in transit. A valid DKIM signature is one of the strongest signals that mail is legitimate. Solves provides the DKIM record to publish and confirms it is signing correctly before you send.

DMARC: the policy that ties it together

DMARC (Domain-based Message Authentication, Reporting and Conformance) builds on SPF and DKIM. It publishes a policy telling receiving servers what to do with mail that claims to be from your domain but fails those checks, and it asks them to report what they see. A sensible DMARC policy improves how mailbox providers treat your real replies and protects your domain from being spoofed by scammers. Solves aligns its checks with the principles in the NCSC Mail Check guidance, which the UK National Cyber Security Centre publishes to help organisations get exactly these records right.

Common causes of support email going to spam

Most spam-folder problems for support teams come from a short list of causes. Sending from a free mailbox such as a gmail.com or outlook.com address instead of your own domain is near the top: you cannot authenticate a domain you do not control, so filters treat it warily. Missing or broken SPF, DKIM or DMARC is the next big one, as is a domain or sending IP with little or poor reputation. Replies that break the conversation thread arrive looking unsolicited. And sending to addresses that bounce or have already complained quietly erodes your reputation until even good mail starts to slip.

What triggers spam filters

Beyond authentication, filters weigh content and behaviour. Deceptive or shouty subject lines, an unusually high ratio of links to text, image-only messages, and mail that suddenly arrives from a new, unauthenticated source all raise the score against you. So does a rising complaint rate, when recipients press the spam button. Bulk messages without proper List-Unsubscribe handling get penalised. For day-to-day support, the way to stay clear of these triggers is to authenticate your domain, keep your sending reputation clean, thread replies so they look like part of a real conversation, and stop sending to addresses that have bounced or complained. Solves is built so the technical side of that list is handled for you.

Solves sends your replies through Postmark, an established transactional email provider, rather than running its own outbound mail servers. That is a deliberate deliverability choice. Reputation on a sending platform is earned over time, and a brand-new server has none; it would need warming up and defending against abuse before mailbox providers trusted it. By sending through a proven provider from your verified domain, you inherit well-managed infrastructure and a strong sending reputation from your first reply.

Owned outbound SMTP is not part of the current product. If that changes, it will be additive, and the principle will not: your replies always go out as your own brand, from your own domain, with authentication in place. The goal is the same whatever sits underneath, which is to give a small support team the kind of deliverability that usually takes a dedicated email team to achieve.

Keeping a clean reputation after you go live

Deliverability is not a one-time setup. Once your mailbox is verified and sending, Solves keeps the signals that matter in front of you. Hard and soft bounces are recorded against the contact and ticket. Spam complaints are surfaced. Addresses that bounce or complain are suppressed so you are not repeatedly mailing inboxes that hurt your reputation. Abuse and loop controls catch auto-responders and mail loops before they turn into hundreds of pointless replies. None of this needs a separate deliverability tool; it is part of the desk your team already works in every day.