> 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/getting-started-for-admin.md). # Getting Started for Admin The admin controls which agents can use CallBlaze and how their calls should be synchronized with Picky Assist. An organization can connect multiple agents and devices to CallBlaze. Each agent can use their own Android device, while the admin can configure and monitor their calling activity from Picky Assist. ## Phone Bridge To get started with CallBlaze, enable the **Phone Bridge** channel under [**Channel Settings**](https://app.pickyassist.com/settings/channels)
Phone Bridge is the core of CallBlaze. It connects Android devices with Picky Assist and handles call synchronization with the CRM. All admin-side CallBlaze configurations are managed from the Phone Bridge channel settings. {% hint style="warning" %} Make sure each user has downloaded and configured the CallBlaze app. You can share the Play Store URL with them to install the app. {% endhint %} ## Global Settings Global Settings define the default CallBlaze configuration that is automatically applied whenever an agent logs in to the CallBlaze mobile app. Admins can configure and save these settings once, instead of configuring each agent individually. ### Configure Global Settings From Phone Bridge Global Settings, admins can configure: * **Call Tracking** – Choose how calls should be tracked on the agent's device. * **Add Contact** – Automatically add unknown numbers to CRM Contacts when a call is made or received. * **Follow-up Action** – Allow agents to create follow-up tasks against the call log after answered calls. These settings are controlled by the admin and cannot be changed by agents from the CallBlaze app. * **Prefix/Country Code** – Configure the country code and phone number length for number formatting. * **Ignore Prefix for International Call** – Keep international numbers starting with 00 or 011 unchanged. Below sample gif shows how the Global Settings can be configured;
### Trigger Connectors CallBlaze can send call events to configured connectors. Here you can create new Connectors or use already configured Connectors with Call blaze as the trigger. This allows organizations to perform additional automations based on call activity. Supported call events can include: * Answered * Missed Call * Not Answered * Rejected
{% hint style="warning" %} Only the connectors created from this section or from the **Connector** module with **Call Blaze** selected as the [event source](https://help.pickyassist.com/setting-up-guide/setting-up-connector/getting-started#event-source) will be listed in the **Select a Connector** dropdown {% endhint %} **Example: Automated Missed Call Follow-Up** An organization can configure a connector to automatically send a message when a customer call is missed. Example flow: * Customer calls the business. * The agent does not answer. * CallBlaze records the call as a missed call. * The missed call event is sent to the configured connector and triggers it. * In connector a Send Message action is configured with the customer Phone number field mapped from the log and The connector sends a WhatsApp message to the customer. * The agent can follow up with the customer later This helps businesses respond to customers even when agents are unable to answer a call immediately. #### How Global Settings Apply to Agents The new CallBlaze setup eliminates the need to manually select and configure each agent. Admin configures Global Settings → Agent logs in to CallBlaze → Global Settings are automatically applied → Agent configures app with SIM settings This makes agent onboarding simpler and avoids repeated configuration by the admin ## User Settings Once an agent logs in to the CallBlaze app, an user entry is created in the User Settings tab with the configurations made for that particular user. Admins can view and update each User’s Settings with all the configuration that made through Global Settings

Global Settings options and configuration

## Devices The Devices tab allows admins to view and manage the Android devices connected through CallBlaze. Here you can see the device details including Device Info, Synced Status, Linked Date, Linked agent, Last seen. Also you can take certain actions against each device they are; **Edit Name** - Editing and updating the preferred name of the connected device **Permissions** - View mandatory device permissions are enabled or not **Test Notification** - Used for testing whether the device notifications are showing properly in the device **Delete** - Clicking delete will logout the user from the app automatically and delete the device from the list Use this section to monitor and manage the devices associated with your agents.
## Stats The Stats tab provides an overview of CallBlaze call log activity, helping admins monitor call usage across the organization and based on agents. It is a visual representation of entire call log analytics based on the selected Date ranges. Below gif shows an overall view of sample Stats data
**For Example - The admin can analyse the monthly performance of each call agent by analysing the data instead of verifying each one manually** --- # 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/getting-started-for-admin.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.