List suitable topics
Publish concrete examples of routine questions the team can answer. Keep the list aligned with staff training, service hours, and the systems available to them.
Trust centre
Safe Use and Limitations of RoomLnk
A useful communication tool is clear about what it does not do. RoomLnk supports focused private conversation; it should not become an emergency line, identity proof, payment terminal, or substitute for specialist systems.
Direct answer
What you need to know
Use RoomLnk for routine one-to-one questions, coordination, directions, availability, preparation, and customer follow-up within the responding team’s authority. Do not rely on it for emergencies, passwords, one-time codes, payment credentials, verified account access, public alerts, group chat, or records that must be handled in a regulated system.
The practical context
Why this matters in a real conversation
The room interface can make a request feel direct, but response is not guaranteed to be immediate. Businesses should state monitored hours and make urgent routes visible before the customer opens chat. Staff should recognise when a routine question becomes a safety, complaint, fraud, safeguarding, health, financial, or legal matter.
Link possession and a chosen display name provide context, not identity assurance. A person may forward a link or use another name. Before disclosing protected details, changing an account, releasing property, or accepting a consequential instruction, use the organisation’s approved verification and authorisation process.
A workable approach
Build safe boundaries into the invitation
List immediate alternatives
Place emergency, safety, phone, portal, formal complaint, and accessibility routes where users can see them without waiting for a chat reply.
Train escalation triggers
Teach staff to stop and hand off when identity, authority, urgency, specialist advice, payment, safeguarding, or formal evidence becomes relevant.
Review incidents and near misses
Use misrouted and unsuitable conversations to improve signs, greetings, training, access, and channel design rather than blaming the customer for choosing the visible option.
Operating checklist
Make unsuitable requests easy to redirect
A useful room starts with clear expectations. Keep the invitation specific, make ownership obvious, and give people another contact route when chat is not the right channel.
- Never request passwords or security codes.
- Publish emergency routes prominently.
- Verify identity outside guest display names.
- Keep accessible alternatives available.
- Record formal actions in approved systems.
Where RoomLnk does and does not fit
RoomLnk is not an emergency, medical, legal, financial, crisis, safeguarding, identity, payment, access-control, mass-notification, public-community, or regulated records service. This page is operational guidance, not legal or professional advice. Each organisation must assess its customers, risks, jurisdiction, and duties.
Questions and answers
Common questions about safe use and limitations
Can RoomLnk be used in an emergency?
No. People should use the relevant emergency service, venue procedure, safety contact, crisis line, or urgent provider channel. A browser room may not be monitored continuously and should never delay immediate help.
Can staff ask for a password to verify someone?
No. Do not request passwords, full payment credentials, or one-time security codes. Use the organisation’s approved authentication process and explain why the conversation must move.
What if a customer shares sensitive information anyway?
Avoid repeating it unnecessarily, follow organisational privacy and incident procedures, restrict access, move required action to the appropriate specialist system, and give the customer clear guidance about the safer channel.
Try the workflow in a temporary room
Create a room, open its QR code, and see what the invited person experiences.