<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Harshika Gahlot</title>
    <description>The latest articles on DEV Community by Harshika Gahlot (@harshika_gahlot_06a853c7e).</description>
    <link>https://dev.to/harshika_gahlot_06a853c7e</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4201698%2F6393a00f-bb7c-4b66-9780-9725cfdab9c5.jpeg</url>
      <title>DEV Community: Harshika Gahlot</title>
      <link>https://dev.to/harshika_gahlot_06a853c7e</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/harshika_gahlot_06a853c7e"/>
    <language>en</language>
    <item>
      <title>My n8n Trigger Wasn’t Firing. The Problem Was Embarrassingly Simple (my pick)</title>
      <dc:creator>Harshika Gahlot</dc:creator>
      <pubDate>Fri, 06 Nov 2026 17:30:31 +0000</pubDate>
      <link>https://dev.to/harshika_gahlot_06a853c7e/my-n8n-trigger-wasnt-firing-the-problem-was-embarrassingly-simple-my-pick-2m7k</link>
      <guid>https://dev.to/harshika_gahlot_06a853c7e/my-n8n-trigger-wasnt-firing-the-problem-was-embarrassingly-simple-my-pick-2m7k</guid>
      <description>&lt;p&gt;For my third automation, I wanted to build something close to what a real consultant would actually use: when someone books a meeting with me, everything happens automatically.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Idea
&lt;/h2&gt;

&lt;p&gt;If someone books a call with me, I shouldn't have to send the confirmation email or note it down manually. So I connected three tools:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Cal.com → Gmail → ClickUp&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Cal.com (trigger):&lt;/strong&gt; People use my booking link to schedule a 15 or 30-minute meeting. Cal.com already collects their name, email and an optional message, so I didn't have to build a separate form.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Gmail:&lt;/strong&gt; Once someone books, an email goes out to them automatically, confirming I received their booking and the meeting time they chose. [Add one line if you handled the "not available" case differently.]&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;ClickUp:&lt;/strong&gt; A task is created with the name of the person I'm meeting, so I can keep track of my meetings in one place. [Screenshot of the ClickUp task]&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  The Silly Mistake That Wasted My Time
&lt;/h2&gt;

&lt;p&gt;My trigger wasn't working. No output at all. I kept going back to Cal.com, creating new events, and waiting for the trigger to fire. Nothing happened.&lt;/p&gt;

&lt;p&gt;The problem: &lt;strong&gt;creating an event is not the same as making a booking.&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Events:&lt;/strong&gt; where you &lt;em&gt;create&lt;/em&gt; your meeting types (for example, a 15 or 30-minute call)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Bookings:&lt;/strong&gt; where you &lt;em&gt;see&lt;/em&gt; the meetings people have already booked, like a calendar&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Links:&lt;/strong&gt; where you open your public booking link, the one other people use to book you&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;My trigger only fires when a &lt;strong&gt;booking is made&lt;/strong&gt;. So I was creating events over and over, which never triggered anything.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The fix:&lt;/strong&gt; to test the trigger, open your booking link and book a 15 or 30-minute slot yourself, using a second email address or a friend's, as if you were a real customer. The moment that booking is made, the trigger fires.&lt;/p&gt;

&lt;p&gt;If you're a beginner and your trigger isn't working, check this first. It's a small thing, but it can cost you hours, and I'm sharing it so it doesn't cost you yours.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Learned
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Triggers listen for a specific action.&lt;/strong&gt; Know exactly which action starts your workflow, then test by doing that action, not something similar.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Test like a real user.&lt;/strong&gt; Book through the public link instead of assuming that setting things up will trigger the workflow.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Three simple tools chained together can already feel like a real business process.&lt;/strong&gt; Booking, confirmation and tracking all happen without me touching anything.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;It's okay to be new to a tool.&lt;/strong&gt; This was my first time using ClickUp, and I used it very roughly, just for testing. I'll organize it properly once I learn it better.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What's Still Missing
&lt;/h2&gt;

