Find out which ads actually brought people in
If you run Click-to-WhatsApp ads, every click you paid for used to arrive looking exactly like somebody typing your number off a poster. The one question you buy the ad to answer had no answer anywhere in DMLY. It does now, in three places.You can see the ad on the conversation
When somebody taps an ad and messages you, DMLY keeps the ad. Their contact Source reads the ad’s own headline, so you getWhatsApp ad: Summer Sale rather than a number nobody
recognises, and the message itself carries the ad in the Inbox.The first ad that brought someone in keeps the credit. If they tap a second ad next month,
the ad that actually won them the customer is still the one on their record, though each
message still records the ad it came from.Your bot can answer the offer they tapped
A new Click-to-WhatsApp ad trigger starts a flow when somebody arrives from an ad, and the ad’s own words are available inside it. So a salon running a two-for-one can open with that offer instead of a generic hello:A new Ads tab on Reports
Configurations → Reports → Ads gives you one row per ad: how many conversations it started, how many of those people were new to you, and how much they have since paid you. With a date range, and a CSV to take away. See Ads report.This is response, not spend. DMLY only ever sees an ad when somebody taps it and messages
you, so it can tell you what an ad brought back but never what it cost. To work out whether an
ad paid for itself, set the revenue on this page against the spend in Meta Ads Manager
yourself. An ad with no messages does not appear at all, so read the list as “ads that got a
reply” rather than “the ads I am running”.
DMLY is on your phone now, on both stores
The DMLY app is out on iPhone and iPad and on Android. It is a real app from the store, not the dashboard in a browser window, and it is built for the half of DMLY you do while you are away from a desk.Download for iPhone and iPad
DMLY: Inbox, CRM & Bookings on the App Store.
Download for Android
DMLY: Inbox, CRM & Bookings on Google Play.
The thing the browser could never do
Push notifications. A new message, a chat assigned to you, an @mention, a booking, a payment, a failed one, a review. Your phone tells you while the app is closed, which is the whole point of having it there. Each one has its own switch, and there is a morning digest of the day ahead if you want one.What you get
The Inbox on every channel you have connected, with the WhatsApp reply window shown as a pill on each conversation so you can see how long you have left. Reply, attach a photo, drop in a saved reply, assign, tag, mark done, pause the bot.Today’s schedule and the calendar, so you can move a booking from the car park. Money in, and the invoices behind it. Four quick actions for the things you do most: new booking, record payment, new message, add contact.It is a companion to the dashboard rather than a replacement. Building automations, sending broadcasts and setting up channels stay on the dashboard, and the app opens it for you when a job belongs there.See The DMLY mobile app.Run your workspace by talking to an AI assistant
DMLY now has an MCP server. Connect Claude (or any other assistant that speaks MCP, including Claude Code, Cursor and VS Code) straight to your workspace, and just ask.How many conversations are waiting? Who hasn’t paid me? What did Maria’s last message say? Is there a slot on Tuesday afternoon? The assistant reads your real data and answers, instead of you clicking through screens to find it.Connecting takes about a minute
In your assistant, add a connector forhttps://dash.dmly.io/mcp, sign in to DMLY, and choose
which workspace it may work in. There is no key to create and nothing to paste, and that one
workspace is the only one it will ever see. See Connect Claude.It can only do what you can do
Sign in and the connection inherits your own DMLY role. A Viewer’s assistant can read and nothing else. Change someone’s role and their assistant changes with it, so giving a teammate an assistant isn’t a way around the permissions you already set. If you’d rather the connection didn’t belong to a person at all, create a key instead and pick read-only or read-and-act.Reading is the safe half, and most of the value
It can search contacts, read a thread, check the diary and free slots, and tell you what’s outstanding. Nothing there reaches a customer.Let it act and it can also reply, book and reschedule, raise and send invoices, record payments and pause an automation. Three limits stay on regardless of what anyone asks it for:- A broadcast always needs a person. The assistant can prepare one and show you exactly who it would reach, but it cannot send it. It waits in your broadcast list for someone to approve in DMLY.
- There’s a cap on how many people it can message, per hour and per day, counted across everything it does, including the confirmation that goes out when it books someone in.
- Everything it changes lands in your audit log.