Clients who need attention

Open Studio → Needs attention for live signals from your private business records. Each card explains the source, its current revision, and the action that opens it. A shared wedding invitation never exposes this desk or another business’s finances.

Set practical thresholds

Owners and administrators can change Attention rules. Blank thresholds turn an individual rule off. The starting rules are a first inquiry reply after 24 hours, an unanswered client message after 24 hours, a quiet issued proposal after seven days, and an unsigned issued agreement after five days. Open invoices and unfinished project tasks appear on the first calendar day after their due date. An issued invoice without a due date appears after 14 elapsed days.

For example, an invoice due September 30 is not overdue on September 30. With zero grace days it appears on October 1. With one grace day it appears on October 2. Due dates and event proximity use the workspace timezone; hours and proposal age use elapsed time, including nights, weekends and daylight-saving changes.

The default event window is 30 days. Signals for events within seven days appear first, followed by the rest of the window and work that has waited at least seven days. The desk explains priority instead of assigning an invented client “health score.”

Know what counts as an answer

Only recorded sent or delivered email, text or picture messages answer a conversation. Queued, failed, uncertain or cancelled sends do not. Messages across the same private conversation are considered together: a sent text can answer an earlier email. The first unanswered incoming message starts the waiting period; another incoming message does not reset it.

Automatic workflow and follow-up email or SMS do not count by default. An administrator can choose to count them. Explicitly closed conversations are omitted unless enabled in settings. A first-inquiry signal applies to open NEW or CONTACTED inquiry records without a qualifying sent response since creation. Archived, merged and lost inquiries are excluded; private project contacts remain separate from acquisition inquiries.

The desk cannot infer a phone conversation, personal inbox response, or message in an unconnected source. Open the source record before deciding to follow up. Nothing in this desk sends a message.

Follow proposals and signatures accurately

A quiet proposal has a current selector invitation and no newer issuance, first-open signal or saved selection within your target. An open signal is not proof that the recipient read it. Expired links require review before reuse. Draft and unissued proposals do not become client follow-ups.

Issued signing requests identify the people still needed, including a business countersigner. Declines and expired signing windows appear in the explanation. Open the original signing page to review the exact retained document, signer status and valid next action. Snoozing never changes a signed record.

Review money against the ledger

Invoice cards use the original issued amount and recorded principal receipts or adjustments to calculate what remains. Refunds stay separate from original contractual balances. Draft, void and paid invoices are excluded, as are issued invoices whose ledger already shows no outstanding principal.

A pending checkout or automatic payment changes the suggested action to Review original payment. Reconcile that original attempt before asking the client to pay again. The invoice link opens its exact current private ledger, including an older invoice outside the usual recent list. Viewing the attention desk never creates a payment, changes a balance, charges a saved method or issues a refund.

Snooze a reviewed source

After reading a card, choose a deadline and record a private team reason. Snoozes last up to 30 days. They apply to the exact source revision, event date and rule settings you reviewed. A new client message, changed invoice ledger, new proposal progress or changed settings makes the old snooze stop applying. Use Snoozed to find work intentionally set aside and bring it back early.

If a save response is interrupted, Recover original decision reuses the same request. A changed source asks for a fresh review. Signals disappear when their underlying condition resolves; there is no permanent “dismiss” that hides future problems.

Read proposal conversion as a cohort

Choose the past 30, 90 or 365 days. The cohort contains distinct proposals with a selector invitation created during those local calendar days, including a reissue during the period. Reissuing the same proposal does not add a second proposal to the denominator. Outcomes are current, so an older cohort can change when a client accepts later.

An accepted proposal requires a retained accepted selection. Agreement prepared means the accepted proposal has been converted into its canonical agreement. Neither figure claims that all signatures or payments have completed. Use the linked source-attribution report to follow actual collected principal.

For example, 12 distinct issued proposals with three current acceptances have a 25% acceptance rate. Two prepared agreements out of those three indicate one accepted proposal still needs its document step; they do not mean two fully paid bookings.

Permissions, limits and API

Current full-access private workspace members can read the desk and review snoozes. Only an owner or administrator can change its rules. Named account clients use /api/v1/client-health; scoped read credentials require analytics:read. Read credentials cannot change settings or snoozes. Responses are private and not cached, paginated with a source revision, and require a restart if those sources change.

A source class above 5,000 records, a proposal above 100 invitation versions, or an invoice above the bounded history size stops the report with an explicit limit instead of silently dropping work or inventing totals. Operational provider failures remain in Operations; this desk stays focused on client work and its recorded sources.

Prepare a cited business brief

Choose Prepare a cited brief to open the review assistant with the current business-attention source. Read the request and approve its displayed model-usage price. The request includes current rule settings, a 90-day proposal-issuance cohort and the first 20 unsnoozed signals ordered by event proximity and age. It discloses additional signals rather than implying it reviewed every client. Open the attention desk to review the complete list or another cohort.

Each included signal has its own source link and retained source fingerprint. The brief is read-only, including follow-up turns that retain its business source. It cannot propose record changes, send a follow-up, modify a price, or charge a client. Suggestions still need your judgment; the model’s cited interpretation is not an independent verification of the underlying records.

For example, an invoice with an original payment in progress should suggest reviewing that attempt, not requesting a second payment. Proposal acceptance remains distinct from a signature or collected revenue. Missing phone calls or messages from unconnected inboxes remain unknown.

When you reopen or refresh the response, its source check reports whether current attention sources match the captured snapshot. If records, priorities, snoozes or rules have changed, request a fresh brief with a new usage approval. A follow-up refreshes the underlying sources. An old response never silently rewrites itself.

The automatic source contains client names, attention facts and current recorded outstanding balances, but no message bodies, personal notes, guest contact lists or shared-media/face-search data. Additional sources you explicitly select follow their normal assistant permissions; personal notes make the whole conversation private to their author. Connected Gmail/Outlook message bodies remain held from assistant processing.

A brief needs assistant read/write permissions plus analytics, finance, clients, messages, tasks and projects read access. Removing a required permission prevents reading saved briefs as well as preparing new ones. Scoped assigned-work collaborators do not receive this business-wide assistant access.

The same brief kind is available through the native assistant, Chrome companion and the existing versioned assistant API as BUSINESS_BRIEF. Model activation, usage configuration and real-provider verification remain part of the coordinated setup phase.