All articles

Reports and the leads export

Where: open Reports from the side menu. The Leads & Deals tab lists your deals for the dates you pick, per business, and Export leads CSV downloads them as a file for Excel.

/reports/activity

Which deals a date range includes. By default (Dates: Activity date) a deal is in the file when, inside your dates, it was created, closed as won, or moved into a new stage for the first time. So a booking made on the 10th for an appointment on the 12th is in the file for the 10th. To list the deals whose appointment is inside your dates instead, choose Dates: Appointment date next to the export button. Deals without an appointment are not included in that file.

Times are in your team's time zone. Every date and time in the file is written as day/month/year hour:minute in the time zone set for your team, and the column heading names that zone, for example *created_at (Africa/Cairo)*. If no time zone is set, the times are in UTC and the heading says UTC.

Choosing the columns. Press Columns next to the export button to choose which columns the file has and their order (use the arrows to move a column up or down). The choice applies to everyone in your team, and only the account owner can change it. Reset to standard returns to the usual columns. Two options you can add: Appointment (the deal's appointment date and time) and Booked on (when the deal first entered a booking stage).

Hide automatic reminders. In the same window, Hide automatic reminders removes system reminders such as "new deal assigned to you" or "hot lead with no reply" from the automatic notes column.

A deal's appointment. Open the deal's customer (from the pipeline or the inbox), find the deal, and press Set next to Appointment. Enter the date and time in your team's time zone, then Save. You can change or remove it the same way. You can also ask the nashir assistant from your Claude connection to set it.

/pipeline

Which stages count as a booking. In the pipeline, open Manage stages and tick Counts as a booking on every stage that means "booked", for example one stage per branch. The Booked on column then uses the first time a deal entered any ticked stage. If you tick nothing, the last open stage before the closing stages is used, as before.

Slow replies. The Slow replies tab shows the customer messages that waited too long for a person to reply, and who was responsible. A run of messages from a customer before you reply counts once. The owner chooses the limit (10 minutes unless changed). For each person you see how many messages they had, how many waited over the limit and over an hour, how many got no reply, and their average and median reply time. Below that is the list of slow chats with a button to open each one, and Export slow replies CSV downloads it all.

  • Who is responsible: the person the chat was assigned to when the customer wrote. If nobody was assigned, the person who replied. Replies sent from the WhatsApp Business app on the phone do not record who sent them, so they are shown together as "WhatsApp phone app (no employee recorded)". To see each person's own replies, reply from nashir.
  • Not counted: chats your assistant answered, chats an employee followed up outside the chat (by changing the deal's status or stage, or adding a note), and messages that need no reply, such as "thanks".
  • Opening hours: when your opening hours are set, the wait only counts while you are open. If they are not set, the wait includes closed hours and the report says so.
  • One person at a time: above the list of slow chats, choose a person (or "WhatsApp phone app (no employee recorded)" or "Unassigned") to see only their slow chats. The list shows 50 chats at a time, longest wait first; use Next and Previous to move through it. Export slow replies CSV downloads the chosen person's chats, or everyone's when nobody is chosen.
  • Duty hours: when your team sets staff shifts (Settings → Duty hours), a wait counts against a person only while they are on duty, and the report adds the share answered within the limit and the customer's real waiting time.
  • Former members: a person who has left your team keeps their figures for the time they worked, marked "(former member)".
  • Who was responsible is approximate for messages before 20/08/2026, because assignments were not recorded before that date.
Reports and the leads export — Nashir