Every channel in, one request out.

A customer might start on your website, send the boiler photo on WhatsApp and follow up by email. Every message lands in the same queue and stays with the same enquiry, so your team sees one customer and one job rather than three loose conversations.

Every channel, one place to answer

Website chat, email, WhatsApp, Telegram, Instagram, Messenger, Discord, Slack and SMS land in one queue. Your reply goes back on the channel the customer used.

One request per job, not per message

A customer who writes on WhatsApp and then emails does not become two jobs — the follow-up joins the request that already exists.

01

Every message arrives the same way

Whatever channel it came from, it is stored the same way, with the customer identified and the attachments carried across.

02

It joins a request

A new one if this is a new job, the existing one if the customer is continuing — decided by the rules, not by whoever happens to read it.

03

It reaches the right person

Ven proposes what it can, a teammate takes ownership, and the reply leaves on the channel the customer used.

The channel it came from

Visible on the thread, so the reply matches how the customer wrote.

The request it belongs to

One per job, however many messages and channels it took.

The customer behind it

Address, equipment and past visits, attached before anyone replies.

That is why arriving twice is not a problem here. Somebody who asks on WhatsApp and then emails a photo of the rating plate has added to one request — the second message is evidence, not a second job for somebody else to pick up and duplicate.

  • The channel stays visible

    Whoever answers can see where the customer wrote and match the register they already used.

  • Ownership is explicit

    Assigned, unassigned or handed over — always visible, so two people never answer the same person at once.

  • Attachments become evidence

    A photo of a rating plate is linked to the request and to the equipment it identifies, not lost in a thread.

  • History follows the customer

    Past visits, the address and the equipment are on the conversation before anyone starts typing.

Stop checking four apps for the same customer

Connect the channels you already answer on and watch them arrive in one place, already attached to the work they are about.