How Continually Handles Live Chat and Automatic Meeting Scheduling
Updated
Continually combines a shared live chat inbox with automatic meeting scheduling so that website visitors get an immediate response and qualified leads can book time with you without any back-and-forth. Live chat lets anyone on your team reply to incoming messages or take over a bot conversation, while automatic scheduling lets customers pick a slot that works for both sides once you connect your calendar and set your availability. Both features are aimed at the same problem: you can't be available 24/7, but potential customers expect an immediate reply.
Live chat: a shared inbox, not a personal one
When a visitor gets in touch through live chat, the conversation lands in Continually's inbox rather than being tied to one person's account. According to the site, "anyone in your team can quickly reply" to incoming messages.
Two things follow from that design:
- Coverage without shifts. If the person who normally handles chat is in a meeting, out of office, or in a different time zone, another team member can pick up the message.
- Bot-to-human handover. You can take over a bot conversation when a visitor needs a real person, so the automated flow doesn't become a dead end.
The practical setup is simple: the chat widget is added to your site, and your team works from the shared inbox. The site describes installation as one line of embed code, or a WordPress plugin if you prefer not to touch the theme files.
What the bot does before a human joins
Continually's bot builder is drag-and-drop and requires no coding skills, so you can script the first layer of the conversation yourself. The site notes that bots can engage visitors with images, GIFs, videos and emojis, and that you can build "complex bots" in minutes. In practice this means the bot handles the initial greeting, qualifying questions, or common answers, and a teammate steps in through the inbox when the conversation needs one.
Automatic meeting scheduling: how the handoff works
Scheduling is where chat turns into a booked meeting. The mechanism described on the site has three parts:
- Connect your calendar. You link the calendar Continually should read from and write to.
- Set your availability. You define the windows when meetings can be booked.
- Let the customer choose. Visitors book "at a time that suits you both," and the site says qualified leads go "straight to your calendar."
The value is in removing the manual step. Instead of a chat that ends with "I'll email you some times," the visitor picks a slot inside the conversation. That matters most outside working hours or across time zones, where a reply-then-wait cycle can lose the lead entirely.
Where the lead data goes
Booked meetings and captured leads aren't locked inside Continually. The site states you can send lead data to 1,500+ apps, using Zapier or native integrations that include Mailchimp, Drip, ActiveCampaign, HubSpot and Moosend. So a chat enquiry can flow into your email list or CRM without manual copying.
What you need before this works
| Requirement | Why it matters |
|---|---|
| Calendar connected | Scheduling can only offer slots that reflect your real availability |
| Availability configured | Defines the boundaries of what customers can book |
| Chat widget installed | One line of embed code, or the WordPress plugin |
| Bot flow built (optional but useful) | Handles the first response when no one is online |
| Integration chosen (optional) | Routes lead data to your CRM or email tool |
The site also states that getting started requires no credit card, and that you can begin with a free account. Pricing details beyond that are listed on a separate pricing page, so check there for current plan limits before committing a team to it.
Where this fits and where it doesn't
Continually's live chat and scheduling are a good fit if you run a small or mid-sized site, want lead capture without a developer, and need coverage across time zones or outside office hours. The shared inbox and no-code bot builder lower the barrier to getting something live quickly.
It's a weaker fit if you need deep, custom conversational logic that a drag-and-drop builder can't express, or if your scheduling rules are complex enough that a simple availability window won't capture them. In those cases the automatic scheduling may still work, but you'd want to verify the calendar rules against your actual booking policy before relying on it.