FAQ
What problems is VoiceFox designed to solve?
VoiceFox is designed for repetitive, high-frequency phone communication that needs consistent messaging and retained results, such as customer reception, reminders, confirmations, follow-ups, and satisfaction surveys.
Do I need a technical integration to use VoiceFox?
No. Basic scenarios can be used through the VoiceFox console. API or Webhook integration is only needed when VoiceFox needs to connect with CRM, ERP, ticketing, or internal business systems.
What should I prepare before using VoiceFox?
Start by clarifying the business scenario, communication goal, user scope, common questions, service boundaries, and success criteria. Clearer scenarios make configuration and validation easier.
How does VoiceFox keep answers consistent?
Teams can organize business materials, service descriptions, policy language, and FAQs into unified knowledge sources, then use business flows to keep assistant responses within the expected scope.
Does VoiceFox support both inbound and outbound calls?
Yes. VoiceFox can support inbound reception as well as outbound notifications, confirmations, follow-ups, and surveys. The actual setup depends on the business scenario, line resources, and service plan.
Can call results be used for later review?
Yes. VoiceFox retains call process, results, and quality-related data so teams can understand user feedback, identify service issues, and continuously improve business language and communication flows.
Can VoiceFox integrate with enterprise systems?
Yes. Teams can use API or Webhook capabilities to connect VoiceFox with internal systems, data platforms, or business workflows. Before integration, confirm the required data, trigger timing, and security requirements.
What should I do if I have account or login issues?
If sign-up, login, or password recovery fails, first check the phone number/email, verification code, network environment, and account permissions. If the issue remains, contact VoiceFox support.