Move your Gmail support inbox to owned tickets.

You do not have to abandon your Gmail support address to get real ticketing. You point it at Solves with a forwarding rule, and from that moment new email to your support@ address becomes an owned ticket. Your Gmail keeps receiving mail, your old threads stay in Gmail, and your team starts working a proper queue instead of a crowded inbox.

This works because Solves is forwarding-first by design. You do not change your domain's MX records, you do not hand Solves the keys to your mailbox, and you do not run a risky bulk migration of years of mail. You add one forwarding rule in Gmail or Google Workspace, verify the mailbox with plain-English checks, and go live.

Be clear on one thing up front, because we will not oversell it: Solves does not bulk-import your old Gmail history at pilot stage. You start clean. New mail becomes tickets from go-live, while every old thread stays searchable in Gmail where it already is. That is a feature, not a gap: you get a tidy queue from day one instead of importing years of noise.

No one owns a message

Gmail shows you mail, not work. A shared inbox has no concept of who owns a given email, so two people open the same one and both reply, or each assumes the other has it and the customer waits a day for nothing. The usual fixes, coloured stars and a spreadsheet of who is doing what, are manual and fall apart the moment things get busy. Solves gives every ticket a single owner, so there is never a question of who is on it.

You cannot see status or history at a glance

Is this email new, in progress, waiting on the customer, or done? Gmail cannot tell you. Read and unread is not status, and a thread tells you nothing about whether a colleague is mid-reply. When a customer writes back, you have no clean record of what was promised last time without scrolling and guessing. Solves gives each ticket a real status and a full history, so anyone can pick it up and know exactly where it stands.

Replies go out as the wrong person, or the wrong brand

In a shared Gmail inbox it is easy to reply from the wrong identity, or, if you run more than one support address, to answer a customer of one brand with another brand's signature. Internal context lives in forwarded emails and side chats that a customer can accidentally be copied into. Solves separates public replies from private notes with a hard wall, locks each reply to the ticket's brand and mailbox, and stops a stale reply going out after the conversation has moved on.

There is no clock, and no proof you are keeping up

Gmail has no idea you promised a four-hour first response. There are no SLA timers, no view of what is about to breach, and no report at the end of the month showing how you actually did. You are managing response times on a feeling. Solves runs first-response and resolution SLA timers against per-brand or organisation targets, shows you what is breaching, and gives you reports you can stand behind.

Access is all-or-nothing

Sharing a Gmail inbox usually means sharing a login or handing out broad delegated access, then untangling it when someone leaves. There is no clean way to let a part-time helper add an internal note on one brand without seeing everything. Solves gives each teammate their own login and their own permissions, down to reply, notes-only or manage, per brand.

Delegation versus forwarding

Google Workspace lets an administrator grant delegated access to a shared mailbox, so teammates open it from their own Gmail. That keeps mail inside Gmail, with all of Gmail's limits: no ownership, no statuses, no SLA timers, and access that is hard to scope per person. Solves takes a different route. You forward the support address out to Solves and your team works the resulting tickets from their own Solves logins. You are not replacing delegation with another inbox, you are turning the mail into owned, timed work.

A practical upshot: with forwarding you do not need to add or pay for Google Workspace seats just to let someone help with support. A notes-only helper needs a Solves login, not a Google one.

Your MX records do not move

This is the part that worries people most, so to be plain: moving to Solves does not touch your MX records. Gmail stays your mail host and carries on receiving everything. Forwarding sits on top of that, sending a copy of new support mail to Solves. If you ever stop forwarding, mail simply keeps arriving in Gmail as before. There is no flag day and no domain cut-over to schedule.

Replies, and keeping the conversation in one place

Once you are live, the right place to reply is Solves, so a single ticket holds the whole conversation with one owner, a status and the audit history. If a stray reply still goes out from Gmail during the changeover, nothing breaks, but you lose the ownership and timing that are the whole point of moving. A short habit change, reply in Solves rather than Gmail, is all it takes, and saved replies make that faster than typing in Gmail ever was.

Your old Gmail archive stays put

Because there is no history import, your years of past threads remain in Gmail, fully searchable, exactly where your team already looks for them. You lose nothing. New work flows into Solves as tickets, old context stays one Gmail search away, and you avoid the risk and downtime of dragging an archive across.

None of this is hard, but a couple of minutes of planning makes go-live calm rather than chaotic.

1. Confirm which Gmail or Google Workspace address you are moving, usually support@, info@ or accounts@.
2. Decide who owns tickets first thing, so the queue has clear owners from the moment mail starts flowing.
3. Add the brand in Solves with the from-name and signature your customers should see.
4. Connect the mailbox and pass the plain-English checks so live sending is allowed.
5. Add the Gmail forwarding rule, send a test email, and confirm it lands as a ticket.
6. Agree the one habit change with your team: reply in Solves, not in Gmail.

That is the whole move. No MX change to schedule, no archive to drag across, no shared password to rotate. If you would rather not do it alone, the early-adopter pilot includes guided mailbox setup and a hand through these steps.