314 comments found.
If we are using a single (shared) OpenAI account and a single Twilio account to handle AI agent calls for multiple clients, how should we:
1. Calculate billing separately for each user/client?
2. Define a credit value so that we do not incur losses due to OpenAI and Twilio usage costs?
3. Handle different country calling rates, since Twilio pricing varies by destination country (for example, one client calling the USA and another calling the UAE)?
Specifically: Twilio charges different per-minute rates based on country codes. OpenAI voice usage also has per-minute costs.
How should we calculate or define a credit system that fairly accounts for these differences while maintaining profitability?
I understand your situation however we have credit system where you can calculate a upper cost as per twilio & openai and set credit packages as per same if your target audience is worldwide.
For example: Lets assume that $0.015 per min call for you then keep min 75-100% margin on this and set credit package on this. 100 credits for $8-10 to keep enough margin.
Can you please clarify what you mean by “ElevenLabs Native SIP Trunk which supports 10+ SIP providers” which you are going to release soon as separate plugin?
Specifically:
1-Will the SIP providers be fixed/pre-integrated (similar to how Twilio or Plivo are currently handled), meaning we can only choose from those 10+ vendors?
2-Or will the platform allow us to add any SIP provider of our choice by pointing to our own VoIP/SBC/Gateway (via static IP, SIP URI, or IP-to-IP routing) so we can use existing wholesale VoIP carriers?
3-If custom SIP providers are supported, how will billing and call rating be handled? Example: will call billing remain external at the SIP provider level? Or will AgentLabs expose CDRs/usage so we can map them to SIP provider invoices?
You will get documentation and complete details once it will be launched. Please wait till then. thanks
Thanks for the update. Understood that full documentation will be provided upon release. For planning purposes, could you clarify two quick points so we can prepare our deployment model accordingly:
1-Will the upcoming ElevenLabs Native SIP module support custom SIP providers (via IP authentication), or will it be limited to a list of pre-integrated carriers?
2-Do you have an estimated release window for the module so we can align our infrastructure plans?
1. Elevenlabs supports a list of SIP providers and only those will be supported 2. Its under development, hopefully by Feb
I want to update my current system without doing a complete over whole of the existing installation. Are there specific files for this?
Sir, due to some unavoidable reasons, our support team has been unable to work, please allow this week as we assure to fix your issues by Sunday.
Thanks for your understanding
Hello, could you help me attend to ticket #4524421
I have been waiting for a response for over two days and I don’t if I should proceed too install the new version or wait for reply on the ticket.
Thanks
Sir, due to some unavoidable reasons, our support team has been unable to work, please allow this week as we assure to fix your issues by Sunday.
Thanks for your understanding
Alright, thank you
Hello, you promised to help me fix my issue on Sunday, but this is Tuesday and I haven’t heard from you.
Hi can you please connect to whatsapp +919310797700
How the CRM works, Any Video tutorials ? Any promotional offer for New Year (like free installation) ?
We will make video tutorials soon, more coming by next week. | No offer for now.
IS SIP Trunk feature available now ?
Not nowz however we will add plugin soon. It will be a separate item.
Pre-purchase query: Since, this is a mere website wherein all app features are driven by API calls to Twillio , OAI & 11Labs , why not release a Laravel / PHP version that can be hosted on shared server ??
As for now , what’s the kind of suggested median config for let’s say Hostinger VPS ?
Thank you for your question – this is a very valid point.
Although AgentLabs may appear like a simple website, it is actually a real-time AI calling platform, not just an API wrapper. The system depends on persistent WebSocket connections, live audio streaming, background workers, and event-driven processing, which are not supported on shared hosting environments.
Why not a Laravel / PHP version on shared hosting?
- Real-time voice streaming (Twilio ↔ OPENAI ↔ ElevenLabs) requires long-running processes
- WebSockets, SIP handling, and concurrent call sessions are not possible on shared servers
- Queue workers and live call orchestration cannot run reliably in PHP shared hosting
- Overall stability, scalability, and call quality would be compromised
Because of these technical limitations, a shared-hosting PHP/Laravel version would break core functionality and result in a poor user experience.
Recommended VPS Configuration (Median Setup)
- 2 vCPU
- 4 GB RAM
- 40–50 GB SSD
- Ubuntu 20.04 / 22.04 LTS
- Node.js 18+
- PM2 for process management
This configuration works well on providers such as Hostinger VPS, DigitalOcean, aws, etc.
In summary, AgentLabs is designed as an infrastructure-grade AI calling system, not a traditional PHP website. A VPS is required to ensure reliability, performance, and real-time voice quality.
Ok ! But, why websocket ? Does it also doubles as chatbot apart from calling ?
Without websocket, how are you going to make or receive calls? Thats how it works.
I purchased one more script during Black Friday for slack that use Web sockets for free calling , conference & chat . But they’re not using Twillio API like you.
So I was wondering what’s the exact role of websocket when Twillio is already facilitating the two way communication via its own websocket ?
Look, twilio websocket works for them, not for you, you need to have your own websocket in order to process the connection without that you cannot even connect.
We have 3 engines on agentlabs which works on websockets - elevenlabs works natively with twilio - OpenAI <> twilio works on our infra - OpenAI <> plivo works on our infra
Own infra means websockets & all the arrangements we have development to make the calling smooth.
If you need more knowledge on websockets, please try google. Thanks
Ok ! Is the entire user onboarding process is via Twilio / Plivo ? Does user get to know that they’re using Twilio / Plivo and not really Agent Lab ? Or we tell users clearly in the beginning that everything is being done via API of Twilio / Plivo ? Can they buy numbers from our website or via Twilio only ?
Please confirm SIP Trunk features, As its a Option to add static IP to route calls on VoIP switch ? or a option where can add any SIP Provider company IP address/ Gateway to route calls directly from Agentlabs? Also please confirm if adding sip trunk that will be compatible with Open AI and Eventlabs both as current combinations are going on with twilio and pivilio ?
We will be adding Elevenlabs Native SIP Trunk which support 10+ SIP providers.
It means these 10 SIP Providers will be fixed like twilio or pivilio ? or we can add any sip provider as per our choice by VoIP IP Gateway directly to any voip provider company ? and if yes (we can add any sip provider then how can see biling with that sip provider ?).
hi,
The installation done by you is having some issues. i have raised ticket 2 days back, still waiting for reply
Let me tell you that we dont work on weekends. You need to keep patience to get free installation & support. And please dont use comment section for support. Thanks
he product itself is very good, but we noticed that monetization could be challenging. Many users create an account and then leave because the onboarding feels complicated — for example, buying a number, completing KYC verification, etc. A common question from customers is whether they can use their own existing number instead.
If something like this ( where user can use their own existing number ) is planned, it would significantly improve adoption and conversion. With a simpler onboarding flow, this project could easily become one of the most SaaS-ready products on the entire platform.
Allowing Customers to add their own number requires SIP TRUNK which we are launching soon as a plugin.
and to make onboarding easy, we suggest to create product onboarding videos for your own clients or walkthrough as there are lot of free tools out there and target on quality rather quantity of clients as few of our users are even started making good revenue. Wish you good luck
Thanks. When do you think SIP TRUNK will be added?
Our team is working on it.. I dont have any timeline but expect it soon.
can i use my own sip number from tata telecome india
We are launching SIP TRUNK plugin soon then you will be able to use.
Weldone for the Job weldone. I have a feature request, I don’t know if it is possible to implement it into the system.
Can we have different credit charges for Elevenlabs Voice and OpenAi voice (e.g Elevenlabs voice = 5 credits/min || OpenAi Voice = 1 credit/min)
In my Country (and I believe in most countries outside US and Europe), Elevenlabs is very expensive and this means that mose businesses would not be able to afford it.
But with this option, users can choose their voice and be aware of the cost implications.
For users who can’t afford ElevenLabs, they can use OpenAi and use less call credit.
Also, I have a suggestion about the KYC. Can we have more fields like; - Full Legal Name - Date of Birth - Residential Address - Nationality/Citizenship - Contact Information: Email address and phone number.
Then make all document upload fields optional. I want a situation where an individual can also fill the KYC form. What we have now is only for Companies.
Apologies if I am making much requests, I just wanted to contribute to the development of this great product.
Thanks
Thanks for writing. This can be done for sure however we cannot accommodate this in the core item. You can get this done by customisation. We are available for custom work. Contact us via whatsapp.
Hi, do you have integration with Hubspot or salesforce?
Agentlab doesnt support native integration however you can use our webhooks & make.com to connect it with any software to share events.
Hello, and congratulations on the update with the language management system. I really appreciate it. Keep up the good work!
Thanks
Ho does numbers work, so if i have a business number and want to integrate this how can this ai answer incoming calls or thi feature is not available ?
If you number is in twilio then you can sync it with agentlabs and start receiving incoming or outgoing calls.
which is better i notice 2 pricing wise or are we meant to use both at the same time – Twilio or Plivo
No you can use any one or both lets your user decide as Plivo support Indian numbers as well.
i dont plan on targeting india, also Plivo has ai agent too, it doesnt make sense so if i get a client i would tell them to create an account to get a phone number or twilio before they can use my service ? or can they generate a number from AgentLabs and also add their number
sending them to does platform is bad for business as im sending them to my competitor
Firstly they dont need to go to plivo or twilio, your customers will buy & release numbers from agentlabs using your keys.
oh okay makes sense ill purchase now
thanks, for any further clarification, feel free to write to us.
done, also the logo on the widget can it be changed i saw someone comment same thing and you said next update
Logo on the website widget is dynamic, user can change and so as admin.
okay – Integrations Salesforce, Hubspot, ZohoCRM, Shopify, Zendesk, and more. do you have this plans? the ai agent can edit an order on shopify, or check status,
You can still connect agentlabs with any 3rd party using webhooks and our upcoming RestAPI plugin.
Agent can do wonders and making an order edit will be an interesting one, will surely this with dev team
Hi also can you add livechat widget like livechat for website and you can train it ai agent to reply and also be able to pass to human, some people may not want to call and would want to chat on the live chat if you could add that, also knowledge base and ticketing, it will then make this platform a one stop shop for automating their customer support and relationship
Okay we will surely consider this in future updates.
Better to share it to our support rather here. Tech team will reply you better. Kindly dont use comment section for support purpose. Thanks
When a user creates a website widget and embeds it on their site, attempting to initiate a call via the widget results in the error “Failed to initialize AI session.” This issue occurs only in the latest updated version; the previous version functions correctly. Additionally, the embedded widget displays “Powered by Agentlabs” on client websites, which undermines the product’s branding. This label should be dynamically replaced with the configured brand name.
Thanks for reporting the widget issue, have shared with the dev team, they fix it in few hrs & update. (Please next time, raise a ticket for this)
Regarding website widget, user’s widget will only have admin’s branding thats how system works.
As bulk calls how many can it make per day, if it depends of the API then for 1m calls how much will it cost ? if a company having 100 people working for tele calling the making 250 calls per day like 250×100 in a day x 28 days and responding to 500 calls in a day. I want to make sure will it be good.
Agentlabs has no such limit, it can even handle million calls a day however the actual limit comes from your provider’s API i.e. elevenlabs or OpenAI voice and your telephone provider twilio or plivo.
You can check their plans for concurrency rates.
When will the new updates and additions arrive? Is the release date clear? Can we say approximately 15 days? We will plan our PR efforts accordingly.
Additionally, we are applying to Plivo, but they haven’t responded at all. What should we do about this?
Thanks for raising this question.
To clarify the update process: whenever you update AgentLabs (or any of our items) from an older version to the latest one, we always provide clear, step-by-step instructions to ensure your existing database remains safe.
There is no need to delete or recreate your database. The correct approach is to replace the application code, back up your `.env` file and database, and then migrate the latest files. This ensures the application is updated, not reinstalled.
We hope this clarifies the process. If you need assistance, our support team can guide you through the steps. Please note that hands-on implementation by our team is available at an additional cost.
Hello,
Thank you for the detailed explanation regarding the update process. That part is clear and noted.
However, to clarify our original question: we were not asking how the update is performed, but rather when the next update will be released.
Specifically, we are currently waiting for two features that were mentioned to be included in an upcoming release. The timing of this update is important for us, because it directly affects our marketing plans. If the update is expected to be released within 15 days or less, we are planning to proceed with our advertising campaigns accordingly.
Could you please clarify:
Whether these two features will be included in the next update
The estimated release timeframe for that update
Additionally, we would like to ask for your guidance on another matter. We have applied to Plivo, but despite multiple attempts over the past month, we have not received any response from them.
From your experience:
Is this normal for Plivo?
Is there a recommended contact method or escalation path we should follow?
Or would you suggest an alternative provider in the meantime?
Thank you in advance for your clarification. This information will help us finalize our rollout and marketing plans.
Best regards,
I dont know which features are you referring to? We are regularly updating the item. We have mentioned on the item page regarding whats coming next.
Regarding plivo, we have no idea about their approval process. We have been approved in just 2 days. You can contact them for this.
Hello,
Thank you for your response.
To clarify, the feature we are referring to is SIP Trunk support. This is one of the key items we are currently waiting for and the main reason we asked about the update timeline.
We have reviewed the “what’s coming next” section on the item page; however, we would like to confirm whether SIP Trunk is planned to be included in the next release, and if so, the estimated timeframe for that update. This information is important for us, as it directly impacts our launch and advertising plans.
Regarding Plivo, thank you for sharing your experience. We will try to reach out to them again and explore alternative contact or escalation options if needed.
Looking forward to your clarification.
Best regards,
SIP trunk plugin will be launched as separate item and is planned to get live by next week.
Thank you for the clarification.
That’s great to hear. Launching the SIP Trunk plugin as a separate item and having it planned to go live by next week works well for us. We will align our planning accordingly.
Appreciate the update and looking forward to the release.
Best regards,
As a suggestion, you could implement support for message management on WhatsApp, allowing agents to both send and receive messages, thus offering two support channels: messaging and phone calls. Thank you!
Thanks for the suggestion however our focus is on calls for now. We will surely add whatsapp message after call in future updates.
Improvement suggestion: When navigating to Admin → SEO Module → Structured Data → Product Schema, updating the details triggers an error. Additionally, during page load the system briefly displays “Agentlabs” before switching to the custom brand name, which looks unprofessional for a SaaS product. I hope it will make the product more amazing.
We have resolved SEO saving issue & logo loading issue and will be updated tomorrow.
Additionally, the embedded widget on client websites displays “Powered by Agentlabs”, which completely undermines the product’s branding. This should be replaced with the configured brand name.
i will get this checked & fixed. Thanks for your valuable feedback
