Phased Rollout — Launching a Chatbot to Part of Your Traffic First, the Four Dials, and Which Ones Vendors Give You

Quick answer: A phased rollout puts a chatbot in front of some of your customers before all of them. The first phase is small enough that you can read every transcript it produces; each later phase is wider, and you move to it only when the previous one has held its fallback rate and containment rate for long enough to trust. The reason it is a defined practice rather than common sense is that chatbot platforms expose it unevenly. Intercom's help center says outright that "it's a good idea to introduce your AI agent in stages" and gives you audience rules to do it with, down to a filter on your own staff's email domain. Tidio gives you page, domain, country and device visibility for the widget, but not a percentage of visitors. Manychat gives you a Set Live button that publishes an automation and a Default Reply that can fire once per user per 24 hours, which is a throttle, not a phase. And on WhatsApp, Meta's Messaging Limits page caps a new business portfolio at 250 unique recipients per moving 24 hours outside a customer service window, which means your first phase on that channel is sized by Meta whether or not you planned one.

This entry owns the definition, the four dials and which platforms turn them. The week-by-week procedure around the switch, including what to have ready to turn it back, is the same-day chatbot launch checklist; the tests that should already have passed before any phase begins are the QA testing protocol; the re-test after every later change is the regression testing guide.

The four dials

A rollout is phased by limiting exposure, and exposure to a chatbot can be limited on four independent axes.

The dials are independent, so a first phase can be "support page only, team only, web only, business hours only," and each later phase opens one dial at a time. Opening two at once is the mistake that makes a bad number impossible to attribute.

What the three platforms actually give you

Intercom: audience rules, and a recommended order. Fin's audience rules are configured in the Who will see Fin section of the chat and email deploy screens, or in a Workflow's trigger settings; the article notes that "audience rules will apply to all channels you've enabled for Fin AI Agent." For the team-only phase it suggests selecting Users and filtering on "Email contains" your company domain, which "will also allow you to check that your handover rules are running as you intended." For customers it recommends "rolling Fin AI Agent out in stages by customer segment, such as starting with lower-tiered customers who would benefit the most from self-service, or by region," and gives examples: a custom attribute such as "VIP customer is false," or "Plan is Free," or a Current Page URL rule that targets the support page. One cost note from the same article: "If you test Fin in your live environment, Fin will be billed per resolution," but a conversation where the tester asked to "Get more help" or to speak to the team counts as unresolved and is not charged. Our Intercom review records the per-resolution meter this rides on.

Tidio: visibility, not audience. Tidio's controls live under Settings, Live Chat, Appearance, in a section the help page calls Visibility and position. There you can hide the widget on pages by an Exact URL or by a Contains string, separately for desktop and mobile; restrict it to Trusted domains with "Show only on listed domains"; and under Country visibility either "Hide for specific countries" or "Show only in specific countries," which the page notes is "based on their IP addresses." Showing the widget only on named pages, rather than hiding it on named ones, needs the whitelist script from the second help article, which calls tidioChatApi.show() or .hide() on ready. Beyond country, there is no rule on who the visitor is (identity, plan, login state) and no percentage split on the two visibility pages. The bot itself has a second layer of scoping that those pages do not cover: our Tidio review recorded, hands-on on 28 May 2026, a Flows trigger picker with "On certain days and time," "Visitor opens a specific page," "First visit on site" and "Visitor returns to the site" among its triggers, so a Flow can be limited by hour, page and new-versus-returning visitor independently of where the widget shows. The same review records that the Lyro AI agent cannot be activated until the widget is live on at least one site, which orders the phases for you: widget on a narrow page set first, AI second.

Manychat: a switch per automation and a per-channel safety net. Manychat's unit of exposure is the automation. The Default Reply help page has you publish the automation with a Set Live button, and its troubleshooting section says to "confirm that the automation linked to the Default Reply is published," looking for "a small yellow dot next to the automation title, which indicates there are unpublished changes that need to be addressed." The Default Reply itself, the automation that answers any message no other trigger claims, is configured per channel (Facebook, Instagram, WhatsApp, Telegram) and can fire "every time a user sends a message or limit it to once every 24 hours for the same user." That once-per-24-hours setting is a frequency throttle on one person, not an exposure limit on the audience, and it is easy to mistake for one. The phase control on Manychat is therefore the channel dial (connect Instagram, leave WhatsApp unconnected) and the automation dial (set one flow live and leave the others unpublished, which the pages read imply rather than state). On Instagram specifically, the connection help pages add a gate that is not a phase but behaves like one when it is missed: the account must be a professional account, and in the Instagram app under Settings and activity, Messages and story replies, Message controls, Connected tools, Allow access to messages must be on; Manychat's troubleshooting page lists that toggle as the second check for an account that fails to connect, and a bot behind an unconnected account is, in effect, not launched. The Instagram DM automation entry covers what follows once it is on.

