ARIA Voice documentation
How ARIA Voice runs conversations across your website and phone line, how it's set up, and how your team works with the leads, records, and escalations it produces.
Who this is for
Businesses that want website and phone conversations answered consistently — sales and service teams, appointment-based businesses, and anyone currently relying on staff to catch every inbound conversation. You'll get the most from this page if you're the person setting up ARIA Voice for your organization or the person reviewing what it captures day to day.
Website assistant setup Requires setup
The web conversation surface runs on the same conversation engine used across the platform. Setting it up on your site is coordinated with your Random Target AI implementation contact rather than done through a self-service dashboard control at this stage:
- Confirm ARIA Voice is included on your plan (see pricing).
- Provide your business knowledge (see FAQs and knowledge below).
- Your implementation contact embeds the assistant on your site and confirms it against your domain.
- Once live, conversations appear in the ARIA Voice section of your dashboard.
Telephone assistant setup Requires setup
Telephone conversations use the same underlying assistant as your website. Connecting a business phone line is handled during implementation with your Random Target AI contact, not through a public self-service form. This documentation does not publish telephone numbers or telephony configuration details. Once connected, calls appear in your dashboard the same way web conversations do.
Greetings and behavior Requires setup
Your assistant's greeting, tone, and general conversational behavior are configured as part of setup, based on how you want ARIA Voice to represent your business. There is no self-service dashboard editor for greeting text yet — changes go through your implementation contact.
Business hours Requires setup
Business hours determine when ARIA Voice tells callers and visitors your team is available versus when it should handle things fully on its own. Hours are configured during setup. A self-service hours editor in the dashboard is Planned and not yet available.
FAQs and knowledge Available now
Answers are grounded in your organization's knowledge base — documents made up of titled entries your team provides (services, pricing, policies, FAQs). Admins and managers can view the current knowledge library from the Knowledge dashboard section. Adding new documents today happens by sending content to your implementation contact or through direct API submission; a self-service "add document" form inside the dashboard is Planned. Full detail is in the Knowledge documentation.
Lead capture Available now
Names, contact details, and expressed interest are captured automatically during conversation and saved as lead records — no separate form required during the call or chat itself. Leads are also created from the public contact form. Admins and managers can review captured leads from the Leads dashboard section. See Leads & conversations for the full lead lifecycle.
Booking Requires setup
ARIA Voice can capture appointment and callback requests during a conversation and record them as bookings. Booking activity is reflected in your account's overall activity counts. A dedicated booking calendar view inside the dashboard is Planned — for now, booking follow-up is coordinated with your team directly.
Call routing Requires setup
Routing rules — which conversations ARIA Voice resolves directly versus hands to a person, team, or queue — are configured during implementation based on your business's escalation needs. A self-service routing rules editor in the dashboard is Planned.
Conversation records and transcripts Available now
Every conversation produces a record with its channel, duration, and outcome, visible from the ARIA Voice and Conversations dashboard sections. Records are limited to your organization only. A dedicated full-transcript reader inside the dashboard (beyond the summary-level view) is Planned.
Permissions
Dashboard access follows your account role:
- Admin / Manager — full access to conversations, leads, and the knowledge base.
- Member — can view conversation activity but does not have access to the full lead list or knowledge base management; the dashboard shows a clear message rather than an error when this applies.
All access is scoped to your own organization — no organization can see another organization's conversations, leads, or knowledge.
Testing Requires setup
Before going live, your implementation contact can walk through test conversations with you against a preview of your configured assistant. A self-service "test mode" inside the dashboard is Planned.
Usage Planned
Conversation, lead, and booking counts are visible in your dashboard's activity metrics today. Metered usage tracking (for example, voice minutes against a plan allotment) is not yet connected — see Usage & billing for the full picture.
Known limitations
- Greetings, business hours, and routing rules are configured with your implementation contact, not self-service yet.
- Knowledge documents are viewable in the dashboard, but adding new ones isn't a self-service dashboard action yet.
- Full transcripts are not yet browsable in the dashboard — only summary-level conversation records are.
- There is no dedicated bookings calendar view in the dashboard yet.
- Metered usage reporting is not yet connected.
Troubleshooting
Example: a manager notices a call is missing from the dashboard. First check the Conversations section, which lists the most recent activity — the ARIA Voice section shows the same data filtered to voice. If it's still missing, confirm with your implementation contact whether the call reached a connected line. For sign-in or access issues, see the general troubleshooting guide.