An AI assistant inside your CRM that cannot see more than you can

Most CRM AI features are a text box bolted onto a product, wired to a model that has been handed a copy of the database. That arrangement works until the first time a junior salesperson asks "what is our biggest open deal?" and gets an honest answer about an account they were never meant to see.

The design decision that matters

In TicAte CRM, the model never touches the database.

Tic Buddy — the assistant in the corner of the workspace — can do exactly one thing to read your data: call a single query tool. That tool runs on our server, as the person who asked, through the same permission scope that every list and every board already uses.

The consequence is worth stating plainly. Two people ask the same question on the same afternoon:

• An admin asks "how many leads came in this week?" and is told about every lead in the workspace.
• An agent asks the identical question and is told about theirs.

Neither of them had to think about it. And if somebody asks about a module their role cannot read, the tool refuses, and the assistant explains the refusal rather than inventing a number to be helpful.

What it is actually useful for

Not writing poetry. The questions a sales manager asks between meetings:

• How many leads came in this week, and where did they come from?
• Which deals are due to close this month?
• What has not been touched in three weeks?
• How many tasks are open on the Chennai team?

It reads leads, deals, contacts, companies and tasks, over the period you name — today, last week, this month, last quarter — and answers in a sentence. The alternative is building a report, which is why most of those questions never get asked.

Your model, your key, your bill

Connect Anthropic, OpenAI or Google with your own API key. You pay the model provider directly, at their rates, and you can switch when a better or cheaper model lands.

This is deliberate. AI billed per message by the vendor gets expensive at exactly the moment it starts being useful, and it quietly makes your software provider a reseller of someone else's tokens. Your key is encrypted at rest, the same way every other secret in the workspace is.

It is also optional in the strongest sense: switch the assistant off and nothing else in the CRM changes.

The controls that make it safe to switch on

• Read-only, or allowed to act. By default it answers. You can let it do small jobs on request, or keep it strictly read-only.
• Mask personal details before anything leaves for the model, if you would rather it never saw customer names.
• A turn limit, so a conversation that is going nowhere ends rather than wandering.
• A full log — every question, every answer, every lookup. Not a vendor's black box you have to trust.

The question to ask any CRM vendor selling AI

Ask what the model can read, and how that is enforced. If the answer is "it only sees what the user sees", ask how. A prompt instructing a model to respect permissions is not a permission system; it is a request. The enforcement has to live in the query path, where the database is, not in the instructions.

Tic Buddy is on Professional and above. If you want to see it against your own records, ask us for a walkthrough — and how we decide what to build explains why it was built this way round.