solves.
Menu
Changelog

What we have shipped on Solves

Dated release notes for the pilot, newest first. Solves is built in the open and actively shipping. This is what has landed so far.

Subscribe via RSS  ·  Last updated 2026-06-13

2026-06-13 Added

Product, comparison and guide pages

A full set of public pages explaining how Solves works, UK-first and email-first, with honest comparisons and plain-English setup guides.

  • Feature pages for shared inbox ticketing, multi-brand, replies and private notes, SLA timers and email deliverability.
  • Honest comparison and switching pages that carry a last-verified date and never claim feature parity.
  • A shared component kit so every page reads as one product.
2026-06-13 Added

GBP team-band pricing and the founding pilot

Transparent pricing in pounds, ex VAT, with no per-seat penalty for occasional helpers, plus the early-adopter pilot for the first 20 teams.

  • Starter begins at GBP 29 a month, ex VAT.
  • Team bands from GBP 29 a month, twelve months for ten when you pay yearly.
  • Founding pilot: Team at GBP 49 a month for six months, with setup help included.
2026-06-12 Added

Run several brands from one queue

Support more than one brand from a single login and one unified queue, with brand-specific mailboxes and signatures.

  • Brand badges and brand filters on every row of the queue.
  • A hard guard that locks the reply to the ticket brand and mailbox, so a reply cannot go out as the wrong brand.
2026-06-12 Added

Guided mailbox setup in plain English

A human checklist with copyable DNS records, forwarding-first for existing business email, and live sending blocked until a real test passes.

  • Plain-English steps for SPF, DKIM, DMARC and Return-Path.
  • No risky root MX change required: forwarding-first by default.
2026-06-11 Added

First-response and resolution SLA timers

First-response and resolution SLA timers with per-brand or organisation targets, plus a live breaching view that surfaces overdue tickets.

  • Per-brand or organisation targets, set in minutes.
  • A breaching view sorts the most overdue tickets first.
2026-06-11 Security

Customer support content encrypted at rest

Ticket subjects, message bodies, private notes, saved replies and contacts are encrypted at rest with per-organisation keys, and logs are metadata-only.

  • Each organisation has its own data-encryption key, wrapped by a key held outside the database.
  • Normal logs and audit events record metadata only: no message bodies, raw email addresses or secrets.
2026-06-10 Added

Public replies and private notes, kept apart

A hard separation between customer replies and internal notes, so a private note can never reach a customer by accident.

  • Light collaborators can add private notes but never send a public reply.
  • A stale-reply warning when a newer customer email has arrived.

Be part of the next entry

Join the founding pilot and help shape what ships next.