← Help

Business operations

Business insights: inquiries, replies and workload

Product team · Reviewed

Business insights

Open Studio → Business insights to connect pipeline outcomes, response times, workload, workflow holds, and gallery cash. Choose a period of up to 367 days and export the summary as CSV. Only full private workspace operators can open this report. Integration credentials need the separate analytics:read permission; a wedding invitation does not grant it.

Follow the same inquiry cohort

The inquiry total counts records created within the selected UTC dates. Won and lost are their current pipeline outcomes, so the same cohort can improve after its creation month. Project communication contacts and merged duplicate inquiries are excluded. Archived inquiries stay in the cohort to avoid making the rate look better by hiding losses.

For example, 20 inquiries created in May with 6 currently won have a 30% won rate. Those wins do not establish a payment: use Sources → collected cash for reviewed project attribution and retained invoice receipts. The source table in Business insights uses recorded lead labels, while the attribution report uses separately reviewed source evidence.

Find unanswered conversations

A reply episode starts at the first incoming email or text within the period in a linked business conversation. Unlinked provider inbox threads are not included. Sent picture messages also count as text-channel replies. Consecutive incoming messages wait together until a successfully sent reply. Queued, failed, cancelled, and uncertain sends do not count as replies. Email and SMS are measured separately. Automatic replies are included and counted separately; these numbers are not a human-response SLA.

If a client emails at 10:00, follows up at 10:10, and receives a sent reply at 11:00, the elapsed reply time is 60 minutes. A client who has not received a reply remains in the waiting list instead of disappearing from the report. The median and 90th percentile use answered episodes only; check the pending list alongside them. Weekends and nights are included.

Read workload without invented availability

Project dates and appointment intervals use the selected period. Accepted crew shifts are clipped to its boundaries. Two simultaneous two-hour assignments count as four booked hours but only two distinct occupied hours, and the overlap is flagged. This does not assume an eight-hour working day or claim a utilization percentage. Open Crew & inventory for available people, staffing requirements, offers, time off, and unfilled roles.

The task list includes unfinished work on active projects due before the period ends, plus tasks without dates. It shows current work, not a reconstructed historical backlog. Workflow summaries similarly include runs created in the period and older runs that still need attention. Open a workflow to review a missing-information hold, approval, failure, or paused run before continuing it.

Separate sales from collected money

Gallery cash comes from retained ledger movements in the period, grouped by currency. Unpaid carts, discounts, and package credits are not cash receipts. Refunds are counted when recorded, even if the original order was paid earlier. Net cash includes shipping and tax, and does not claim to be profit. Known processor fees and included tax appear separately; unknown allocations remain visible. Gallery activity counts events, not unique people.

Financial reports provide project costs, signed scope, month-by-month operating results, and allocation review. Dates in these reports use UTC. If a query exceeds 10,000 records in a source family, it asks for a narrower period instead of silently truncating its totals. Refresh after resolving a record or workflow to see the current result. API callers can page source, reply, task, project, crew and workflow lists and must restart when the report revision changes.