Hello Botpress Support, Please investigate a conversation-specific handover issue in our PracticeFlow AI bot. My personal WhatsApp number, receives no AI replies, while my husband and other patients receive replies through the same business WhatsApp number. Affected conversation:

conv_01M2BBA3N17ZJSB3EDGETXD8CP

At 14:56 SAST on 24 September 2026, I sent “Hi.” Botpress created

message_created

event

evt_01M39QV0R973S3E8H7V879TTES

at 12:56:53 UTC. Inspect → Events shows processed and

failureReason: null

. Inspect → Logs records the incoming WhatsApp “Hi,” but shows no subsequent AI reply. The conversation remains associated with

system-escalation

in Studio Monitor. The earlier

deskTicketClosed

event

evt_01M39QMTVS0X2TT3B6AGR4163P

and

continueWorkflow

event

evt_01M39QMX8PNDKNYQ5EYX8XBDWB

were both marked processed. Botpress sent a message saying it would continue assisting, but AI responses did not resume. Could you inspect the internal handover and conversation state for this ID, determine whether the 14:56 event triggered AI execution or was suppressed by escalation state, and identify the cause? Please advise whether you can safely restore AI control for this conversation only, without affecting other patients, and let us know what you find before applying a change. Please preserve the bot, contact, and conversation history. Do not change global escalation rules, disconnect WhatsApp, or modify booking or Cal.com integrations. Thank you, Zama Thusi

I manage the corporate email for a former employee, but Botpress login returns “identity is disabled” (401). Password recovery returns to the login page. We need to recover authorized access to our workspace and bot. Error ID: 010235e4-86d5-4686-a956-8f08da6d049e. Bot ID: 58695bfe-642b-41e0-8e80-9710e7d0a85c. Could a Botpress team member provide a private channel for ownership verification?

Reproduje el problema en un agente de diagnóstico completamente nuevo. La herramienta HTTP se creó y configuró, y el playbook requiere explícitamente su llamada inmediata. Sin embargo, Preview solo lee el playbook y nunca genera un evento "HTTP ejecutado". Informa que la herramienta HTTP configurada no está disponible para su ejecución en la sesión actual. Esto confirma que el problema no se debe a las instrucciones originales del agente, la base de conocimientos ni el punto final de WordPress. La herramienta HTTP no se expone al entorno de ejecución, ni siquiera en un agente limpio. https://cdn.discordapp.com/attachments/1552451157799084052/1552451157992153118/e5367f99-f7f7-4792-b194-b13c98a8de6b.png?ex=6ab5a84f&is=6ab456cf&hm=355caab163e27fa8748bdf997feab6ea486c43457bff47281263c50e3a7baf39&

I reproduced the issue in a completely fresh Preview conversation. Botpress Runtime Inspector shows that both HTTP tools are registered in `customTools`: * Original:

Get mattress recommendations

— ID

http_1t9c6

* Test duplicate:

Get mattress recommendations V42

The Product Recommendation Playbook explicitly requires the V42 tool to be called once with the complete customer profile. However, the execution trace only shows: *

Read Product Recommendation

* Knowledge/website searches There is no HTTP invocation attempt or HTTP error. The agent simply ignores the registered tool and falls back to Knowledge search. The endpoint works correctly when tested independently and returns valid JSON with products, size variants, technical attributes, exact prices and stock. We previously tested the original tool and got the same failure. It had worked before, with the historical trace showing

Ran Http 1t9c6

