For online stores that run on email.

Your agent thinks. Wolp gets answers.

Tell your agent what you need from a customer or supplier. Wolp emails them, follows up until they answer and brings you the result.

Works in your agentChatGPTClaudeGeminiPiHermesCursor
How it works

The plan is yours.
The chasing shouldn’t be.

You know what needs to happen. Getting there takes dozens of emails, reminders and replies that arrive days apart. Hand that part to Wolp.

Twenty conversations.
All waiting on you.

A customer who promised to pay last week. A supplier who went quiet. A delivery that needs chasing. Different people, different threads. You’re the connection.

GmailGmail“Any update on the quote?”
CustomerCustomer“We’ll pay at the end of the month.”
DHLDHL“Where is the shipment?”
SupplierSupplier“Is the minimum still 500?”
SlackSlack“Did they ever pay invoice 2291?”
Supplier emailSupplier“Six units arrived damaged?”
OutlookOutlook“Invoice attached, please confirm”

Most of it
is waiting.

Who owes you a reply, who promised Friday, which invoice slipped past its due date. None of it is hard. It just never ends, and it all lives in your head.

Daysbetween one reply and the next

Your agent builds the workflow.
Wolp runs it for days.

Agent automations run a task and stop. Wolp waits days for a reply, follows up and picks the thread back up. Your agent sets it up over MCP or the API. You approve once.

They reply days later.
Your agent gets the result.

Replies come at 3 a.m., next Tuesday, after the second reminder. The workflow keeps running in the cloud and handles each one. When something needs a decision, it comes back to you with the context.

  1. D

    Dana, Northfield We’ll pay on the 15th.

    Date set
  2. K

    Karl, Bergen Tools Sorry, missed it. Paying Friday.

    Date set
  3. M

    Mia, Alder & Co The amount is wrong.

    Needs you
Wolp, back in your agent

12 of 14 invoices now have a payment date. Two customers dispute the amount. Those two need you.

One Wolp.
Endless workflows for your store.

Start from a workflow by Wolp or the community. Each one knows how the conversation should go, when to follow up and when to stop and ask you.

  • Overdue invoicesBy Wolp

    To accounts@northfield.co

    Invoice 2291 is 14 days overdue

    Hi Dana, could you tell me the date you plan to pay?

  • Supplier ship datesBy Wolp

    To wei@lumen-trading.cn

    PO 4471: can you confirm the ship date?

    Hello Wei, when does PO 4471 leave your warehouse?

  • Damaged goods claimsCommunity

    To claims@fastfreight.eu

    Claim: 6 cartons damaged in delivery 88213

    Photos attached. We would like a credit note or a replacement.

  • Missing trackingCommunity

    To dispatch@packright.nl

    Tracking for order 5120?

    The customer is asking. Could you share the tracking number?

  • Restock datesBy Wolp

    To hello@oakandfern.com

    When is the linen throw back in stock?

    We are sold out. Could you give us a restock date?

  • Quotes from new suppliersCommunity

    To sales@boxworks.de

    Quote request: 2,000 mailer boxes

    Could you share your price, minimum order and lead time?

  • Price list updatesCommunity

    To orders@alder.co

    Your price list for next season

    Could you send your updated prices before 15 November?

  • Wholesale enquiriesCommunity

    To hello@juniper-home.com

    Re: Stocking your candles in our shop

    Thank you for reaching out. Here are our wholesale terms.

  • Sample requestsCommunity

    To studio@milaceramics.pt

    Samples of the speckled mugs

    Could you send two samples before we place an order?

  • Supplier documentsBy Wolp

    To compliance@greenweave.in

    Updated certificate for organic cotton

    Our file expires this month. Could you send the new one?

Or make your own.

Describe it to your agent once. Wolp turns it into a workflow, runs it and comes back with what matters.

Example: you ask your agent to have Wolp collect next season’s prices from every supplier and flag rises over 5%. Wolp sets up the workflow, emails 14 suppliers and, four days later, your agent reports the two that went up.

Whichever you pick, every workflow plays by the same rules.

The work between
“sent” and “sorted”.

Not another place to manage messages.
A layer that moves the work forward.

Work to your terms.

Price, payment date, lead time. Wolp compares the answers, pushes for what fits your brief and never concedes past your limits.

Chase the answer.

Follow-ups that don’t wait for you to remember. Wolp keeps track of who owes you a reply.

Says who it is.

Wolp writes from its own mailbox and introduces itself as your AI assistant. No pretending to be you.

Decisions stay yours.

Within scope, Wolp keeps going. A dispute, an exception or any commitment comes back to you, with the whole conversation attached.

Reaches people byEmailWebhook, OpenAPI, your MCP server Coming

Good questions.
Straight answers.

A little more context
before you jump in.

What exactly is Wolp?

A service that runs your store’s email conversations with customers and suppliers. You or your agent describe the job, you approve it, and Wolp writes, follows up and brings the result back. You control it from your agent over MCP or the API, or from the dashboard.

Which jobs can it take on?

Any job that means emailing people and waiting for an answer: overdue invoices, ship dates, damage claims, restock dates, quotes, price lists, documents. The workflows above are starting points. Describe your own and Wolp builds it.

How long can a workflow run?

As long as the job takes, often days or weeks. Wolp waits for replies, follows up on schedule and keeps track of every thread in the cloud, so nothing depends on your chat or laptop staying open.

How is this different from ChatGPT or Zapier?

They work inside your company: ChatGPT writes a message, Zapier moves data between your tools. Wolp works with a person outside it. It has its own mailbox, matches every reply to the right conversation, follows up when there is silence, negotiates within the limits you set and does not let the other side talk it out of them. ChatGPT writes your supplier an email. Wolp runs the whole conversation, until you have the price, the date or the paid invoice.

Do I need a big team?

No. Wolp is built for stores that are short on hands. If you can describe the job, Wolp can run it.

Can I use the agent I already have?

Yes, that is the idea. Wolp connects over MCP, so ChatGPT, Claude, Cursor or your own agent can design, launch, check and pause a workflow and answer its questions without leaving the chat. The API covers your own systems, and the dashboard shows every run. You are not locked to one vendor.

How much control do I keep?

You set the goal, the hard limits and the tone, and you approve the first outreach. Any commitment, such as a price, a discount or a payment plan, comes back to you. Wolp never places orders or moves money on its own.

Does the other side know it is talking to an AI?

Yes, from the first message. It is your company’s AI assistant, not you.

Which channels does it use?

Email today, from Wolp’s own mailbox, because it reaches any business inbox. Next: your own channels and systems through a webhook, an OpenAPI spec or your own MCP server, without custom development. Messaging apps such as WhatsApp or WeChat are not part of the first version.

How do I get access?

Join the waitlist. We’re opening access to stores in batches and will reach out when your spot is ready.

Make the next move.

Let your agent
take it from here.

Less chasing. More moving forward.
Be first to put Wolp to work.