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.

I have been subscribing to RS for nine months but am still struggling to go live and make the switch from my current system. I need to ensure RS can do everything I need - or else be confident I have a satisfactory workaround before I go live. RS has some great features and major benefits but also some worrying flaws or omissions (albeit relatively minor) which I must be confident can somehow be resolved and tested in order to pull the plug on the old system.

It is extremely reassuring to see that I can export ticket data to CSV – Fantastic! This could really help should I discover cases where RS does not do quite what I need.

But is there any means of importing tickets as is possible with customers and inventory items? I can see many possible benefits to this - though at this point the first would be enable loading data from my current system in order to run both in parallel for thorough testing.
regards, David

When a ticket is created, regardless of how (email, manual, etc) , there should be a specific New Ticket email template that is fired off.

If the "Don't Email" checkbox is removed during manual ticket creation, an email is delivered to the client using the ticket comment template which can be very confusing for the end user.

When a ticket is opened, we want our customers to be notified that, in fact, a ticket was JUST opened. We can then write up the New Ticket Email template to cover things like the ticket subject, ticket description, a short description of our responding procedures, our hours etc.

Having a dedicated template for new ticket emails, as well as a way to automatically fire them when a ticket is opened will go a LONG way towards managing customer expectations.