Skip to main content
DMLY has no separate Reports screen. Overview — the first page you land on — is both your dashboard and your analytics. Everything reported about conversations lives there: the Message volume chart and the Reply rate card.
There is no Analytics or Reports entry in the sidebar, and no per-agent or per-conversation breakdown. If you are looking for numbers about a single automation, open the ⋮ menu on its row in the Automation list and select Analytics instead — see Automation overview.

​
What is measured

1

Message volume

A two-line chart headed Message volume, described as Outbound vs inbound messages over the last 14 days. One line is Outbound, the other Inbound. If neither side has any activity in the window, the panel shows No message activity yet.
2

Reply rate

A card in the At a glance grid. It is the share of your contacts who have ever sent you an inbound message, out of all your contacts.
3

Messages sent

A card in the same grid — an all-time count of messages sent for the selected channel.
4

Calls and Call answer rate

Two extra cards that appear only when the selected channel is WhatsApp. They render even with no call history, reading 0 and 0%. See WhatsApp.
The At a glance grid also carries Contacts, Flow completion, Broadcast delivery, Growth clicks, Opt-out rate and Active sequences. Those are covered on Analytics overview.

​
Filters and date ranges

This is the part people most often get wrong, so read it before you draw conclusions.
  • The only filter is the channel selector. Pick a channel at the top of the page and the conversation numbers follow it. There is nothing else to narrow by — no agent, no tag, no segment.
  • There is no date-range picker. You cannot change the period, and you cannot compare two periods.
  • The chart window is fixed at the last 14 days. It is not adjustable.
  • Every other number is all-time. Reply rate, Messages sent and the rest count everything since the workspace started, not the last 14 days.
Because the chart is 14 days and the cards are all-time, the two never add up. A quiet fortnight will show a flat Message volume chart while Messages sent still reads high. That is expected, not a bug.

​
How to read them

Reply rate answers “how many of my contacts have ever replied to me?” — not “what share of my messages got a reply?” and not “how fast did my team answer?”. A contact who replied once, two years ago, counts the same as one who replies daily. It moves slowly and it only ever moves up unless you add contacts who never reply.This makes it useful for one thing: spotting a contact list that has gone cold or was imported from a source that never engages. It is not a service-level measure.
Switch channels and the chart redraws. If you run WhatsApp and Instagram, neither view shows a combined total — check each one. A completely flat chart on a channel you know is busy is a connection symptom, not a reporting one; see No inbound messages.
The Recent activity panel lists the last handful of events on the selected channel with a status dot and a time. It is there for a quick “did that just work?” check. For anything you need to investigate properly, use Logs.

​
What you will not find here

  • No CSAT scores. The CSAT Survey node routes each rating to its own branch inside a flow, but ratings are never totalled or charted anywhere. See CSAT.
  • No export. Overview has no export button. Contacts and appointment data can be exported — see Exporting reports.
  • No scheduled or emailed reports.
Reporting is not restricted by plan. What you see is set by your role — a team member without Appointments access simply loses the appointments panel. See Roles and permissions.

Analytics overview

Every card on the Overview page and what it counts.

CSAT

Collect ratings in a flow and route by score.

Exporting reports

What can leave DMLY as a CSV, and what cannot.

Inbox overview

Where the conversations these numbers describe actually happen.