Sales and flow analytics
Start with the question you want to answer. Payments tells you about recorded transactions; Terminal Sales groups item values; Flow Executions shows where recorded journeys completed or stopped. Their totals describe different activity.
The walkthrough uses populated Maple Plumbing Co. test data. It inspected existing reports and downloaded CSVs without creating a sale, running a customer flow, or changing a payment.
Analytics
Open Analytics in SRVZr, then choose a report. The report menu can collapse to icons; expand it when you need the labels. Available reports depend on business access permissions.
| Report | Useful question |
|---|---|
| Services | How are services discovered, viewed, saved, and used to start orders? |
| Terminal Sales | Which recorded items account for the sales value in this period? |
| Event Summary | What activity is recorded for an event? |
| Inventory | What do the stock, sales, and rental records show? |
| Flow Executions | Which flows complete, fail, or get abandoned? |
| Yearly Expenses | How does spending vary by month and category? |
| Calls | How many calls were answered, missed or handled by an AI agent or the team? |
Choose the business, resource, period, and filters before comparing reports. A loading state or access message is different from a completed report with no activity. Services returned No activity in this period for the reviewed test-business period. See Inventory, Expenses, and Events for their related workflows.
Sales analytics
Choose Terminal Sales, or open that report directly.
- Select Selected range and review the start/end dates and times.
- Choose a preset such as Last 30 days, or set the intended range, then select Apply. The picker states that times are applied in UTC.
- Review All Payments, currency, and All Menus. Keep the same currency when comparing monetary totals.
- Read Total Items Sold, Total Sales, Total Tips, and the item table together.
- Inspect the trend, Top Items, Payment Mix, and heatmap when there is enough relevant activity to make them useful.

The example initially opened a roughly 24-hour range with no matching activity. Applying Last 30 days loaded INV-0008, INV-0011, and INV-0012, one item each, totaling $771.79, with zero recorded tips. Changing the range resolved the empty result without adding records.
Understand the report’s scope
Total Sales is calculated from recorded item quantities and prices under the report filters. It is not a profit calculation or a processor payout. Review refunds and transaction statuses in Payments when reconciling money.
The selected-range query uses transaction timestamps, while the Payments list uses its recorded date. In the walkthrough, Payments showed 48 matching records, but this report’s selected period loaded three records with transaction times and item lines. Some older test records lacked the fields needed for that comparison. Match the actual date basis and item data before expecting totals to agree.
Card event-ticket items are excluded from this item report and belong in Event Analytics. Cash event-ticket items can remain available here for drawer review. A menu or payment-method filter can narrow the scope further.
Explore and export
- Switch the revenue chart between Per Day, Per Hour, Per 10 Min, and Per Minute to suit the period.
- Compare Top Items by Revenue or Quantity, and review the selected Top count.
- Check whether the heatmap is displaying UTC or Local time before comparing busy hours.
- Under Exports, choose Export CSV for aggregated item rows or Raw CSV for the loaded payment-level summary. Excel and PDF controls are also offered.
Both CSV paths were downloaded and inspected. The aggregated file contained three item rows and a Total row; the raw summary contained three payment rows with nine fields. It was a transaction summary, not an export of every internal payment field. Excel, PDF, and printing were not exercised in this walkthrough.
Flow execution analytics
Choose Flow Executions, or open the report directly, to investigate recorded runs across services, rentals, events, and Stints.
- Choose Last 7 Days, Last 30 Days, or Last 90 Days, or use Pick date range.
- Leave All Flows selected for an overview, then select a named flow to investigate it.
- Compare Executions, Completed, Failed, Abandoned, and Completion Rate.
- Use Executions Over Time and By Flow to locate the main pattern.
- Read Where Users Give Up for the last recorded steps of abandoned runs. Inspect Where Flows Fail Most and Recent Failures when errors exist.

The reviewed Last 30 Days report had 32 runs, 2 completions, 0 failures, and 30 abandoned runs, with a rounded 6% completion rate. Last 7 Days returned 30 runs. These counts describe the selected recorded data; they are not a count of unique customers or completed paid jobs.
Investigate a specific stopping point
Selecting Bathroom Renovation Consultation & Booking Flow narrowed the report to 14 runs: two completed and 12 abandoned, with a 14% completion rate. Its largest stopping point was Project Intake, with six abandoned runs.

