Danube CRM · Ticketing

Every request becomes a ticket with an owner.

Emails to support@, WhatsApp conversations and website forms land on one board, sorted by AI and assigned to a colleague. You answer from the ticket, and the whole history stays on the client. From €6 per user a month.

  • Shared inboxes from Gmail, Outlook / Microsoft 365 and IMAP
  • WhatsApp Business conversations become tickets
  • Assigned in rotation, with nobody answering twice
Danube screen: Danube CRM · Ticketing

Requests today

A shared inbox is not a queue. It is a place where requests wait.

Today

Two people answer, or nobody does.

In a shared mailbox nobody knows who took what. Some clients get two answers, others none.

Today

The history is in someone’s inbox.

When a colleague is away, the conversation with the client is away too.

Today

You cannot count what you cannot see.

How many requests came in this week, how many are open and who is overloaded stays a feeling.

How it works

One board for everything clients send you.

Intake

Email, WhatsApp and web forms arrive as tickets, already filled in.

Danube reads the mailboxes you choose, personal and shared. AI sorts each email, fills in the company, the person and the phone number, puts the attachments on the ticket and assigns a colleague.

  • Replies in the same thread join the existing ticket instead of opening a new one
  • The sender gets an automatic confirmation, from a template you edit
  • Emails that are not requests are forwarded to the address you choose
Danube screen: Email, WhatsApp and web forms arrive as tickets, already filled in.
Assignment

Every ticket has an owner from the first minute.

Requests from shared inboxes are handed out in rotation to the colleagues you choose. Whoever is offline or on leave is skipped, and their tickets go to a replacement.

  • Stages and groups of your own: open, in progress, waiting for the client, solved
  • Priority, deadline and any other column your process needs
  • Overdue tickets show as a number next to the menu
Danube screen: Every ticket has an owner from the first minute.
Replies

Answer from the ticket. The history stays with the client.

The conversation opens next to the ticket: you reply by email from your own mailbox or on WhatsApp, and every message, file and note stays on the record and on the company’s page.

  • Internal chat on the ticket, with mentions that also arrive by email
  • On WhatsApp: free text within 24 hours of the client’s last message, an approved template after that
  • An AI agent can draft the reply that asks for missing details; a person sends it
Danube screen: Answer from the ticket. The history stays with the client.
Follow-through

Rules that move tickets, and numbers that show the load.

When a status changes or a date arrives, Danube notifies the owner, creates the next task or sends the email. Dashboards show tickets by stage and by colleague, live.

  • Automations and visual workflows, with branches and waits
  • Follow-up sequences that stop when the client replies
  • Dashboards shared read-only and exported to Excel
Danube screen: Rules that move tickets, and numbers that show the load.

Screens are from the platform, with sample data. Some show the Romanian interface; the app also runs in English.

What comes with it

A help desk that already knows your clients.

Tickets sit in the same CRM as companies, contacts and deals, so nobody asks the client the same thing twice.

  • One page per client

    Tickets, orders, activities and every email the system sent, on the company’s page.

  • AI that sorts

    Request, existing client, supplier or spam: each email is classified before it reaches the board.

  • Your own AI agents

    Agents with your instructions that search the CRM with the user’s rights and never send anything on their own.

  • WhatsApp agent

    On the Business plan an agent can sort new conversations and send the first reply.

  • Tasks on tickets

    Calls, meetings and to-dos tied to the ticket, synced with Google Calendar and Outlook.

  • History and undo

    Who changed what and when, with “Undo” and a bin that brings tickets back.

Getting started

From a shared inbox to a queue, in an afternoon.

  1. 1

    Create the board

    Describe your support flow and Build with AI proposes the stages and rules.

  2. 2

    Connect the channels

    A guided setup walks you through the mailboxes and WhatsApp Business.

  3. 3

    Choose who gets what

    Rotation between colleagues, with replacements for leave.

  4. 4

    Answer from the ticket

    New requests arrive assigned; the history builds itself.

Questions

What teams ask about ticketing.

Is ticketing a separate product?

No. It is part of Danube CRM, at €6 per user a month on every paid plan. Reading emails with AI comes with the Team plan, and AI agents with Business; the boards, automations and WhatsApp intake are on every plan.

Which mailboxes can we connect?

Gmail, Outlook / Microsoft 365 and IMAP mailboxes, like the ones on cPanel hosting, personal and shared.

Does AI answer clients on its own?

No, unless you decide otherwise. AI sorts, fills in and drafts; a person sends. The exception you can switch on is the WhatsApp agent’s first reply, on the Business plan.

Does it have SLA timers and reports?

Tickets have deadlines, overdue alerts and dashboards by stage and by colleague. Contractual SLA reporting, with your own rules and calendars, is something we add as a custom build.

What happens when we reach a plan limit?

Admins get an alert at 80% and at 100%. Nothing that exists stops working: automated emails and actions over the limit wait in a queue until you add a pack or the month resets.

Give every request an owner.

A 15-minute demo on your real inbox. We show you the board, the rotation and what it would cost.