Repairshopr custom fields on intake form

HCHTech

Well-Known Member
Reaction score
4,227
Location
Pittsburgh, PA - USA
I'm just getting started with RS, so I'm working to get the customer communications up to snuff. I have some custom ticket fields for the intake form (basically, what all are they dropping off and what are the usernames/passwords, etc.). I've seen the video and have created the fields just fine, but I'm struggling with formatting on the PDF that goes to the customer. Basically, it looks like the custom fields are only addressable in their entirety. The source code for inserting them on the intake form is:

<tbody>{{ticket_custom_fields_table}}
</tbody>

In other words, there doesn't seem to be any control over the format of that table -- which is a problem since the spacing of the table that is created isn't ideal. I have a combination of checkbox, dropdown and text items and that appears to be throwing the spacing off.

It is plunking the fields in there but the format leaves a lot to be desired, and not 100% up to what I'd like to hand to my customers. Is there a way to edit that table, or perhaps insert the custom fields one-at-a-time into the pdf template?
 
I'd also suggest contacting support. My suggestion is to be very specific about the request, ask only one issue at a time, and including all articles you read on the subject and any videos you've watched.
 
Support's recommendation is to basically create my own intake form as a worksheet, which can be attached to the ticket. While you can create custom fields like I have done, you don't have access to those fields as individual items, so they aren't really the correct vehicle to use if you want to control the layout of them. This is quite a bit of a bigger job than just modifying the existing template, so I'll need to carve out some time to take a run at it.
 
The only custom field we insert is passwords and customers are happy not to have that appear on their invoices.

My original goal was to record the equipment that customer's left for repair. I used my paper intake form for that purpose, so that's why I started with the system's intake form in the first place. Maybe I'm just looking at this task incorrectly. Let me ask how you use the system to keep track of the individual bits that the customer leaves for repair - e.g. 1 Dell laptop (visible damage to left hinge) service tag DD1UE7, 1 bag, 1 power adapter, 1 external mouse. Tracking what they drop off makes it easier to make sure we give them everything back when the repair is complete.
 
I use custom customer fields during the intake for immediate drop off details then add their asset into RS after the fact. The immediate details take care of the condition and items dropped off.

*Edit : This attribute is labeled {{CUSTOM_CUSTOMER _FIELD}} after you have enabled them so you may add it to your intake forms if need be. It's been a while so forgive me if im slightly off in naming.
 
Last edited:
I use custom customer fields during the intake for immediate drop off details then add their asset into RS after the fact.

Just to clarify, you use a single text field and just type it all in there (the items that were dropped off and their condition)?

I guess I'm still trying to understand the particular value of keeping track of a customer's computer as an "asset". When exactly does this come into play? Especially with residential customers, you might only get a computer in for repair once in it's lifetime, maybe twice. Sure, there are some outliers, but on average that's probably right. How does it help if you already have the thing as an asset? Can't you track past tickets by customer anyway regardless of whether you record the asset? If your invoice description is detailed, I would think that would give you the same information without the extra bother of keeping the asset fields.

I'm not saying it's wrong to keep asset data, just that it's value isn't readily apparent to me.
 
Just to clarify, you use a single text field and just type it all in there (the items that were dropped off and their condition)?

I guess I'm still trying to understand the particular value of keeping track of a customer's computer as an "asset". When exactly does this come into play? Especially with residential customers, you might only get a computer in for repair once in it's lifetime, maybe twice. Sure, there are some outliers, but on average that's probably right. How does it help if you already have the thing as an asset? Can't you track past tickets by customer anyway regardless of whether you record the asset? If your invoice description is detailed, I would think that would give you the same information without the extra bother of keeping the asset fields.

I'm not saying it's wrong to keep asset data, just that it's value isn't readily apparent to me.

To directly answer your question, RS ties all things together to make your workflow seamless. Having the ability to add assets to each ticket that is directly involved with it keeps you organized. It lets you and the client know what is being worked on as they can also preview their work order status through the customer portal as well as open invoices etc.. Id be happy to walk you through a complete workflow I use in my day to day processes.
 
In other words, there doesn't seem to be any control over the format of that table -- which is a problem since the spacing of the table that is created isn't ideal. I have a combination of checkbox, dropdown and text items and that appears to be throwing the spacing off.

I hear a lot of people just fiddling with the fields, ordering, etc - to make it fit well on the page. If you need one more checkbox to make a row balanced, just add another checkbox.

eg, maybe you have fields like:

Laptop Bag [ ] Power Cord [ ] External Hard Drive [ ]

And you need a 4th to make it a full row, just add something else like "Approved Antivirus Install [ ] " - whatever.. make something up :)

Of course you can do it the hard way too if you want..
 
Ahh, thanks!! I figured that there was some obtainable order using this methodology, unfortunately, I couldn't tease it out of Alex when I emailed for support. I think if I can get the grid of checkboxes working, then adding text fields at the end of the list might work without gunking up the display of the checkboxes. I'm going to tinker with that a bit.

I don't really want to reinvent the wheel if I can avoid it, so I appreciate this kind of guidance. Thanks!

Note that it's also possible I just need to rethink what I'm asking for. I started by just trying to mimic the paper form I've been using for years - that is probably holding me back. Change is hard!
 
We print labels on our Brother label printer and stick them on everything the bring in.
We were checking in each item but found this works just as well.
 
We are using the Brother QL720WN wireless printer to print the Repairshopr labels on a roll of 400 white stickers.
We get the ticket number, users name, issue description and a barcode to scan to find the ticket quickly all one the label.
 
We are using the Brother QL720WN wireless printer to print the Repairshopr labels on a roll of 400 white stickers.
We get the ticket number, users name, issue description and a barcode to scan to find the ticket quickly all one the label.

How are the labels with this? I use the Dymo and the labels are not professional. I want glossy ones that can't peel easily
 
Really professional looking and they stick on well. Have a look at the Brother supplies they have stacks of options on rolls of labels you can use.
 
Back
Top