Michael Leone
My feedback
11 results found
-
36 votes
For our Domo subscribers we have pretty much added every report that’s been suggested if we have the data to accomplish it.
This will probably not get worked on for anything that is possible in Domo – if you haven’t tried it, I would recommend it – and let us know if there is a report you want.
Making a “report builder” is a major project, which is why we bought Domo even though it’s the most expensive piece of software our company has bought.
Michael Leone
supported this idea
·
An error occurred while saving the comment -
73 votes
An error occurred while saving the comment Michael Leone
commented
Silly question... Why do you guys have your invoices copied to a folder at all (Google or otherwise). They are all sitting there in Repairshopr, why duplicate them and clog up your cloud storage?
Michael Leone
supported this idea
·
-
24 votesMichael Leone
supported this idea
·
-
20 votes
An error occurred while saving the comment Michael Leone
commented
We have a set of ticket types starting with "Lead - " for example, "Lead - iPhone Repair". We convert ALL LEADS to what we call "Lead Tickets" (which are tickets with the "Lead - XXX" ticket type). This can then be used for ticket automation or to manually progress the ticket through different lead stages (using custom lead statuses), follow up emails etc.
-
47 votes
An error occurred while saving the comment Michael Leone
commented
Agreed. Tear apart inventory (the ability to break an item into inventoried "used" parts and make whole items out of individual parts), linked to purchase order AND to customer purchases is desperately needed. But this needs to be part of an entire refurb module, the "Customer Purchases" module is ridiculously limited (its really just a list of things you have bought, that cant even be sorted or filtered!). A refurb module needs to be created that allows purchasing, internal ticketing (including allocation of refurb jobs to techncians and the ability to add parts to the refurbs), and then conversion to inventory. The way RS deals with serial numbers also needs reassessing. Customer purchases serials can be converted to inventory items, but the serials are seperate from the ticketing system (i.e. if you sell an inventoried serial to a customer, that serial doesn't show as an asset on that customer). Serials should flow from "Customer Purchase" to Refurb Ticket to Inventory item and then to a customer when the item is finally sold!
-
4 votesMichael Leone
shared this idea
·
-
1 vote
An error occurred while saving the comment Michael Leone
commented
Hey Jordan! I am the boss of my store and we have a similar system. We solved it by adding a ticket status "Approve order" (or you could use "Order part") and then on the bosses ticket list, make sure this status is being shown (we use custom "Saved searches" for different staffs ticket lists to make sure each staff member sees the status types that they need to only). The boss just has to keen an eye out for any jobs that pop up on the ticket list with status "Approve order"
-
1 vote
An error occurred while saving the comment Michael Leone
commented
Thats an easy one to create using Repairshopr API mate. Grab the sample leads web form (have copied it down below for you) and pay a cheap programmer from upwork.com to make a slide out webform out of it for your website. Here is the code, give them this and tell them you want a slide out widget, piece of cake for any most web programmers:
<?php
if( $_POST["name"] )
{
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL,"http://YOUR_SUBDOMAIN.repairshopr.com/api/v1/leads?api_key=YOUR_API_KEY");
curl_setopt($ch, CURLOPT_POST, 1);
// example splitting a name field into first and last name bits
$pieces = explode(" ", $_POST['name']);
$last_name_parts = array_slice($pieces, 1); //each word
$last_name = implode(" ", $last_name_parts); //combined words, with space separators
// build up the lead post data here, you can combine fields into the data you are sending
// see subject for an example
curl_setopt($ch, CURLOPT_POSTFIELDS,
http_build_query(array('first_name' => $pieces[0],
'last_name' => $last_name,
'email' => $_POST['email'],
'phone' => $_POST['phone'],
'ticket_problem_type' => $_POST['problem'],
'city' => $_POST['city'],
'ticket_subject' => $_POST['device'] . " Pri: " . $_POST['priority'],
)));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$server_output = curl_exec ($ch);
curl_close ($ch);
//redirect to thanks page
header("Location: /thanks.html");
exit();
}
?><html>
<body>
<form action="<?php $_PHP_SELF ?>" method="POST">Name: <input type="text" name="name" /> <br>
Email: <input type="text" name="email" /><br>
Phone: <input type="text" name="phone" /><br>
Problem: <input type="text" name="problem" /><br>
City: <input type="text" name="city" /><br>
Device Type: <select name='device'>
<option value="volvo">Volvo</option>
<option value="saab">Saab</option>
<option value="mercedes">Mercedes</option>
<option value="audi">Audi</option>
</select>
<br>
Priority: <select name='priority'>
<option value="p3">Low</option>
<option value="p2">Medium</option>
<option value="p1">High</option>
</select>
<br>
<input type="submit" />
</form>
</body>
</html> -
4 votes
An error occurred while saving the comment Michael Leone
commented
I like the sound of this too. Not an urgent issue but certainly something to keep on the board down the road?
-
185 votes
We recently added multiple addresses, more to come.
An error occurred while saving the comment Michael Leone
commented
@Ryan - Agreed mate (with your original, well considered, suggestions), i'll add my votes... Though i'm a little worried they may be wasted... It seems slightly concerning that these (fairly significant) issues are still hanging around after all this time, especially considering the significant feedback and support shown by Repairshopr users?
@Troy - G'day Troy, I understand your comment to Ryan - "We have to balance complexity, dev time, and weigh the pain on all this stuff", this is absolutely fair. But your last comment about semi-implementation could really do with a little more detail? Can you perhaps take a moment to explain (for the benefit of all the RS users that have support this suggestion) your current thinking (in a a bit more detail) on these issues and/or ideas/concerns/constraints/timeframes/etc with Ryans originals points?
Cheers,
Mick - ITSGC
-
3 votesMichael Leone
shared this idea
·
The DOMO integration leaves much to be desired...
- For one its heavily limited in that the only data tables you can work with are those provided in the pre-built "Cards".
- You can't build reports from scratch... And then, lets say you pick an existing card, drill down to the data and modify the filters etc, YOU CAN"T SAVE IT. You have to re-build your report overtime (which is useless for ongoing weekly/monthly reporting as far to time consuming). You should be able to save you new "Card" for constant viewing on the dashboard somewhere...
- A BIG Glitch is that the report for Sales By Item only works for items that exist in inventory at the root level. I.e. Categorised inventory items at all levels of nesting don't show up! SO for us, with all our inventory items categorized, DOMO says we have no items in the Sales by Item report. :(