- What is TestInvite?
- Build Your First Test
- Run Your First Assessment
- Taking the Assessment
- Viewing the Results
- Question Bank Overview
- Common Question Features
- Question Types
- Creating Questions
- Organizing Questions
- Content Blocks
- Roles & Access
- Media Library
- Import & Export
- Question Submissions
- Question Bank Schema
- Browsing Questions
- Cloning Questions
- Bulk Updating Questions
- Tests Overview
- My Tests
- Creating a Test
- The Test Editor
- Test Settings
- Sections & Pages
- Adding Questions
- Page Builders
- Test Profile
- Reporting
- Test Papers
- Analytics
- Publishing a Test
- Test Library
- Marketplace
- Tasks Overview
- Creating a Task
- Task Dashboard
- Steps
- Task Settings
- Candidates
- Test Sessions
- Sent Mails
- Proctoring
- Analytics
Live Chat
Open a live message line between candidates and your team — offered on the login page (with a pre-chat contact form and temporary-chat option), in the workspace, and inside the test, and answered from the task or live from the Exam Monitor.
Private chat gives candidates a live message line to your team — no email round-trips while an exam clock is running. It is enabled per task and configured under Task Settings → Communication → Private Chat.
Turning It On
The master Active switch enables chat for the task. Once active, you choose exactly where candidates can start a conversation — each surface is a separate checkbox, so the channel opens only where you want it.
Where Candidates Can Chat
- Login page — visitors can open a chat before signing in. This is the support channel for the people who need it most: candidates who cannot get in at all (“my code doesn't work”, “I never received the invitation”).
- Assessment page — authenticated candidates chat from their workspace, between tests and around the pre-start steps.
- Test page — chat stays available during the exam itself, so a candidate can report a problem without abandoning a running test.
Login-Page Chat Options
Because login-page visitors aren't authenticated, this surface has its own options:
- Contact form — email / phone — ask the visitor for an email address and/or phone number before the chat starts, so your team can follow up if they leave before an answer arrives.
- Temporary chat — the conversation is not remembered in the visitor's browser: a page refresh starts a fresh chat. Leave it off and a returning visitor's conversation is restored where they left it.
- Guest conversations have no candidate record behind them; they surface to your team alongside candidate chats — in the Exam Monitor they collect under Other chats — and can be archived once handled.
Answering as the Team
- Reply from the task — and during live sittings, directly inside the Exam Monitor: every roster row has a chat button, unread counters surface new messages, a notification sound (mutable) announces them, and the docked chat window keeps monitoring running while you type.
- Conversations are per candidate and persist — a candidate's chat history stays with their record across the assessment.
- Delivery is live in both directions; candidates hear a notification sound when your reply lands, even while working in the test.
For proctored, scheduled sittings enable the test-page surface: it is the difference between a candidate silently abandoning a technical problem and a proctor fixing it in one message. And keep the login-page surface on for exam day — access problems happen exactly when candidates have no other way to reach you.