Inbox is an operational aggregation screen—not yet a provider-neutral shared inbox. It reads the newest 150 Dialpad events, 100 CentriCRM journey events, 80 store interactions, and 80 POS sale-communication notices returned for the active CentriPOS account. Email inboxes are labeled Next via CRM, internal chat is Planned, and assignment, SLA, provider-neutral replies, and CentriAI actions are described on-screen as a future layer.

Before you beginConfirm the operating line or sender, the customer match, and the intended recipient before sending or calling.

Step by step

  1. Open Communications in the primary navigation and choose Inbox beside the MessageSquareText speech-bubble icon. Inside the Communications workspace, the Inbox tab uses the tray-style Inbox icon. The default Open view includes any thread that is unread, open, or marked for review.
  2. Start with the four summary cards. Open work selects unread, open, and review threads. Dialpad selects threads containing Dialpad activity. CRM journey selects threads containing CentriCRM activity. Matched shows the All filter—it does not limit the list to matched records—even though its number counts threads with at least one matched event.
  3. Use the filter chips to choose All, Open, Dialpad, CentriCRM, Interactions, or POS. Source filters include a thread when any event in that thread has the selected source. Search checks the displayed contact name or detail, customer phone, operating-line proof, latest message or call body, latest activity title, and channel. The screen shows at most 80 filtered threads.
  4. Choose Refresh to reload all four connected feeds. Refresh does not bypass each source’s load limit, and it does not activate an unconfigured provider. Use Provider readiness to distinguish Connected Dialpad, the CentriCRM sync layer, email marked Next via CRM, and internal chat marked Planned.
  5. Read each row before acting: source icon and badge, contact, Unread/Open/Review/Matched/Sent state, latest communication type and direction, date and time, source detail or receipt, contact detail, message or call summary, customer phone, operating line, assignment, and unread-event count. A missing call transcript or message body is stated rather than inferred.
  6. Understand the grouping. Events are kept separate by source, normalized customer phone or contact name, business-side operating line, and channel. Items inside a thread are chronological. Pinned threads sort first, then unread threads, then newest activity. Because source and channel are part of the grouping key, one customer can correctly have several rows.
  7. Open a matched row or choose Activity to open that customer’s profile directly on the Activity tab. Opening an unread matched thread submits a read-state update for its supported imported events. If the row is not matched, choose Contact to search by the best available customer ID, phone, detail, or name; clicking the row itself explains that a contact link is required.
  8. Choose Call only after confirming the displayed customer number and operating-line context. This control opens the device’s tel link; the inbox does not choose a CentriPhone or Dialpad sender for you. Confirm the resulting provider activity before treating the call as logged.
  9. Use the eye control to toggle the entire thread read or unread. The update is written only to Dialpad or CentriCRM items backed by crm_external_events. Logged interactions and POS notices can appear in the thread but do not receive that imported-event state. The list refreshes after a successful update; an error toast means the state was not fully saved.
  10. To begin outreach, choose Start communication, enter a name, phone, or email, and choose SMS, Call, or Email. Find contact opens Contacts with that search. The chosen channel does not send, call, or preselect a provider—the contact profile owns the final sender, schedule, notes, and activity thread.
  11. Choose Log interaction to record an in-store interaction. Use Attribution intelligence for conversion analysis, Log a store interaction for a new operational record, or Dialpad mapping to manage the external provider mapping. These Work queues are links to specialist screens, not inbox filters.
  12. Verify the result in the system that owns it. A real call, SMS, email, customer activity, or saved interaction should appear once against the intended customer and operating line. A rendered row, Connected badge, or selected channel alone is not proof that communication occurred.

Screen and contract reference

Control or areaWhat it means
Primary navigation iconMessageSquareText—the speech bubble with text lines used by the actual Communications and Inbox entry in the main CentriPOS navigation.
Workspace tab iconInbox—the tray-style icon used for Inbox inside the Communications workspace.
Open workThreads that are unread or whose latest item is Open or Review.
Matched summary cardDisplays the count of threads containing matched activity, but selecting it switches to All threads.
Thread groupingSource + normalized customer phone or contact name + operating line + channel. Different sources, lines, or channels remain separate rows.
UnreadInbound Dialpad and CentriCRM events default to unread unless their stored communication_state says otherwise.
Pinned orderingPinned threads appear first, followed by unread threads, then newest activity. No pin control is exposed on this screen.
MatchedAn imported event, interaction, or notice is tied to a supported CentriPOS customer or activity record.
ReviewA CentriCRM journey event is new and still needs review.
LineThe provider business-side number or other proof showing which operating identity handled the activity.
ActivityOpens the matched customer profile directly on its Activity tab and marks supported unread imported events read.
ContactOpens Contacts using the customer ID or best available search value so an unmatched row can be resolved.
CallOpens a tel link for the displayed customer number; it does not select or prove a business sender.
Eye controlToggles read/unread state across supported Dialpad and CentriCRM records in the selected thread.
Start communicationFinds a contact using the entered value. Channel selection is informational at this step and nothing is sent.
RefreshRefetches the four capped source feeds for the active tenant.
Provider readinessDescribes current integration status and roadmap state. Connected Dialpad does not imply email inbox or internal-chat availability.
Privacy-safe screenshot statusThe Harbor & Hearth /interactions/inbox capture is intentionally rejected because it is a sensitive customer-message surface. No unrelated or invented screenshot is substituted.

Expected result

The selected conversation belongs to the intended customer and operating line, new inbound and outbound activity appears once in chronological order, and unread or assignment state updates correctly.

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.

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.