Your settings are assigned by an administrator and picked up automatically by the browser extension after you sign in there.
| Company | |
|---|---|
| Extension number | |
| Phone | |
| Click to call | |
| PBX URL | |
No call icons on these websites or their subdomains, in every browser you are signed in to. One per line, such as example.com. The browser extension can change them too.
Sends a fake incoming call to your own signed-in browsers so you can check the call window.
Each user gets an extension number (which phone's calls open their call window), a phone to control and click to call settings. Changes reach signed-in browser extensions instantly.
| Username | Company | Ext | Phone | Click to call | Role | Browser | |
|---|---|---|---|---|---|---|---|
| Custom URL | |||||||
|
Signed in browsers
No browser extension is signed in for this user. | |||||||
No users yet.
Group users by company. Each company has its own phone hook key, so extension numbers can repeat across companies.
| Name | PBX domain | Users | |
|---|---|---|---|
| Open |
No companies yet.
The PBX domain fills {pbx_domain} in click to call URLs for this company's users.
Add these lines to the Yealink provisioning template for this company's phones. They send phone events (ringing, answered, ended, held and so on) to the portal and turn off the phone's "Allow remote control?" prompt.
Copy lines · Key rotate
Each user gets an extension number (which phone's calls open their call window), a phone to control and click to call settings. Changes reach signed-in browser extensions instantly.
| Username | Company | Ext | Phone | Click to call | Role | Browser | |
|---|---|---|---|---|---|---|---|
| Custom URL | |||||||
|
Signed in browsers
No browser extension is signed in for this user. | |||||||
No users in this company yet.
Global integrations (Integrations tab, "All companies") also run for these users.
| Name | Type | Enabled |
|---|---|---|
Add or edit them in the Integrations tab and choose this company under "Applies to".
Deleting a company is refused while it still has users. Delete this company
Each enabled integration runs on every incoming call and adds its result to the call window. With none enabled, agents still get the caller ID.
No integrations yet.
When a user has a phone assigned, their browser extension controls it over the local network: dial, answer, reject, hang up, hold, resume, mute, blind and attended transfer, DND, keypad tones and redial. Commands go straight from the agent's computer to the phone, so both must be on the same network.
Each phone needs: remote control allowed for the agents' computers (Action URI Allow IP List, for example "any"), a web user account whose login is stored on the user (Edit), and the phone setup lines below so the portal knows about calls. The portal keeps each user's phone IP up to date from the phone's own events.
Phones of users that belong to a company use the lines on that company's page. These lines are for everyone else:
Copy lines · The key is HOOK_KEY in the portal's .env file.
The last 100 calls: incoming calls pushed to browsers, and click to call dials.
| Time | Direction | Company | Ext | Number | Matches | Browsers | Error |
|---|---|---|---|---|---|---|---|
| PBX URL |
No calls yet.
No changelog on this install. The deploy copies it, so it appears after the next update.