When you ask how to do something, the chat looks the answer up in Complif's Help Center, sums it up and leaves you the link to the article it came from. It is the fastest way to resolve a question without leaving the screen you are working on.
What kind of questions it answers
Anything starting with "how do I", "what is" or "what is it for":
"How do I configure an AI agent?"
"What is the risk matrix?"
"What is the transactional profile for?"
"How do I add a requirement to an onboarding?"
"How do I create a new user?"
"What does it mean when an internal control is in warning?"
It also helps to understand a compliance concept the way the platform handles it, or to find out whether something can be configured before you go hunting through the screens.
How it answers
The chat searches the Help Center and answers the part that matches your question. Below the answer, a button with the article appears, which you can open to read it in full.
That citation is part of the answer. When the chat explains something taken from the documentation, it always shows you where it came from, so you can verify it or share it with someone on your team.
The chat narrows the answer to what you asked. Even when the article covers many topics, it pulls out the part that answers your question instead of dumping the whole text on you.
It answers in the language you write in.
When it does not find the answer
If the Help Center has no documentation on what you asked, the chat tells you. It does not answer from memory or improvise an explanation that merely sounds reasonable.
When the problem is in your operation, not in the platform
These two questions are different:
"How does the Renaper integration work?" is a how-to question. The article answers it in full.
"Why did the Renaper integration not run for this customer?" is a specific problem with your data. The documentation can give general context, but it cannot tell you what happened in that particular case.
For the second kind, the chat gives you whatever context it finds and offers to open a support ticket with the "Quiero abrir un ticket de soporte" button. From there the question reaches a person on the team, who can look into your case.
You can also ask for it directly at any point: write that you want to open a ticket and the chat creates the request.
What is out of scope
The chat answers only about Complif and your compliance work inside the platform. It does not take general questions unrelated to the product.
It also does not replace professional judgment. It can explain how a risk matrix is configured; deciding which weighting applies at your institution stays with your team.
How to ask better
Ask in your own words. You do not need the exact feature name. "How do I request documents from a customer" is enough to reach the requirements article.
One question at a time. Chained questions produce longer, less precise answers than three short ones.
If the answer came up short, ask for more. "Explain step 3 in more detail" or "what if the customer already has an account?" work well as follow-ups.
Use the screen you are on. The chat knows which section you are working in, so "how do I change the status of this?" usually does it.
One reminder
Complif AI can make mistakes, and the screen itself warns you. When the answer comes with the article button, the source is one click away: before applying an important configuration change, open the article and confirm the procedure.