This screen is labeled Interactions Center inside the workspace. It analyzes logged interaction and sale-attribution records; it is not a response-time, live-inbox, or agent-workload dashboard. There is no generic Save or Export action: filters update the analysis in place, Refresh reloads its feeds, and Log Interaction opens a separate capture workflow.
Before you beginConfirm the operating line or sender, the customer match, and the intended recipient before sending or calling.
Step by step
- Open Communications in the primary navigation, then choose Intelligence beside the Activity pulse-line icon. The Interactions Center heading repeats that same Activity icon. If reporting migrations are unavailable, the screen shows an explicit reporting-not-available message instead of trustworthy metrics.
- Set Range to Last 30 days, Last 90 days, Last 12 months, All history, or Custom range. Custom range exposes From and To dates. Then choose one Location, Register, and Associate with the searchable pickers, or leave each on All.
- Use Submission history to understand the loaded evidence. The dashboard requests as many as 5,000 interaction activity records through paged responses beyond Supabase’s 1,000-row response window. The box distinguishes imported rows currently in view from total activity records loaded; it is not a promise that the account has no older records beyond the request cap.
- Read the four metrics together. Tracked interactions splits the filtered activity into bought, saved, and left. Close rate is purchased interactions divided by all filtered interactions. Sale-linked revenue uses compatible receipt-attribution rows under the filters. Quote save rate measures saved quote/card/follow-up opportunities among filtered interactions.
- Use Intelligence workbench for coaching, saved-sale conversion, source leakage, and demand signals. These are synthesized from the current filter set. Treat low-volume rankings cautiously because some insight rules require minimum interaction volume before identifying a person or location.
- In Ask Centri interactions, type a question or choose a prompt such as source leakage, coaching, saved-quote follow-up, or interaction summary. The answer and Evidence list are recalculated from compact source, associate, quote, receipt-link, and CRM-match buckets. Ask Centri limited / Local proof means deterministic evidence mode; Ask Centri active / Gemini-ready means the plan is entitled for the governed AI path, not that every displayed conclusion is autonomous.
- Review Customer Journey / Activity. The feed requests up to 30 recent CRM journey rows for the selected date range and shows the first six cards. Matched activity counts rows with at least one receipt candidate. Open a card to inspect the source touchpoint, contact details, preferred receipt candidate, confidence and match reasons, and other candidates.
- Treat receipt confidence as a suggestion. Choose View receipt to inspect the proposed sale, or Log interaction to create the supported link. If a card lacks a source URL, opening it may silently attempt one customer-activity refresh using phone, email, or external contact ID. Refresh from CRM imports or enriches up to 50 matching activities; Open in CRM appears only when a source URL exists.
- Use Conversion story to compare first and return visits, purchases, no-purchases, and quote/card saves. Use Data coverage to separate imported form history from receipt-linked interactions. An imported record without a receipt link may be matched later, but it is not proven attributed revenue yet.
- Compare Sources, Associates, Left without buying, and Locations. Sources normalize imported history into the vocabulary managed in Settings. Associates hides inactive users unless All users is switched on; the signed-in effective profile is still retained where required. Lost-sale reasons combine historical values with current managed options.
- Read Hour and day heat as interaction volume by local day and hour. Desktop shows the 24-hour grid; mobile shows up to eight busiest nonzero slots as a percentage of the peak. It does not independently prove revenue, staffing need, or conversion quality.
- Owners and super-admins see Interaction Submissions. Its count reflects every matching filtered activity row, while the rendered review list is limited to the first 50. Open submitted card to inspect the record. Other compact activity lists farther down the screen may show only their first 20 rows.
- Choose Refresh to refetch conversion reporting, activity, and CRM journey intelligence. Choose Log Interaction to create a new operational interaction. After any new link or log, verify the submitted card, customer activity, and receipt independently before treating the attributed revenue as settled.
Screen and contract reference
| Control or area | What it means |
|---|---|
| Navigation and heading icon | Activity—the pulse-line icon used by the actual Intelligence entry and Interactions Center heading. |
| Range | The interaction period: 30 days, 90 days, 12 months, all history, or explicit From and To dates. |
| Location / Register / Associate | Searchable single-selection operational filters applied to logged interactions and compatible receipt-attribution rows. |
| Activity load boundary | Up to 5,000 interaction activity records are requested through paging; the CRM journey request is capped at 30 rows for the selected date range. |
| Tracked interactions | Filtered interaction count, split into bought, saved, and left outcomes. |
| Close rate | Purchased interactions divided by all filtered interactions. |
| Sale-linked revenue | Revenue from compatible conversion rows linked through the supported interaction/receipt chain. |
| Quote save rate | Share of interactions that created a saved quote, card, or follow-up opportunity. |
| Submission history | Imported records in the current view plus the activity records loaded through paged database responses. |
| Ask Centri evidence | A compact proof packet made from source, associate, saved-quote, receipt-link, and CRM-match buckets under the active filters. |
| Local proof | Deterministic evidence mode for a plan without the Ask Centri entitlement. |
| Receipt confidence | A ranked candidate based on the available customer, timing, location, associate, status, and receipt evidence. A person should verify it. |
| Matched activity | CRM journey rows with one or more receipt candidates—not rows whose match has necessarily been approved. |
| Refresh from CRM | Attempts to import or enrich up to 50 customer activities using the current contact and receipt context. |
| Data coverage | Separates imported history from receipt-linked records so unattributed activity is not presented as proven revenue. |
| Hour and day heat | Interaction volume by local day and hour, not revenue or staffing demand by itself. |
| Interaction Submissions | Owner/super-admin review of matching submitted interactions; count is complete for the filtered loaded set, list renders the first 50. |
| Privacy-safe screenshot status | The Harbor & Hearth /interactions/overview route redirected to /intelligence/interactions and did not produce a verified screen match, so no invented or route-mismatched screenshot is used. |
Expected result
The communication metrics and drill-down records reconcile with the selected date, location, channel, line, user, direction, and outcome filters.
Troubleshooting
- Confirm the operating line, sender identity, customer match, and recipient before sending.
- Review the conversation or interaction log before repeating an outbound message.
- Check browser microphone and notification permissions when calls or alerts do not work.
CentriPOS API explorer · API Center administration
More guides
Build an itemized payment in MoneyUse Products or Amount & description to build one receipt, attach the customer, and follow the appropriate payment or service-estimate workflow.
Take a one-time payment in Virtual TerminalReview a one-time amount, tax and contact at the correct payment station, use its verified secure checkout, and recover the original receipt after an uncertain result.
Review booking payments, refunds and earned careKeep a booking’s customer payments, unused advances, completed care, cancellation fees and refunds distinct, then read a correctly scoped accrual report.
Configure booking properties and customer pagesSet accommodations, service packages, availability, required intake and payment terms, then review the correctly branded booking page before sharing it.