Ab Singh AI systems

Project / Customer-facing systems

Inbox triaged, drafts written, exceptions surfaced.

Live demo
app.sifter.email
Account · Primary4 signals armed
Inbox · 5 sample messages Walking the inbox — pick one to stop
  • Accounts 08:12 re: invoice 2291 — payment terms We can pay this, but our terms are 45 days net and the invoice says 14. Can you reissue?
  • Procurement 09:41 Quote request — 40 units Looking for pricing on 40 units delivered to two sites, ideally before the end of the month.
  • Customer 10:03 Third time asking about my delivery Nobody has replied to either of my last two emails. This is the third time I am asking and I want it resolved today.
  • Partnerships 11:20 Quick intro — mutually beneficial I work with brands in your space and would love 15 minutes to explore a partnership opportunity.
  • Ops lead 11:47 Portal down for our whole team since 09:00 Nobody on our side can log in. We have twelve people sat doing nothing. Please tell me what is happening.
Triage rubric
Sentiment 0.15 below −0.5 the agent stops writing and hands the thread over
Intent billing · terms query one of eleven classes; anything unmatched routes to a person
Urgency 38 70+ jumps the queue and pings the owner
Route Finance · draft the queue it lands in, and whether a draft is written at all
  • read thread of 4 · invoice 2291 attached
  • matched customer record · terms on file = 30 days
  • rule terms change > 30 days needs finance sign-off
Draft reply Draft ready · awaiting send

re: invoice 2291 — payment terms

Your account is set to 30 days, not 14 — the invoice was issued on the wrong template and I've flagged it to be reissued. 45 days is outside what I can agree here, so I've put it to our finance lead with the history on this account. You'll hear back on this thread. The corrected 30-day invoice will follow either way.

app.sifter.email
Demo environment — sample inbox.
  • Claude API
  • OpenAI API
  • LangChain
  • LlamaIndex
  • Pinecone
  • n8n
  • Make.com
  • Zapier
  • Supabase
  • Airtable
  • PostgreSQL
  • Google Sheets
  • Python
  • FastAPI
  • Node.js
  • Cloudflare
  • Google Cloud
  • Hetzner
  • Shopify
  • Slack
  • HubSpot
  • GoHighLevel
  • Klaviyo
  • Chatwoot
  • WhatsApp Business API
  • Meta API
  • Mailgun
  • OpenAI Vision
  • ClickFunnels
  • Twilio
  • ElevenLabs
  • Whisper / TTS
  • Docker
  • Redis
  • Stripe

What it is

A shared inbox where most of the work is deciding what each message is before anyone can answer it.

Every inbound email is scored against four signals — sentiment, intent, urgency, and route — before a word is drafted. The score decides where it goes: an auto-draft sitting in the thread ready to send, a routed handoff to whoever owns that account, or a flag if something in it reads as a problem. Roughly seven in ten drafts go out unedited.

The rubric is visible in the demo, because the rubric is the system. Anyone can generate a reply. The value is in a triage decision you can read back and argue with.

From a real engagement. Names are changed; the numbers are not.

How it works

The rubric is the system. The draft is just the payload.

  1. Every message is scored first

    A new email fires a Gmail push notification into a Make.com / n8n flow. The flow loads the message and its thread history before a single word of a reply is written.

  2. Four signals, not a vibe

    Claude API scores the message on sentiment, intent, urgency, and route. All four scores are shown in the demo, because a triage decision you can read back is the thing worth having.

  3. The score decides the action

    Routine, high-confidence mail gets an auto-draft left in the thread ready to send. Anything account-specific is routed to whoever owns that account. Anything that reads as a complaint is flagged, not drafted.

  4. Answering becomes approving

    Roughly seven in ten drafts go out unedited. Mailgun handles the send. The work shifts from writing every reply to approving most of them and arguing with the few the rubric got wrong.

  • “It cleared the queue we could never keep up with. We only look at the handful it flags now.”

    Operations lead · multi-store retail operator

  • “Condition grading and pricing that used to be a weekend is now a photo upload.”

    Founder · collectibles brand

  • “The drafts are good enough that answering is now approving.”

    Operations lead · B2B services

  • “I stopped waiting for yesterday's numbers. Today's are just there, all stores in one view.”

    Owner · multi-store retail operator

  • “It books and qualifies before we're even awake. The morning list is just the ones worth a callback.”

    Founder · home-services company

  • “It shipped in pieces we could check as they landed, and the pieces we argued with got changed.”

    Operations manager · logistics

  • “None of it is rented. I did not expect that to matter as much as it turned out to.”

    Founder · consumer goods

Proof

"The drafts are good enough that answering is now approving."

Operations lead · B2B services

Walkthrough
A message arriving and being scored on all four signals, then the draft written and left in the thread.
Next project Ops dashboard Live demo inside Start a conversation What is your team still doing by hand? hey@theabsingh.com

The operation

Founder-led. Specialist-built.