AI writes the reply.
You press send.
Every support email, chat and DM arrives as a ticket with a draft already written — from your own website, your store, and the carrier holding the parcel.
An example support email, and the reply Wilph drafts for it
sarah@example.com
Where's my order?
Hi — I placed order 1042 on Tuesday and haven't heard anything since. Is it still coming?
Hi Sarah — order 1042 left the warehouse on Wednesday, and UPS is reporting it in transit, due Friday. If it's not right when it arrives, you have 30 days to send it back.
Every fact above came from:
Why this exists
Most of your inbox is the same four problems
None of them need a person to think. All of them need a person to look something up.
- “Where is my order?”
- Opening the shop, then the carrier, then typing the same reply again.
- The answer is already written down
- It is on your delivery page already. Finding it takes longer than writing it.
- Bots that cannot look anything up
- One that cannot read the order deflects to a form. They email you anyway.
- Peak does not wait for hiring
- One sale doubles the inbox overnight. The team is the size it was yesterday.
Before you trust it
What if it gets something wrong?
Nothing sends itself
No tag, setting or plan lets a ticket reply leave unattended. A person presses send on every one.
Answers from your own site
It reads your delivery, returns and product pages. When they don't cover a question it says so instead of guessing.
Judge it on your old tickets
Upload an export of past support mail and read each draft beside the reply your team really sent.
Built for US shipping
Connect your store and a carrier — UPS, FedEx, USPS, ShipStation or Shippo — and a reply quotes the status the carrier reports right then.
Getting started
Live in four steps
Connect your stack
Forward your inbox. Connect your shop and carriers.
Teach it your policies
Your return window, your tone, your escalation rules.
Check it against your own history
It drafts your old tickets beside what you really sent.
Decide what it may touch
Tag by tag. A person still presses send.
Channels and integrations
Where it answers, and what it reads
Four channels working from one set of policies — and the store, carriers and payment providers behind them.
Pricing
Everything included. Priced by volume.
No per-resolution fees. No per-agent pricing.
Questions
Straight answers, before you book anything
- Does Wilph reply to my customers on its own?
- No. Wilph writes the draft and a person on your team presses send. No tag, setting or plan lets a ticket reply leave unattended.
- Where do the answers come from?
- Your own website — delivery and returns pages, FAQs, product pages. When your site doesn't cover a question, Wilph says so and hands the ticket to a human instead of guessing.
- Can I see how good it is before I trust it with real customers?
- Yes, and it is the step we recommend first. Upload an export of your past support mail and read each draft beside the reply your team actually sent at the time.
- Where do order and tracking details come from?
- Two places, in order. Your store says which order this is and the tracking number it handed over. Then the carrier says where that parcel actually is — connect UPS, FedEx, USPS, ShipStation or Shippo and the reply quotes the live status and the carrier's own delivery estimate. Without a carrier connected you still get the tracking number, just not where it is.
- What do I have to set up before it works?
- Forward your support inbox to the address Wilph gives you, and point it at your website. Connecting your store, carriers and payment provider is optional, and it is what makes order-specific answers possible.
Ready to see it on your own tickets?
Start free, connect your inbox, and watch it draft replies before you let it send anything.