Live chat & message lifecycle
New messages, edits, deletes, replies, reactions, attachments, typing, delivery, reads, callable numbers, links, and transcripts.
Live support + visitor operations
WhaChat
Chat. Connect. Convert. A customer-support workspace for businesses that need their website conversations, teams, visitors, tickets, and updates in one accountable system.
Why WhaChat exists
Customer support should feel close, organized, and alive.
WhaChat gives a business the familiar simplicity of messaging while adding the operational controls a support team needs: tenant workspaces, roles, routing, assignments, presence, statuses, tickets, notifications, visitor context, and reporting.
- A branded widget that installs on approved client websites
- A responsive owner and agent workspace for daily operations
- Real-time message, typing, presence, delivery, and read lifecycle
- Attachments, reactions, replies, edits, transcript export, and tickets
- Free, trial, Pro, account, plan, email, and deployment foundations
Platform capabilities
From first website visit to resolved customer request.
Each area is designed to support the same conversation rather than fragmenting customer context across unrelated tools.
Agents & departments
Owners, support agents, department roles, assignments, invitations, transfers, participation, availability, and public agent identity.
Visitor intelligence
Sessions, location context, device and browser details, last seen, page activity, unread state, and quick profile access from chat.
Status Center
Business stories, media, scheduling, expiry, views, replies, analytics, and a premium status ring on the visitor widget.
Tickets & support continuity
Create, route, reply, attach files, track state, and continue work beyond a single live session with a complete ticket flow.
Widget Studio & Install Kit
Business identity, avatar, verification, colors, launcher, position, welcome copy, pre-chat messages, domains, embed code, and preview.
Tenant & role controls
Separate business workspaces, role-safe views, plan enforcement, allowed domains, account controls, and protected administrative actions.
Notifications & mobile operation
In-dashboard alerts, sound routing, email flows, PWA behavior, background-aware notification foundations, and mobile-safe workflows.
Analytics & business visibility
Chat activity, response performance, visitor movement, status engagement, agents, routing, tickets, and operational trends.
Designed for real teams
Owners keep control. Agents receive the access needed to serve.
The client owner manages the workspace, business identity, domains, plan, team, and policies. Agents operate through role-safe dashboards, accept or decline eligible chats, collaborate across departments, update public identity, and work tickets without inheriting owner-only controls.
Typical operating flow
- 1. Install: approve the website and place the generated script globally.
- 2. Brand: set business name, public agent identity, avatar, badge, colors, welcome copy, and quick messages.
- 3. Organize: create departments and agents, define availability, and prepare routing.
- 4. Serve: receive visits and messages, accept or assign chats, invite specialists, and resolve requests.
- 5. Improve: review analytics, visitor context, ticket outcomes, and status engagement.
Commercial & deployment path
Choose the level of ownership your business needs.
Exact pricing, licensing, storage, user limits, and support coverage are confirmed in a written offer. We do not publish invented figures before the commercial package is approved.
Managed WhaChat
Operate through the Starlife-managed platform with onboarding, workspace setup, approved domain connection, and plan-based features.
Request hosted accessManaged installation
Starlife handles application setup, environment configuration, database connection, email, domains, storage, health checks, and handover.
Review installationCommercial licensing
For broader deployment, customization, white-label discussions, or resale scenarios, licensing and scope are reviewed directly.
Discuss licensingImportant: WhaChat deployment requires a compatible Node.js environment, database access, SSL, storage permissions, domain configuration, and email settings. Starlife verifies these before production cutover.
Production requirements
WhaChat depends on the complete service environment.
Exact requirements are confirmed against the release package and hosting provider before deployment. The application should not be uploaded into an unknown environment and treated as production-ready.
- HTTPS application host and approved public website domains
- Compatible Node.js runtime and package installation support
- MySQL-compatible database with protected credentials
- Writable private storage for attachments, statuses, avatars, and logs
- SMTP mailbox for verification, invitations, recovery, and notices
- WebSocket-compatible proxy and sufficient process, memory, and upload limits
- Push keys and browser permission flow when background push is enabled
- Backup, monitoring, restart, health-check, and incident ownership
| Layer | Required outcome |
|---|---|
| Application | Health route, admin routes, widget assets, APIs, sockets, and background tasks respond correctly |
| Data | Database connection, tenant isolation, migrations, backups, and recovery are verified |
| Communication | Email, notifications, sound policy, push, and deep links reach the correct role and action |
| Website | Embed code appears globally on approved pages and respects widget configuration |
| Mobile | PWA install, safe-area layout, uploads, background expectations, and notifications are tested |
Release, documentation, and support
A commercial product needs an accountable change path.
Each production deployment should identify the supplied release, environment changes, database changes, configuration requirements, known limits, and verification result.
Documentation
Account setup, email verification, onboarding, widget installation, owner operations, agent workflows, tickets, status, notifications, plans, and support preparation.
Read the operating guideRelease record
Deployment packages should include a version or build identifier, change summary, required environment updates, database notes, and production validation checklist.
Review deployment processSupport and feature requests
Defects, configuration, installation, training, provider incidents, and new feature requests are assessed through separate support and commercial paths.
Open WhaChat supportSee WhaChat in your business context
Bring your website, support team, and workflow to the demo.
We will show the relevant owner, agent, widget, visitor, ticket, status, and deployment flows rather than giving you a generic sales tour.