The use case this solves
Live chat is useful in exactly two contexts:
- The visitor is asking something the chat assistant genuinely can't answer, and a real person can.
- The visitor specifically asked for a real person.
In both cases, the question is not whether live chat would help. It would. The question is whether the owner can be a live person on demand. A small business owner cannot sit in front of a dashboard all day. But they can tap a push notification on their phone while in the car, at lunch, or between meetings. That's the setup that actually works.
How it works, step by step
- Visitor asks for a person (or says something the assistant flags as needing human attention).
- Your phone gets a push notification. Something like: "Customer wants to chat. Tap to join."
- You tap the notification. Your phone opens the conversation in the browser or in a pinned web app.
- You reply. The visitor sees your message. The conversation is now live.
- You hand back when you're done. Either the visitor ends the conversation, or you mark the handoff complete and the assistant takes over again for any follow-up questions.
The key is that the time from "visitor wants a person" to "a person is typing" can be under 10 seconds from when the owner pulls out their phone, taps the notification, and taps Join in the app.
iOS vs Android setup
Both work, with one gotcha. In SBB's setup (and in many phone-first small-business chat tools), the dashboard runs as a progressive web app (PWA): a website that behaves like an app when installed to your home screen. That's how you get push notifications. Other vendors may route alerts through a native mobile app, Slack, or email instead; check how your specific platform delivers them before assuming the PWA flow below applies.
Android
- Open the chat dashboard in Chrome on your phone.
- Tap the three-dot menu, choose "Add to Home Screen" or "Install App."
- Grant notification permission when asked.
- Send a test notification to confirm it works.
iOS
iOS only supports push notifications from PWAs when the app is installed from Safari, not from Chrome.
- Open the chat dashboard in Safari on your iPhone (not Chrome).
- Tap the share button, choose "Add to Home Screen."
- Open the installed app from the home screen (not the Safari tab).
- Grant notification permission when asked.
- Send a test notification to confirm it works.
What visitors see during handoff
A clean handoff should be visible to the visitor but not jarring. Good patterns:
- A short status line: "A team member has joined the conversation."
- A change in tone of replies. The visitor can tell a person is typing now.
- The owner typing in their real voice, not pretending to still be an AI.
Bad patterns to avoid:
- The owner pretending to be the bot. Visitors usually notice and trust drops.
- A jarring "Agent assigned: Owner123." Feels enterprise in a bad way.
- Silence, where the visitor sees the assistant stop responding but no indication a human is coming.
When to step in (and when not to)
Every push notification is a small interruption. Common starting points — not rules:
- Step in when the visitor has specifically asked for a person, is signaling urgency, or is mid-purchase with a specific question the assistant can't answer.
- Step in more if personal touch is your brand. Some owners deliberately jump in on most conversations — small-business customers often reach out specifically because they want to talk to the owner. The assistant covers what it can while you're busy; you take over whenever it's convenient. A valid style, not overkill.
- Don't step in for spam or test messages (they happen). The assistant is better at filtering these than you are.
Volume varies a lot by owner style. Some owners only take over on clear escalation moments and see a handful of live handoffs a week. Others jump in on most conversations because that personal contact is why customers chose a small business in the first place. Both are fine. The one signal to watch: if you're NEVER seeing handoff-worthy moments come through, the platform probably isn't flagging them, and you may be missing chances you'd want to take.
When you can't step in right away
Sometimes you're on a call, driving, or genuinely unable to respond. A good setup handles this gracefully:
- The assistant captures the visitor's name and contact info.
- It tells the visitor honestly that a person isn't available right now and when to expect a reply.
- The conversation is queued in the owner dashboard for the next time you can look.
The worst version of this is the assistant pretending someone is coming and then... silence. A well-built handoff acknowledges reality: "No one is available right now, but I've got your info and we'll reply first thing tomorrow."
How Simple Business Bots handles it
The Premium plan includes push notifications to your phone via a PWA. Install from Safari on iOS or Chrome on Android, enable notifications, and you get pinged when a visitor wants a person. One tap opens the conversation. You type your reply, the visitor sees it. Hand back when you're done and the assistant takes over. No separate tool, no inbox to watch.