Keeping is a focused choice for a support team that wants to turn a shared email address into a manageable ticket queue while agents stay in Gmail. Choose it for assignment, internal notes and a visible status on each request. Essentials covers a small two-mailbox setup; Advanced is the relevant tier when shared drafts, more routing rules or response-time policies become requirements.
A Gmail queue with individual access
The administrator setup guide separates the address receiving customer mail from the agents responding to it. A dedicated Gmail or Workspace mailbox can connect by Google sign-in. A Google Group, alias or other address uses forwarding. Keeping processes the incoming message as a ticket and distributes it to the team's individual Gmail accounts. This avoids using one shared password for everyone.
Choose the connection method before rollout. A business with support@ as a Group has a different setup from one with a licensed Google mailbox. Test the actual receiving address and sender name, not merely whether an agent can open the extension.
Ticket ownership is the everyday working model
The Gmail workflow guide shows open requests through Unassigned, Mine and Assigned views. Agents change priority and status and leave private notes in the conversation. The activity view makes it possible to follow a handover. Replies route through Keeping so they use the support identity and reach the other agents' records.
Assignment can involve one or several agents, and the default reply behavior can assign the responder. Agree on a lead owner when multiple colleagues are involved; adding everyone to a ticket does not decide who owes the customer the next update. Defaults that close a ticket after replying should also match the team's actual definition of finished work.
When to move beyond the basic queue
Keeping's workflow conditions can inspect assignment, priority, status and elapsed time. Business or calendar-hour delays support time-sensitive workflows. The corresponding actions assign agents, add tags, change status and notify selected people. A useful example is an urgent unassigned request that should notify a supervisor after a defined wait.
Essentials' two-rule allowance can cover a deliberately small workflow. Advanced removes that capacity limit and adds shared drafts, round robin and SLA rules. Compare the actual behavior if duplicate replies are the main problem.
Who should choose Keeping?
Choose Keeping when Gmail email support is the core job and a clear ticket queue is more useful than a broader service platform. Compare Gmelius for shared-label and distribution-heavy work, Hiver for its documented Gmail service controls, or Drag for email-plus-task boards. Choose the required Keeping plan against mailbox count, team size and rules, then use the Gmail shared-inbox comparison to finish the shortlist.