Agreed! Actually, my idea was to include the current tech first name, followed by a dash, followed by the business name. Example: Ryan – Pinellas Computers
Would my recent comment on this post on July 1 with a mock up image solve this?
Perhaps this topic would be a better solution for you?:
Would you agree?
I really think it's better to have a ticket for this. That way there can be an SLA and reminder to the tech when parts are taking too long to arrive, and you can easily keep the customer alerted when the part is ordered and received.
What is the downfall of using a ticket? We have a separate ticket type call "Part Order". Then we make comments like: Initial Issue, Parts Order, Parts Arrival, Completed, Contacted.
Yes! This is very annoying, especially for big chain accounts with multiple locations in printers that are always being added.
That’s a REALLY good idea.. hadn’t thought of it, but I’ll see if I can get that worked in to the system at some point soon.Ryan (CTO, Pinellas Computers) supported this idea ·
I'm hating our current LAN-based time clock more and more every Tuesday when I'm doing payroll. We constantly have tech's forgetting to clock in or clock out, and the records at the end of two weeks are almost always a mess.
This time clock enhancement would really be valuable, not only to help tech's remember to clock in/out, but also to eliminate yet another third party program we're stuck with, as of right now.
Any idea when this idea will be on radar to implement? It sounds relatively simple to add prompts based on specified times of day. Thanks!
This was totally MY idea, but I didn't voice it quickly enough ;) Here's my additional information to enhance the idea:
Several times a week, one tech or another will forget to clock in or clock out. It's easy to get sidetracked when you come in the door, and hard to remember after a long day. My idea is to have some place in the Employee Settings where you can set the "Normal operating hours".
Then, if a tech accesses ANY ticket/invoice/estimate/page on RS during those hours, it will prompt them with a popup that says something like "Do you want to clock in?" (as long as they are not already clocked in).
Same thing goes for the end of the day: If your hours normally end at 6pm, you can have the system prompt you "Would you like to clock out?" if any ticket/invoice/estimate/page is accessed after the time set as "end of the day". Even better if it would re-prompt users 5 minutes if they ignore the first prompt. Kind of a "snooze" feature.
This would not only help employees remember to clock in and out, but would also help keep them close to their pre-scheduled hours for the week. I've seen plenty of industries where employees try to "milk the clock" or "didn't realize it was that late". This would help both techs and admins.
With a feature like this enabled, we would definitely switch off our current LAN based time clock program. Especially with the hopes of integrating the time clock records into reports to calculate labor costs (whoops, did I say that out loud?)
I agree Chuck, this would be a nice and simple feature to add. Even better if it could be added as a start to a bigger picture - multi ticket invoicing. Not saying it needs that in the first version, but it would be a start to the idea.
Are you currently checking in each piece of equipment as individual assets? If so, you can simply set triggers in Google Cloud Print to automatically print asset labels when tickets are created. By default (right now) you must specify if you want 1, 2, or 3 copies. We always print 1 copy, and if we need more, you can simply click "print asset label" for additional copies. Is this what you were looking for?
unfortunately, this could also enable customers to update their information with bogus info. Like if they don't want to get follow up emails, they may update their email address in order to opt out of email communication, rather than doing it the right way with the opt out button. Also, they may delete their address if they feel like we don't need it, when we may in the future...