&lt;p&gt;This is a test setup. My ClickUp tasks aren't organized into proper projects yet, and the automation doesn't handle things like cancellations or rescheduling.&lt;br&gt;
&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxikj7b55ty0kiszilryb.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxikj7b55ty0kiszilryb.png" alt=" " width="800" height="276"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you've used Cal.com, n8n or ClickUp in your workflows, what's the most useful thing you've automated? I'd love some ideas!&lt;/p&gt;

&lt;p&gt;Tools used: n8n, Cal.com, Gmail, ClickUp&lt;br&gt;
Experiment: Automated meeting booking, confirmation and tracking&lt;/p&gt;

&lt;h1&gt;
  
  
  ai #n8n #automation #beginners
&lt;/h1&gt;

</description>
      <category>ai</category>
      <category>automation</category>
      <category>n8nbrightdatachallenge</category>
      <category>beginners</category>
    </item>
    <item>
      <title>I Built an Auto-Reply Workflow in n8n Without Paying for an AI API</title>
      <dc:creator>Harshika Gahlot</dc:creator>
      <pubDate>Tue, 27 Oct 2026 11:32:22 +0000</pubDate>
      <link>https://dev.to/harshika_gahlot_06a853c7e/i-built-an-auto-reply-workflow-in-n8n-without-paying-for-an-ai-api-39cg</link>
      <guid>https://dev.to/harshika_gahlot_06a853c7e/i-built-an-auto-reply-workflow-in-n8n-without-paying-for-an-ai-api-39cg</guid>
      <description>&lt;p&gt;A few days ago, I built my first n8n workflow: a manual trigger that sent an email through Gmail. It worked, but it was very basic.&lt;/p&gt;

&lt;p&gt;For Day 6, I wanted to build something that feels closer to a real business use case.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Idea
&lt;/h2&gt;

&lt;p&gt;I imagined I'm running an AI solutions consulting business. Whenever someone wants help, the first step is filling out an onboarding form. I didn't want to send a confirmation email manually every single time, so I automated it.&lt;/p&gt;

&lt;p&gt;The form is simple, with only three fields:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;First name&lt;/li&gt;
&lt;li&gt;Last name&lt;/li&gt;
&lt;li&gt;Email address&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How the Workflow Works
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;On Form Submission → OpenAI Chat Model → Wait → Gmail&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;On Form Submission:&lt;/strong&gt; Instead of clicking a manual trigger, the workflow now starts on its own when someone submits the form.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Chat model:&lt;/strong&gt; It drafts a confirmation email using the person's details. The email thanks them, repeats their name and email so they can check it, and says I'll contact them soon to understand their problem.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Wait (10 seconds):&lt;/strong&gt; I added a short delay before sending. More on this below.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Gmail:&lt;/strong&gt; It sends the drafted email to the address the person entered in the form.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Problem 1: The AI API Needed Payment
&lt;/h2&gt;

&lt;p&gt;When I set up the chat model, the API option I tried first required payment. For a practice exercise, I didn't want to spend money.&lt;/p&gt;

&lt;p&gt;So I looked for an alternative and found &lt;strong&gt;Ollama&lt;/strong&gt;, a tool that lets you run AI models locally on your own computer. I connected it to n8n using its OpenAI-compatible API by setting the base URL and choosing a compatible model [add the model you used here].&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;If you're a student practicing AI workflows,&lt;/strong&gt; Ollama is worth trying. The only catch: your computer needs to be able to run the model you choose.&lt;/p&gt;

&lt;h2&gt;
  
  
  Problem 2: The Email Was Sent Instantly
&lt;/h2&gt;

