I’m using Ideta’s Web chat widget and I’m running into a limitation: the message input seems to have a strict character limit. When I try to paste a longer block of text (e.g., a bigger set of parameters / structured data that the bot should work with), the message can’t be sent (the send button becomes inactive or the input is blocked).
This makes the bot much harder to use in real workflows, because splitting the input into many smaller messages is inconvenient and increases the risk of missing details.
Questions:
Is there a documented character limit for the message input in the Web widget?
Can this limit be increased (globally or per bot / per channel), e.g. via Publication / Design settings?
If it can’t be increased, what is the recommended approach for users who need to send longer inputs (e.g., best practices, attachments, API bubble, etc.)?
Channel: web chat widget embedded inside our internal, authenticated platform (agents-only). It’s not public-facing and requires login, so access is limited to our team.
Use case: we’re building an assistant for our real estate agents to generate high-quality property listing descriptions for multiple portals (based on our strict in-house standards). To do that, the agent needs to paste a fairly detailed property brief: key parameters, room-by-room details, condition/finish, building info, utilities, legal/ownership notes, parking/storage, neighborhood highlights, target audience, etc.
With the current character limit, agents often have to split the same input into 5–6 separate messages, which is frustrating and leads to worse results (context gets fragmented, more back-and-forth, higher chance of missing details).
Is there any way to:
increase the character limit for private/internal deployments (even if it’s a paid option),
allow longer inputs via an “attachment / form / knowledge block” style input,
or 3) whitelist our workspace / domain for a higher limit?
Happy to share more specifics about our implementation if needed.
Thanks!