# See where customers stop in an automation > In the SkedX Flow automation builder, click Activity in the top bar, then Numbers. The automation is drawn as in Build, read-only, and every card carries its numbers for the period you pick (7, 30 or 90 days): a question says Replied 74% · 2 waiting · 9 stopped; a message says Delivered 96% · Read ≥ 71% · 4 failed; the start says how many started against the period before. The one question that loses the largest share of the people who reach it wears an amber Biggest drop tag (only when at least five reached it and three stopped). The steps list on the left gives each step its number, under Needs attention: at most three cards, each with one fix. Click a card or a row and the panel shows Where people stop — asked, replied, waiting now, and Stopped here by reason (no reply came, their answer didn’t fit even after asking again, the question couldn’t be sent), which answer they chose, how many a reminder brought back, and since you published the latest version against before. See who lists the people (the first 25) with Nudge, Hand to team and Open chat. A message step’s panel shows Did it arrive: sent, delivered, read (at least), the messages WhatsApp refused with its reason, and the cost from your wallet. Edit this step goes to Build with that step open. Runs, beside Numbers, is the list of runs. Numbers count runs, not people. Product: SkedX Flow · Topic: Automation · Verified in the live product on 2026-10-24 So that you can see which question loses your customers, why, and who they are — and bring them back in one click. ## Step 1: Open the numbers Open an automation and click **Activity** in the top bar. **Numbers** is open: the automation drawn as in Build, read-only. Pick **7**, **30** or **90 days**. Open it directly: https://flow.skode.ai/automation ## Step 2: Read the cards and the list Every card carries its numbers — a question **Replied 74% · 2 waiting · 9 stopped**. The question that loses the largest share wears **Biggest drop**, and the steps list says each step’s number under its name. ## Step 3: See why they stopped Click the card or its row. **Where people stop** says how many were asked, replied and are waiting, then **Stopped here** by reason: no reply came, their answer didn’t fit even after asking again, the question couldn’t be sent. **See who** lists the people. ## Step 4: Bring them back Beside each person: **Nudge** shows a short message you can change, then sends it — if their 24-hour window has closed it says a template is needed and opens the chat to choose one. **Hand to team** gives the chat to your team; **Open chat** opens it. ## Step 5: See whether a message arrived Click a message. **Did it arrive** shows sent, delivered, read (at least — a customer can turn read receipts off) and replied, the messages WhatsApp refused with its own reason, and what they cost from your wallet. ## Step 6: Fix what needs attention first At the top of the steps list, **Needs attention** shows at most three cards in plain words, each with one fix: the question that loses most, messages refused because the 24-hour window had closed, an empty wallet, a template WhatsApp paused. ## Step 7: Change the step, or see every run **Edit this step**, in the panel’s header, goes to Build with that step open. **Runs**, beside Numbers, lists every run and what happened in it. ## Common questions ### Does it count people or runs? Runs. Someone who enters twice counts twice. The panel’s footer says so. ### Why is “Read” “at least”? A customer can turn WhatsApp’s read receipts off, so some read messages are reported as delivered only. ### No one reached a question — what now? Its panel says so and offers **Look at the last 90 days**. ### Can I change a step from here? Numbers is read-only. **Edit this step** takes you to Build with that step open. Videos and screenshots © 2026 SkedX, with sample data only. Share and link to them freely; copying the SkedX product or its design is not allowed. Terms: https://skode.ai/terms/ ## Related guides - See the orders and revenue an automation brings, and where buyers came from: https://skode.ai/help/flow/automation/see-orders-and-revenue-from-an-automation/ - Build an automation step by step in SkedX Flow: https://skode.ai/help/flow/automation/build-an-automation-step-by-step-in-skode-flow/ - Find a step in a long automation: the steps list and its search: https://skode.ai/help/flow/automation/find-a-step-in-a-long-automation/ - Set the rules for a whole automation: https://skode.ai/help/flow/automation/set-the-rules-for-a-whole-automation/ Source: https://skode.ai/help/flow/automation/see-where-customers-stop-in-an-automation/