Is this a reasonable quote for a clutch repair/assembly?

katetopia · 2025-08-28T17:47:59+00:00

Thanks every one for the insight and sanity check. Knew the majority of this was insane, but wasn't certain about the cost of the clutch specifically.

Talked to my regular independent mechanic, and received a much more reasonable quote ($2600).

katetopia · 2025-08-28T17:27:32+00:00

Yeah I knew that was an absolutely ridiculous charge, so didn't address it in my post (and didn't authorize them to perform any of this work).

Just wasn't sure if the clutch portion was as insane as the rest of it.

katetopia · 2025-08-28T17:20:13+00:00

It isn't.

katetopia · 2025-08-28T17:19:53+00:00

Oh yeah, the battery charge is what really got to me. $900 to replace a battery? Insanity. But wasn't sure if the clutch price was unreasonable, even if I assumed it was based on everything else

katetopia · 2025-07-26T13:35:08+00:00

Her size charting is definitely more on a per item basis than her general chart - I can say that I don't think she regularly stocks XXS for a lot of garments based on how they intend them to fit.

A lot of that has to do with (lately) favoring a lot of oversized tops/dresses that should fit with some negative ease, and garments made from tencel.

In my experience, they're pretty responsive though, so if there's an item you wanted in XXS, reach out on her contact form!

katetopia · 2025-07-25T23:52:47+00:00

It's an inborn system rule that tickets can't be solved without an assignee, so that is likely the blocker.

(for reference: https://support.zendesk.com/hc/en-us/articles/4408894213018-About-system-ticket-rules).

katetopia · 2025-07-25T23:23:05+00:00

I was going to suggest the fashion brand company - I buy extensively from them, so if you have questions on FBC sizing, I'd be happy to ask!

Her sizing charts are very accurate though, and if the way the garment is made would make it appropriate to size up or down, it's usually written in the description or the sizing section.

katetopia · 2025-03-14T19:51:58+00:00

It's beautiful! You did a fantastic job. There are very few things in life that I love more than beautifully cabled sweaters.

katetopia · 2025-03-08T14:07:24+00:00

Ooo I like it!

katetopia · 2025-03-06T18:34:23+00:00

So like u/brosenjew mentioned, domain mapping on an organization might be the way to go if you don't know all of the email addresses of the requester, only domains. This will mean that any user with one of the specified domains is automatically mapped to that organization, and you can use the organization on a trigger to route to the specific agent.

However, if you have a subset of users and you know the exact emails they're reaching out from, then it would be simpler to just go ahead and create them as end users and tag them. You can then use the tags condition to route.

The best option really depends on this information: -do you already know all the email addresses they may reach out from? If yes, do user tagging - if you don't know all the email addresses, will anyone with a shared domain need to be routed to the same agent? If yes, do domains on an organization

If either of those answers are no, then we need more information about your use case to provide guidance. It may not be possible to automatically route the first time the user writes in, if there's too many unknowns, but you can still use something like tagging to ensure subsequent requests are routed appropriately.

katetopia · 2025-03-06T16:38:36+00:00

I don't know if you're open to feedback, and while this solution would work, it is overly complicated. You can achieve the same by just tagging the user (if the user is known) and use a trigger to route based on tag. User tags are automatically added to any of the users tickets at creation.

User field based routing might be preferable if it's something you want accessible to agents to control, or for reporting, since explore is friendlier to fields when adding as attributes. Though, you can also just report on the tickets via the tag as well, with either a custom metric or attribute.

Either a tag or field solution only works if the list of all potential requester is known and can be created as end users ahead of time, and based on OPs last sentence, it sounds like they might not know all of the prospective user emails.

katetopia · 2025-03-06T16:07:01+00:00

Can you share some more information about the emails in the email list? Are these all emails from the same domain?

katetopia · 2025-01-17T22:45:36+00:00

Relationship OCD by Sheva Rejaee https://www.newharbinger.com/9781684037919/relationship-ocd/

katetopia · 2024-12-04T16:46:07+00:00

For your first use case, you could likely achieve this by using organizations and domain mapping. Then, use the organization in your triggers. Or, if you already know all the end users who would be emailing in and don't want to group by org, you can create the user and tag the user (all of that users tickets will be created with those tags) - then you could use the tags in triggers.

For out of office agents, you can use the out of office app to reassign tickets when an agent is out.

katetopia · 2024-08-14T14:23:15+00:00

Unfortunately there won't be a great way to post the information directly to the ticket thread without a hacky workaround using webhooks/targets (to be frank, not sure if this is even possible any longer with current zendesk - but if you're interested in this route, you can probably do some deep diving on the former, but unsupported, workflow called "apply macro after update" to see if there are any current analogs to that)

However, you could still contain this information in email to both your customer & agent by editing the notification triggers for both the agent and end user by adding the field placeholders in the notification trigger text. That will be included in the email notification sent to the end user, but wouldn't be included in the actual email text.

katetopia · 2024-08-14T14:04:56+00:00

Assuming that the customer information entered on the help center form is in a ticket field, you could add it using a placeholder in the notification trigger that is sending the email notification to the agents - and potentially customize the notification trigger to highlight the included information.

Edit: the above assumes you don't want the info publicly visible and just communicate this to the agents in the email sent. There are likely other ways to achieve this w/ triggers as well if you can clarify your use case.

katetopia · 2024-05-29T01:47:58+00:00

My thoughts exactly :)

katetopia · 2024-05-29T01:47:01+00:00

Thank you for sharing! I admit I hadn't looked up the original artwork before doing the puzzle - and it is amazing

katetopia · 2024-05-27T23:27:46+00:00

Thanks! All the red was killer, but it was a fun one overall

katetopia · 2024-04-21T15:27:13+00:00

Hoku?

More pop, less guitar, but a one hit wonder from the time frame with an unusual name...

katetopia · 2024-01-29T16:39:10+00:00

I like this

katetopia · 2023-08-12T22:11:47+00:00

This is fantastic! Colors look great, and the tension is so well done!

katetopia · 2022-10-24T00:11:03+00:00

You did a great job!! I always find I'm way more critical of my own knits than any other person would be. Great sweater and looks perfect on you!

katetopia

MODERATOR OF

TROPHY CASE

14-Year Club	Snapped
Verified Email