> For the complete documentation index, see [llms.txt](https://docs.zero.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zero.inc/features/dialer.md). # Dialer {% hint style="info" %} **Early access.** The dialer is being rolled out to selected workspaces. Talk to the Zero team if you would like access. Full documentation follows once it is generally available. {% endhint %} The dialer brings calling into Zero, so the phone stops being the one channel that never makes it into the CRM. You call a contact from their record, take inbound calls in the app, and the call is logged against the right company, contact and deal without anyone writing it up afterwards. What it covers today: * **Calls from a record.** Dial a contact from Zero and handle the call in a panel inside the app, with your own choice of microphone and speaker. * **Inbound calls.** Answer or decline calls in Zero, or forward them elsewhere when you would rather not take them there. * **SMS.** Send and receive text messages alongside calls, from the same workspace number. * **Transcripts.** Calls are transcribed, so the conversation is searchable and available to agents and reports like any other activity. * **Workspace phone numbers.** Admins manage the workspace's numbers, pick which one is the default, and set where inbound calls should go. Once a call ends it behaves like every other touchpoint in Zero: it shows up on the [Activity feed](/tracking-context/activity-feed.md) of the people and companies involved, and counts toward their touchpoint history. --- # 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://docs.zero.inc/features/dialer.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.