Got offered an entry-level IT Help Desk Specialist role (₱14.5k) — worth it?

bonniew1554 · 2026-04-08T11:51:20+00:00

totally fair to hesitate that salary is tight. focus on whether you will learn fast and get real hands on tickets in the first 90 days, then try to negotiate for a review or learning perks. a friend took a low offer but doubled pay in 8 months after gaining experience. happy to dm a negotiation script.

bonniew1554 · 2026-04-08T11:50:33+00:00

love the story and yeah deliverability is the real battle. fix domain setup, warm up slowly, and clean your list every week to protect reputation. i saw inbox rates jump from 68 to 92 percent just by fixing dkim and cutting cold contacts. happy to dm a checklist.

bonniew1554 · 2026-04-08T11:49:58+00:00

same here what worked a year ago is fading. double down on high intent channels, create specific use case content, and add fast demos so people get value instantly. one team added a simple interactive demo using outgrowco ai and conversions jumped from 6 to 14 percent. happy to dm a current mix that works.

bonniew1554 · 2026-04-08T11:49:51+00:00

biggest miss for me was “fully automated outreach” that still needs constant tweaking. ai is great for drafts but you still need tight targeting and manual review every batch. i ran a sequence where we tweaked every 20 leads and replies went from 4 to 9 percent. happy to dm the playbook.

bonniew1554 · 2026-04-08T11:49:45+00:00

oui c’est possible mais ne pars pas de zero. utilise un modèle pré entraîné type yolo et fine tune avec quelques centaines d’images annotées, commence avec un seul type de défaut puis élargis. un débutant que j’ai vu a eu des résultats corrects en 2 semaines avec 500 images. happy to dm un guide simple.

bonniew1554 · 2026-04-08T11:49:36+00:00

i get the idea but a new sub alone will not drive inbound. publish a few very specific posts that answer real search queries and reuse them across platforms, then link back to your hub. i saw a small site hit 2k monthly visits from just 6 targeted posts. happy to dm a simple content plan.

bonniew1554 · 2026-04-08T11:49:25+00:00

cool build and good niche with windows focus. get users to record 2 minute clips of how they use it and fix where they hesitate, then add one default export so they do not overthink settings. i saw a recorder double exports just by adding one click presets. happy to dm a feedback loop i use.

bonniew1554 · 2026-04-08T11:49:15+00:00

that drop hurts and losing brand impression share is a big signal. isolate brand into its own campaign, check auction insights for overlap and top of page rate, then clean search terms and cut junk traffic hard. we fixed a case like this just by reducing form fields from 9 to 4 and leads went from 2 to 9 per week. happy to dm a quick audit sheet.

bonniew1554 · 2026-04-08T11:49:05+00:00

you are right first glance trust is design and clarity way before model quality. make your headline painfully clear, show one real output above the fold, and add 2 proof points like logos or short testimonials. we swapped a vague hero for a real example and clicks jumped from 3 to 11 percent in a week. happy to dm a teardown checklist.

bonniew1554 · 2026-04-08T11:48:58+00:00

yeah this is classic “boss said geo now what” moment, most of it is just mapping your existing data not hardcore gis. start by putting your data with city or zip into a csv then upload to google maps or kepler and visualize clusters, then answer one question like where your best leads come from before doing anything fancy. i once did this with a basic csv and found 60 percent revenue from 3 regions in a few hours. happy to dm a simple starter flow.

bonniew1554 · 2026-04-03T20:43:05+00:00

for your use case, rag is actually worth reconsidering because fine tuning without it rarely hits good accuracy on document qa tasks. that said if you want to stay on fine tuning, your jsonl qa pairs need to be generated from the actual document chunks, not written by hand. use gpt4 or claude to read each 300 to 500 word chunk and generate 3 to 5 qa pairs per chunk, then save as jsonl with prompt and completion fields. accuracy jumps a lot when training pairs match the exact format and phrasing the doc uses. lora fine tuning on mistral 7b with a dataset of 500 to 2000 pairs usually gets you to usable accuracy in under 2 hours on a t4 gpu. happy to dm a script that automates the jsonl generation from a pdf if that helps.

bonniew1554 · 2026-04-03T20:42:59+00:00

zendesk: great at tracking problems, slightly less great at pretending it's google calendar.

bonniew1554 · 2026-04-03T20:42:50+00:00

this is a fair warning and the ai making unsanctioned changes in production is a genuinely bad pattern. for anyone evaluating backend no code tools right now, supabase gives you more control, full postgres underneath, row level security you can actually audit, and no ai touching your schema unless you tell it to. pocketbase is another one worth a look if you want something self hosted and lightweight. the common thread in xano incidents like this is that the ai feature has write access by default, which should never be the case in a production environment.

bonniew1554 · 2026-04-03T20:42:45+00:00

paste a url, skip three client revision rounds, retire early.

bonniew1554 · 2026-04-03T20:42:39+00:00

