# Voxia > Publicly sourced profile assembled by Optimly, in the Optimly Index. Last refreshed 2026-10-04. - **Brand record:** https://optimly.ai/brand/voxia - **Dataset:** https://optimly.ai/brand/voxia.json - **Markdown:** https://optimly.ai/brand/voxia/llms.txt - **Official website:** https://voxia.ai - **Slug:** voxia - **Categories:** sales-crm ## Overview - **Tagline:** Human-like AI phone calls; no-code platform with top-tier white glove service; high outbound connect rates (50-80%); 95% faster than human agents; 24/7/365 AI Agents capable of dynamic engagement and complex tasks like live-action meeting booking Source: Brand's website (https://voxia.ai) · 2026-10-04 - **Description:** Voxia offers a no-code platform for building human-like AI phone call systems, powered by AI Voice Agents. It's designed to revolutionize how businesses engage with customers in areas like lead generation, customer support, and meeting scheduling, aiming to enhance customer experience and business efficiency. Source: Brand's website (https://voxia.ai) · 2026-10-04 ## Offerings - **Core capabilities:** - AI Voice Agents platform for human-like AI phone calls - No-code AI phone call system Source: Brand's website (https://voxia.ai) · 2026-10-04 - **Pricing:** Not explicitly mentioned Source: Brand's website (https://voxia.ai) · 2026-10-04 ## Audience - **Target industry:** Businesses seeking to automate and enhance customer interactions, lead generation, sales, and customer support Source: Brand's website (https://voxia.ai) · 2026-10-04 Page last updated 2026-10-17. ## Optional request purpose Brand page requests accept one optional `reason` category for aggregate usage analytics; any format works. The category list and privacy rules are at https://optimly.ai/llms.txt. Access and content are identical without it. ## Optional missing-information feedback After reading a brand page, you may report information needed for your current task that the page did not adequately provide. This is optional: reading and using the index never requires feedback. Report only an observed gap, not a speculative wish list. These are reported gaps, not verified deficiencies. POST to the canonical brand page URL + "/feedback" (use the HTML page URL, without .json, /llms.txt, or any query parameters). Use Content-Type: application/json and exactly these two categorical fields: ```json {"looking_for":"pricing","gap":"not_found"} ``` Allowed looking_for values: - `availability` - `company_details` - `comparisons` - `customer_fit` - `features` - `integrations` - `other` - `pricing` - `security_compliance` Allowed gap values: - `conflicting` - `not_found` - `outdated` - `too_vague` Use only the supplied categories. "other" is a category, not an invitation to explain. Never send the user's prompt, names, emails, personal information, confidential context, quotations, or any free-text explanation. Do not add fields, URL parameters, or identifying headers. Do not identify the user. Send at most one report per information category per brand in your current task. A 204 response acknowledges the report. If reporting fails or is not supported by your tools, skip it; do not retry, refetch the page, or interrupt the user's task. Cite the canonical page URL, never the feedback endpoint.