The phase Meta sizes for you

On WhatsApp the first phase has a number attached before you choose one. Meta's Messaging Limits page: "Newly created business portfolios have a messaging limit of 250," defined as "the maximum number of unique WhatsApp user phone numbers your business can deliver messages to, outside of a customer service window, within a moving 24-hour period," and the limits "are calculated and set at the business portfolio level and are shared by all business phone numbers within a portfolio." Messages inside a customer service window (the 24 hours after a customer's last message or call, as Meta defines it on its send-messages page, cited in Sources) are not counted, so on our reading a WhatsApp bot that only answers inbound messages is not phased by the limit at all; a bot that sends templates first is capped at 250 unique recipients per moving 24 hours until the portfolio completes one of three scaling paths (business verification, partner verification, or 2,000 delivered high-quality templates to unique numbers in a moving 30 days). Completing a path is not the raise itself: the page says Meta then "analyzes your message quality" and approves or denies eligibility, and a denial keeps the limit where it was. Once approved at 2,000, the limit rises by one level within 6 hours when quality is high and at least half the current limit was used in the last 7 days. Read as a rollout, that is a phase ladder with Meta holding the dial: 250, 2,000, 10,000, 100,000, unlimited. The verification guide covers the paperwork that moves it.

The widen-or-pull-back rule

Ours, not a vendor's. Between phases, read three numbers on the phase just finished and compare them to the golden dataset run you did before launch: fallback rate, containment rate, and the share of handoffs that reached a person inside your promised time (the launch checklist adds a fourth for launch week only, conversations the bot never answered). Widen one dial if all three held for a full weekly cycle, because a bot that looks fine on Tuesday has not met Saturday's questions yet. Pull back to the previous phase, not to zero, if fallback has risen by more than a third over its pre-launch baseline for a full day or a handoff went unanswered, and fix the cause before repeating the same phase. Never widen to repair a number; a wider audience does not dilute a broken flow, it multiplies it. The launch checklist turns this into a day-by-day schedule.

What our fifteen reviews record

