Botstar

@Botstar show me the current application ID and open the live chat widget for our support team

Retrieved your Botstar application ID: `app_5x9k2m7n`. The live chat widget is now visible on the page. This example assumes the widget was previously initialized in 'livechat' or 'popup' mode. If the widget hasn't been bootstrapped yet, you'll need to call the boot tool first with your configuration settings.

This demonstrates read + action: fetching the app ID (useful for debugging or re-initialization) and programmatically opening the chat window. Requires the widget to already be configured in livechat or popup mode—won't work if your deployment uses modal-only mode.

@Botstar update the current chat session with user email support@acme.com and name 'Jordan Lee', then register a callback to log when they close the window

Updated the active live chat session with email `support@acme.com` and display name `Jordan Lee`. Registered an onClose callback that will log 'Chat closed by user' to the browser console when the widget is dismissed. These changes apply immediately to the current conversation and persist until the session ends or the page reloads.

Showcases write operations: updating user profile attributes mid-conversation and attaching event handlers. Useful for progressive profiling or analytics tracking. The callback fires client-side only—server-side logging requires additional integration with your backend.

@Botstar retrieve any webview parameters passed from the chatbot, then summarize what data the bot sent to this page

Extracted webview parameters: `user_intent=pricing_inquiry`, `plan_tier=enterprise`, `session_id=sess_8k3m`. Summary: The chatbot routed this user to the pricing page because they expressed interest in enterprise plans during the conversation. The session ID links back to the bot transcript for context. This data was passed via `bs:input` meta tags when the page loaded in modal mode.

Highlights the webview parameter retrieval tool, which bridges bot conversations and embedded web content. Only works when your page is loaded inside a Botstar modal webview—returns empty if accessed directly. Requires the onChatbotReady event to fire before parameters are available.

When Botstar fits a product-led growth support stack

A 6-person SaaS startup runs onboarding through a chatbot that escalates to live agents when users hit billing or integration questions. Botstar's livechat tools let you programmatically open the widget when a user clicks "Talk to support" in your app, update their profile mid-conversation (passing plan tier or account ID), and register callbacks to log handoff events back to your analytics. This works if your support volume is under 200 conversations a week and you already use Botstar's chatbot platform. If you're stitching together Intercom or Zendesk with a separate bot vendor, the integration overhead outweighs the benefit. The API key auth and 9-tool scope make this a clean fit for teams already committed to Botstar's ecosystem.

Botstar for high-intent visitor engagement at scale

A 12-person B2B marketing team runs paid campaigns to product landing pages and wants to capture leads before they bounce. Botstar's widget can be opened programmatically when a visitor scrolls past the fold or idles for 15 seconds, then update user details as they answer qualification questions in the chat. The onClose callback logs abandonment events to your CRM. This setup works if you're driving 500-plus visitors a day and need chat to feel native to your site, not bolted on. If your traffic is lower or you're already using HubSpot's chat, the integration lift isn't worth it. The real win is when you need the chatbot logic and the live handoff in one vendor, not two.

When Botstar misses the mark for high-touch CS workflows

A 20-person customer success team manages 80 enterprise accounts and wants to automate quarterly check-in outreach via chat. Botstar's livechat tools can open a widget and pass account metadata, but the 9-tool scope doesn't include proactive messaging triggers or CRM sync beyond manual updates. If your CS motion depends on Salesforce data or scheduled outbound nudges, you'll spend more time building workarounds than running check-ins. This MCP is a better fit for reactive support scenarios where the customer initiates the conversation. For proactive enterprise CS, look at integrations that hook directly into your CRM and support workflow automation, not just widget lifecycle events.