Skip to main content

baton.

Morning. Evening. Overnight.

A healthy eBay business isalways^ always answering messages.

Each one takes 5 to 7 minutes to review, respond, and act on. Across a busy store that is over 8 hours, every day.

Introducing

baton.

Every message worked, start to finish. It runs inside Claude, so there is no new software to learn.

The morning starts with one sentence.

54 conversations came in overnight. Ask Claude for the board and every one arrives read, researched, and drafted.

A Claude prompt bar with the message Show me the message board, sent with the send button. The message board below is the answer.

Claude Desktopclaude.aiClaude app on your phone

Ready for your review and approval. Grouped by what each conversation needs.

Per message

7 minutes

35 seconds

That's 8x faster.

The research, the context, and the draft are already done. What remains is the one part that should be yours: the decision.

Every card arrives fully briefed.

Ten evidence tabs under every draft, straight from eBay's records. Point at one to open what Baton already pulled.

A Baton review card with the ten-tab evidence rail from the product: buyer, messages, listing, order, shipment, return, cancellation, inquiry, case, and pictures. Each tab opens the record it names; tabs with no record stay dimmed. All sample data.

You read. You decide.

A Spanish question arrives translated and answered in Spanish. A scuff complaint arrives with the $30.00 make-it-right refund staged beside the reply. 35 seconds, then the next.

Interactive demonstration of the Baton review card. A Spanish pre-sale question arrives translated, with a reply drafted in Spanish, the rationale beneath it, and the buyer's photos one tap away; Approve and Next stages it. A condition complaint follows with a thirty dollar partial refund prepared to travel with the reply; approving it arms a Confirm thirty dollars button, and the confirming press stages the refund with the reply. All sample data.

baton.MESSAGES
← Back to board3 of 41

Sony PlayStation 4 Pro 1TB Gaming Console ONLY Fair

Pre-sale questionGENERALWAITING <1H
luis_retrogamesBuyerJul 21, 9:12 AM

¿Cuál sería el total con el envío a Texas?

What would the total be with shipping to Texas?

Draft reply · SpanishAsk baton.
¡Hola! El envío se calcula al finalizar la compra: si ingresas tu código postal en la página del artículo, verás el total exacto antes de pagar.

Hi! Shipping is calculated at checkout: enter your zip code on the listing page and you'll see the exact total before you pay.

Buyer wrote in Spanish. Baton detected the language, translated the message, and drafted the reply in Spanish with the shipping policy applied.buyer_messages_not_english · auto_translated · policy_ship_calculated
15
HoldSkip

The buttons are live. Approving the refund card arms the real Confirm $30.00 press.

Coached once. It sticks.

Say the play in plain words and the draft rewrites in your voice. The same box takes action: apply a partial refund, cancel an order, start a return. Tell Baton to save the play as a memory and every future card like this one arrives already following it.

One confirm sends them all.

The button says exactly what it will do, then asks again. Refunds execute before the replies they travel with, duplicates are suppressed on purpose, and the board flips to Sent as eBay accepts each one. Nothing sends until you approve it.

Done by lunch.

The whole queue, start to finish in under 30 minutes, with receipts for all of it.

41

replies sent

13

closed, no reply

0:35

per message

Watch a full pass.

Thirty seconds of the board at work: conversations land grouped and drafted, one review stages a $30 refund beside its reply, and a single confirm sends both. The operator guide covers every workflow behind it.

Open the Operator Guide
30 seconds

The board, a review, and a confirmed send, end to end.

Messages is one of nine queues.

One agent, working the whole support business. Each queue assembles on request with the orders, deadlines, and dollar amounts attached.

Buyer messages

Every open thread pulled, matched to its order, and drafted for review.

Returns and refunds

Delivered returns arrive with tracking proof and exact refund math.

Cancellations

Each request arrives with its deciding fact: shipped, or still on the shelf.

Item not received

Tracking events and inquiry deadlines side by side, ready to answer.

Cases and escalations

Respond-by dates front and center. Case deadlines decide cases.

Best Offers

Offers compared to list price and recent sales, with a recommendation.

eBay notices

System messages sorted into action needed and acknowledged.

Orders needing attention

Unshipped, unpaid, and unusual orders flagged with a next step.

Sales reports

Revenue and units, reconciled against eBay's own numbers.

The model proposes. The engine checks. You approve.

Baton ships read-only. Writes stay off until you turn them on, and each class of action has its own gate.

Preview, then approve

Every write dry-runs first and shows the exact action your approval releases.

Money moves last

Refunds preview first; the action you approve is the action eBay receives.

Stale writes blocked

If eBay changed since your review, the action stops and asks for a fresh queue.

Duplicates suppressed

A message that already went to a conversation is skipped on purpose, and the receipt says so.

Private by default

Names, addresses, and payment details are masked before anything reaches Claude.

The same gate guards every write: replies, refunds, offer responses. You approve the exact action, and eBay readback confirms what happened.

8x your productivity. Pass the baton.

We connect Baton to your store, run your first batch beside you, and hand over the playbook. Twenty minutes on a live queue shows the whole loop.

Every demonstration on this page, including the film, runs on sample data. Buyers, orders, and amounts are fictional. Baton reads live stores through eBay's APIs with personal information masked before it reaches Claude. Writes stay off by default, and every action requires operator approval of a previewed change.