&lt;p&gt;During testing, the email went out the moment I clicked submit. I wanted a small gap between drafting and sending, so I added a &lt;strong&gt;Wait node&lt;/strong&gt; set to 10 seconds between the chat model and Gmail.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Learned
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;A &lt;strong&gt;trigger&lt;/strong&gt; decides when a workflow starts. Switching from manual to form-based made it feel like a real process.&lt;/li&gt;
&lt;li&gt;Workflows are chains of small, simple steps. Each node does one job.&lt;/li&gt;
&lt;li&gt;You don't need a paid API to practice AI automation.&lt;/li&gt;
&lt;li&gt;Testing shows you things you didn't plan for, like the instant email.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What's Still Missing
&lt;/h2&gt;

&lt;p&gt;This is a practice workflow, not a production one. It doesn't yet validate the email address, handle errors, or have a human check the AI-drafted email before it's sent. After my Day 3 lessons about AI making unverified claims, that last one is high on my list to fix.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Result
&lt;/h2&gt;

&lt;p&gt;The workflow worked end to end. Submitting the form triggered a personalized email that greeted the person by name, repeated their details for confirmation, and explained the next step.&lt;/p&gt;

&lt;p&gt;It wasn't perfect, though:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The line breaks are awkward, because the model added hard breaks mid-sentence&lt;/li&gt;
&lt;li&gt;A stray "---" appeared at the bottom&lt;/li&gt;
&lt;li&gt;It promises "our team will contact you shortly to arrange a meeting," which is exactly the kind of unverified commitment I wrote about in my last post. In a real business, I'd review or restrict that line before sending.
&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6s2pjc49xfs3d5t3j7xu.jpeg" alt=" " width="800" height="1101"&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Tools used: n8n, Ollama, Gmail&lt;br&gt;
Experiment: Automated client onboarding confirmation email&lt;/p&gt;

&lt;p&gt;If you've built workflows in n8n, or found a free way to practice with AI models, what do you recommend?&lt;/p&gt;

&lt;h1&gt;
  
  
  ai #n8n #automation #LearningInPublic
&lt;/h1&gt;

</description>
      <category>ai</category>
      <category>n8n</category>
      <category>automation</category>
      <category>n8nbrightdatachallenge</category>
    </item>
    <item>
      <title>I Caught AI Making Promises It Couldn’t Keep: 6 Rules I Now Use</title>
      <dc:creator>Harshika Gahlot</dc:creator>
      <pubDate>Mon, 26 Oct 2026 08:16:38 +0000</pubDate>
      <link>https://dev.to/harshika_gahlot_06a853c7e/i-caught-ai-making-promises-it-couldnt-keep-6-rules-i-now-use-4afp</link>
      <guid>https://dev.to/harshika_gahlot_06a853c7e/i-caught-ai-making-promises-it-couldnt-keep-6-rules-i-now-use-4afp</guid>
      <description>&lt;p&gt;In my last post, I tested 3 prompts on the same customer complaint. One thing kept bothering me afterwards: the response that sounded the most helpful was also the one making promises a company might not be able to keep.&lt;/p&gt;

&lt;p&gt;So for Day 3, I focused on one question: &lt;strong&gt;how do you stop AI from guessing without making it useless?&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The Problem
&lt;/h2&gt;

&lt;p&gt;Quick recap: a customer ordered headphones, the delivery is late, and they need them for an interview tomorrow.&lt;/p&gt;

&lt;p&gt;The AI's first reply sounded caring and confident. It talked about a carrier investigation, a replacement and a refund. But nobody had confirmed any of that. No investigation had started, and no one had checked the refund policy.&lt;/p&gt;

