Vagle AI FAQ

Vagle is an AI voice calling platform for business calls, lead qualification, follow-ups, appointment workflows, call logs, transcripts, summaries, and tool updates.

An AI voice agent is software that can speak with callers over the phone, follow business instructions, collect details, and trigger configured next actions.

Yes. Vagle supports outbound calling workflows such as campaigns, lead qualification, reminders, and follow-up calls when the phone setup is configured.

Yes. Vagle can answer inbound calls when a connected phone number is assigned to an assistant.

Yes. Vagle can ask qualification questions, capture answers, detect outcomes, summarize the call, and save lead status.

Vagle can collect appointment details and update calendars or tools where the required integration is configured.

Vagle can update connected tools such as Google Sheets, Airtable, Notion, Gmail, Google Calendar, webhooks, and APIs where configured.

Yes. Call logs can include transcripts depending on the call configuration and transcription setup.

Yes. Vagle can create short summaries and outcomes for calls so teams can review what happened.

Yes. Follow-up funnels can schedule calls, keep short lead memory, retry no-answer leads, and save outcomes.

Yes. CSV lead upload is supported for lead calling and follow-up workflows.

Multilingual support depends on selected speech, model, and voice configuration. It should be tested for each language and use case.

Vagle uses usage-based calling where configured. Cost depends on connected voice minutes, telephony, AI model, speech providers, and platform settings.

Vagle is positioned around pay-as-you-go style calling usage where supported. Follow-up automation setup may require a one-time activation.

Yes. Agencies can use Vagle for lead qualification, appointment workflows, follow-up calls, call logs, and tool updates for client workflows.

Yes. Real estate teams can use Vagle to call leads, qualify interest, schedule site visits, follow up, and save summaries.

Yes. Clinics can use Vagle for appointment enquiries, reminders, follow-ups, and call summaries where compliant with local rules.

Yes. Home service teams can use Vagle for missed calls, quote enquiries, booking requests, and follow-ups.

Vagle can be configured with handoff or escalation behavior where supported, and the team can review call context.

Call recording is available where enabled and supported. Customers are responsible for any required notice or consent.

Yes. Assistants can be configured with scripts, instructions, questions, and routing behavior.

Yes. Vagle can detect or save outcomes such as qualified, callback, booked, no answer, not interested, or opted out depending on setup.

Yes. Retry behavior can be configured in follow-up and campaign workflows.

Response speed depends on telephony, speech-to-text, language model, text-to-speech, network, and configuration. Test your setup before production use.

Use the contact page to request access or contact sales.

Vagle supports tool workflows for Google Sheets, Airtable, Notion, Gmail, Google Calendar, webhooks, and REST APIs where configured.

Yes. Vagle is designed for small and growing businesses as well as sales, service, and appointment-led teams.

Vagle is best used to automate repetitive calls and first-level workflows. It should complement human teams for sensitive or complex conversations.

Yes. Vagle can be configured for reminder and follow-up calls where the business has the required consent and lawful basis.

Yes. Vagle can send mapped call data to Google Sheets when the Google Sheets tool is connected and configured.

No. New accounts start with 0 calling credits unless credits are explicitly granted by Vagle AI in writing. There is no free trial, free credits, or bundled minutes by default. Calling usage is drawn from your credits or wallet balance.

Calling and other usage consume your credits or wallet balance based on the selected configuration. You top up to keep a sufficient balance; if it reaches zero, calling pauses until you add more.

Workspace API keys are read-only, scope-limited keys created per client workspace. The full secret is shown only once at creation; after that only a non-secret prefix and safe metadata are displayed, and the secret is stored hashed.

You can revoke or rotate a workspace API key at any time. Revoking immediately stops further access with that secret; rotating issues a new secret (shown once) and retires the old one.

Vagle offers workspace-scoped API and MCP tooling so teams can build dashboards and integrations on their own call, lead, and outcome data. Access is limited by scopes, read APIs are separated from write actions, and write actions are audited. See the Developers & API page.

Connected tools act only on the fields and actions you configure (for example, updating a Sheet row, creating a calendar event, or calling your webhook). Write actions run with your configured credentials and scoped workspace permissions and are recorded in audit logs.

Yes. Outbound webhooks are signed with a per-endpoint signing secret so your server can verify authenticity. Webhook URLs are validated to block private, internal, and metadata addresses, and the signing secret is shown only once.

The Client Portal is a read-only, workspace-scoped view that lets a client see their own calls, leads, reports, and notifications based on the access an agency enables. Client roles cannot reach other workspaces or admin areas.

The Lead Inbox is a daily board of calls that need attention (hot leads, missed calls, callbacks, booked, follow-up needed, and more). Your status changes, notes, and callbacks are saved without altering the original call records, and phone numbers are masked by default.

Scheduled Reports email a safe summary (totals, answered, missed, failed, hot leads, booked, follow-ups) on a daily, weekly, or monthly schedule. Reports never include transcripts, recordings, secrets, or raw provider data.

Important actions are recorded in audit logs that capture who did what and when, without exposing raw secrets such as API keys, tokens, or webhook secrets.

Customers are responsible for honoring opt-outs and do-not-call requirements. Workflows can be configured to stop or route a contact who opts out, and the do-not-call list is respected where wired into the calling and follow-up flow.

The customer using Vagle AI is responsible for required call-recording notices, AI disclosure where required, consent, and lawful use under their local rules. See the Acceptable Use Policy.

You can contact us to request access, export, or deletion of personal information where applicable law gives you those rights. Some lead or caller data may need to be handled by the business that collected it. See the Privacy Policy.