SimpleSupport — Luo Solutions
Luo
LoginGet Started

SimpleSupport

Turn a dedicated support inbox into one focused queue: triage incoming requests, keep ownership and status clear, and reply in the original Gmail thread without losing internal context.

Start for Free Customize with AINo credit card · Nothing to install
Built by
Valentin Sattinger
Category
Customer Support
Updated
Sep 7, 2026
Price
Free to start

Gallery

One queue for every customer request Search, filter, and focus the team on the tickets that need attention.
Keep ownership and next action visible Status, assignee, and customer history travel together.
Reply without leaving the ticket Customer responses and team notes share one readable timeline.

Overview

One ticket queue for your support mailbox, with replies in the original Gmail thread.

SimpleSupport turns each message in a dedicated Gmail support inbox into a ticket with status, owner, and customer context. Agents triage from one queue, leave private notes the customer never sees, and reply from the ticket — the email goes out in the originating thread.

  • 1queue for every requestsearchable, filterable by status and assignee
  • 5workflow statesNew, Open, Pending, Responded, Resolved
  • 0duplicate tickets from re-delivered mailincoming messages are deduplicated by message ID
  • 1connectiona dedicated Gmail support mailbox

SimpleSupport turns messages from a dedicated Gmail support inbox into a compact ticket queue. New requests become support tickets with a subject, customer context, latest-message preview, workflow status, optional assignee, and timestamps. The queue is searchable and filterable by status, assignee, and resolved visibility, with quick actions for open tickets or tickets assigned to you.

Open a ticket to work from one focused detail page. The timeline keeps the newest customer message at the top, distinguishes incoming email, agent replies, and private internal notes, and can reveal quoted history when you need it. Close or reopen the request from the toolbar, change ownership, add a team-only note, or send a reply in the originating Gmail thread.

The workspace keeps the operational state close to the conversation. Incoming Gmail messages are deduplicated by message ID, successful replies are recorded in the ticket timeline, and failed sends leave the draft intact with an error. The connected mailbox and reply workflow can be adjusted as the support process changes.

What's inside

  • Support inbox

    One queue for every customer request

    Incoming support mail appears as a dense, selectable queue. Filter by New, Open, Pending, Responded, or Resolved, narrow by assignee, search subject, customer, or preview text, and use Show open or Show my tickets as quick actions. Resolved tickets stay out of the default view until you ask for them.

  • Ticket workflow

    Keep ownership and next action visible

    Each ticket has a clear workflow state and optional owner. Agents can assign or unassign a teammate, move a request through New, Open, Pending, Responded, and Resolved, or use the compact Close and Reopen action. The timeline shows the latest activity first and keeps private notes separate from customer-facing email.

  • Threaded replies

    Reply without leaving the ticket

    Use separate Reply and Internal Note modes beneath the latest message. Replies are sent in the originating Gmail thread and appended only after successful delivery; internal notes remain visible only to the support team. When a message includes quoted history, the workspace keeps the current content readable and lets the agent expand the rest on demand.

How it works

The support loop

  1. Receive

    a new Gmail message creates or updates the matching support ticket.

  2. Triage

    search, filter, assign, and set the workflow status from the compact queue.

  3. Resolve

    reply in the original thread or leave a private note for the team.

  4. Reopen

    new customer follow-up returns the request to the working queue.

Who it's for

Built for teams answering support from a shared inbox

  • Founder handling support between everything else“Support lives in a shared Gmail login, and nobody knows which requests are still waiting on us.”
  • First support hire“I need statuses and an owner per request without setting up a full help desk.”
  • Small team sharing one mailbox“Two of us reply from the same inbox, and we keep answering the same customer twice.”

What changes

From a shared inbox to a ticket queue

Shared Gmail loginSimpleSupport
Scan the inbox to guess which requests are still openFilter the queue by New, Open, Pending, Responded, or Resolved
Ask in chat who is handling a customerAssign an owner on the ticket and use “Show my tickets”
Keep internal context in a separate doc or threadLeave a private note on the ticket timeline, invisible to the customer
Reply from the inbox and lose the ticket contextReply from the ticket; the email goes out in the originating Gmail thread
Let follow-ups on closed issues slip byA new customer message reopens the ticket into the working queue

Getting started

  1. Connect Gmail

    Enroll the dedicated support mailbox so inbound messages can create or update tickets and replies can stay in their originating thread.

  2. Describe your workflow

    Tell the assistant how your team assigns requests, uses statuses, and wants internal notes or response steps to work.

  3. Run support from the queue

    Triage incoming requests, open the ticket timeline, collaborate privately, and close or reply when the work is complete.

Built on Luo

  • Ready on day one. Start from the template and connect your tools — nothing to install, no developer involved.
  • Change it in chat. Add a field, rename a stage, wire up an alert: say it and the assistant reshapes the workspace.
  • Part of your Company OS. It lives beside your knowledge base and every other tool you build on Luo.
What is Luo? →

FAQ

Do we need a new support address?

No. Connect the Gmail mailbox your support already arrives in. Each incoming message creates a ticket or updates the matching one.

Will customers see our internal notes?

No. Reply and Internal Note are separate modes; notes stay on the ticket timeline for the team only, and only replies go out by email.

What happens if a reply fails to send?

The draft stays intact with an error shown on the ticket, and nothing is appended to the timeline until Gmail confirms delivery.

What if a customer writes back after we resolved the ticket?

The new message reopens the ticket and returns it to the working queue, so follow-ups don't disappear into the resolved view.

Can we change the statuses or the workflow?

Yes. Tell the assistant how your team assigns requests or which states you use, and the queue and ticket workflow change to match.

More solutions

Browse all →

3D Asset Generation Pipeline

Create a six-view 3D asset reference composite, correct its detected viewports, and generate saved slices for downstream mesh work.

Creative productionLuo

AI SEO Assistant

Run bounded SEO audits from one public site URL, preserve the evidence, and turn findings into a trackable remediation backlog.

SEOLuo

EasyRenewal

Upload vendor contracts and never get auto-renewed by surprise again: AI extracts the renewal terms, a dashboard computes every cancellation deadline, and the contracts you can still act on are flagged before the window closes.

FinanceLuo