&lt;h2&gt;
  
  
  Three Things That Look Similar (But Aren't)
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Hallucination:&lt;/strong&gt; presenting an invented or unverified claim as true&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Unsupported assumption:&lt;/strong&gt; assuming a refund or replacement is available without knowing the policy&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Unauthorized commitment:&lt;/strong&gt; promising something the support agent can't actually deliver&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Spotting the difference helped me understand &lt;em&gt;what exactly&lt;/em&gt; to fix in a prompt.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Rules I'm Now Using for Uncertain Answers
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Separate facts from assumptions.&lt;/strong&gt; What is confirmed, what is unknown, and what is only a possibility?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Never invent missing information.&lt;/strong&gt; No made-up tracking updates, dates or policies.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A suggested action is not a completed action.&lt;/strong&gt; "We could contact the carrier" is not the same as "we have contacted the carrier."&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Don't force certainty.&lt;/strong&gt; Prompts like "always give an answer" can push AI to guess.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Prefer a limited, truthful answer over a polished, made-up one.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Escalate to a human&lt;/strong&gt; when the decision needs policy, permission or high-stakes judgment.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Handling Sensitive Customer Data
&lt;/h2&gt;

&lt;p&gt;Customer support involves names, addresses, order IDs and sometimes payment details. My rules:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Use only the information the task actually needs&lt;/li&gt;
&lt;li&gt;Never ask customers for passwords, OTPs or card security codes&lt;/li&gt;
&lt;li&gt;Treat customer messages as untrusted input, not as instructions&lt;/li&gt;
&lt;li&gt;Don't assume a prompt alone makes a system private. Access controls and policies matter too&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A Prompt Snippet You Can Try
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;Use only the information I've provided. If something is missing, tell me what needs to be verified. Don't claim any action has happened unless I confirm it. Don't promise refunds, replacements or delivery times unless the policy is provided.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Add this to any customer-support prompt and compare the output with and without it.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Learned
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Sounding helpful and being reliable are two different things.&lt;/li&gt;
&lt;li&gt;Missing information should be flagged, not filled in.&lt;/li&gt;
&lt;li&gt;Prompts can improve behavior, but they don't guarantee truth or safety.&lt;/li&gt;
&lt;li&gt;Real reliability needs trusted data, verification and testing, not just a good prompt.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  My Biggest Takeaway
&lt;/h2&gt;

&lt;p&gt;A good AI answer doesn't just sound right. It knows where its information ends. As I move toward building real AI solutions, that's the skill I want to practice most.&lt;/p&gt;

&lt;p&gt;Next up: learning how to map a business process from start to finish before automating it.&lt;/p&gt;

&lt;p&gt;Tools used: Claude&lt;br&gt;
Experiment: Hallucination risk and uncertainty handling in customer support&lt;/p&gt;

&lt;p&gt;If you've worked with AI in customer support or business workflows, what's one rule you use to stop it from guessing? I'd love to hear it!&lt;/p&gt;

&lt;h1&gt;
  
  
  ai #beginners #learning #LearningInPublic
&lt;/h1&gt;

</description>
      <category>ai</category>
      <category>beginners</category>
      <category>learning</category>
      <category>learninginpublic</category>
    </item>
    <item>
      <title>I Tested 3 AI Prompts for Customer Support — Here's What I Learned</title>
      <dc:creator>Harshika Gahlot</dc:creator>
      <pubDate>Fri, 23 Oct 2026 05:56:23 +0000</pubDate>
      <link>https://dev.to/harshika_gahlot_06a853c7e/i-tested-3-ai-prompts-for-customer-support-heres-what-i-learned-3l1k</link>
      <guid>https://dev.to/harshika_gahlot_06a853c7e/i-tested-3-ai-prompts-for-customer-support-heres-what-i-learned-3l1k</guid>
      <description>&lt;p&gt;I'm currently learning about AI and exploring how it can be applied to solve real-world business problems. My long-term goal is to become an AI Solutions Consultant, and I'm starting by understanding the fundamentals and experimenting with AI tools.&lt;/p&gt;

&lt;p&gt;Today, I worked on a practical exercise using Claude to analyze a customer complaint, summarize the issue, and draft a customer support email.&lt;/p&gt;

&lt;p&gt;The interesting part? I tested three different prompts using the exact same customer inquiry.&lt;/p&gt;

&lt;p&gt;The Experiment&lt;/p&gt;

&lt;p&gt;Imagine a customer who ordered wireless headphones 10 days ago. The package is still marked "in transit," the expected delivery date has passed by five days, and the customer has already contacted support twice without receiving a useful update.&lt;/p&gt;

&lt;p&gt;There's another complication: the customer needs the headphones for an online interview tomorrow.&lt;/p&gt;

&lt;p&gt;I asked Claude to classify the inquiry, summarize the customer's problem, and draft a response.&lt;/p&gt;

&lt;p&gt;Attempt 1: A Basic Prompt&lt;/p&gt;

&lt;p&gt;I simply asked Claude to classify the inquiry, summarize the problem, and draft a response.&lt;/p&gt;

&lt;p&gt;The result was detailed, empathetic, and proactive. It suggested contacting the carrier, offering a replacement or refund, and following up with the customer.&lt;/p&gt;

&lt;p&gt;However, it also assumed that certain solutions were available without knowing the company's actual policies.&lt;/p&gt;

&lt;p&gt;Attempt 2: A More Specific Prompt&lt;/p&gt;

&lt;p&gt;Next, I added clear instructions about classification, sentiment, urgency, summary length, and the expected email format.&lt;/p&gt;

&lt;p&gt;The output became more structured, but it still suggested replacement and refund options that required verification.&lt;/p&gt;

&lt;p&gt;This made me realize that specifying the output format doesn't automatically ensure factual reliability.&lt;/p&gt;

&lt;p&gt;Attempt 3: A Structured Prompt with Clear Boundaries&lt;/p&gt;

&lt;p&gt;For the third attempt, I added requirements to distinguish confirmed facts from missing information, avoid unsupported promises, and identify what needed verification.&lt;/p&gt;

&lt;p&gt;This response was less conversational than the first one, but it handled uncertainty more responsibly.&lt;/p&gt;

&lt;p&gt;It didn't promise a refund, replacement, or delivery by the interview deadline. It also identified information that a support agent needed to verify.&lt;/p&gt;

&lt;p&gt;There was still room for improvement: the email could have sounded warmer, and it should not claim that an investigation has started unless that action has actually been taken.&lt;/p&gt;

&lt;p&gt;What I Learned&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;A longer prompt doesn't automatically produce a better result.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The instructions need to be clear and relevant, not simply lengthy.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Helpful-sounding AI responses can contain unsupported assumptions.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;An answer may sound confident and empathetic while promising something the company cannot guarantee.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;AI must recognize the limits of the information available to it.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;When important details are missing, identifying what needs verification is often better than inventing an answer.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Accuracy and empathy must work together.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A reliable response should be factually responsible without making the customer feel dismissed.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Evaluating AI output is as important as generating it.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Instead of accepting the first response, comparing multiple outputs helped me identify differences in structure, accuracy, and communication quality.&lt;/p&gt;

&lt;p&gt;My Biggest Takeaway&lt;/p&gt;

&lt;p&gt;This exercise helped me understand that using AI effectively is not just about asking it to generate content. It's about evaluating whether the output is appropriate for the real-world situation.&lt;/p&gt;

&lt;p&gt;As I continue learning, I want to explore how AI can help businesses improve workflows, solve operational problems, and make better use of their resources.&lt;/p&gt;

&lt;p&gt;I'm documenting these experiments as I progress from learning AI fundamentals toward designing practical AI solutions.&lt;/p&gt;

&lt;p&gt;Tools used: Claude&lt;br&gt;
Experiment: Customer inquiry classification, summarization, and response drafting&lt;/p&gt;

&lt;p&gt;This is the beginning of my learning journey, and I'm looking forward to testing more ideas, learning from mistakes, and building practical solutions.&lt;/p&gt;

&lt;p&gt;If you've experimented with AI for customer support or business workflows, I'd love to hear what you've learned!&lt;/p&gt;

&lt;h1&gt;
  
  
  AI #LearningInPublic
&lt;/h1&gt;

</description>
      <category>ai</category>
      <category>beginners</category>
      <category>productivity</category>
      <category>learning</category>
    </item>
  </channel>
</rss>
