I would like to see RepairShopr integrated with the Vonage Desktop Connect app. I have tested this with our vonage install and got this to work. Here is the routine I used.

Download the Vonage Deskptop Connect client to your desktop. I used Google Chrome and it worked.
Make a test call and make sure that you do not have pop-ups blocked.
Switch over to Repairshopr and go to App Center and click on the Free PBX integration. Generate a token for your company.
Switch back to Vonage Desktop Connect and go to the settings area.
In settings click on the Web Launcher tab.
In Web Launcher I used the following variables.
URL - I typed in "RepairShopr" (note: do not use the quotes)
In the box next to the name put this URL in minus the quotes - "http://uniquedomainname.repairshopr.com/api/callerid/?did=[NUMBER]&token=tokenfromfreePBX"
Now click the Add button. You should see the URL you just built in the box below the Insert button.
Check the box for Incoming Calls and then click save.
Test by making a call into the system from a customer record associated with you calling from a number on your record.

You want to mark 'COMPLETED' to a huge percentage of ideas in this feedback forum? Open the Zapier floodgates.

There are some conversations around here talking about getting Zapier to do stuff with other things like Contacts, Slack, etc. While nice... those things only scratch the surface and only help those of us that use those specific services.

What about using Zapier to integrate Repairshopr WITH REPAIRSHOPR.

The possibilities are absolutely endless.

Trigger:
- New ticket created by ABC Company.

Possible Actions:
- Email the customer saying a new ticket is opened. Right now, if email is selected, when creating a ticket the customer gets the same exact email as if you just wrote an emailed comment. There's no indication that a new ticket was opened. There's no way to formally acknowledge the ticket was received and say some things that would manage the customer's expectations. 'we respond to tickets in the order we received them in. we're open from 9-5.' etc. etc.
- If there's an overdue invoice, send an email to the tech who opened the ticket alerting them.
- Does ABC Company have a certain SLA / Contract / Warranty ? Change ticket priority to HIGH. Send email to the team that handles high priority tickets.
- If it's a certain type of customer, automatically fill in some custom fields.
- Automatically create an estimate based on the issue type.
- Automatically add additional addresses to the emaill address notify box.
-

Trigger:
- Ticket Resolved
Actions:
- Create a warranty / contract / SLA if certain conditions are met.
- Send email notice to customer that their ticket has been closed.
- Create reminder for tech to follow up with a phone call if certain conditions in the ticket are met.
- Create follow up or rework ticket if certain conditions are met.
- Automatically assign ticket to specific person (supervisor) if ticket was closed by a specific person. (hell, you could make a 'Under Review' ticket status that would handle this better)
- Automatically generate an invoice of anything that is unbilled.

Other random things:

- Automatically send email back to customer if they respond to a ticket owned by someone who is currently in a meeting.
- Automatically create reminders / emails / tasks if tickets get stale.

I will personally fly out to wherever the hell Troy and the gang are and I'll buy the whole team a delicious meal at a fine establishment like Applebees. And drinks. oh there WILL be drinks.

For a reference point of what services utilize this really well, check out www.pipedrive.com I just started playing in there and it's INCREDIBLE. I can have pipedrive zap itself with all sorts of things automating the whole sales process.

The way I run my repairshop is to try and book appointments for people to bring their device in for repair - more so for repairs to mobile devices where people require a quick turn around for example.

Using the appointments feature would be ideal for this but here is some things I think would be better

1) Allowing different opening times on a "per day" basis. My weekend opening times are different to during the week.

2) Ability to change the default appointment length to say half hour rather than an hour as it currently is.

3) On the form the customer fills out for the appointment, they should be able to choose their device type, a title of the problem (ticket title) and a description of the problem.

I currently use the Due Date field within a ticket as a way to track the day and time I am expecting a customer to arrive but this would be suited for its obvious reason of when you expect to complete the ticket.

Hope the feedback helps and can be taken into account.

European General Data Protection Regulation (GDPR) compliance

Anyone one with clients in Europe will need to ensure compliance for GDPR before May 18.

1: Amazon's cloud platform will be backed by certification for the standards required and or having a separate uk based server should bring it closer.

2:Then prominent "opt" in boxes clearly labelled for consents and automation's to seek 12 month renewals to items such as marketing. You have already a means to enable us to opt out a client from marketing.

3: A feature to "part delete a client" - Archive (so still accessible)

4: Reporting of each user and searches/access to data logged/stored.

5: Alert of data breach

These are just a few i could think and no doubt has missed many considerations. Hope you are already working on solutions to enable us in Europe to continue with you. From what i understand the US is having a revised data protection policy too which will likely be closely built to the new standards being adopted in many places.

Fingers crossed, if you need access to more information on GDPR and what would be involved let us know.

Thank you! Joe.

Would be nice to be able to split off a comment or series of comments onto a new ticket from an existing one. Sometimes, when working on a project, one thing will lead to another which ends up being a new and totally separate project from the existing ticket. But there's no good way to quickly copy the documentation from the existing ticket to the new one. Being able to start a new ticket from an existing one and then select any comments or items (timer entries, charges, etc) to be moved over into that new ticket would do wonders for more complex workflows.