A persistent alert that requires acknowledgement.
BRANCH BUDDY
Presence and attention.
One touch.
A quiet coordination board for small in-person teams. Know who is ready, send a clear signal, and keep the branch moving without starting another chat.
Private beta · not affiliated with or approved by any financial institutionWHAT IT DOES
Signals, not conversations.
A brief five-second request for a coworker.
A lightweight arrival notification.
A targeted request sent only to available, opted-in teammates.
A shared view of aligned thirty-minute lunch windows.
Session controls and a sign-out test for shared devices.
SAFETY BOUNDARY
Coordination without customer data.
Customer-data prohibition
Branch Buddy is designed only for generic employee coordination. Customer, account, transaction, authentication, and confidential bank information are prohibited.
Collect the minimum operational data, avoid free-text communication, restrict access by branch, and disclose honestly where service processing occurs.
Use only for non-customer operational signals. Never use it for surveillance, personnel scoring, regulated records, or emergency instructions.
Use short delivery windows, daily guest and session expiration, deliberate branch deletion, and a documented production retention schedule.
Stop access, revoke sessions, preserve necessary security evidence, assess exposure, and notify affected organizations and authorities when required.
FAQ
How Branch Buddy handles data
What does Branch Buddy do?
It gives a branch team a simple shared view of who is available, lunch scheduling, direct attention signals, lobby alerts, and customer-line assistance. It is an operational coordination tool—not chat, core banking software, or a system of record.
What must never be entered?
Never enter or communicate customer names, account numbers, balances, transactions, authentication information, Social Security numbers, card data, case details, or other confidential bank or customer information.
Is the current beta end-to-end encrypted?
No. Network traffic uses HTTPS, recovery PINs and session credentials are stored as one-way hashes, but operational branch data is processed by the service. Do not treat this beta as local-only or as approved for regulated production use.
What data does the beta use?
Branch and employee labels, presence and device-session metadata, lunch selections, alert routing and acknowledgements, preferences, and invite records. Voice recording and Walkie Talkie functionality have been removed.
How long is data retained?
Guest access expires daily, active sessions are ended at the daily cutoff, and short-lived alerts stop appearing after their delivery window. Branch profiles and configuration remain until they are deliberately deleted. A formal production retention schedule is required before workplace deployment.
Can this replace approved bank systems?
No. It must not be used for transactions, customer servicing records, emergencies, regulatory communications, surveillance, timekeeping, performance evaluation, or any workflow that must be retained by the bank.