If you are using Angular JS, load this lib and it is a single line of code.
 https://github.com/szimek/signature_pad


On Tue, Aug 25, 2015 at 9:29 AM, Simon Westlake <
[email protected]> wrote:

> Yeah, I saw that one a while back. Looks like a good one. I used a
> different one in Powercode when I built the signature/contract stuff in
> there, but I think the one you linked is a lot better now.
>
>
> On 8/25/2015 9:19 AM, Chuck Hogg wrote:
>
> I rolled my own using HTML5 and SVG.  Here's some source, there are
> various options and different ways to do it.
> https://github.com/szimek/signature_pad
>
>
> Regards,
> Chuck
>
> On Tue, Aug 25, 2015 at 9:16 AM, Simon Westlake <
> [email protected]> wrote:
>
>> You roll your own digital signature capturing interface, or are you using
>> Echosign or something similar?
>>
>> On 8/25/2015 7:51 AM, Chuck Hogg wrote:
>>
>> I have digital contracts setup with Platypus.  Installer hands his laptop
>> to the customer, they fill out the information, select rate, etc., and sign
>> with the mouse on the laptop.  We do everything by MAC address, so that
>> information is input into their rate plan as a service, and we have
>> mechanisms in place to provision speeds based on rates when the SM
>> authenticates to the tower.
>>
>> Regards,
>> Chuck
>>
>> On Mon, Aug 24, 2015 at 11:30 PM, Brett A Mansfield <
>> [email protected]> wrote:
>>
>>> I'm with ya. I'll sign up for that.
>>>
>>> Thank you,
>>> Brett A Mansfield
>>>
>>> On Aug 24, 2015, at 7:21 PM, Sterling Jacobson <[email protected]>
>>> wrote:
>>>
>>> Ok, I’m going to tell you all what I want to program.
>>>
>>>
>>>
>>> I’ve been wanting to do this for a long time now, and I hope to start it
>>> this year (with Platypus integration).
>>>
>>>
>>>
>>> I want a simple web site AND an app that pretty much does the same thing.
>>>
>>>
>>>
>>> The interested customers goes to web site and downloads the app or
>>> creates an account online (preferably logging in with Faceboog/Google etc
>>> button).
>>>
>>>
>>>
>>> That starts the ‘step’ process.
>>>
>>>
>>>
>>> The App/site pretty much takes over from there.
>>>
>>>
>>>
>>> They input their information, the app tells them what’s available.
>>>
>>> They chose what they want and digitally ‘sign’ the agreement.
>>>
>>> That kicks off the App/site to notify them that install is pending.
>>>
>>> The crew, using the SAME App/Site in ‘installer’ mode gets notification
>>> that there is a pending install.
>>>
>>> They have put in their availability, so one of them can accept the task
>>> and is now responsible for completing it on time.
>>>
>>> If this step involves the customer then they will have already put their
>>> availability on the App/site and the customer will chose from an available
>>> time.
>>>
>>> In my case there are several pre-steps for installing fiber with two or
>>> three different crews, so this gets passed around the members or crew
>>> chiefs by the App/site until it’s complete.
>>>
>>> The customer get’s notified by the site/email and/or App during the
>>> various stages.
>>>
>>> During installation, the installer can ask the customer to finalize by
>>> going to the App/site and paying etc. etc.
>>>
>>> Then it turns on the internet, the installer leaves and the App/site
>>> goes into Support mode.
>>>
>>> Now if the customer has an issue they can report it through the site/app
>>> via phone or tablet if their internet isn’t working.
>>>
>>> Again from a pool of available tech support people, it can be accepted
>>> and acted upon.
>>>
>>> Also if there is a network wide problem affecting several, the App/site
>>> can alert with ETA.
>>>
>>>
>>>
>>> All of this technology is basically SQL database stuff with some middle
>>> software to tend to events.
>>>
>>> Nothing hugely complicated, and can integrate with Platypus or another
>>> CMS/Billing at the database level easily.
>>>
>>>
>>>
>>> Once developed, should be highly adaptable for all of us.
>>>
>>> And basically reduce staff required to track all of this crap to
>>> virtually none.
>>>
>>>
>>>
>>> Who’s with me??
>>>
>>>
>>>
>>> *From:* Af [mailto:[email protected] <[email protected]>] *On
>>> Behalf Of *Ty Featherling
>>> *Sent:* Monday, August 24, 2015 3:54 PM
>>> *To:* <[email protected]>[email protected]
>>> *Subject:* [AFMUG] Platypus + paperless
>>>
>>>
>>>
>>> We are trying hard to reduce/eliminate all of the data entry of entering
>>> new customers after installation. Currently they fill out a paper contract
>>> form, collect payment for the installation, and turn that in at the office.
>>> We then process them individually using the customer wizard to create a new
>>> customer in Plat and then manually fill in all of the data, create invoice
>>> for installation, and set their billing rates. We would much rather have
>>> the installer fill all of that same data from the contract out in digital
>>> format that can then be imported somehow into platypus to do almost all, if
>>> not all of the customer creation steps. As we grow faster and faster the
>>> paperwork is getting to be a serious load.
>>>
>>>
>>>
>>> Has anyone else solved this problem with Platypus? If not does anyonw
>>> know of an avenue I might look into? We hope to turn this solution into a
>>> way for the customer to sign their contract digitally but that is secondary
>>> to the main task.
>>>
>>>
>>>
>>> -Ty
>>>
>>>
>>
>>
>
>

Reply via email to