> For the complete documentation index, see [llms.txt](https://biz-card.gitbook.io/bizcard/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://biz-card.gitbook.io/bizcard/enterprise-version.md).

# Enterprise Version

BizCard Enterprise is designed for teams and organizations that want to go beyond individual digital business cards. It provides advanced tools to **scale communication, capture leads, and enhance customer engagement** with AI-powered solutions.

* **Centralized Contact Management**\
  Keep all your team’s contacts in one place, ensuring accuracy, visibility, and seamless collaboration across the organization.
* **SDR Agent on WhatsApp & Telegram**\
  Deploy an AI-powered Sales Development Representative to chat with prospects, qualify leads, and book meetings on popular messaging apps.
* **AI Widget**\
  Engage visitors on your website with a 24/7 AI assistant that answers questions, captures leads, and routes them to the right sales rep.
* **Effortless Personalized Emails**\
  Send AI-generated, tailored emails at scale — with smart subject lines, natural tone, and automated follow-ups.


---

# 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://biz-card.gitbook.io/bizcard/enterprise-version.md?ask=<question>&goal=<endgoal>
```

`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.