Wildix in Microsoft Teams testing guide

Your details

Tester name

Extension

Test date

Browser used

Your answers are saved in this browser as you go. When you've finished, click Print / save as PDF and send the PDF back with any issues.

How it works

This guide takes you through setup and a set of call tests, so we can confirm Wildix works inside Microsoft Teams before go-live.

x-bees in your browser = your phoneIt carries the call audio. Keep it open in a browser tab all day.

Wildix tab in Teams = your remote controlDial, answer, hold, transfer and hang up here. The audio plays through x-bees.

You make and receive phone calls from the Wildix tab in Teams, not from the Teams Calls tab. Teams chat, meetings and Teams-to-Teams calls carry on working as normal.

Before you start

Tick these off before testing day. Your IT contact owns the first three items.

IT admin: the Wildix app has been added to Teams for the organisation and pinned to the left-hand bar for testers
IT admin: a Microsoft 365 Global admin is available if Teams presence sync is being enabled
IT admin: testers have received their Wildix login details (or can sign in with their Microsoft account)
Tester: Google Chrome or Microsoft Edge is up to date
Tester: your headset is plugged in and working
Tester: you know your Wildix extension number and direct dial number
Tester: you have a mobile phone to hand, to make and receive external test calls
Tester: you have a colleague also testing, for internal call and transfer tests

Setup steps

Do this once, in order. It takes about 10 minutes.

Open x-bees (your phone)

In Chrome or Edge, go to app.x-bees.com
Sign in with your Wildix details or Microsoft account
Click Allow for the microphone and notifications
In x-bees settings, choose your headset for mic and speaker
Right-click the tab, choose Pin, and leave it open

Stop the tab going to sleep

Chrome: Settings › Performance › Memory Saver › Always keep these sites active › Add app.x-bees.com
Edge: Settings › System and performance › Never put these sites to sleep › Add app.x-bees.com

Sign in to Wildix in Teams

Click the Wildix icon on the Teams left-hand bar (or Apps › search Wildix › Add)
Choose x-bees and sign in with the same account
Check your x-bees browser session shows as the active device

Turn on presence sync

In x-bees settings, find Microsoft Teams Presence
Click Install and sign in with your Microsoft account
Set Teams to Busy and check x-bees follows within a minute

Only if your IT admin has enabled it.

Test scripts

Run every test from the Wildix tab in Teams, with x-bees open in the browser. Set the result for each row and add a note for anything that isn't a clean pass.

#	Test	How to do it	Expected result
1	Outbound external call	Dial your mobile from the Wildix tab	Mobile rings and shows the company number; audio clear both ways
2	Inbound external call	Call your direct dial number from your mobile	Wildix tab and browser both ring; answer in Teams; audio through headset
3	Internal call	Dial a colleague's extension	Colleague's Wildix tab rings; audio clear both ways
4	Hold and resume	On a call, press Hold, wait 10 seconds, resume	Caller hears hold music; audio returns cleanly
5	Mute	On a call, mute then unmute	Caller can't hear you while muted
6	Blind transfer	Transfer a call straight to a colleague	Colleague rings and gets the caller; your line clears
7	Attended transfer	Speak to a colleague first, then complete the transfer	Caller held while you consult; colleague gets the caller
8	Transfer to a mobile	Transfer a call to an external mobile number	Mobile rings and gets the caller
9	Voicemail	Let a call from your mobile go unanswered and leave a message	Missed call shows; voicemail can be played back
10	Call history	Open call history and click a recent number	History is correct; click-to-call dials the number
11	Group or queue call	Call the main company number (if you're in a group)	Call reaches you via the group or queue
12	Keypad tones	Call an automated menu and press menu options	Menu responds to each key press
13	Presence sync	Change your Teams status; then go on a call	x-bees follows Teams within about a minute; colleagues see you busy
14	Do Not Disturb	Set DND in Wildix, then call yourself from your mobile	Call goes to voicemail or your forwarding rule
15	Call during a Teams meeting	Join a Teams meeting; have a colleague call you	Wildix call alerts you; headset behaviour is acceptable

Resilience tests

These check everyday situations that can stop calls reaching you. They matter because x-bees in the browser is your phone: if it isn't running, nothing rings.

#	Test	How to do it	Expected result
R1	x-bees tab closed	Close the x-bees tab, then call yourself from your mobile	Call doesn't ring you; it follows your unavailable rule (voicemail or forward). Reopen x-bees and repeat test 2
R2	Browser left idle	Leave x-bees in the background for 30+ minutes, then call yourself	Call still rings (confirms the sleeping-tab setting from setup step 2)
R3	PC restart	Restart your PC, open Teams and x-bees, call yourself	Calls work once both are open again
R4	Network change	Move between office Wi-Fi and wired, or Wi-Fi and home	x-bees reconnects on its own; next call works
R5	Headset unplugged	Unplug and replug your headset, then make a call	Audio returns to the headset; if not, reselect it in x-bees settings

Expected behaviour (not faults)

Please don't log these as issues. They are how the system is designed to work.

The Teams Calls tab and dial pad don't make phone calls. All phone calls go through the Wildix tab.
Wildix can't control Teams-to-Teams calls. Hold, transfer and so on in the Wildix tab only apply to Wildix phone calls.
Presence can take up to a minute to update between Teams and x-bees.
Use Teams for chat. The Wildix app has its own chat, but please use Teams chat so messages stay in one place.
If the x-bees tab is closed, calls won't ring you. They follow your unavailable rule (voicemail or forward) until you reopen it.

Reporting issues and sign-off

Report any Fail or Partial result the same day, so we can fix it before go-live. For each issue, please send:

The test number (for example, Test 6 or R2)
The time it happened, and the numbers involved
What you expected, and what actually happened
A screenshot if there was an error message
Your browser, and whether you used the Teams desktop app or Teams in a browser

Send issues to: [support contact – email / phone]

Once all testers have finished and any issues are resolved, the customer's project lead signs off below.

Name	Role	Date	Overall result	Signature
	Customer project lead
	Provider engineer

Wildix in Microsoft Teams: testing guide