Use Communicator in a browser

Communicator for the web gives you the same calling, chat and contacts in your browser. There's nothing to install, so it suits a shared computer or one you can't add software to.

This feature needs the Communicator apps add-on on your account. See plans and pricing

Some labels in your portal or apps may look slightly different from this guide.

Open it

1. 1
   Step 1:

   Go to the address

   Open proxy.callsprout.com/webapp/login in a supported browser. It's listed for Chrome, Edge, Firefox and Safari. On Contact Center Pro, add /webapp/login to your company's own callsprout.com address, which CallSprout gives you.
2. 2
   Step 2:

   Sign in

   Choose password, or single sign-on if CallSprout turned it on for your company, and enter your details. Sign in to Communicator has the steps. Unlike CallSprout Communicator NEXT on your computer, the web app has no Host field.

What your account needs for calls

To place calls in a browser, WebRTC needs to be turned on for your extension, and the system needs to allow the audio and security settings browser calls use. CallSprout support turns these on. If something is missing, calls fail, and you may see a message that the call failed because of incompatible settings. Ask your admin to check with support.

Hear your ringtone in Safari

Safari may block the sound of an incoming call.

1. 1
   Step 1:

   Open Safari settings

   Go to Safari, then Settings, then Websites.
2. 2
   Step 2:

   Open Auto-Play

   Select Auto-Play.
3. 3
   Step 3:

   Allow sound for the web app

   Set the Communicator site to Allow All Auto-Play.

How the web app differs from Communicator NEXT

The web app doesn't have remote keypad entry. In meetings, it can't act as the presenter who gives someone remote control. Busylight works only in Chromium based browsers.

The call window may show an encryption indicator when your call is encrypted. It isn't shown for calls on other devices.

Troubleshooting

• You hear no ringtone in Safari. Follow the Auto-Play steps above.
• A call fails right away. Ask your admin to have CallSprout support check that WebRTC is on for your extension, then try again.