. This does not appear to be an endpoint, registration, tool-name or stale-conversation issue. It appears to be a Botpress runtime/tool-selection problem occurring before HTTP execution. Where can I inspect the tool-selection/decision logs in the current Agent Studio? Is this a known issue, and is there a supported way to force the Playbook to invoke the HTTP tool before searching Knowledge? Screenshots attached. https://cdn.discordapp.com/attachments/1552423979497689179/1552423979703074947/10c85c83-baa8-43b5-bf6a-b0e01f1a2223.png?ex=6ab58eff&is=6ab43d7f&hm=308326ea0bee989d121e7e5840d2e704efae662a05572ed25dc9048ae85a66af& https://cdn.discordapp.com/attachments/1552423979497689179/1552423980890067084/f1c844ad-a830-4701-b83c-6acd6a17d32b.png?ex=6ab58eff&is=6ab43d7f&hm=a5290b4567596f2ac4370e134598db022393dbd4fa9f04de5141ccc26939bf56& https://cdn.discordapp.com/attachments/1552423979497689179/1552423981720543292/7999239e-c939-430d-ab7a-8ea2c3b5c8a2.png?ex=6ab58eff&is=6ab43d7f&hm=7b1737e09df67debdeaf31c832a8c23967d7a32a43159f85472d9d65d3d770cc& https://cdn.discordapp.com/attachments/1552423979497689179/1552423982274322534/1d8ad60c-c84e-4723-ae65-4e912c476657.png?ex=6ab58f00&is=6ab43d80&hm=ef836c4c2b3c9690d6c18839b54194039811a490f5dd645333cfa541387e034a& https://cdn.discordapp.com/attachments/1552423979497689179/1552423982941212773/eea0957f-81a1-415a-9566-dd0d93bfe489.png?ex=6ab58f00&is=6ab43d80&hm=79fdab66cc6d9c49bb7d604b274536ac9d091adb48bcd7c9f5a4dc1813ec4c52& https://cdn.discordapp.com/attachments/1552423979497689179/1552423983604039731/1f00395e-f8e7-442b-8e2c-000728c8dec0.png?ex=6ab58f00&is=6ab43d80&hm=71a212c2f2157d3a5e375beed85c3b4d6216c9aad62f44bfcf57fb0677a0fca2&

My production agent suddenly stopped invoking HTTP tools that previously worked. The tools remain visible and correctly configured in Agent Studio, but the runtime does not expose or execute them. Expected trace: Read Product Recommendation Ran Http Get mattress recommendations Actual trace: Read Product Recommendation Searched for... The agent explicitly says it has no access to the HTTP tool. Endpoint: https://tucolchon.com.ar/wp-json/tu-colchon/v1/recommend Method: GET Required inputs: size weight_1 weight_2 position_1 position_2 comfort The endpoint is online and returns valid JSON. PHP, WooCommerce and the API were not changed. I also created a duplicate HTTP tool with a new name and internal ID, but it is not invoked in Preview. Please check the agent/tool registry and whether HTTP tools are being exposed to the runtime. Workspace/Agent URL: [PEGAR AQUÍ LA URL DEL AGENTE] This is affecting a production sales agent. https://cdn.discordapp.com/attachments/1552094356343890130/1552094356654260294/05_ENDPOINT_VALIDO_36_FILAS.png?ex=6ab45c03&is=6ab30a83&hm=aa1c1314743a53f92280b6b648e05d4f6718d108c445b067ea39cea69b165820& https://cdn.discordapp.com/attachments/1552094356343890130/1552094358470271006/04_AGENTE_DICE_SIN_ACCESO_A_TOOL.png?ex=6ab45c03&is=6ab30a83&hm=632b4de07a1db34b15c022a5e4c3e314e9adee5535b1fd99be08098763dd2115& https://cdn.discordapp.com/attachments/1552094356343890130/1552094359548198963/03_RUNTIME_IGNORA_HTTP_Y_BUSCA_WEB.png?ex=6ab45c03&is=6ab30a83&hm=4937a2ed0319e7128fee28d477baa2884c7331260712dc5ffe71a9f3f8ab8d4d& https://cdn.discordapp.com/attachments/1552094356343890130/1552094360265560155/02_INPUTS_REQUIRED_TIMEOUT.png?ex=6ab45c04&is=6ab30a84&hm=d5b4504841be575801af17003ed36ce029adf70cd52cc511160bd818f8ac40b5& https://cdn.discordapp.com/attachments/1552094356343890130/1552094361141903460/0ab2d056-760c-475e-8dcb-3067876b31ef.png?ex=6ab45c04&is=6ab30a84&hm=6f6de8245f845bada915fce21b893007bba8c21790c47292fc2cf3c3a455cce4&

