Every reply, sorted by who is waiting on you.
One inbox for every rep's replies, in a frame that never jumps: the list, the conversation and the prospect side by side. Replies are labelled, grouped by what needs a person, and a positive one goes to your own CRM.
A rep who sees only their own prospects sees only their own threads. The database enforces that, not the screen.
Waiting on you
Emma Lindqvist · 12 min ago
AI draft · your edits are kept
Great, Emma. Invite for Thursday 10:00 is on its way to you and your plannerEmma Lindqvist
Head of planning · Nordvik AB
Lawful basis
Consent on call, 4 Nov
Owner
Sanne de Wit
CRM hand-off
On meeting booked
How it works
Three bands, and nothing moves when you click.
The frame is drawn before anything is selected. Opening a thread fills it without shifting a pixel, so your eyes stay where the work is.
1List
Waiting on you 3
New 2
Older 41
2Conversation
Today
Queued
3Prospect panel
- Owner
- Sanne de Wit
- Lawful basis
- Consent on call
- CRM
- In CRM
The list
Grouped into Waiting on you, New and Older, each with its true count. Filters show as chips, search is instant, and the list keeps its scroll and cursor when you open a thread.
The conversation
The whole history by day, in the market's time zone, theirs on the left and yours on the right. Sends on their way show at the bottom, a paused one with its reason.
The prospect
Owner, lawful basis, CRM state and the rest, docked beside the conversation on a wide screen, floating on a narrower one, a sheet on a phone. Closed or open, it remembers.
What happens to a reply
From the moment it lands to the moment your CRM owns it.
Grouping, filters and search
Waiting on you is a queue, not a pile.
A thread waits on you when the prospect spoke last, a person needs to answer, and nothing of yours is already on its way. Interested replies come first, then whoever has waited longest. The counts are true counts, from the same rule as the badge in the navigation and the number on the dashboard.
- Filter by intent and channel; each filter is a chip you can clear, and it survives a shared link
- Search folds accents: “muller” finds Müller, “strasse” finds Straße
- When the inbox is bigger than what is loaded, the same search runs over all of it, and says so
- Read state is per person: opening a thread marks it read for you, nobody else
Waiting on you3
New2
+1 more
Older8
+7 more
Search “muller” finds Müller · all 1,240 threads asked
Labels and corrections
Labels you can correct, and every count follows.
Every reply gets a label: interested, not interested, referral, wrong person, out of office and so on. When the label is wrong, the pill on the message opens the correction menu. The correction is kept with who, when and why, and the counts, the funnel and the manager view all read the corrected label from then on.
- A label the classifier is not sure about pauses the sequence instead of ending it
- Out of office pauses the sequence until the return date in the reply
- Without an LLM key, labelling falls back to keywords instead of stopping
- Viewers read; editors and admins correct
Correct the label
- Interested
- Reply
- Neutral
- Referral
- Not interested
- Wrong person
- Out of office
Reason
Wants a call in January
Label history
09:52 · Sanne de Wit
Not interested to Interested
“Wants a call in January”
09:41 · Classifier
Not interested · confidence 0.74
The hand-off
A positive reply goes to your CRM. PEMAX is never a second one.
When a reply is interested or a meeting is booked, PEMAX sends one signed webhook to your own CRM with the prospect, the company, the owner, the lawful basis and the recent history. Your CRM answers with its ids, and the prospect shows In CRM with a link straight to the record. From there, your CRM owns the lead.
- Signed with HMAC over a timestamp and the body; replays keep the same delivery id
- Retries with backoff; after eight failures a dead letter you can replay in one click
- A test delivery with a fictional lead before you go live
- Your own URL, events, signature format and header name
POST https://crm.brightwater.example/hooks/pemax
X-PEMAX-Event: lead.qualified
X-PEMAX-Signature: t=1762425720,v1=9f2c…e41a
{
"schema": "pemax.lead.v1",
"reason": "meeting.booked",
"prospect": { …, "lawful_basis": { … } },
"company", "owner", "sequence", "history"
}
In detail
Small things that save a rep an hour a day.
A composer that never blocks typing
A send clears the field at once and shows in the conversation as Sending, then Queued or Waiting in Review. If it fails, your words come back with the reason.AI drafts that never overwrite you
Ask for a draft and keep typing. Anything you wrote in the meantime stays; the draft waits behind Use the draft. The AI marking stays on the email after your edits.Replies from the right mailbox
A reply goes from the mailbox the thread started on when you may use it, else from your own. A rep limited to their own prospects connects a mailbox first. A colleague's is refused.Own scope, in the database
A rep set to their own prospects sees only those threads, through row-level security in Postgres. Owners and admins see the team. Viewers read without replying.Read state per person
Opening a thread marks it read for you alone, and Mark unread puts it back. A manager cannot see when someone read what, and staff never change it.Out of office, handled
An out of office pauses the sequence until the return date it mentions, or 30 days. It lands in New, not in Waiting on you, because nobody has to answer it.Bounces from the delivery report
Bounce reports are parsed properly. A hard bounce suppresses the address that failed, never your own; a soft one makes that person's emails wait 24 hours.Every channel in one list
Email, LinkedIn, WhatsApp, SMS and call threads sit in one list, the channel as a small badge. Replying from the inbox is email today; other channels draft and say why.Search from anywhere
The command palette finds prospects, sequences and threads with the same accent folding, shows recent activity when empty, and never prints an email address or phone number.
The details that matter
Built for the keyboard, with rules you can predict.
A rep works through a queue faster with hands on the keys. The list is a single tab stop with the arrows inside it, and an open menu or dialog always keeps the keyboard.
| Keys | What it does |
|---|---|
| / | Focus the inbox search, whenever you are not typing somewhere else. |
| ↑or↓ | Move through the visible threads. Down from the search enters the list. |
| Enter | Open the thread. Focus moves to the conversation's heading. |
| Esc | Close a floating panel or sheet; otherwise back to the thread's row in the list. |
| ⌘+Enter | Send an email reply. Ctrl + Enter on Windows and Linux. |
| Shift+Enter | A new line in a chat message, where Enter alone sends. |
| Group | Rule and order |
|---|---|
| Waiting on you | An open thread where the prospect spoke last and a person needs to answer: interested, a question, a referral, a wrong person, or not labelled yet. Nothing of yours is queued, sending, paused or in Review.Interested first, then whoever has waited longest. A queue, so nothing starves. |
| New | Unread by you, but not waiting on you: an out of office, an automatic reply, or a thread where your answer is already on its way.Newest first. |
| Older | Everything you have read and that does not need you now.Newest first. |
The navigation badge, the dashboard and the inbox count with this one rule, so the numbers always agree.
FAQ
Questions about the inbox
Is PEMAX a CRM?
No, on purpose. PEMAX runs the outreach and the conversation until a prospect qualifies. Then it hands the lead to your CRM, which owns it from there. Your pipeline, deals and accounts stay where they are.
Which CRMs does the hand-off work with?
Anything that can receive an HTTPS POST and check an HMAC signature. You set the URL, the events, the signature format and the header name; PEMAX shows the secret once and keeps it sealed. A test delivery lets you check the whole path before a real lead arrives.
Which mailboxes feed the inbox?
Replies are read from the reps' Google Workspace mailboxes. A Microsoft 365 mailbox can send a reply from the inbox, but PEMAX does not read incoming mail from it, so replies and bounces to an Outlook mailbox do not show up here.
How are replies labelled, and how long is that kept?
With an LLM key, a classifier reads the words of each reply; without one, a keyword classifier takes over. Labels that are a judgement, such as interested or not interested, become a plain reply after 180 days by default, and corrections go with them. Bounces, out of office and unsubscribes keep their label, because suppression depends on it.
Who sees which threads?
Owners and admins see the team's threads. A rep set to their own prospects sees only theirs. Viewers read without replying or correcting. PEMAX staff see a workspace only by acting as it through an audited grant, and entering and leaving it are both logged.
One workspace
Works with the rest of PEMAX
See PEMAX on your own pipeline.
Thirty minutes with the people who build it. We show the product on a real workspace, answer the hard questions about deliverability and compliance, and tell you honestly whether it fits.
Invite-only workspaces · Hosted in the EU · Bring your own keys