Softphone CRM Tab: Put Your CRM or Helpdesk Inside the App

Tom Reed · Updated 11 November 2026

A softphone CRM tab pins your CRM, helpdesk or internal portal inside the softphone, so agents see customer records one tap from every call. In SessionTalk you set the URL, label and icon in the cloud portal, and placeholders like {username} and {deviceId} load each signed-in user's own view.

This guide is for IT admins and team leads who want their staff to stop switching between the phone app and a browser. It explains what a custom web tab is, how to plan one, how the placeholders work and where a web tab fits next to click-to-dial and a separate CTI connector. It keeps to generic steps, because the exact screens depend on the app release and your account.

What is a custom web tab in a softphone?

A custom web tab is a web page that you pin as a tab inside the softphone itself. Instead of alt-tabbing to a browser to find the customer on the line, the person taking the call sees the page they work in right next to the dialler. It is one tap away from every call.

You choose the page, and the softphone simply shows it. That makes the web tab flexible: whatever your team already uses in a browser can sit inside the app. If you are choosing an app for this, look at business softphone apps with a custom web tab, which are managed from a cloud portal.

Which tools can you pin inside the softphone?

Any web page can be pinned. The common choices are a CRM, a helpdesk, an internal portal or a knowledge base. If your team looks something up on most calls, that page is a good candidate.

You can embed pages from tools such as Salesforce, HubSpot, Zendesk and Freshdesk. These are examples of pages you can embed, not native connectors: the tab shows the web page you choose and nothing more. For the HubSpot side of this, read HubSpot and your VoIP softphone.

How do you set up a CRM tab?

You set it up from the cloud portal. Give the tab a URL, a label and an icon, and the change reaches your users without a reinstall of the app. The steps below are generic, because the exact screens depend on the app release.

• Decide which page the team uses most on calls.
• Enter the URL for that page in the cloud portal, and give the tab a clear label and icon.
• Add any placeholders the page needs, so each user lands on their own view.
• Push the change to your users.
• Test it on one desktop and one mobile device before you tell everyone.

Because the portal manages the tab centrally, you can change the URL later and your users do not have to reinstall anything. That is also useful when your CRM changes address or you move a portal.

How do the {username}, {password} and {deviceId} placeholders work?

Placeholders are values the softphone fills in for each signed-in user. Drop {username}, {password} or {deviceId} into the URL and the app loads that user's data on the fly. Two people on the same team can open the same tab and each see their own page.

A practical caution, which is general good practice and not a product claim: only pass {password} to a site you control, over HTTPS. Wherever you can, prefer {username} or {deviceId}, because they give you the per-user view without sending a credential in a web address.

On the desktop, the same placeholders pass the signed-in user and device ID into the page, so you can build click-to-dial and screen-pop workflows against your own web apps. The desktop softphone for Windows and macOS is where the tab is most useful. You can build these workflows without a separate desktop CTI connector, but the building is yours to do: nothing here is a ready-made screen pop.

Web tab, click-to-dial or a CTI connector: what's the difference?

These three ideas often get mixed up. A web tab shows a page inside the softphone. Click-to-dial starts a call from a link in your CRM, email or browser. A CTI connector is separate desktop software that links a phone and a CRM. You can use more than one, and the table shows where each fits.

Click-to-dial is covered in click-to-call for SIP softphones on the desktop, and the wider picture of connecting a softphone to business tools is in connecting your softphone to CRM and helpdesk tools. This post is only about the in-app tab.

Can each tenant or brand get its own tab?

Yes. Each tenant or brand profile can have its own tab, with no custom build. That suits providers who run branded softphones for several customers: each customer sees the page that belongs to them, set up once in the portal.

For a team with a single business, one tab for the whole company is usually enough. Split tabs only when different groups really work in different tools.

Pair it with a hosted PBX

Pair it with a hosted PBX so calls, extensions and transfers sit on one system while your agents keep the CRM open in the same app. That keeps the phone side and the customer record side close together, and it is a natural fit for running a contact centre on a hosted PBX.

Checklist: rolling out a CRM tab

• Pick the page your team uses most on calls
• Decide the URL and which placeholders it needs, using {password} only if essential
• Set the URL, label and icon in the cloud portal
• Use a separate tab per tenant or brand profile if you serve several customers
• Push to users and test on one desktop and one mobile device
• Confirm each user sees their own data after signing in
• Add click-to-dial links in the CRM if you also want one-click outbound calls

FAQ

Can I see my CRM inside the softphone?

Yes. Pin your CRM, helpdesk or internal portal as a custom web tab, so it sits one tap away from every call. You choose the page, set the URL, label and icon in the cloud portal, and the tab reaches your users without a reinstall of the app.

Is the web tab a native Salesforce or HubSpot connector?

No. It embeds the web page you choose. Placeholders pass the signed-in user and device ID into the URL, so you can build click-to-dial and screen-pop workflows without a separate desktop CTI connector. Salesforce, HubSpot, Zendesk and Freshdesk are examples of pages you can embed, not native connectors.

Where do I configure the tab?

In the cloud portal. Set the URL, label and icon there, add any placeholders the page needs, and the tab reaches your users without a reinstall. Because the portal manages it centrally, you can change the URL later without asking people to update anything on their own devices.

Can different customers or brands have different tabs?

Yes. Each tenant or brand profile can have its own tab, with no custom build required. That makes it a good fit for providers who run branded softphones for several customers, because each customer sees their own page, configured once in the cloud portal.

Which apps support it?

The tab runs in SessionTalk's softphone apps, which are managed from the cloud portal, and the desktop softphone runs on Windows and macOS. Check the softphones page for the current list of platforms before you plan a rollout, and test on one desktop and one mobile device first.

Want your CRM one tap from every call? Explore SessionTalk's softphone apps.