Phase 1–3
AI Studio, rebuilt
A faster, clearer workspace for building, testing, guarding, and publishing AI agents.
AI Studio
We rebuilt AI Studio from the studs up.
AI Studio was rebuilt across three phases to make agents easier to build, test, guard, and improve. This is where teams shape the agent: its knowledge, behavior, tools, follow-ups, feedback loops, and escalation rules.
- Knowledge
- Guardrails
- Tools
- Follow-up
- CSAT
- Priority
- Escalation
- Publish
Follow-ups built in
When a customer goes quiet, the agent can re-engage instead of letting revenue leak out of the thread.
CSAT after every AI chat
Measure where the agent earns trust — and where the experience still needs work.
Priority from AI tags
AI-generated intent becomes triage, helping urgent conversations rise before the queue buries them.
Surfaces
WhatsApp’s still home — not the only room.
WhatsApp remains the anchor for conversational commerce. But customers do not only ask questions in one place. This release pushes bitbybit toward one agent layer across web chat, full-page chat, connected social surfaces, and commerce touchpoints.
One
AI Agent
AI Agent
WhatsApp 
Instagram 
Facebook 
TikTok Web widget
Full-page chat
Storefront
One agent layer across the surfaces you connect — WhatsApp stays the anchor; supported social and chat surfaces join where enabled.
New bitChat web widget
Bring the agent and live team into the storefront, not just the WhatsApp thread.
Full-page chat surface
A standalone chat experience you can link from campaigns, bios, ads, and support flows.
Connected social surfaces
Keep moving toward one customer conversation layer across WhatsApp and supported social/chat channels such as Instagram, Facebook, and TikTok where enabled.
WhatsApp templates upgraded
Headers and footers give broadcasts more structure, branding, and campaign flexibility.
Data & automation
Every conversation leaves data you can act on.
The next jump in AI quality is not only the model. It is the context around the customer. AI tags, customer fields, birthday capture, and cleaner records make bitbybit automations more targeted, more timely, and less manual.
Customer record
BirthdayIntentPriorityLast orderChannelLoyalty statusAI tagSegment Automation output
- Follow-up
- Campaign
- Routing
- Priority
- Loyalty reward
- Meta CAPI event
Context turns conversations into triggers — illustrative fields, not real customer data.
The unlock
AI tags as triggers
Use AI-generated intent and classification to prioritize, segment, route, and trigger the next step.
Birthdays, captured
The Data Collection skill now captures birthdays, turning conversations into useful retention data.
Cleaner customer records
Customer context is easier to scan, act on, and reuse across support, sales, and retention.
Branching automations
Custom conditions let flows follow the customer, not a fixed script.
Meta CAPI signal improved
Cleaner conversion signal helps ad reporting better reflect what campaigns actually drove.
Open API · developers
Now there’s an API to build on.
For teams that want to build deeper workflows, bitbybit’s Open API exposes more of the commerce and customer system. Developers can connect bitbybit to internal tools, custom storefronts, reporting stacks, fulfillment flows, and loyalty experiences.
- Customers
- Orders
- Products
- Messaging
- Loyalty
- Webhooks
Webhook events
{
"event": "resource.updated",
"delivered": true
} API Custom storefrontERP / internal toolsBI / reportingFulfillmentCRM
Customer API
Create, read, update, and manage customer records programmatically.
Orders API
Connect order data and fulfillment workflows to the systems your team already uses.
Products API
Sync catalog data between bitbybit and external commerce systems.
Messaging API
Send and track WhatsApp messages through API-based workflows.
Loyalty API
Work with loyalty settings, points, rewards, redemptions, and customer reward activity.
Webhooks
Receive real-time event notifications so external systems can react when something changes.
Commerce infrastructure
Sell, charge, and ship without leaving the thread.
Agents perform better when they can rely on real commerce infrastructure: payments, vouchers, locations, order tags, analytics, courier booking, same-day delivery, and cleaner address capture.
Agent
Cart
Payment 
Order
Courier 
Tracking
Loyalty
Loyalty loops the buyer back to the agent
DOKU payments
Accept payments inside Commerce with DOKU — checkout on rails the brand controls.
Discount vouchers
Create and redeem voucher codes for campaigns, drops, and retention flows.
Multi-store locations
Operate multiple store locations from one account without fragmenting the business.
Order tags + live analytics
Organize orders your way and watch what is selling as it happens.
KiriminAja, end to end
Quote, book, and track KiriminAja shipments from inside a Commerce order.
RideBlitz + GoSend
Support same-day and on-demand delivery flows from the order context.
Map-pinpoint addresses
Customers drop a pin instead of typing an address, reducing delivery ambiguity and failed attempts.
The app
One workspace, not seven tabs.
A refreshed home screen, a unified design system, cleaner navigation, in-app announcements, and tidier customer records all point in the same direction: fewer disconnected tools, more operating layer.
- Customer record
- Inbox
- Automation
- Commerce
- Loyalty
- API
- Home
One agent. One record. One commerce system.
Refreshed
New home & design system
A refreshed home screen and a more consistent design language across the product.
Cleaner navigation
A tidier app structure that makes conversations, automations, commerce, and customer records easier to move between.
In-app announcements
Product updates now surface inside the app, so teams can see what shipped without leaving their workflow.
Tidier customer record
Customer context is easier to scan, act on, and reuse across support, sales, and retention.
What’s next
The next release is about the agent doing more.
Summer 2026 moves bitbybit closer to one agent layer across every connected customer surface. Next, the work is deeper context, better tools, stronger automations, and more programmable commerce infrastructure — so brands can sell, support, fulfill, and retain from the system they own.