By Gmelius

Gmelius

What it does

Gmelius turns a shared email address into a team inbox inside Gmail. A support team can see an incoming conversation, assign an owner, use Pending while waiting, and close it when handled. New replies reopen a closed conversation, keeping the thread in the active queue.

The product suits email-centered support work. It is built around Gmail and Google Workspace addresses and offers collaboration and workflow rules around shared conversations. Check address setup, plan rights and From-address behavior before treating it as a replacement for an existing help desk.

Category
Help Desk
Last updated
Oct 21, 2026
Gmelius · Editorial illustration
Conceptual paper-and-clay shared mail flows through assignment, waiting and closed trays.

Work at Gmelius?

Help customers find accurate information about your software.

Manage this listing →

Find your fit

Who it is for

A small support team sharing support@ or info@ can use Unassigned, Mine and Assigned views to see what has arrived and who owns each thread. A brief sample queue will show whether the team’s current email habits fit the workflow.

Teams that already live in Gmail can use notes and mentions for internal context, plus collision alerts when another teammate is viewing or replying. The note stays internal to shared participants rather than going to the outside sender.

A manager handling higher email volume can consider round-robin or load-balancing rules and a board view. Test availability and exception handling before assigning a real support queue automatically.

Back to sections

The work it supports

Core capabilities

Gmelius can build a shared inbox from a Gmail account, Google Group or Google Workspace alias. The correct setup depends on the address type; the default inbox receives mail for its exact address, and additional aliases need to be added separately.

Incoming conversations start in Unassigned. Assigning a teammate moves the conversation into the assigned workload; Mine and Assigned show active or pending work, and a board view can show conversations as cards by teammate.

Open, Pending and Closed express the state of a conversation. Pending keeps an item visible while the team waits for a reply or more information. A new reply to a closed thread reopens it, and Send & Close combines a reply with closure.

Shared notes and @mentions let teammates add context without exposing the note to the outside email recipient. A collision alert warns when another member is viewing or replying; check the alert rather than assuming it prevents duplicate sends.

Automation Rules can distribute new conversations with round-robin or load-balancing assignment. Criteria and available teammates matter, so try a small queue and inspect where each conversation lands.

To answer from the shared address, teammates may need to configure Gmail’s Send mail as option. Separately, a brand-new outgoing email from that address is not shared with the team by default, although replies are; an Inbox setting can change this.

Back to sections

Understand the offer

Pricing and getting started

Current pricing places shared inboxes in Growth or higher. The lower Meli tier is a personal AI assistant offer and does not show shared-inbox entitlement in the comparison grid. Choose a shared-inbox tier for this workflow.

The page displays Growth at $25 per user monthly with yearly billing or $33 with monthly billing, and Pro at $40 or $50 respectively. These are viewed dollar displays; confirm selected currency, taxes, included agent work and renewal in checkout or a quote.

Enterprise is quote-led with a stated fifty-user minimum. Every team member must use the same plan tier, so budget the intended roster rather than only the people assigned to the shared inbox.

The signup trial gives seven days of Growth access. Gmelius says the account is suspended if no paid plan is selected afterward; test a representative inbox and check data access before the trial ends.

Back to sections

Look a little closer

Before you choose

Create an internal test mailbox or harmless sample thread using the intended Gmail account, Group or Workspace alias. Check that inbound messages appear in Unassigned, the correct teammates can see them, and assignment moves them where expected.

Verify both incoming and outgoing address paths. Additional aliases need setup beyond the exact inbox address, and each teammate’s Gmail Send mail as configuration affects what customers see in the From field.

Test a fresh outbound email separately from a reply: new outgoing mail is not shared by default. Decide whether team visibility is required and set the sharing option before sending real support outreach.

Compare the Growth-or-higher feature matrix, seat price, included agent work and team-wide tier rule with expected volume. A seven-day trial may be enough to test the workflow but requires an exit or upgrade decision.

Back to sections

9 distinct sources behind this profile. Research observed Oct 21, 2026. Features and offers can change.
View sources and research →

Help keep this profile useful

Spotted an outdated detail? Send the correction with a supporting source. A verified account is needed to submit.

Suggest a correction ↗