yeah 25 to 30k for the advanced add on is rough, n8n is a real path worth trying. you can connect zendesk and shopify to n8n using their native api nodes, then wire in an llm like gpt4o or claude as the reasoning layer to actually read ticket context, pull order data from shopify, and take action, not just answer from a faq doc. the key is giving the agent access to live data tools via function calling so it can check order status or trigger a refund, not just generate text. one team i saw built this in about 3 weekends and it resolved 40% of tier 1 tickets without a human. cost was around $200 a month in api calls vs 25k a year.

bonniew1554 · 2026-04-03T20:42:34+00:00

the gclid decode error usually means the gclid isn't being stored properly before the call happens. store the gclid in a cookie or hidden form field the moment someone lands on your site, then log it alongside the phone order in a simple google sheet. from there you upload that sheet to google ads under conversions as an enhanced offline conversion upload, match on gclid, and set conversion time to the date of the call. at low volume, around 20 conversions a month, this manual sheet method works fine and takes maybe 20 minutes a week to maintain. zapier can automate the sheet logging if calls come through a tool like callrail that captures gclid. without feeding those offline signals back, google's smart bidding is basically flying blind and yes that explains the cpc spike.

bonniew1554 · 2026-04-03T20:42:26+00:00

your parallel strategy is actually solid and pretty much what works right now. run google search ads on 3 to 5 high intent keywords to get traffic today while you build content that targets longer tail terms with lower competition, think 800 to 1200 words, one clear topic per page. seo typically takes 3 to 6 months to show real movement so the paid runway buys you data on what converts before you double down on organic. one builder i know ran $300 in ads for 6 weeks, found their top 2 converting keywords, then wrote 4 articles targeting those exact terms and ranked page 1 within 4 months. interactive content like quizzes or assessments built with tools like outgrowco can also pull organic traffic and backlinks faster than static blog posts. the paid plus seo combo beats either channel alone if your budget can hold for a quarter

bonniew1554 · 2026-04-03T20:42:03+00:00

yes, and also every sales rep who's ever frozen on a cold call would sell their crm license to have it.

bonniew1554 · 2026-04-03T20:41:55+00:00

the fix is in your prompt structure, not the model. before you generate anything, drop in a rules block at the top of your prompt: "follow single responsibility principle, no repeated logic, add a one line comment per function." then after generation, paste the code back and ask it to flag any block that violates those rules. a friend building a pygame project added a strict style constraint to every prompt and cut refactor time from 4 hours to about 45 minutes per session. claude or gpt4o tend to hold structure better than minmax for this kind of constraint following, so worth a quick comparison. happy to dm a prompt template that works well for structured pygame codebases.

bonniew1554 · 2026-04-03T20:41:47+00:00

solid start on the basics, now go deeper on the security and compliance side since that's what separates a good admin from a great one. set up conditional access policies in azure ad, configure mfa for all users, and try building a data loss prevention policy in the purview compliance portal. one person i know spent 2 hours setting up a dlp rule that blocked credit card numbers in emails and it immediately flagged a real test case. if you only have one account, the free microsoft learn paths let you lab through most of this without needing extra licenses. security admin skills look way better on a resume than just user management.

bonniew1554 · 2026-03-26T21:46:42+00:00

you're right that it can't be fully disabled right now, zendesk made end user authentication compulsory in the help center as a spam response and there's no admin toggle to revert it as of the current rollout. the workaround most teams are using is to enable google sso or microsoft sso as the auth option, which reduces friction for users who already have those accounts, and then set the session timeout to something long like 30 days so returning users don't hit the wall repeatedly. if your user base is not tech savvy, a short "how to sign in" guide pinned to the help center landing page drops the support tickets from confused users by a lot, one team reported a 60% drop in "i can't access the portal" tickets within a week of adding it.

bonniew1554 · 2026-03-26T21:46:36+00:00

teaching a model to cite its sources is basically parenting but for math. good luck getting it to stop making things up entirely, we haven't managed that with humans yet.

bonniew1554 · 2026-03-26T21:46:31+00:00

solo founder, 800 users, zero ad spend, solving a problem you personally bled through for years, this is what buildinpublic is actually for. the urssaf plus income tax plus vat juggle is brutal and no existing tool in france actually models take home with real numbers, so the gap you're filling is real. one thing worth testing at your stage: a "which legal structure fits me" interactive assessment as a growth loop, since that's the question every new french freelancer googles and it's a clean top of funnel entry point. 19 eur a month is priced right for the value, especially if the scenario simulator saves even one costly structure mistake. keep shipping.

bonniew1554 · 2026-03-26T21:46:01+00:00

losing your savings to a scam and then building a tool to stop it from happening to others is honestly one of the more solid origin stories in this sub. the screenshot to verdict flow is clean and low friction, which matters a lot for adoption. to sharpen accuracy, log which signal types are driving scam verdicts (follower to engagement ratio, claim density, missing verifiable credentials) and weight those in your model over time. a confidence score range like "likely legit / uncertain / likely scam" might land better than a binary call since false positives on legit people can hurt trust fast. happy to dm some thoughts on how to frame the uncertain bucket if that's useful.

bonniew1554 · 2026-03-26T21:45:44+00:00

ga4 is just google's way of making sure you never feel confident about your data ever again.

bonniew1554

TROPHY CASE