Share your use case and provide as many details to support your idea as possible:
Id love to see a rate calculator widget. For example, If Im working on a limo service website, and I need a rate for NYC to JFK airport. Thats x miles @ ($20) mile or something = [PRICE] that I can plug in to a payment portal and the custom can pay directly instead of having to do it all manually.
That’s a very interesting suggestion, thanks a lot, @Martha_Lynn!
We’ll try our best to consider your idea in the future, and I’ll make sure to post here if I’ve got any news ![]()
Thank you for your help and for joining the community! ![]()
This would be EXACTLY what a couple of my clients are after right now, and actually myself included! I just discovered UCALC have this, so I’m going to have to go with this for now. But would be much better to have this under my existing ElfSight subscription. I’ll keep an eye on this thread!
@Spacetime_Health thank you very much for your comment, and welcome to the community! Really happy to have you join ![]()
Well yes, the idea really sounds nice, thanks a lot for mentioning the service you’re going to try, it’ll be helpful for the devs to check out.
By the way, feel free to let us know what features you’d want to see in such a widget exactly, it will be a great help, too ![]()
Thanks a lot for your help, I’ll be happy to see you in other threads on our forum!
Thank you, @Helga !
There would be a load of ways to configure it, for example Ucalc has templates for loan estimates, taxi fares, etc. For me personally, I’m a composer and I often charge per minute of finished music. So would be SUPER handy to have a way (with ElfSight) to have a slider that prospects can adjust to their specific requirements for their project, e.g. 25 minutes of music, ready in 2-3 weeks, and get a quote on their screen, pay right away and schedule an appointment.
Excited to see if this is something the devs at Elfsight could do!
@Spacetime_Health a huge thank you for the details, I got your idea!
Love the use case you’ve described, I also hope we’ll be able to give such a widget a go, cuz I believe it would be a great solution for a lot of users ![]()
I’m afraid I cannot say anything about the timeline as our devs have a roadmap they try to stick to, but I’ll make sure to post here in case of any news ![]()
Thanks again for your help, much appreciated!
Hi friends! I just wanted to drop by and share that we’ve recently released a Calculator widget! You can give it a try here: https://dash.elfsight.com/apps/calculator
While it doesn’t support your specific use case just yet, it might still be useful for you, so feel free to check it out ![]()
We’ve also moved your request to the dedicated category and will get back to you if we have any news or progress ![]()
The other option on this would be Excel integration. Then you could just input your info into Excel and do what you need.
Hi there, @Carlos_Scarpero ![]()
Thank you for the feedback!
We have a separate request for the Excel integration and all the updates will be posted here
- Excel integration
I really like this idea because a rate calculator would make things much easier for service businesses that need to give quick pricing without long back-and-forth messages. Having options like distance, time, add-ons, and the ability to connect the final price to a booking or payment step would make the whole process feel smooth and professional for customers. It would be useful across many industries, and even when researching service pricing models such as those used by companies like Bnlboston Limo it shows how helpful instant estimates can be for customers. It would also be great if there were ready-made templates for common services so people could set it up faster. Do you think this would need automatic distance calculation through maps, or would a manual input field work for your case?
Hey there @user33334 ![]()
Many thanks for sharing your feedback with us!
We’ll keeo this idea in mind and see for more votes from other members. As for your question, it’s hard to say which option would work best in this case.
However, if this idea becomes popular, we’ll try to consider both options ![]()