SemiCircuit
My feedback
4 results found
-
291 votes
We were prepping to start this and realized the narrow-scope version we were willing to commit to would just make most people upset that we “built it half way” – but we aren’t in a position to compete with docusign/etc and spend a year building a proper solution.
We could more easily help make a zapier/webmerge solution work if you wanted some automation, if we get a lot of feedback supporting that idea I’ll make it happen pretty quickly.
An error occurred while saving the comment An error occurred while saving the comment SemiCircuit
commented
@Troy
as its now 2018...any updates for this?
SemiCircuit
supported this idea
·
-
27 votes
You could use zapier to send gravityforms into RepairShopr leads as structured data – once we add the new customer action we’ll probably mark this as complete via zapier.
An error occurred while saving the comment SemiCircuit
commented
seriously, this is one of those necessity features, if an adequate internal solution is not available. It certainly should have priority over some of the 3rd party service provider integrations. If not gravityforms, then ninjaforms or something similar.
Custom forms is a fundamental feature for almost everyone operating a repair/contract based business and custom forms have certainly become a fundamental feature for websites.
Additionally, a webform plugin integration removes the burden of creating forms from repairshoprs plate. No more need to respond and consider every users form needs. You simply create your base forms and then direct all custom request to your forms integration. I know that you all have invested time and energy into creating the custom widgets. However, those widgets are rigid and far from fully functional. They clutter the custom data sets with forced data fields that are not desired, they fail to offer the level of customization needed (as a custom widget) and they require more effort than necessary to work around their haphazard creation.
it feels like repairshopr has grown to fast and too much was attempted without fully fleshing out some of its best and/or most needed features that are already partially implemented. I can see where repairshopr is trying to get things cleaned up with the new UI, but it really feels like your devs could benefit from dumping some of those partially working internal features, consolidating your focus and allowing use of more flexible modules. Custom forms was obviously a large undertaking that hasn't really succeeded. However, a solution already exist that is fully ready and thoroughly tested; ie. webform plugins. No need to reinvent the wheel.
zapier is not the way forward for this feature at avg cost of $1.00 per zap ($1.00 per data conversion). That would get massively expensive, very quickly. Zapier is more for rare use cases that dont merit direct integration. stating zapier capability should mark the job as complete on a feature that solves an issue that effects nearly the entire user base is a disservice to your users. One shouldnt have to pay someone else to fix fundamental flaws in the primary app. Im not trying to offend with the flaw statement, but in opinion form creation is flawed and obviously others agree.
Just as an fyi, is the reason I left XERO and switched back to quikbooks, as XERO felt and still feels that negative inventory is not their responsibility and that their users should subscribe to 3rd party service providers to cure that need at an added cost of 75-125 per month. Please dont become that app maker. One can say that your still paying for gravityforms, but comparatively its much more cost effective. However, I do prefer formNinja as it starts out free for about 80% functionality and then allows users to add-on deeper customizations as needed.
SemiCircuit
supported this idea
·
-
44 votesSemiCircuit
supported this idea
·
-
4 votesSemiCircuit
supported this idea
·
@troy.
Ive said it before and i will say it again. Under gpl, you can purchase the bulk license of wpesign/approveme and integrate and distribute to all subscribers. Perfectly legal under gpl.
Then you only need to make an easy api integration between wpesign app and repairshopr for document creation, distribution and storage/link with repairshopr. WordPress is already the officially supported website.
Users would then be able to create and manage their own signature forms and signing devices which massively eases the support required from your coders for managing both the code and the hardware pertaining to esign