Hi Botpress team, I’m trying to connect my existing WhatsApp Business App number to Botpress using coexistence, while keeping the WhatsApp Business app and chat history. During Meta Embedded Signup, the correct number (+54 9 3571 62-4485) appears under the WABA “tucolchon.com.ar”, but Meta marks it as “No cumple los requisitos” (“Doesn’t meet the requirements”), so I cannot continue. What I have already verified: * The number has been actively used in the WhatsApp Business App for several years. * The WhatsApp Business App is updated. * The WABA account is approved. * The phone number is connected and has high quality status. * My Meta user has full access to the WhatsApp account. * I am using the official Botpress OAuth connection. Technical information: * Meta Business ID: 2318360515059205 * WABA ID: 437270652803638 * Botpress Bot ID: a4e1925f-07c7-411d-b0bb-5625cf055a0f * Workspace ID: workspace_01M1PDBVP8SDJPDMQCTJEE0C5K * OAuth Session ID: 01a0cab9-7095-7520-8043-e693422cb069 Could you please check the OAuth/Meta logs and help escalate this coexistence eligibility issue to Meta? I do not want to migrate, delete, deregister, or replace the existing number because I need to preserve the WhatsApp Business App and its chat history. https://cdn.discordapp.com/attachments/1552065024879624212/1552065025202724864/0ab2d056-760c-475e-8dcb-3067876b31ef.png?ex=6ab440b1&is=6ab2ef31&hm=001e159a26c2559742284d0de1a5d45476fa85987aa443a5fc2c0e153dde7c87&

"Hello, I am building an agent using Botpress Viber, on the free Pay as you go plan. My use case requires the agent to read text content from PDFs and images attached by users during the conversation, for example payslips to analyze. I understand this feature is called Vision Agent and is configured through the Autonomous Node in Botpress Studio, but I cannot find a way to access the Studio view from my agent created in Viber. Could you tell me how to enable this feature, and whether it is available on the free plan or requires an upgrade?"

Hi Botpress team, I built an agent using Viber (Vibe) and I'm stuck in a publishing loop I can't resolve on my own. Details: Workspace: Raising's workspace Agent: Raising with Eyes Bot ID: cef95647-a1df-46c2-ba58-61440910e563 Issue: My agent is built as an ADK/Vibe draft. I enabled the Webchat channel successfully (confirmed — the Channels page shows "Disable" instead of "Enable" for Webchat), but the "Publish Changes" button in Deploy Settings remains disabled/unresponsive. When I follow the suggested "Open Studio" / "Edit in studio" link from the warning banner, Studio rejects the bot with this message: "Can't edit in Studio — This bot was built using the ADK runtime, which is not compatible with Studio." So I'm stuck: Deploy Settings says I must publish from Studio, but Studio refuses to open the bot at all. I asked Vibe directly about this, and it confirmed this is a Vibe deployment-state issue rather than a Webchat configuration problem, and recommended I contact support rather than try to work around it (not recreating the agent in Studio or disabling Webchat, since that would not resolve the runtime mismatch). Could you please help me publish this agent, or let me know what's causing the mismatch? Thank you! https://cdn.discordapp.com/attachments/1551475632448344084/1551477209804443668/WhatsApp_Image_2026-09-21_at_09.13.56.jpeg?ex=6ab21d3f&is=6ab0cbbf&hm=e79a747394c65624b7f535ef6bf6c813e435181cf0ba6075e6e42edc7b3eee52& https://cdn.discordapp.com/attachments/1551475632448344084/1551477212543189092/WhatsApp_Image_2026-09-21_at_09.13.52.jpeg?ex=6ab21d40&is=6ab0cbc0&hm=8aeca9a536a00ef47c70006b4dc6a4535a090dd3c47645a2114eb4469193cac1&

Hi, I need help with the WhatsApp integration. Objective: I want customers to contact my published Botpress agent through WhatsApp. Issue: The WhatsApp channel is connected, enabled, and published in Botpress. Meta WhatsApp Manager also shows the phone number as Connected with High quality. However, external users searching for the number see “Invite to WhatsApp” or “This person is no longer on WhatsApp”, so they cannot send a message. What I have already tried: * Removed the number from the WhatsApp mobile app. * Connected it through Botpress OAuth. * Enabled and published the WhatsApp channel. * Confirmed that Meta shows the number as Connected. Could you please verify whether the phone number was successfully registered/provisioned by the Botpress integration and explain how to re-register it safely without deleting the WABA or breaking the OAuth connection? I can provide the phone number, WABA ID, bot ID, and screenshots if required.