Review the intake’s length, required questions, and instructions in Flow Builder before changing it. Compare the same flow and period after a change; do not treat a small test sample as proof of a customer-behavior cause.
Read the measures accurately
- Completed means the tracked flow emitted a completion event. It does not by itself establish a paid invoice, fulfilled rental, or finished service job.
- Failed means the recorded run includes an error and was not classified as completed. The walkthrough had no failed runs, so populated error details were not verified.
- Abandoned includes explicit abandonment and runs whose last event has been stale for more than 30 minutes. A closed page, missing event, or interrupted journey can contribute.
- Avg Checkout Price averages the last recorded price-bearing step in the loaded runs. The example showed $4,500; it is not collected revenue or the total value of successful jobs.
- Form Fields Filled In describes logged field-completion metadata. The reviewed report displayed field identifiers rather than readable question labels; no customer answer values are shown in the screenshots here.
This dashboard reads production-mode flow events for the selected business. Development-mode simulator activity is excluded, so a simulator run need not appear. The reader has a 20,000-event limit; a high-volume or long-range report may require a narrower period for a complete investigation. No new event or customer run was created for the screenshots.
Calls analytics
Choose Calls, or open Calls insights directly. This report follows Phone Section access.
- Confirm the business and choose 7 days, 30 days or 90 days.
- Compare Calls, Answered, Missed and Voicemail. Answered distinguishes agents from the team; the call total includes incoming and outgoing calls.
- Review average length, new callers, AI minutes, credits used and missed-call texts.
- Inspect Calls per day, Busiest hours and Calls per line to find where coverage needs attention.
- Use How calls ended and Why people called as summary-based signals, then inspect the actual records in Phone.
Call outcomes derived from an AI summary are not proof of a completed booking or delivered text. Check the corresponding work order or message result. These report controls were source-confirmed; no live call activity was created for this guide.
Troubleshooting
| What you see | What to check |
|---|---|
| Terminal Sales opens empty | Check the selected range before assuming there were no transactions. |
| Payments and item totals differ | Compare date fields, item lines, currency, methods, menu scope, event-ticket handling, and refunds. |
| No Services activity | Review the period and actual discovery activity; do not substitute flow runs for service views. |
| A simulator run is missing | Flow Executions reads production-mode events. |
| Many abandoned runs but no failures | Review the last recorded steps; abandonment is distinct from a recorded error. |
| A report is unavailable | Check the selected business and the permission for that report. |
Continue with Review payments and sales reports for a practical comparison, or use Financial reports for the accounting view.
Explore the expanded analytics hub
The expanded report chooser brings operational, audience, financial and device reporting together. Available reports depend on your permissions, integrations and collected data.

| Reports | Use them to investigate |
|---|---|
| Social, Website, Reviews | Content attention, page visits, booking taps and ratings. |
| Orders, Customers, Deals | Job progress, returning customers and pipeline stages. |
| Menu orders, Payments, Rentals | Ordering patterns, transaction states and equipment use. |
| Team & shifts, Messages, Forms | Staffing, response times and submission drop-off. |
| AI agents, Snippets | Runs, approvals, credits and app usage. |
| Servos, Displays | Recorded device activity, uptime and screen use. |
Choose a report, then check its period, filters, source and setup state before comparing values. Not set up yet, an error and a valid zero result mean different things. Newly introduced tracking may have no earlier history; it cannot reconstruct events that were never recorded.
Use the relevant underlying records to investigate an unexpected value. Payment totals are not the same as sales, profit or payouts, and a recorded device heartbeat is not proof of successful physical work. The chooser was inspected; data accuracy and every report's integrations were not validated end to end.
Audience: Social, Website and Reviews
For a campaign review, start with Social, choose the relevant account and period, and compare attention and watch-time measures for the actual posts. A project cut awaiting release has no published-post results to compare.
Use Website for visits, top pages and booking taps. Compare the page and period with the campaign's destination. A booking tap measures intent; open Orders to establish whether the customer submitted a request.
Use Reviews for ratings and review activity. Confirm whether the records are from Google or SRVZ before comparing averages. An empty connected-source result is different from having no connected source.
Customer work: Orders, Customers and Deals
Choose Orders to inspect job progress and timing, then open the relevant work order when a stage takes longer than expected. Use Customers to compare new and returning activity or identify customers needing follow-up. Check the customer's actual history before contacting them.
Use Deals to investigate pipeline stages and stalled opportunities. Check stage history and the chosen period before treating a missing transition as time spent in a stage; newly introduced tracking does not establish older transition dates.
Commerce: Menu orders, Payments and Rentals
Choose Menu orders when investigating menu and QR ordering patterns, best sellers or busy periods. Compare its order scope with Terminal Sales before expecting the same total.
Choose Payments for card/cash mix, refunds, disputes and payouts. Match the transaction and status when reconciling a difference. A dispute or refund belongs to its own lifecycle, and a payout can group several transactions.
Choose Rentals to investigate utilization, idle equipment, return activity and deposits. Review the rental record and booking dates before concluding that an item is available for another booking.
Operations: Team & shifts, Messages and Forms
Use Team & shifts to compare recorded hours, overtime and staffing against sales. Check whether hours are planned, recorded or missing before treating the result as payroll-ready.
Use Messages for response activity across the supported email, text and chat records. Open the thread to understand whether a reply actually resolved the customer's question.
Use Forms for submissions, completion measures, time to fill and new bank entries. Completion tracking applies to the supported public-link journey and starts with the new tracking. Compare submissions with the destination bank; a form needs the appropriate bank connection to retain answers there. Frequently empty fields can suggest a clearer question, but do not automatically make a required field optional.
AI and apps: AI agents and Snippets
Choose AI agents to review tasks, outcomes, credit use and approvals. Investigate the run itself when a task is waiting for input; an approval count is not a count of completed business transactions.
Choose Snippets for opens, active users, data calls, errors, bank reads/writes and agent-hook calls. Switch Used to All snippets when an unused app is missing from the usage list. Check the app's bank access and actual error before changing permissions.
Devices: Servos and Displays
Use Servos to compare recorded jobs, uptime and working versus idle time. Uptime starts from the available check-in tracking; missing earlier data cannot establish that the robot was offline.
Use Displays for recorded screen time, content and device activity. Confirm the intended screen and its player separately. A heartbeat establishes contact with the reporting service, not that the audience saw every frame correctly.