> For the complete documentation index, see [llms.txt](https://help.pickyassist.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pickyassist.com/setting-up-guide/connecting-channels/call-blaze-v2.md). # Call Blaze V2 Call Blaze V2 is the upgraded, SIM-based call tracking solution by Picky Assist. It allows organizations to automatically log, track, and monitor incoming and outgoing calls directly from Android mobile devices into the Picky Assist CRM and can also send call events to third-party platforms through Connectors in real-time. For example, an organization can connect multiple agents and their Android devices. Agents can make and receive business calls from their devices while the admin can manage and monitor call activity from Picky Assist. CallBlaze records important call information such as * Phone Number * Call direction * Call status * Call duration * SIM used for the call * Call start and end time * Agent associated with the call The call details are automatically synchronized with Picky Assist and stored in the Call Logs CRM module. > **A Better Experience with CallBlaze V2** > > CallBlaze V2 provides a simpler and more user-friendly experience for setting up, managing, and monitoring business calls. #### What's New in Call Blaze V2: * Improved and simpler interface * Guided agent onboarding * Better call activity and synchronization visibility * Simplified configuration #### Before You Start Make sure: * The device is an Android phone. * The latest [**Call Blaze**](https://play.google.com/store/apps/details?id=com.pickycallblaze.callblaze\&pcampaignid=web_share) app is installed. * The required SIM card is active on the device. * The users should be provided with Phone Bridge channel access ## Real word Usecases 1. **Real Estate** A real estate company receives enquiries more through phone calls * Call Blaze captures incoming calls from potential buyers and the call log is added to the CRM. * A [Workflow](https://help.pickyassist.com/setting-up-guide/setting-up-modular-crm/workflows) can trigger a [Chatbot](https://help.pickyassist.com/setting-up-guide/setting-up-flow-builder/fundamentals-must-read) against the contact * A WhatsApp chatbot can collect additional information such as property type, budget, and preferred location. * The lead can be moved into a Sales Funnel. 2. **Automobile Dealerships** Car dealerships receive calls from customers interested in vehicles, test drives, financing, and service. * Customer calls the dealership and log will created * Based on interaction the Lead can be added as to a Chatbot * Chatbot can send available vehicle options or collect requirements * Can confirm Test drives, bookings, services etc --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.pickyassist.com/setting-up-guide/connecting-channels/call-blaze-v2.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.