The morning after the night shift you didn't hire

While you slept, the agent answered from the pool. What's left is a short, sorted queue — each thread carrying a summary and its full history.

Refund missing after a cancelled order

Resolve
Conversation
Lea T.11:41 PM

I cancelled order #7241 last week — still no refund

ReplyPool Support11:42 PM

Your refund was issued the same day you cancelled — banks usually post it within 2–4 business days.

Lea T.11:46 PM

It's been six business days now and nothing has arrived

Nina11:49 PM

Hi, I'm Nina — tracing your refund right now.

ReplyNotesCopilot
Type your reply or type "/" for macros
Send

Open one tab. Most of the work already happened

By nine, the repeats are closed and the queue holds only what genuinely needs a person.

The pool absorbs the repeats

Where-is-my-order and how-do-returns-work never reach a human — the agent closes them as they arrive.

The remainder arrives dressed

Every escalation lands with an AI summary and the whole history — pick it up in one click.

Nobody answers blind

Notes, @mentions, and live presence show who's on a thread, so two people never reply to one shopper.

The queue shows up pre-sorted

Threads file themselves by state, and fresh work spreads across whoever is actually on shift.

  • Built-in views: Mine, Mentions, Snoozed, Needs human, AI handling, AI resolved
  • Any filter becomes a shared view in two clicks
  • Round-robin or least-busy dispatch that knows shifts and time off
  • Away teammates are skipped — no thread waits on an empty chair
Inbox
Your inbox
Mentions2
Mine6
Queues
Needs human1
Folders
AI Agent
Channels
More

Type the returns spiel never again

Macros, drafts, private notes, and delivery status live inside the reply box — the housekeeping happens where your hands already are.

  • Rich replies with inline images and attachments
  • Shopper-facing replies and private notes share the thread, clearly split
  • Half-written reply? Switch threads — the draft waits for you
  • One slash command fires a macro that replies, tags, assigns, and closes
  • Every message shows its delivery state, with one-click resend

The order details are
already on screen

Asking twice reads as not listening. The shopper's profile, past orders, and previous conversations sit one glance from the reply box.

  • Profile, company, and custom fields pinned beside the thread
  • Tags, folders, page context, and every earlier or linked conversation in reach
  • The same buyer on email and Telegram resolves into one contact
  • Ambiguous matches wait for you — merge by hand through a search dialog
  • Matching keys off identifiers, never guesswork — merging stays your call
Every channel, one person — and zero "can you confirm your order number again?"
MK
Mia KarlssonUser
mia.k@lumen.io
Berlin, DE 14:32

Details

CompanyVela Commerce
Conversations3
First seen21d ago
Last seen4m ago
OutboundSubscribed

Recent conversations

  • Late refund on order #63904m ago
  • Card update before renewal2d ago

Segments

VIPBillingEU
Send messageUnsubscribeMerge…

Change helpdesks without amnesia

The usual toll: lost history, a bot that knows nothing, macros rebuilt from memory. Coming from Zendesk, Freshdesk, or Intercom, you skip all of it.

  • Day one starts with your full history, searchable
  • Nothing rebuilt by hand, nothing configured twice
  • The team keeps answering while the move runs
Zendesk
Freshdesk
Intercom
ReplyPool

What travels with you

  • Every past conversationImported and searchable from the first morning
  • Contacts & companiesDeduplicated on arrival — no tangle to clean up
  • Help center articlesStart feeding pooled answers immediately
  • Macros & canned repliesArrive working, not as a to-do list
  • Teams, tags & workspace settingsRecreated the way you had them

Friction compounds. So does its absence

Bulk actions, snoozes, priorities, previewed search, synced badges, and a spam folder — ten-second savings that add up to an hour.

Bulk actions

Sweep a promo-day backlog: close, tag, or assign in batches.

Snooze presets

Waiting on the carrier? Snooze it — the thread returns on its own.

Priorities

Flag the VIP order so it stands out in every view.

Search with previews

See the message before you ever open the thread.

Unread counts in sync

Badges agree across every tab and device.

Spam folder

Junk files itself away from the working queue.

Asked before the switch

Straight answers on channels, routing, and how the queue behaves with the AI on it.

13 channels in total — email, the storefront widget, WhatsApp, Instagram, Telegram, Facebook Messenger, and more. They all feed one queue, and each shopper keeps a single continuous history even when they jump channels halfway through a return.
Every new conversation goes to the agent first, on the pool's dime. When a person is needed, the thread surfaces in the Needs human view with an AI summary and its complete history attached. Teammates can grab an AI-handled thread with a single click — and give it back just as fast. Replies written by your people never count against the pool.
You choose round-robin or least-busy dispatch. Routing understands working shifts and time off, and skips teammates who are away — so the 2 a.m. escalation waits for the morning shift instead of pinging someone on vacation.
Yes. Open the AI handling view for a live list of everything the agent is working on this minute; AI resolved holds what it finished. Click into any thread, read along, and step in the moment you want to.
No — a macro fires from a slash command right in the composer, and it can do the chores too: assign the thread, drop tags on it, or close it as your reply sends. One keystroke, answer plus housekeeping.
No. Deduplication runs the moment a message arrives: the same person writing from email and Telegram becomes one contact with one history. Anything automation can't match safely waits for you in a manual merge dialog with search.

Give the queue a night shift

Connect your channels, switch the agent on, sleep. 14 days free, no credit card required.