How Delvra works.

A message comes in. Delvra understands it, acts or asks you, and logs every step.

One loop, every request.

The same four steps run for a question about an order and for a refund. Only the rules change.

  1. Message

    A customer writes on WhatsApp or on your site.

  2. Understand

    Delvra reads the request and looks up what it needs in your systems.

  3. Act or ask

    It acts within your rules, or prepares an approval for you.

  4. Log

    Every step is written down, with undo where the action allows it.

From sign up to live.

What happens in your first weeks, and what is ready today.

  1. Sign up

    In pilot

    Request early access, or book a demo and our team sets it up with you.

  2. Connect

    In pilot

    Link WhatsApp, your store or the built in CRM. Keys are stored encrypted.

  3. First run learning scan

    In pilot

    A read only scan lists your data and the actions it allows. Scanning any system with an API is being built.

  4. Shadow, then live

    Being built

    In the first week Delvra prepares replies and actions without sending them. You review, then switch it on.

  5. Approvals from your phone

    In pilot

    Approve or reject in the portal on your phone. Approving inside WhatsApp is planned.

  6. The log

    In pilot

    Every message, action and decision, with who approved it and an undo where possible.

  7. Comments

    Being built

    Write a note on any approval or run, and turn it into a standing rule.

The next morning

Coffee first.

No inbox to dig through.

Illustrative scene
The next morning
While you were away
14conversations handled
3waiting for your approval
2handed to your team
  • Cancel 1 item · order 5203−₪89✓
  • Exchange size · order 5188₪0✓
  • Refund shipping · order 5171−₪29✓
  1. Coffee first.

    No inbox to dig through.

  2. The night, on one screen.

    What was answered, what was done, and what waited for you.

  3. Three approvals. Done.

    Before the first customer walks in.

One request, end to end.

An address change, from the first message to the log line.

Illustrative interface. Sample data, not a real customer.In pilot
  1. Customer asks to change the delivery address.
  2. Delvra reads order 1042, read only.
  3. Delvra drafts the address change.
  4. An approval card reaches the owner.
  5. Dana approves the change.
  6. The change is logged and can be undone.

Try a request yourself.

Pick a message and see what Delvra would do with it.

Customer chat

← Where is my order?

What Delvra did

    Demo store, sample data. Nothing here reaches a real system.

    Live in four steps, with our team.

    1. Map

      One workflow, one success metric. We check that your systems expose what is needed.

      You bring: 60 minutes and the person who owns the process.

    2. Connect

      Read-only connections, your approved knowledge and a short list of actions.

      You bring: account access, through the secure portal only.

    3. Test

      At least 50 scenarios, including wrong customers, duplicates and attempts to break the rules. A shadow week before customers see anything.

      You bring: a review of the answers.

    4. Launch

      Gradual go-live by channel or task type, with monitoring and a pause switch.

      You bring: the final approval.

    Start with one workflow. We set it up and run it with you.

    Tell us which messages eat your team’s day. In 30 minutes you will see it running on a demo store, what it would cost you and what stays in your hands.