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.
- Runs on a dedicated Gmail mailbox you already have
- Private internal notes stay separate from customer-facing email
- Replies are recorded only after Gmail confirms delivery
Built by Luo · Updated Aug 24, 2026
Built for teams answering support from a shared inbox
“Support lives in a shared Gmail login, and nobody knows which requests are still waiting on us.”
“I need statuses and an owner per request without setting up a full help desk.”
“Two of us reply from the same inbox, and we keep answering the same customer twice.”
From a shared inbox to a ticket queue
Ready to run, and built to be changed.
SimpleSupport is a Luo workspace, not a locked app. It works the moment you connect your accounts — and when your process differs, you tell the assistant and it reshapes the pages, fields, rules, and automations for you.
Ready on day one
Start from the template and connect your tools; there is nothing to install and no developer or migration involved.
Change it in chat
Add a field, rename a stage, change a rule, wire up an alert — say it, and the assistant rebuilds the workspace around it.
- Reply to the customer: ask for the report date range and confirm we are investigating.
- Add a private note that we should reproduce this before the next reply.
Part of your Company OS
It lives in your Luo workspace next to your knowledge base and every other tool you build there — your data, your accounts, one assistant across all of it. What is Luo? →
What's inside.
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.
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.
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.
Up and running in three steps.
Connect Gmail
Enroll the dedicated support mailbox so inbound messages can create or update tickets and replies can stay in their originating thread.
Describe your workflow
Tell the assistant how your team assigns requests, uses statuses, and wants internal notes or response steps to work.
Run support from the queue
Triage incoming requests, open the ticket timeline, collaborate privately, and close or reply when the work is complete.
Common questions.
If something isn't covered here, the assistant inside the workspace can answer it — and change whatever you want changed.
- Maintained by
- Luo
- Category
- Customer Support
- Setup
- Connect a dedicated Gmail support mailbox
- Price
- Free to start
- Runs
- On inbound support email and agent actions
- Your data
- Tickets and notes stay in your workspace
- Customizable
- Ask the assistant to change the workflow
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.
Start with the inbox,keep every request moving.
Connect the support mailbox, give the workflow a shape, and let one focused workspace carry the queue, context, team notes, and threaded replies.
Start freeNew to Luo? See what it is →