At most one email a week. Unfollow anytime with one click.
Transcript
The full narration of this video. The current sentence is highlighted while the video plays; click any sentence to jump there.
Show transcript
Introduction
Hi, and welcome back to Claude from Zero to Expert. In the previous episode the agent only read pages. Now we climb one rung: filling in web forms. We'll sort the data an agent may fill in, prepare the data and limits, watch the agent fill a registration form, then check it before the submit button is pressed.
Step 1: Which forms suit an agent
Not every form needs to go to an agent. The best fits are forms that are long, repetitive, or whose data is already available. First example: event registrations, such as bazaars, expos, or training. Second, price quote requests, especially when you send the same data to several suppliers. Third, routine orders whose entries are almost the same every week. Fourth, data collection forms or surveys from partners, which can run to dozens of fields. A short one-time form, say three fields, is usually quicker to fill in yourself than to explain to an agent. So who fills in what? General business data such as the name, business address, and opening hours can be filled in by the agent. Passwords and OTP codes you always type yourself. Product descriptions and prices are fine for the agent. Card numbers, bank accounts, and PINs are never handed over. Order quantities and delivery dates are fine. ID card numbers and other identity data are better filled in by you. Business contacts that are already public are fine. But the agree-to-terms checkbox and signatures are legal decisions, so they stay yours. The practical rule: if that data leaking would cost you, don't hand it to the agent.
Step 2: Preparing data and limits
Laras wants to join a year-end small business bazaar. The registration form is on the organizer's site, fictional for this example. She writes a task for the agent, starting with the form's address. Then the complete form data: business name, featured products, and power needs. All of this is safe, because it will appear in the bazaar brochure anyway. The first limit is very important: don't fill in any field whose data isn't given here. Ask first. This stops the agent from making up entries. The second limit: stop before the submit button, and don't tick any agreement. Registering is a commitment, so Laras presses submit. One small habit helps a lot. Before the agent starts, Laras asks for its plan first. The agent explains four steps: open the form, fill in three fields from Laras's data, ask about any other fields, and stop before submitting. The plan matches the limits Laras wrote. Laras says go ahead. If the plan were wrong, for example if the agent intended to tick an agreement, Laras could correct it before anything happened.
Step 3: The agent fills the form
Let's watch the agent work. It opens the vendor registration form. There are four fields: business name, featured products, power needs, and the business ID number. The first field is filled: Sunset Coffee. Notice the field starts turning green. The second field, featured products, is filled exactly from Laras's data: palm sugar iced coffee, cold brew, and hampers. The third field, power needs of nine hundred watts, with a note on the equipment. Then the NIB field, Indonesia's business ID number. Its data isn't in the task. The agent doesn't guess, and doesn't look for it elsewhere. It stops and asks. The red line marks the moment the agent waits for you. Laras types the NIB herself. She chooses not to keep this number in the notes for the agent, and that's a reasonable choice. All fields are filled. The agent stops right before the submit registration button, as instructed. Now it's Laras's turn to check. In the Claude panel, the agent summarizes the entries in a table, marked as not submitted. It also mentions a box to accept the booth fee terms, which it deliberately left unticked. Laras is curious about that booth fee. When does it have to be paid? The agent reads the terms section on the same page: it's paid after passing curation. Laras can now decide with complete information, then tick the box and press submit herself.
Step 4: Checking before submitting
Before pressing submit, use this checklist. First, read the entries on the real page, not just the agent's summary. The summary may be right, but what gets sent is the form itself. Second, check the spelling of names, numbers, and dates. One missing zero in the power needs could leave your booth without enough electricity. Third, make sure no field was filled in with a guess. Fields you gave no data for should be empty or filled in by you. Fourth, read the terms and fees before ticking the agreement, as Laras just did. Fifth, after submitting, keep proof of registration, such as a confirmation email or a screenshot. These five checks take only a minute or two, far less than sorting out a wrong registration. As you check, watch for the three most common mistakes. First, an entry lands in the wrong field, such as the full address in the city field because the layout is confusing. Second, date or number formats. Ten slash eleven can be read as November tenth or October eleventh, depending on the site. Third, the wrong dropdown choice, especially when the options are similar, such as the drinks and food categories. If you find a mistake, you can fix it yourself, or ask the agent to correct that field and stop again before submitting. Think of the submit button as a digital signature. The agent may prepare the document neatly, but the signature is still yours. With this division of work, Laras saves typing time without losing control over the commitments she makes.
Step 5: Repetitive forms
The last example is from Dewi. Every month she sends price quote requests to several suppliers, with forms that are very similar. The agent fills in the company name from Maju Bersama Co.'s standard data. Then the item and quantity: A4 copy paper, seventy gsm, one hundred fifty reams, matching this month's needs list. The needed-by date is no later than November tenth. The agent writes the full date with the month name, so it can't be misread. And a note asking suppliers to include shipping to Bandung, so the quotes can be compared fairly. Then the agent stops before the send request button, and Dewi presses it herself after rereading. For the second and third suppliers the standard data is the same, so Dewi only changes the form's address. Three tips for repetitive forms. First, keep your standard business data in one note or Project: name, business address, products, opening hours. The agent doesn't need to ask the same things every time. Second, do one form first, check the result, then move on to the next. A mistake in the first form won't be repeated in the fifth. Third, a CAPTCHA, the I'm-not-a-robot check, and verification codes are a human job. The agent will stop and hand them to you. The screens in this video are simulations, and Claude in Chrome may look different because it's updated often. With standard data and a checking habit, forms that used to take half an hour are done in a few minutes, without giving up accuracy.
Done!
We've sorted the data an agent may fill in, prepared the data and limits, watched the agent fill a form and stop when data was missing, then checked before submitting. In the next episode the agent works across several sites at once: gathering scattered data into one tidy table. See you there!
Practice exercises
Try these on your own after watching to lock in what you learned.
Write a standard data note for your business for forms you fill in often
Ask the agent to fill in one form and stop before submitting, then check it with the checklist
Note the fields that made the agent stop and ask, then complete your standard data
Ask the class material
Type a question or keyword; we find the part of this episode that explains it and jump the video there.
My notes
Notes are saved with the current video time and are only visible to you.
Questions & answers
Stuck on a step? Ask here; the instructor and other learners can answer.
No questions yet.
Your instructor
Cerdas Inovasi Digital Team
Software developers, BIM & 3D engineers, and AI practitioners
53 video classes1,286 episodes
We build software, BIM models, games and AI automations for clients every day, and turn that hands-on work into step-by-step classes: every step is shown on screen and comes with a PDF guide you can keep.