I am having issues integrating google chat for my bot I keep getting a error message

Hi, I’m having a reproducible issue with the new Botpress Desk human handoff. The flow works like this: bot → human agent in Desk → human replies → ticket is closed. After closing the ticket, Botpress shows: “SUSHI closed the conversation. I will continue assisting you.” However, sometimes the bot does not resume responding after that. New user messages are delivered, but the bot stays silent. I reproduced the issue in both Webchat and WhatsApp Sandbox, so it does not seem to be WhatsApp-specific. Starting a new conversation/session makes the bot work again. Is this a known issue with the new Desk handoff? What is the correct way to return control to the bot after closing a ticket?

Summary: Agent "Waayan Housewares Trading" connected to WhatsApp via Meta Cloud API. Incoming messages initially created tickets, but every bot reply failed with: "I'm sorry, but I'm temporarily unable to send messages because the WhatsApp connection has expired." After a full disconnect/reconnect, incoming messages now don't create tickets at all. Confirmed working (Meta side): - Access Token: valid, non-expiring, correct scopes (

whatsapp_business_management

,

whatsapp_business_messaging

) — confirmed via Meta's Token Debugger - Phone number: Connected, Quality Rating High - Phone Number ID: 1227959283744147, WABA ID: 932986993202522 - Webhook Callback URL in Meta matches Botpress's current URL exactly -

messages

field subscribed Botpress side: WhatsApp channel shows Connected, appears under agent's Tools list. Current issue: Messages deliver fine (double checkmark on WhatsApp) but never reach Botpress as tickets since reconnect — "no WhatsApp conversation logs available." Ask: Is there a known issue with stale webhook bindings after WhatsApp disconnect/reconnect? Everything on Meta's side is confirmed valid. https://cdn.discordapp.com/attachments/1549731359881170954/1549731360183287888/connected.png?ex=6aabc34c&is=6aaa71cc&hm=900a168feb804fdbfa103982cc50ce510181d3e24bbda9b4340157e649a94137& https://cdn.discordapp.com/attachments/1549731359881170954/1549731360565104720/Call_Back_URL.png?ex=6aabc34c&is=6aaa71cc&hm=33d537838f9acff96984410c5a6c90aa68331d9cfa988cc284da32f0098da430& https://cdn.discordapp.com/attachments/1549731359881170954/1549731360963432619/Webhook.png?ex=6aabc34d&is=6aaa71cd&hm=0e681deee56671d13911be21bf21f8e2288089d7b2af50173993b892b993792f&

Hi Botpress team, I have an invoice in my Botpress workspace that is currently showing as VOID, and I would like to pay the amount now. The payment became void because the invoice/charge was unexpected. I did not receive any prior notice or notification that this amount was going to be charged. The invoice was issued and the payment was attempted directly on my credit card without advance notice, so I was not prepared for the charge at that time. I have now arranged the payment and would like to settle the invoice as soon as possible. I have also sent an email to the Billing team regarding this issue, but I have not received any reply yet. That is why I am reaching out here on Discord for assistance. Could you please advise how I can retry the payment, or reissue/reopen the voided invoice so I can pay it? Also, for future invoices, I would appreciate receiving advance notice before a charge is attempted on my credit card, especially for unexpected usage-related charges. I can provide my Workspace ID, invoice number, and screenshot privately if needed. Thank you for your assistance.

Hello Botpress team, I am experiencing an issue with file uploads in my Botpress Webchat. When I try to upload an image using the attachment button, the Webchat displays an “upload error” message. The same issue also occurs when I paste an image directly into the chat. After the error appears, the conversation becomes completely blocked. I cannot continue interacting with the Webchat until I reload or refresh the page. I tested the issue in two different browsers, and it occurs in both of them. I also tested it with a very small GIF file of approximately 3 KB, so the problem does not appear to be related to file size. Steps to reproduce: Open the published Webchat. Click the attachment button and select an image, or paste an image directly into the chat. Wait for the upload to complete. The Webchat displays “upload error”. Try to send another message. The conversation remains blocked until the page is reloaded. Expected behavior: The image should upload successfully, or the Webchat should allow the user to cancel the failed upload and continue the conversation. Actual behavior: The upload fails and the conversation becomes unusable until the page is refreshed. Could you please investigate this issue and let me know whether there is a known fix or any recommended workaround? I can provide screenshots, the Webchat URL, the file format, browser versions, and the date and time of the failed tests if needed. Thank you. Edge, Chrome https://cdn.discordapp.com/attachments/1549597031327342643/1549597031503241296/image.png?ex=6aab4632&is=6aa9f4b2&hm=90da97f8239b1f5edfabcb4dc2f05af0fcbb9ca0c015f6981b9e56ecdbbb2896&

