ChatBotKit (@ChatBotKit) header
ChatBotKit (@ChatBotKit) profile picture

ChatBotKit

@ChatBotKit

ChatBotKit helps you create conversational AI chatbots with your own data to communicate naturally with users on your website, Slack, Discord and WhatsApp.

chatbotkit.com
Joined December 2022
  • Tweets575
  • Following45
  • Followers259
195Media
Photo by ChatBotKit (@ChatBotKit)Photo by ChatBotKit (@ChatBotKit)Photo by ChatBotKit (@ChatBotKit)Photo by ChatBotKit (@ChatBotKit)Photo by ChatBotKit (@ChatBotKit)Photo by ChatBotKit (@ChatBotKit)Photo by ChatBotKit (@ChatBotKit)Photo by ChatBotKit (@ChatBotKit)Photo by ChatBotKit (@ChatBotKit)Photo by ChatBotKit (@ChatBotKit)
Show the screen. Share a snapshot in Slack, then open the desktop in your browser. Illustrative. Links expire. chatbotkit.com
Illustrative ChatBotKit Computer card. A stylised Slack message from Studio Bot shares a desktop snapshot with a terminal and an Open desktop button. A notice says the link is valid for 10 minutes and anyone with it can see and control the desktop during that time. Share the screen in Slack. Open the desktop in your browser.

ALT Illustrative ChatBotKit Computer card. A stylised Slack message from Studio Bot shares a desktop snapshot with a terminal and an Open desktop button. A notice says the link is valid for 10 minutes and anyone with it can see and control the desktop during that time. Share the screen in Slack. Open the desktop in your browser.

1
1
37
Cancel the run. Spare the task. Stop the active execution without deleting its setup. chatbotkit.com/docs/tasks
Card 1 of 3. ChatBotKit card headed Stop this run. Keep the task. An illustrative diagram shows a task marked Running with a progress bar labelled Active execution that ends at a stop marker, and a cursor on a Cancel Task button. Text reads Cancel Task stops the active execution. Every card shows an Illustrative label in the header, next to the card number, and again in the footer with chatbotkit.com/docs/tasks.

ALT Card 1 of 3. ChatBotKit card headed Stop this run. Keep the task. An illustrative diagram shows a task marked Running with a progress bar labelled Active execution that ends at a stop marker, and a cursor on a Cancel Task button. Text reads Cancel Task stops the active execution. Every card shows an Illustrative label in the header, next to the card number, and again in the footer with chatbotkit.com/docs/tasks.

Card 2 of 3. The same task is now marked Idle, and its bar reads Execution stopped. Its Name, Description and Schedule fields each have a tick. Text reads The task stays configured. Every card shows an Illustrative label in the header, next to the card number, and again in the footer with chatbotkit.com/docs/tasks.

ALT Card 2 of 3. The same task is now marked Idle, and its bar reads Execution stopped. Its Name, Description and Schedule fields each have a tick. Text reads The task stays configured. Every card shows an Illustrative label in the header, next to the card number, and again in the footer with chatbotkit.com/docs/tasks.

Card 3 of 3. The idle task has two paths, On its schedule and Triggered manually, both leading to Next run. Text reads It can run again on its schedule or be triggered manually later. Every card shows an Illustrative label in the header, next to the card number, and again in the footer with chatbotkit.com/docs/tasks.

ALT Card 3 of 3. The idle task has two paths, On its schedule and Triggered manually, both leading to Next run. Text reads It can run again on its schedule or be triggered manually later. Every card shows an Illustrative label in the header, next to the card number, and again in the footer with chatbotkit.com/docs/tasks.

1
16
Probably Dave won’t do. Give each issue an owner and a next step. chatbotkit.com
Card 1 of 3. Give the task a useful brief. Instruction asks for each issue, its named owner and stated next step. Missing owners or next steps must be marked NOT PROVIDED. Illustrative.

ALT Card 1 of 3. Give the task a useful brief. Instruction asks for each issue, its named owner and stated next step. Missing owners or next steps must be marked NOT PROVIDED. Illustrative.

Card 2 of 3. Supply the notes. Login error · Ana · reproduce with the customer’s browser version. Export delay · owner not stated · inspect the queue logs. Billing question · Ben · next step not stated. Illustrative.

ALT Card 2 of 3. Supply the notes. Login error · Ana · reproduce with the customer’s browser version. Export delay · owner not stated · inspect the queue logs. Billing question · Ben · next step not stated. Illustrative.

Card 3 of 3. Check the output. Table lists the three issues. Ana owns the login error and must reproduce it. Export delay has NOT PROVIDED for owner and inspect the queue logs for next step. Ben owns the billing question with next step NOT PROVIDED. All three issues included. Missing details remain visible. Illustrative.

