> For the complete documentation index, see [llms.txt](https://eztalks.gitbook.io/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eztalks.gitbook.io/help/introduction-to-eztalks.md). # Introduction to eztalks Brief overview of eztalks products and services eztalks is an all-in-one online engagement platform for effortless and cost-effective communication through text messaging, fax, and phone calls with customers and partners. To learn more eztalks, please check [About us](https://eztalks.com/company/). ### Products and services ### [SMS](/help/products/sms.md) eztalks SMS enables companies to transform customer experiences through its easy-to-use text messaging marketing software, which can be used for sending notifications, alerts, reminders, confirmations, and SMS marketing campaigns anytime, anywhere. ### [Voice](/help/products/voice.md) Our phone call service is designed to be both reliable and affordable. With eztalks, you can make phone calls to anyone, anywhere in the world, at a low cost. Our platform also offers various calling features, such as call recording and forwarding, to meet your unique needs. ### [Phone numbers](/help/products/phone-numbers.md) eztalks provides virtual phone numbers in over 180+ countries, every business could own its dedicated phone numbers for customer support, sales team, and more. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://eztalks.gitbook.io/help/introduction-to-eztalks.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 `build a script that syncs our docs to a CMS` 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.