My account was accidentally deleted, and when I try to access it, I receive the following error message: Error: Identity is disabled Error ID: 942b9539-4971-4f68-a88a-eca57cd338d9 Code: 401 Could you please help me restore my account and regain access? Thank you!

Hello i have trouble when trying publish my bot in testing mode, the published bot didn't answer like my workflow, please check this https://cdn.discordapp.com/attachments/1549033374382039141/1549033374986010654/Screenshot_20260914_191839_Instagram.jpg?ex=6aa93940&is=6aa7e7c0&hm=0150d91c05c3ded7a23ea8525fbe00f1af32451883468e6cbd3a497d480b703a& https://cdn.discordapp.com/attachments/1549033374382039141/1549033375535333386/Screenshot_from_2026-09-14_19-18-25.png?ex=6aa93940&is=6aa7e7c0&hm=f29e514c2cb384a2095b15e6380a19b8190af9772e15173150364d2f1a16ce88&

I'm currently building a bot with Bo press and it's working awesome, one of the things that I would like to happen is to have it full screen on my website which is WordPress and I can easily manipulate code and I could even have it on the website as a HTML file instead of a WordPress file but when I'm not able to accomplish is making it look like the bot press preview which you can find when you go to publish your bot, there's a preview button which opens the bottom up in full screen and has a taskbar or menu bar on the left side. It looks like a standard chat interface that's full screen. I've gone through all of the full screen in bed tutorials but nothing's giving me the same look, and then I tried to map an a record in my DNS to the Preview, but that doesn't work either any direction or guidance would be very helpful here and I thank you in advance for that

My agent somehow got set to Embedded, and I cannot get it to go back to Toggle. If I change it on this page, on refreshing the page it goes back to Embedded. Some technical details: When changing from Embedded to Toggle, when inspecting the payload that is sent, I see

updates: {}

, while any other change has some stuff in

updates

. For example, if I click on "Use bot avatar", it sends a request with

"updates":{"fabImage":"https://files.bpcontent.cloud..."}

https://cdn.discordapp.com/attachments/1547942752870862919/1547942753550336080/image.png?ex=6aa54187&is=6aa3f007&hm=0e3a46c35bb997e12edff7d6f32f2c82bd5775494a3674f5c2c7a400bf3c0992&

Is it possible to use the corner floating toggle in some pages and the embed on other pages? From my testing it seems like you can only have one or the other. I would like to have the corner mode in most of my pages but a couple of specific pages with an embed instead.

Since Sept 2 we can't publish our production bot. Studio shows: Failed to publish bot: quota exceeded Workspace is on the community plan. bot_count is 2/1 and workspace_member_count is 2/1. What we see via the API: publishing DOES write a new deployments/*.json artifact every time, with the correct content (8 written today). But the bot's deployedAt is frozen at 2026-09-02 12:39:41 UTC and never advances, and the runtime keeps serving the definition from that date — confirmed by reading the exact context sent to the model in improvements/iterations/. The odd part: we published successfully many times with these exact same quota values (2 bots, limit 1) right up to Sept 2 at 12:39 UTC. Nothing changed on our side — no new bot, no new member. It just stopped working. That looks more like an enforcement change or a bug than a limit we just hit. Questions: (1) Which quota actually blocks the publish — bot_count or workspace_member_count? (2) Did enforcement of this change around Sept 2? (3) Any chance of a temporary grace period? We have a public open-day event on Sept 18 and the fixes are already written and waiting. (4) Is there a supported way to deactivate or archive a second bot without deleting it? updateBot exposes a