ALT Card 3 of 3. Check the output. Table lists the three issues. Ana owns the login error and must reproduce it. Export delay has NOT PROVIDED for owner and inspect the queue logs for next step. Ben owns the billing question with next step NOT PROVIDED. All three issues included. Missing details remain visible. Illustrative.

11
Your API key called. It would rather stay out of the screenshot. Tokens and secrets now stay masked until you reveal them. chatbotkit.com
ChatBotKit card headed "Keep credentials hidden on screen." An illustrative panel shows two locked fields, "Token" and "Private key", filled only with mask dots; the private key spans four lines. Text below: "Tokens and secrets are masked in the Blueprint Designer and on settings pages until you reveal them. Multi-line keys too, like private keys." Footer: Illustrative, chatbotkit.com.

ALT ChatBotKit card headed "Keep credentials hidden on screen." An illustrative panel shows two locked fields, "Token" and "Private key", filled only with mask dots; the private key spans four lines. Text below: "Tokens and secrets are masked in the Blueprint Designer and on settings pages until you reveal them. Multi-line keys too, like private keys." Footer: Illustrative, chatbotkit.com.

8
Replying to @imsachinshah0
Give the human handoff a packing list: extracted field, source page, rule version and reason for review. “Low confidence” alone is homework.
1
1
8
Replying to @Born_TechK
Give prices their own seatbelt: assert the exact amount, currency and billing period against the source. “On topic” won’t pay for a missing zero.
1
1
9
Replying to @trycua
My vote for the next run: 30 minutes of browser work, with p95 step latency. Give the sprinter a marathon bib.
33
Replying to @cursor_ai
A useful design note: element + viewport + expected behaviour. “This button wraps at 360px” beats “make it pop” every time.
10
Replying to @trq212
Ship each customisation with a test for the behaviour you meant to keep. A clean merge can still delete your favourite trick.
4
Replying to @AvinashDalvi_ @ataiiam
Keep the fork thin: OpenDuet puts branding, bots and skills in one tenant folder. Patch ownership still needs a human name on it.
15
Replying to @LangChain
Move the parrot. Keep the rest of the jungle. Editable beats regenerate-and-pray.
1
83
Your app. Your UI. No need to reinvent the chat wheel. Swift + React Native SDKs: docs.cbk.ai/swift-sdk docs.cbk.ai/react-native-sdk
ChatBotKit SDKs. Bring AI chat into your app. Two abstract chat panels compare Swift, streaming chat for Apple apps, with React Native, headless hooks for your native UI. The React Native panel uses dashed outlines. A coloured edge marks each active response. Footer: Start with the SDK docs, cbk.ai.

ALT ChatBotKit SDKs. Bring AI chat into your app. Two abstract chat panels compare Swift, streaming chat for Apple apps, with React Native, headless hooks for your native UI. The React Native panel uses dashed outlines. A coloured edge marks each active response. Footer: Start with the SDK docs, cbk.ai.

1
1
72
Replying to @hwchase17
For review UX, would you prioritize the full trajectory or a diff from the last accepted run? Showing changed assumptions and proposed external actions could let reviewers focus on what needs a fresh decision.
4
Understand the setting. Keep building. In ChatBotKit’s Blueprint Designer, hover over or focus a field label for help. Click the label to show the explanation below the field. Field help is now live. chatbotkit.com
ChatBotKit | AI Agents for Support, Sales, and Operations

ChatBotKit | AI Agents for Support, Sales, and Operations

Build AI agents from ready-made solutions and let them work in the background - on schedules and triggers, connected to your tools, in every channel. ChatBotKit keeps them running, with security and...

chatbotkit.com
1
1
56
Replying to @liquid_richie @liquidai
Thanks, that separates generic tool calling from adaptation to a specific setup. For deployment, we would still check held-out schemas and multi-step recovery in the target harness. Is there a recommended fine-tuning example for that path?
1
1
24
Replying to @liquidai
Do the tool-use gains transfer between harnesses without retraining, or depend on matching the training harness and tool schemas? A cross-harness breakdown would help builders decide what to evaluate before deploying locally.
1
1
83
Replying to @poteto
When a mistake recurs, do you turn it into a regression test, a type constraint or a written agent instruction? The first two make the lesson executable; curious how you choose which layer should own it.
15
Replying to @LangChain
A reaction is a useful receipt. Do you distinguish queued, running and finished? People need to know whether to wait or intervene.
7
Replying to @cursor_ai
Do your evals cover interrupted runs and repeated tool calls, or mainly the final answer? Those are often where a promising demo turns into an unreliable workflow.
6
Ask your bot to work in the background. Get an update where you started. Turn notifications on for a task your bot creates in a supported conversation. It replies with a text update when the run ends. Illustrative Slack example. docs.cbk.ai/task-notificatio…
1
1
55
Load more