Customer support in a Gemmein app
When a customer replies to a sign-in code, a receipt or an announcement your app sent, the reply lands in the console's Inbox as a thread on their profile — you answer from the console, on your app's own domain. The Customers room can email, suspend, sign out, or delete a person; Logs and Problems show why something failed. Gemmein does not provide a chat widget embedded in your app's own front end.
A customer's reply is the other half of your app's email.
Every transactional email your app sends — a sign-in code, a receipt, an announcement — can get a reply. That reply isn't lost: it lands in the console's Inbox as a thread on the customer's own profile. You answer from the console, and your answer goes out from your app's own sender, so the whole conversation stays in one place for both of you.
Act on one person, directly.
Every customer who has signed in gets one page in the Customers room, with their access, what they've paid, their credits and their activity. Four actions sit right there: email them, suspend, sign out everywhere, or delete.
| Action | What it does |
|---|---|
| Email them | Send this person a message directly from their profile. |
| Suspend | They can't sign in and their current sessions stop. Their data stays, and it's reversible. |
| Sign out everywhere | Ends every session they hold right now. They can sign back in. |
| Delete | Removes this person and their records. Permanent. |
Logs and Problems, for when something goes wrong.
Logs shows everything that happened in your app, newest first, one day at a time: what you did, what Gemmein did on its own, and what your customers did — every event opens into its full account. Problems groups every write Gemmein refused by what went wrong, and quotes the exact refusal your app was told, so a support conversation doesn't end in a guess.
No chat widget in your app.
The console is not an embedded chat widget for your app's own front end — that isn't something Gemmein provides. The Inbox is where replies to your app's own emails land, on your own domain; adding live chat to your product's UI is yours to build, with a provider of your choice.
Give your agent the full task.
Building with Cursor, Claude, Bolt, or Lovable? Paste this so your agent wires customer emails to reach the Inbox correctly.
Read https://docs.gemmein.com/llms.txt. I want customer replies to my app's transactional emails (sign-in codes, receipts, announcements) to reach me so I can answer them from Gemmein's console Inbox, on my app's own verified domain. Confirm what's automatic and what, if anything, I need to configure (a sending domain in Domains). Also show me what the Customers room can do for one person (email, suspend, sign out everywhere, delete) and where to look — Logs and Problems — when I need to explain to a customer why something failed.
npx gemmein devRead the getting-started guide Frequently asked questions.
Does Gemmein have a shared inbox to message customers?
Yes. When a customer replies to any email your app sent — a sign-in code, a receipt, an announcement — the reply lands in the console's Inbox as a thread on their customer profile. You answer from the console, and it goes out from your app's own verified domain, so the conversation stays in one place for both of you.
What can I do for one customer directly?
The Customers room opens one page per person with four actions: email them, suspend them (they can't sign in and their sessions stop, but their data stays and it's reversible), sign them out everywhere (ends every session right now; they can sign back in), or delete them (permanent — erases their account, sessions and records).
How do I find out why something failed for a customer?
Logs shows everything that happened, newest first: what you did, what Gemmein did on its own, and what people did in your app, with every event opening into its full account. Problems groups every write Gemmein refused by what went wrong and quotes the exact refusal your app was told.
Does Gemmein provide a live chat widget for my app's front end?
No. That isn't something Gemmein provides. The Inbox is where replies to your app's own emails land, not a chat widget embedded in your product's UI — adding live chat to your own front end is yours to build.
What happens if a customer's reply goes unanswered?
Once a conversation has been waiting 12 hours for a reply, Gemmein can alert you by email — the alert can be switched off, but the Inbox still shows the thread waiting either way.
Related.
Inbox guide · Customers guide · Logs guide · Problems guide · Alerts guide · Run the business on the product page
See if Gemmein fits your app.
Point your coding agent at docs.gemmein.com/llms.txt and ask it to confirm the fit before it builds.