blocked

boolean but it is undocumented — would that free bot_count, and is it reversible? (5) Can a bot be moved to another workspace? Happy to share workspace and bot IDs privately. Thanks!

The bot does not reply to the user’s first new question after the ticket is closed. In the attached example, the user selected “Positive” and then asked, “I would like to know what programmes do you offer?”, but the bot remained idle. the bot will only reply after the user send a second msg https://cdn.discordapp.com/attachments/1546463462153265153/1546463462400598057/image.png?ex=6a9fdfd5&is=6a9e8e55&hm=20cf13e53cf3cb841c9b44ad08a30362965cf36ef9cb0ff8ced9f55b6c648237&

I'm seeing the Agent Assigned Timeout setting on the hitl plugin (v2.0.2) not fire as expected. Setup: Plugin: hitl v2.0.2, installed alongside desk-hitl for Botpress Desk escalation Config: Agent Assigned Timeout = 150 seconds, Agent Assigned Timeout Message set to custom text, Continue Flow on Session End? = ON, Use Human Agent Info = ON Steps to reproduce: - Trigger escalation via the Escalate To Desk tool from an AutonomousNode (user asks for a human) - Bot confirms transfer, ticket is created in Desk - Do not assign/reply to the ticket in Desk - Wait past the configured timeout (tested at 150s+, waited up to ~200s) **Expected: **The Agent Assigned Timeout Message should be delivered to the user automatically once the timeout elapses, and control should return to the bot flow (per Continue Flow on Session End). Actual: No message is ever delivered, whether waiting passively with the webchat tab open, or sending a follow-up message from the user after the timeout window has passed. Already ruled out: - Confirmed the config is saved correctly (checked via Integration Hub → Installed Integrations → hitl → Configuration) - Tested with the bot's "Always Alive" setting both disabled and enabled.. same result in both cases, so it's not a cold-start/sleep issue - Confirmed escalation itself works correctly (ticket created, transfer message delivered, Desk integration functioning) Bot ID: 99d5f775-83b6-40f1-8774-10eb33062a25 Please help! https://cdn.discordapp.com/attachments/1546420854982840410/1546421182180368394/image.png?ex=6a9fb874&is=6a9e66f4&hm=eb93abd3fa95903b2f40c87b1b0d929def27a3a45cbf08807a19eaaac5711d5a&

I tried to log in today to check conversations on my running bots and wasnt able to acces my old workspaces . a legend : Not available on Viber - requieres the latest pricing is blocking me I was working on my bots yetserday late night and suddenly today , I am locked out from all workspaces and running bots and i need toc heck several things urgently . Please advise ASAP https://cdn.discordapp.com/attachments/1544728929594507334/1544728930152484924/image.png?ex=6a99906c&is=6a983eec&hm=50de566767b244e5ddb2b0d37437db02c9e99aeba39ff2f341a348ad8f1a927f&

I need a strict time-based WhatsApp workflow using the Asia/Dubai timezone. The AI must reply only from 11:00 PM to 10:00 AM. From 10:00 AM to 11:00 PM, it must send no automated replies so our human team can respond. Instructions and escalation rules did not enforce this schedule. How can I configure this automatically in Botpress Vibe?

Hi, I'm trying to connect Botpress Desk to our existing WhatsApp number (already connected to Botpress Studio via the Cloud API), but I'm running into an issue. Setup: - We have a 'New Agent' bot in Studio, with the WhatsApp integration (number +90 543 629 42 63) connected via OAuth and working fine. - When we use the 'Escalate To Desk' card, we get an error. The full error text from Studio's Issues panel is: "This bot is not connected to Botpress Desk. Enable it on the Deflecting Bots page in Botpress Desk, then republish." - In Botpress Desk (desk.botpress.cloud), we tried connecting via Settings > Channels > WhatsApp > Connect. - In Meta's embedded signup pop-up, we tried "Connect with your existing WhatsApp Business app" and entered +90 543 629 42 63, but got "Number not found - not associated with a WhatsApp Business app" (the number isn't on the consumer app, it's already registered via the Cloud API). - "Start with a WhatsApp API account" only offers two options: the same "existing app" flow (same error) or "add a new number" (haven't used this, don't want to risk our real number). We repeated both attempts, same result each time. - Our business verification (SonarHouse) was completed on August 29, 2026. We waited a couple of days in case Advanced Access hadn't propagated yet, tried again — same result. - In one earlier attempt, the number that ended up connected to Desk by mistake was +1 555-399-6811 — looks like a Meta test number, not our real one. - Checked Meta Business Manager: the "Botpress" partner (Code: 416465769304058) already has "Full access" to our WABA (SonarHouse Electronic Music School, code: 158252431546592), so permissions don't seem to be the issue. Question: How can we connect an existing WhatsApp number — already linked to Studio via the Cloud API — to Botpress Desk, without risking our real number? Is there an alternative, like manually entering a WABA ID / access token?

