Source
Public GitHub repository

Frontdesk

A shared support inbox that sorts new messages, prepares an answer, and leaves the final send with a person.

deepak-jha-kgp/frontdesk
READMEHEAD

Why it exists

A busy support inbox creates the same problems every day: unclear ownership, missed response times, answers written without the right context, and risky replies sent too quickly.

Frontdesk gives the team one place to see the conversation, the customer, the deadline, the draft, and the reason behind the draft. The agent does the repetitive preparation; the team keeps control of what reaches the customer.

What it does

  • Bring new support messages into a shared conversation list.
  • Apply the team's routing rules, category, priority, and response-time policy.
  • Use playbooks and customer context to prepare a cited reply.
  • Turn a conversation into an issue when the answer needs more work.
  • Require a person to review sensitive replies before they are sent.

What a normal use looks like

A billing email arrives after lunch. Frontdesk marks it urgent, finds the billing playbook, and prepares a reply with the relevant policy. The support lead changes one sentence and sends it. The original message, draft, review, and send status remain together.

How it is built on Lemma

This repository contains the pod itself, not just a screenshot or a prompt. The interface and the parts that do the work are installed together.

  • apps/frontdesk/ — The inbox and conversation view the support team uses.
  • tables/ — Customers, conversations, messages, drafts, issues, playbooks, routing rules, and response-time policies.
  • agents/desk-agent/ — The support agent's instructions: what to inspect, what it may draft, and when it must stop.
  • functions/ — Message intake, completed sorting, guarded sending, and response-time checks.
  • workflows/ and schedules/ — Handle new mail when it arrives and keep checking conversations that are close to being late.

The files in this repo contain the structure and instructions. Your private records, connected accounts, credentials, and deployed URLs are added after import.

Install and remix on Lemma

The button opens Lemma's import flow for this exact GitHub repository:

https://lemma.work/import/github/deepak-jha-kgp/frontdesk

Connect your own Gmail account, add your playbooks and routing rules, then send a test message. Credentials and customer mail are never stored in this repo.

Import from the command line

git clone https://github.com/deepak-jha-kgp/frontdesk.git
cd frontdesk

lemma pods import . --dry-run
lemma pods import .

Make it yours

You do not need to keep this pod exactly as it is.

  1. Fork the repository.
  2. Change the instructions, app, tables, or rules for the way you work.
  3. Import your fork with https://lemma.work/import/github/<your-github-name>/<your-repo>.
  4. When it is useful, show your version here with one screenshot and a short note about what changed.

If this pod saved you from rebuilding the same thing, star the repo so the useful versions are easier to find.

Repository guide

Share