> For the complete documentation index, see [llms.txt](https://docs.truecaller.com/truecaller-for-business/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.truecaller.com/truecaller-for-business/features/brand-protection/what-problem-does-this-solution-solve-and-how-is-it-different-from-traditional-anti-phishing-tools.md).
# What problem does this solution solve, and how is it different from traditional anti-phishing tools?
Most fraud monitoring solutions focus on online channels such as email, social media, and websites. However, fraud via calls and SMS has been rising rapidly, with scammers frequently impersonating trusted brands to commit customer care fraud, conduct phishing attempts, and carry out unauthorized account takeovers.
Brand Protection addresses this gap by focusing on communication channels such as calls and messaging, which are often overlooked by traditional security tools.
By leveraging Truecaller’s large global ecosystem and over 10 billion daily interactions, the solution can detect impersonation patterns and suspicious activity that many conventional web-based security systems may miss.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.truecaller.com/truecaller-for-business/features/brand-protection/what-problem-does-this-solution-solve-and-how-is-it-different-from-traditional-anti-phishing-tools.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.