How do you handle muting the bot during a human handoff? The issue is that after the bot flow ends and an agent takes over, any new message from the user triggers the bot to restart its flow from the beginning, disrupting the live chat.

Hola, tengo dos canales de mensajería configurados en mi agente "Luxuren" (Viber) que no funcionan: 1. Twilio: conectado correctamente (Account SID/Token guardados, "Connected"), webhook configurada en ambos lados. Al escribir por WhatsApp Sandbox, Botpress recibe el mensaje y lo procesa (aparece en Conversations), pero nunca llega la respuesta. En el Debugger de Twilio aparece el error 12300 - Invalid Content-Type: la respuesta de la webhook de Botpress (https://webhook.botpress.cloud/...) viene como application/json, y Twilio la rechaza porque espera TwiML. 2. WhatsApp (Meta, vía OAuth embedded signup con coexistencia activada): la conexión muestra "Connected" en Channels, y los mensajes SÍ llegan a mi WhatsApp Business App (coexistencia funcionando), pero NO aparecen en absoluto en "Conversations" del agente — parece que el webhook de Meta a Botpress no está entregando el mensaje. ¿Podéis revisar ambas integraciones?

Hey everyone I made some CSS changes a few weeks back. Last week, I wanted to make more, but kept running into an issue. I'd add custom css in Appearance, and click Publish Changes. Everything seemed fine until I'd reload, and all of those changes were gone. After a number of hours poking around, somehow those CSS changes stuck, but the current published styles are incorrect. Like, very incorrect (the text and speech bubbles are the same color, which means its unusable) I've been trying to update changes again, but running into the same issue, where changes are wiped out when I reload after pressing "Publish Changes". Attached is a video showing the issue. Any feedback is appreciated! https://cdn.discordapp.com/attachments/1542158535373234246/1542158536245780510/botpress_css_issue.mp4?ex=6a90368e&is=6a8ee50e&hm=baa8cb8ac9253b10a4b10480550f3d0ebcac7fde62928d423b8d946ed91bb0d0& https://cdn.discordapp.com/attachments/1542158535373234246/1542158536992096362/Screenshot_2026-08-26_at_9.01.15_AM.png?ex=6a90368f&is=6a8ee50f&hm=3370de186aebf48fb4153f26b92b28bd1b88af69421a563bc1e9d05fe58186b1&

Hey everyone! New here .. I'm building a knowledge-based chatbot SaaS (FastAPI backend, Groq for inference) and looking into multi-tenant architecture patterns. Was checking out Botpress as a reference for how you all handle KB integration + tenant isolation. Is this an okay place to ask a few architecture questions, or is there a better channel for that?

I'm currently using the Free plan. I saw this warning: "You've used 95% of your AI spend. Upgrade to avoid hitting your limit." My Conversations count is still below the 100-conversation limit, but my AI spend is already close to $10. I asked the Botpress AI support bot about this, and it said that I don't need to worry about the AI spend limit as long as I stay within the 100 Conversations limit. However, my Workspace is showing a red warning about the AI spend, so I'm not sure which limit actually matters. Does anyone know if the Free plan can still be used after the AI spend goes over the limit, as long as the Conversations count is still below 100? Thank you for your help. https://cdn.discordapp.com/attachments/1541646400817991760/1541646401077772399/20260825.jpg?ex=6a8e5998&is=6a8d0818&hm=dff474bdc230f61e2a0facd96e445b479da663e1101c8c0a16a8380aaebde365&