Dialpad availability is tenant-, location-, user-, and browser-specific. Browser Calling switches are stored only in the current browser and are off until that user opts in. Calls require an assigned Dialpad sender; SMS may also offer an assigned CentriCRM / LC sender. Never assume a connected integration means every user has a callable line, recording, transcript, or permission.
Step by step
- Ask an authorized administrator to open Admin → Integrations → Dialpad and confirm the tenant connection, connected user, company, and assigned numbers. Reconnect only when authorization is genuinely required; do not use OAuth as a status-refresh button.
- In the Dialpad integration screen, find Browser Calling. Turn on Dialpad browser dialer to show the embedded Dialpad dock when CTI is configured. Turn on Incoming call screen pop only for the current browser when this workstation should listen for incoming-call events. These choices do not enable another user or browser.
- Open the operating-context bar and confirm the intended business, location, register, and signed-in user. Then open the customer from Sell or the supported customer profile surface and verify the customer name and phone number before communicating.
- In the customer communication card, choose the recipient number when the customer has more than one. SMS can target multiple selected customer numbers; confirm every checked recipient because each number receives the message. Calling uses the customer’s primary normalized phone.
- Open the sender picker and choose an assigned line. Read both the provider and number: Dialpad and CentriCRM / LC senders can appear together. A profile-default or location-default badge helps prioritize a line but does not replace your confirmation. Only assigned numbers are offered.
- To call, select a Dialpad sender and choose Call. CentriPOS enables the browser dialer and submits the customer number, selected Dialpad sender, and customer context to the Dialpad dock. Complete and end the call in the embedded Dialpad experience; a CentriCRM / LC sender cannot be used for this call button.
- To text now, enter the message, recheck recipients and sender, choose Send now, and submit. Wait for the sent confirmation before retrying. A blank message, missing sender, disconnected provider, or missing recipient keeps Send unavailable.
- To send later, choose Schedule and enter a local date/time at least one minute in the future. Review the Scheduled SMS list. Select a scheduled item to edit its text, time, or compatible sender; use its cancel control only when the message should not send. Wait for the updated or cancelled confirmation.
- Open customer activity after the interaction. Dialpad calls and SMS can be imported into the timeline and live events can update it. Refresh activity only when needed and wait for completion. Confirm direction, participants, time, status, and message/call identity; recording, transcript, AI recap, and review details appear only when Dialpad actually supplies them.
- For an incoming call, keep this browser open with Incoming call screen pop enabled. When Dialpad sends a supported event, CentriPOS shows a call card with matched customer context when available. Verify the caller before opening or creating a customer; do not create a duplicate merely because formatting prevented a match.
- If the dock or screen pop does not appear, return to Browser Calling in this same browser and confirm the switch, CTI configured badge, assigned sender, integration connection, and browser/session state. If another workstation works, remember the preferences are local rather than tenant-wide. Escalate with the user, location, browser, time, direction, and affected number—never with OAuth tokens or credentials.
Screen and contract reference
| Control or area | What it means |
|---|---|
| Connect Dialpad / Reconnect Dialpad | Starts tenant OAuth authorization. Reconnect is a credential action, not a harmless refresh. |
| Connected user, Company, Numbers | Integration status summary; Numbers is the count available through the connection, not proof that every user is assigned a line. |
| Dialpad browser dialer | Browser-local switch that allows the Dialpad dock to render when CTI and sender availability support it. |
| CTI configured / Needs CTI client ID | States whether the embedded calling client has the required client configuration. |
| Incoming call screen pop | Browser-local opt-in that listens for supported Dialpad incoming-call events and displays a CentriPOS call card. |
| Recipient picker | Selects one or more saved customer phone numbers for SMS. Calling continues to use the primary normalized number. |
| Sender picker | Shows only assigned Dialpad or CentriCRM / LC senders, including provider, line kind, number, and supported default badges. |
| Default badge | Marks the profile-preferred sender; location default can be used when no profile default applies. Always confirm the actual provider and number. |
| Call | Available only with a connected assigned Dialpad sender and a valid customer phone; opens/enables the Dialpad dock with customer context. |
| Send now | Submits the message immediately through the selected sender provider to every checked recipient. |
| Schedule | Requires a time at least one minute ahead and creates a scheduled SMS entry. |
| Scheduled SMS | Lists pending or failed scheduled messages with time, provider/line, recipient, body, and an error when present. |
| Edit scheduled SMS | Loads an item back into the composer so its supported message, time, or sender can be updated. |
| Cancel scheduled SMS | Cancels a still-scheduled item; it cannot recall a message already sent. |
| Customer activity | Timeline that can show imported/live Dialpad calls and SMS. Treat status and provider evidence as authoritative. |
| Recording / transcript / AI recap | Conditional call evidence shown only when returned by Dialpad; connection alone does not guarantee any of it. |
| Refresh activity | Requests recent Dialpad import and inbox indexing. Do not repeatedly refresh while a prior request is pending. |
| Screen-pop customer match | Uses incoming caller context to find a customer; verify identity before opening or creating a record. |
| No exact workflow screenshot | The approved Amelia Grant Harbor & Hearth manifest contains a safe Admin Communications readiness image, but no exact customer Dialpad call/SMS workflow image. This guide intentionally uses no unrelated or invented screenshot. |
Expected result
The Dialpad action opens or logs against the intended CentriPOS customer and line context, and completed activity appears once without duplicating the contact.
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