GemBoss
Sign in to the care inbox
Sign in to the care inbox
Nothing here
New customer messages appear instantly.
Select a conversation
Pick one from the list to read it and reply.
Everything the team is working on — what customers asked for, and the team's own tasks. Customers only ever see their own requests, never an internal task.
The same question answered again and again in resolved conversations is an article waiting to be written.
Published articles are what a merchant reads at . A draft is visible only here — which is where an answer nobody has checked belongs.
Who is on the team, what they can do, and whether they can still get in.
Everyone the team knows. Users signed in through GemBoss; leads are website visitors and people who wrote by email or Telegram.
Nothing here
Conversations show up the moment a customer writes.
No one matches
Try a shorter search, or another group.
Locations from IP Geolocation by DB-IP. Map © OpenStreetMap contributors.
Working minutes since it was handed over. The clock stops while the customer is the one being waited on, and outside working hours.
Who is meant to be working, in their own time zone. Check-in says who actually is — the two together are the only way to see a gap before a customer does.
Nobody is scheduled at this moment.
An end time earlier than the start means the shift runs past midnight — a night shift is one shift, not two.
The team tags a conversation with these when sorting it. Retiring a topic doesn’t erase history: old conversations keep their tag; nobody can pick it for new ones.
Every AI call in gemcare counts toward one daily budget, on the team's clock. When it runs out, AI buttons say so and the team works as before until tomorrow.
What the team records about a customer. Anyone fills them in from the Customer panel of a conversation; every change keeps who made it. Archiving hides a field and keeps its history.
Admins and supervisors add and change fields.
Type / at the start of the message box to insert one. It inserts TEXT and stops — no
auto-assign, no auto-close. You can use {{name}}, {{first_name}}, {{shop}},
{{agent}}; anything unknown stays as it is, so whoever sends it sees it and fills it in.
With nothing set, each person’s “Your numbers” card shows no goal line — no default number is made up. A narrower target wins over a broader one: one person → a role → the whole team.
Tết, 30/4, 2/9 — closed whatever the working hours say. Customers are told which holiday it is, and nobody is counted as kept waiting.
The chat is called from the store admin, and we answer only the exact origins on the
list. An origin that is not on it is refused here and then discarded by the browser — so the customer
sees a widget that does nothing and we see an inbox with nothing in it. Most of these are strangers.
If one of them is a place your product actually runs, it belongs in GEMCARE_ALLOWED_ORIGINS.
Cold sales mail from an address we have never talked to. Read one before you trust the filter — if it is a real person, “This is a customer” files it as a conversation and that address is never screened again.