Searched 21 September 2026, case-insensitively, across the fifteen files matched by sample-reviews/*-review.md: phased appears in 0; soft launch in 0; set live in 0; rollout, roll-out or roll out in 1 (Tidio, describing the vendor's own Claude-and-MCP product rollout, not a customer's); publish in 15, mostly in the sense of what a vendor does or does not publish (pricing, compliance pages), with the builder's publish action and a video's publish date behind it, and in no case a staged exposure of a live flow. No review protocol ran a flow live to a limited audience and then widened it; the Manychat review lists "live published flow execution to real production users" among the items its session did not exercise, and it is the review that comes closest. The audience and visibility mechanics above are therefore documentation reads, and that gap is ours to close, not a finding about any platform. Corrections to editorial@chatbotscape.com.

Related terms

• Chatbot fallback rate — the first number to read between phases.
• Containment rate — the second, and the one that decides whether widening is worth it.
• Human handoff — the moment a small phase protects: someone has to be there to take it.
• Golden dataset — the pre-launch baseline every phase is compared against.
• Chatbot handoff rules — what Intercom's help page says a team-only phase also lets you check.
• WhatsApp message template — the message type the 250-recipient limit counts.

FAQ

What is a phased rollout for a chatbot?

Releasing the bot to a limited part of its audience first (a few pages, a segment, one channel, or certain hours), reading how it performs there, and widening in steps while the fallback, containment and handoff numbers hold, with the previous phase kept one switch away. Soft launch and staged rollout mean the same thing.

Is a phased rollout the same as a soft launch?

For a chatbot, yes. "Phased rollout" says what the practice is: exposure widened in phases. A canary release is the software-deployment cousin, where a new build serves a small share of requests; none of the three platforms whose pages we read exposes a traffic-percentage split, so the chatbot version is cut by page, audience, channel or hour instead.

Which chatbot platforms support a phased rollout?

Of the three whose help pages we read on 21 September 2026: Intercom, through audience rules on Fin (users versus leads, custom attributes, page URL, And/Or filters), with a written recommendation to roll out by segment; Tidio, through widget visibility by page, domain, country and device, plus Flow-level triggers by hour, page and first-versus-returning visit recorded in our review, with no rule on identity, plan or login state; Manychat, through per-automation Set Live and per-channel Default Reply, with no audience rule on the pages read. A single-channel launch is possible on any platform by leaving other channels unconnected.

How long should each phase last?

One full weekly cycle at minimum, because question mix changes by weekday and a phase that spans only weekdays has not seen the weekend. Widen one dial at a time so that a changed number has one cause.

Does WhatsApp limit a new chatbot's audience?

For messages delivered outside a customer service window, yes: a new business portfolio can deliver to 250 unique recipients outside a customer service window per moving 24 hours, shared across all its numbers, until it completes one of Meta's scaling paths and passes the quality review that follows, which takes the limit to 2,000; above that the limit rises automatically on quality and usage. Messages inside an open customer service window are not counted, so on our reading an inbound-only WhatsApp bot is unaffected.

Sources

• Intercom Help, Live testing Fin with your team or customer segments (intercom.com/help/en/articles/7837527, dated 14 May 2026), read 21 September 2026: "It's a good idea to introduce your AI agent in stages and monitor the impact as you go"; the Who will see Fin section under Fin AI Agent > Deploy > Chat and > Email; "Audience rules will apply to all channels you've enabled for Fin AI Agent"; the team-only example ("select 'Users' and use the filter 'Email contains…'"), which "will also allow you to check that your handover rules are running as you intended"; "We recommend rolling Fin AI Agent out in stages by customer segment, such as starting with lower-tiered customers who would benefit the most from self-service, or by region"; the "VIP customer is false," "Plan is Free," Users or leads only, and Current Page URL examples; "If you test Fin in your live environment, Fin will be billed per resolution," with the "Get more help" exception.
• Tidio Help, Disable Tidio on specific pages (help.tidio.com/hc/en-us/articles/5454505438620, updated 17 July 2026), read 21 September 2026: Settings > Live Chat > Appearance, Visibility and position; Trusted domains ("Show only on listed domains"); Country visibility ("Hide for specific countries," "Show only in specific countries," "based on their IP addresses"); the Display toggle per desktop and mobile; Page visibility with Exact and Contains rules.
• Tidio Help, Show Tidio Widget Only on Specific Pages (help.tidio.com/hc/en-us/articles/5463603462172, dated 25 October 2024), read 21 September 2026: "this process requires access to your website's code"; the whitelist script calling window.tidioChatApi.show() or .hide() on the ready event.
• Manychat Help, Default Reply in Manychat (help.manychat.com/hc/en-us/articles/14281159586588, updated 3 December 2025), read 21 September 2026: "available across multiple channels, including Facebook, Instagram, WhatsApp, and Telegram"; the trigger can "activate every time a user sends a message or limit it to once every 24 hours for the same user"; "toggle the switch in the bottom left corner to activate the Default reply and click the Set Live button to publish the automation"; "confirm that the automation linked to the Default Reply is published. Look for a small yellow dot next to the automation title, which indicates there are unpublished changes that need to be addressed."
• Manychat Help, How to connect Instagram to Manychat (help.manychat.com/hc/en-us/articles/14281290924444, updated 27 August 2026) and Can't connect Instagram to Manychat (help.manychat.com/hc/en-us/articles/14281291094428, updated 4 December 2025), read 21 September 2026: "your Instagram account must be set to a professional account (Business or Creator)"; "go to Settings and activity → Messages and story replies → Message controls → Connected tools, and toggle Allow access to messages on."
• Meta for Developers, WhatsApp Business Platform, Messaging Limits (developers.facebook.com/documentation/business-messaging/whatsapp/messaging-limits), read 21 September 2026: the definition quoted above; "calculated and set at the business portfolio level and are shared by all business phone numbers within a portfolio"; "Newly created business portfolios have a messaging limit of 250," increasable to 2,000, 10,000, 100,000 and Unlimited; the three scaling paths; the automatic-scaling criteria ("In the last 7 days, your business has utilized at least half of your current messaging limit"; "your portfolio's limit increases by one level within 6 hours").
• Meta for Developers, WhatsApp Business Platform, Send messages (customer service windows) (developers.facebook.com/documentation/business-messaging/whatsapp/messages/send-messages), read 21 September 2026: "When a WhatsApp user messages you or calls you, a 24-hour timer called a customer service window starts. If the user messages or calls you again before the timer expires, the timer resets to 24 hours."
• Chatbotscape review corpus (the fifteen platform reviews at /reviews), searched 21 September 2026 from the repository root. Denominator: ls sample-reviews/*-review.md | wc -l returns 15. grep -liE 'phased' sample-reviews/*-review.md returns 0; grep -liE 'soft launch' sample-reviews/*-review.md returns 0; grep -liE 'set live' sample-reviews/*-review.md returns 0; grep -liE 'rollout|roll-out|roll out' sample-reviews/*-review.md returns 1 (tidio, line 471); grep -liE 'publish' sample-reviews/*-review.md returns 15. Passages cited: manychat-review.md line 749 (the items-not-exercised list); tidio-review.md line 194 (Lyro cannot be activated until the widget is live on at least one site) and lines 566 and 580 (the Flows trigger picker, captured hands-on 28 May 2026, listing "On certain days and time," "Visitor opens a specific page," "First visit on site" and "Visitor returns to the site").
• Chatbotscape evaluation methodology. /methodology (continuously updated).