Can an internal chatbot be limited so it doesn't reveal data outside a defined filter, like active deals only?

Yes. In Jestor, the chatbot agent can be configured with filters on its reference table, so it only sees and answers based on the records that pass that filter — for example, active deals only, ignoring the ones already closed-won or closed-lost.

The risk of an agent with no defined scope

Companies that want to use AI agents on WhatsApp or on internal channels usually have one core concern: the agent might end up exposing sensitive or outdated information, like negotiations that have already closed.

Without scope control, the chatbot becomes an unreliable source of information, since it answers based on everything in the table, without distinguishing what's still relevant.

How to set up the chatbot's filter

Create a new chatbot-type agent in builder mode.
Choose the reference table, if the agent is based on internal data.
Apply the filter you want, like excluding "won" and "lost" phases.
Adjust the prompt to guide the agent's tone and scope.
Test by asking something that should be outside the filter, to confirm the agent doesn't answer it.

Agent setting	What it controls
Filter on the source table	Limits which records the agent sees and uses in its answers
Based on external documents	The agent answers based on attached policies, without depending on a table
Custom prompt	Defines the agent's role and tone (e.g., "sales director")
Logo and background color	Visual customization of the chatbot widget

Why choose Jestor?

Jestor also lets you create agents based only on attached documents, like a time-off policy, with no connected table at all — which shows how automating support with AI agents can apply both to internal data and to a company's static documentation.

Frequently Asked Questions

Can the chatbot answer based on documents, without using a table? Yes, you can attach documents like an HR policy and the agent answers based only on them.

Does the chatbot's filter affect the original table? No, the filter only limits what the agent sees; the table and its records stay untouched.

Can I change the agent's tone, like making it more formal or casual? Yes, the agent's prompt can define its response tone, from more serious to more casual.

Reference Video

Get to know Jestor

With Jestor, you can automate workflows, connect departments, and build internal systems your way — all without code and with AI support.

Get to know Jestor at jestor.com and see how to take your company's management to a new level of efficiency and integration.

How to build an automation roadmap for your company

A good automation roadmap doesn't start by automating everything at once — it starts with a simple starter template, validated with the team, and expands process by process inside a structured BPMS. That's how Jestor recommends starting any implementation. How Do You Build an Automation Roadmap Step

Common mistakes when automating internal processes and how to avoid them

Among the most frequent mistakes automating processes, you'll find automating a poorly mapped process, granting overly broad access to sensitive data, and editing a live workflow without testing it first. Jestor's BPMS, Security, and App Versioning help you avoid exactly these three mistakes. What Are the

How to measure the ROI of a process automation project

Measuring the ROI of process automation requires comparing the tool's cost against the time it saves and the errors it prevents — not just looking at the monthly fee. Jestor's dashboard helps turn this into concrete numbers, comparing before and after automation. How Do You Calculate the

How to identify priority processes to automate first

Priority processes to automate are usually the ones consuming the most team time, generating the most errors, and most affecting the end customer when they go wrong — in that order. Jestor's dashboard and BPMS help you see these three criteria with data, not guesswork. How Do You Prioritize