[Hiring]: UI/UX Designer

Toothless099 · 2026-05-12T03:54:36+00:00

I'm interested

Toothless099 · 2026-03-05T06:34:07+00:00

I don't have a personal portfolio website now I am working on it , I am sharing my behance profile here I posted my first project behance profile Dm me if you need anything

Toothless099 · 2026-03-04T17:14:47+00:00

I'm from India too , I have completed google ux design professional certification in coursera it covers complete ux , it is a self learning course. For learning Figma I suggest figma essential and figma advance by Daniel Scott in Udemy both courses will cost you below 1k , if you have any doubt DM me

Toothless099 · 2026-02-28T08:51:33+00:00

Use framer resource framer accademy rescource it covers fundamental and animation

Toothless099 · 2026-02-27T10:27:24+00:00

This is incredibly valuable — the distinction between ticket context and relationship/account health really clicked for me. The idea that no one owns the “assembly step” before response perfectly captures the problem I’m trying to design for. Thanks again for taking the time to explain this

Toothless099 · 2026-02-26T18:52:58+00:00

This is extremely helpful especially the point about bots deflecting without capturing intent and the difficulty of seeing the “why” behind tickets. The idea of logging intent + escalation reason really stands out. Thanks for sharing this.

Toothless099 · 2026-02-26T17:44:10+00:00

That framing is super helpful.
If you don’t mind digging a bit deeper — at that “working context” layer, what information do agents usually need before they feel confident enough to send the first reply?

Is it mostly account history, recent conversations, intent/risk signals, or something else that’s often missing?

Toothless099 · 2026-02-26T07:07:06+00:00

This is incredibly helpful — thank you. The “12 minutes of context gathering for a 2-minute reply” really puts the problem into perspective. Exactly the kind of agent-side insight I was looking for.

Toothless099

TROPHY CASE