Solid System Performance and Support, Pending Feature Enhancements
I recently acquired Tier 5 of the Dialora service and have begun the setup process, which has been reasonably straightforward. To address specific operational questions, I utilized the included 30-minute support meeting, which proved to be highly valuable.
Support Experience
I was impressed by the speed of service, securing a booking within 24 hours despite being in the Australian time zone. My support consultant, Angela, was exceptional—highly knowledgeable, professional, and helpful in clarifying technical and policy-related inquiries.
Key Operational Findings and Limitations
The support session clarified several important operational aspects crucial for prospective users, particularly those planning to white-label or resell the service.
First, regarding phone numbers, due to Know Your Customer (KYC) requirements and Dialora using local numbers, users are restricted to acquiring numbers only within their country of residence (matching the registered address). This limits the ability to offer international numbers outside of the user's base country. For other types of numbers (non local), like many Toll-Free Numbers, I believe the address requirements can be worldwide, meaning your local country address may be sufficient. However as far as I can see at this stage, toll free numbers from different countries are not offered by Dialora? Please correct me if I am wrong Dialora team.
Second, concerning the client billing model, the system mandates a minimum monthly charge for client plans. It is not possible to bill clients purely on per-minute usage at a custom rate; however, this minimum required charge can be set as low as $1.00.
Third, and most critically, is the process for overage billing. While the system allows clients to exceed their allocated monthly minutes, the overage charges must be calculated and billed manually. The current functionality lacks the ability to automatically aggregate, calculate, or export a detailed overage usage report (e.g., to a spreadsheet) for bulk client invoicing. This manual process will be highly inefficient and challenging for managing potentially hundreds of clients monthly, representing a significant constraint on the workflow.
Overall Conclusion
Despite the current limitations in client billing automation, I believe the core Dialora system is solid and technically impressive given its early stage of development. I am hopeful that the development team will prioritize improving the client billing and data export functionalities in the near future. We look forward to building a successful, long-term Voice AI business in partnership with Dialora as the platform continues to evolve.
-
Avi_Dialora
Dec 13, 2025Thank you for such a thoughtful, detailed, and fair review, we truly appreciate the time you took to document your experience.
First, on support:
We’re glad the Tier 5 session was valuable and that Angela could help clarify both the technical and commercial aspects. We’re intentionally investing heavily in human-led onboarding for agencies because we know this is not a “plug-and-play toy” — it’s infrastructure.
Now, to address your key points transparently:
Phone numbers & KYC (local vs international)
You’re correct on the core constraint, and thank you for explaining it clearly for other buyers.
• Local numbers are tied to telco + government KYC rules, which means:
• The address must match the country/region of the number
• This is enforced by the carrier (not Dialora discretion)
• Toll-free numbers:
• These are less strict in many regions
• We are actively expanding toll-free availability country-by-country
• Some regions are live, others are rolling out based on carrier approval
This is a telco reality, not a platform limitation — but we agree it impacts international resellers, and we’re actively working around it where legally possible.
Client billing model (minimum monthly charge)
Correct again.
• Dialora currently requires a base plan amount (as low as $1)
• This is intentional to:
• Avoid zero-dollar zombie accounts
• Keep Stripe subscriptions stable
• Ensure cost recovery for infrastructure even on low-usage clients
That said, usage-based pricing on top is fully supported, the minimum is just a floor, not the business model.
Overage billing & reporting (the big one)
This is the most important feedback — and you’re right to call it out.
Current state:
• Overage usage can happen
• Billing calculation is currently manual
• No bulk-export / automated overage invoicing yet
Planned improvements already in motion:
• Per-subaccount usage breakdown
• Exportable usage reports (CSV)
• Automated overage calculation
• Optional auto-charge workflows
You’re not missing anything — this is an area we’ve explicitly flagged as high priority for agency scale, and your feedback reinforces that urgency.
Our honest position
Dialora today is:
• Strong technically
• Early in agency billing automation
• Moving fast, with real customers shaping the roadmap
We would rather be honest about current limitations than oversell what isn’t fully automated yet. Reviews like yours help us build the right features instead of vanity ones.
We’re grateful you’re choosing to build with us at this stage, and we’re committed to earning that trust long-term. Expect visible progress on billing, reporting, and exports — this isn’t being ignored.
If you ever want early access to agency-focused improvements or to sanity-check upcoming features, our door is always open.
Thank you again, this is exactly the kind of partnership we want to build.