As long as the popup was optional, AND it would disregard other invoices on the ticket that are already PAID - I love it!
This could be more easily done by having a default "MSRP" price and then having a price "tier" called "Student" or "Senior". There's another post already covering this, and it has more votes: http://feedback.repairshopr.com/forums/165658-general/suggestions/17572705-more-then-2-price-tiers
@Dan: This is a duplicate of a post already getting traction for the same idea. Please redirect votes here: http://feedback.repairshopr.com/forums/165658-general/suggestions/13855287-discount-on-an-invoice-show-original-price
This would be solved with my feedback post which is already highly voted for. Please redirect votes for this to here: http://feedback.repairshopr.com/forums/165658-general/suggestions/14880219-discount-reason-codes-and-report
AGREED! Please add an option to show "total discounts" below the "subtotal" line at the bottom of the invoice! Example:
Item 1 - Price $100 (Discount $50) = Total $50
Item 2 - Price $75 (No Discount) = Total $75
Item 3 - Price $40 (Discount $10) = Total $40
Subtotal (before discounts) = $215
Discounts (listed above) = $60
Tax (FL Exempt) = $0
Total (after discounts) = $155
This is a duplicate of this post: http://feedback.repairshopr.com/forums/165658-general/suggestions/13855287-discount-on-an-invoice-show-original-price
Please redirect votes there...
PLEASE! We also want to use this for a surcharge when customers pay big invoices with a credit card. We want to add 2.75% or 3.5% to the invoice total but can't use the discount item for this because it rounds to whole numbers! PLEASE?
@Ilan: Rockin! I'm out of votes so thanks for getting this one off the ground!
@Seby: Square is a flat-rate of 2.75% for CP and flat-rate of 3.5%+30cents for CNP. We are currently using TNBCI and pay interchange+.05% which totals anywhere from 1.50-2.05% of our gross (including the Auth.net gateway). Square WILL offer anyone with high volume (over $25k/mo) a CUSTOM RATE if you provide them with 1-2 years of past merchant statements. They offered us 2.0% flat-rate for CP and said they would further adjust it after a few months of seeing the card types we often get.
@Troy: Square is by FAR the easiest and "prettiest" merchant company around. I've been with 3 different companies now and miss how simple it was working with Square. Process $50k in cards last month - my cost was 2.0% of that - DONE! No fine print, no interchange fees, no gateway, no per transaction fees - just a flat-rate. Apparently WooCommerce and another [FILTERED_WEBSITE] has figured this out. Could you speak with the rep I emailed to you?
Just received another communication from Square's business consulting team. They are VERY INTERESTED in getting RS to work with their PC API integration, in addition to the (already integrated) iOS API. I provided the rep "Haley" a link to this post and told her to reach out to you guys @RS @Troy @Robert.
Agreed on this!
We recently got a call from square offering us custom rates which are very competitive to our current interchange-plus rates, and Square's simplicity is really worth switching. They said it looks like RS currently uses their "Register-API", but they also have a Web-API allowing payments to process on non-iOS hardware (ie. a PC). It would work just like Authorize.net and Vantive - which is what we want.
This is totally a no-brainer, except, there are tons of implications. If we allow some HTML, what is the subset? Most of the formatting stuff? colors?
Once colors and sizing is allowed, does that carry through to the mobile view, to the template system?
It would take 5 minutes to put a wysiwyg on the ticket comment – but much much more consideration to do it really well in all the places ticket comments show up.
Keep voting and commenting..
@Troy: So can NOTHING be done? We're at square one right now, so ANYTHING would be an improvement... Surprise us?
@Troy: How about exactly what I mocked up? With the exception of two changes in the comments, a fairly large number of votes have been cast following my mocks. The biggest question is rather or not to keep two separate comment boxes; which IMO wastes space and is unnecessary when a [blank] drop-down would force the delivery audience to be specified; therein eliminating incorrect delivery.
As for the HTML subset - how about exactly the same as used in templates on the backend? I think it's obvious that the majority of RS users don't want flashy colors and cat emojis; but instead want some BASIC features like bold, list bullets, and font sizes. As you've said before, why not deliver a feature that is a not-perfected improvement, and then perfect it over time - like everything else in RS seems to be?
@Chris: The default would be NOTHING so it would be required to set it as Public vs Private
@RS: Any updates on this? Almost 2 YEARS with NO UPDATES of any kind?!
I still consider this to be the best solution to this feedback request. Please everyone provide some feedback if you think differently, or remind @RS we really have wanted this for over a year. http://i.imgur.com/AicNdtP.png
@Everyone: I've just finished up my mock-up of the actual view of ticket updates. It's a rough draft only because I'm busy - but I really wanted to let everyone see:
This would cover the following:
Was the ticket update emailed or not?
Who received the email?
Was a sub-contact or CC emailed?
Sending to the tech only and not the customer.
Colors defining who was messaged and in what delivery fashion.
Is the ticket comment public in the portal/PDF?
Ability to edit private (non-emailed) notes.
Ability to change which tech receives the email.
@Chris: With my mock-up, the default settings in the drop-downs for public/private will be [BLANK] which would require techs to always specify how and to whom the message is shown to. Although this is manual (which I hiss at the thought of), I think every ticket update is unique and some need to be emailed to the techs only, others to the customer only, others to no one at all, etc. With this setup, techs will always have the question in their mind ("Who needs to get this message?") before actually submitting it. I think this will result in customers getting only the relevant emails they need, and not getting bombed with unnecessary updates.
Further, it provides more power to email staff-only, without sending the customer unimportant updates. I tried to design the mock-ups to add as much power/features as I could, while being as space saving as possible. Not sure how else we'd have room for signatures, attachments, canned responses, Cc/Bcc, and WYSIWYG with two comment boxes. Really came down to not wasting space (duplicate text boxes) if possible. Your thoughts?
@Troy: Is there any update on this topic? This isn't necessarily a big deal in itself, but it is a prerequisite for updating/fixing other modules in the app, including things like:
- Ability to identify/differentiate between comments that were emailed vs not emailed
- Editing private ticket comments, or public comments that were not emailed
- Audit tracking who exactly was emailed (if multiple contacts exist)
Completely agreed with all of these update suggestions. I have created two mock-up variants of a solution that allows for all of these requests to come alive AND MORE! Some of the features in this include:
Add assigned contacts (linked contacts under that customer) as a CC email
Add external contacts (not in your database) as a CC email
Eliminates the side-by-side duplicate text field boxes
Adds all standard WYSIWYG features (already being used in templates editor)
Allows signature to be inserted (just like canned responses)
Allows files to be attached via drag-and-drop into the message
In addition to all of that, my BIGGEST idea is to upgrade is the comment DELIVERY AUDIENCE and VISIBILITY METHOD. Right now, there's just Public and Private, with the option to not email on Public. These are only 3 delivery scenarios out of a total of 6. We need to be able to specify exactly WHO gets the message, as well as HOW the message can be viewed. Here are the details…
What we have:
Public comments emailed to everyone (both customer and tech)
Public comments emailed at no one
Private comments emailed to no one
What we don’t have:
Public comments emailed to the customer only (tech doesn’t need informed)
Public comments emailed to the technician only (customer doesn’t need informed - rare)
Private comments emailed to the technician only (communication about problems/customer)
This is the ANSWER! It solves ALL of the issues we have! Let’s make it happen
I'm actually in the beginning stages of mocking up a complete revamp to the ticket comments section. It covers a lot of the same topics mentioned here, as well as defaults that force users to specify important details like: whether the comment is emailed or not, as well as specify what the comment type is. Too often our users are emailing a comment without changing the comment type.
I expect to have this done in the next week or so. Stay tuned.
Votes for this might help: http://feedback.repairshopr.com/forums/165658-general/suggestions/17572705-more-then-2-price-tiers
Copying my post that had less votes and redirecting new votes to here:
Pricing Fields for Inventory/Products: MSRP/Retail, Sale/Override, Customer Price, Company Cost
There are more $$$ fields than just price and cost for most product and inventory items. Obviously, Price and Cost are both equally important, but there's also other factors that heavily influence purchasing decisions in the retail and service industry. The two main ones that come to mind are MSRP/RETAIL pricing and SALE/DISCOUNT pricing.
What do customers hate the thought of? Paying FULL PRICE for something! That's why you /show/ them the msrp/retail price, so they know they're NOT paying it. On top of just showing the customer this information, it's infinitely helpful being able to reference these details when working with inventory. We're constantly having to look up the msrp of products we sell, because we don't have a defined field to put that information in on the product page in RS.
What do customers LOVE the thought of? SAVING MONEY! That's why if you are offering products/services below msrp, you want to /show/ the customer how much money you're SAVING them. Adding the "Sale" price field would both make your customer happier (on the psychological side) and would allow us to more easily have sporadic sales and discounts, where we can easily make a temporary price change to a product (including non-serialized inventory) and then change it back without losing our normal reference price.
Simple, simple, simple implementation: Just add "MSRP/Retail Price" and "Sale/Discount Price" fields to the already existing "Customer Price" and "Company Cost" fields in products. MRSP/Retail would just be a reference point for customers and staff, and Sale/Discount (if set) would override the Customer Price. These additions would NOT clash with existing settings, or change anything RS users currently have setup, if the fields are added and start out as blank.
* Call the idea police! We've got ideas coming from left and right over here! *
Along with this, it would also be very helpful to have an "MSRP" price. This would be mainly for internal reference, but would also show on estimates/invoices (with a strikethrough) to show the customer how much we are below retail (even if it's only like $19.99 MSRP compared to $19.95 retail). Perceived value matters to the customer!
In all, there should be a customizable number of pricing tiers (1, 2, 3, etc) and we'd be able to "label" the tiers for reference (MSRP, Retail, B2B, Partner, Wholesale, Employee, Cost, etc).
@RS: This appears to be a duplicate of a similar idea. Can these be merged? http://feedback.repairshopr.com/forums/165658-general/suggestions/5531550-automatically-calculate-markup
Just realized the 'markup percent' part of this (the hard part) is done, but not the 'gross profit margin'. I really love how you integrated the markup percent as a green-popup field when you tab between the cost and price. Can you just add the gross profit margin as a value right next to the markup percent? Maybe even in it's own blue-popup field right next to the green-popup field for markup percent. It's just a simple subtraction equation. Then you can mark this as resolved :)
Margin is almost always a
. I think you can mark this as completed.
This idea is a duplicate. Please redirect votes here: http://feedback.repairshopr.com/forums/165658-general/suggestions/5531550-automatically-calculate-markup