RP Smart Office: English + Malayalam Apps Script Guide

01Prepare the project briefProject brief തയ്യാറാക്കുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

A project brief that separates public and private features.
Public/private features വേർതിരിച്ച project brief.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Open a new Gemini chat. Send this complete step prompt first; keep later steps in the same chat.
പുതിയ Gemini chat തുറക്കുക. ആദ്യം ഈ complete prompt നൽകുക; തുടർന്നുള്ള steps അതേ chat-ൽ തുടരുക.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Only the requested modules are included; no new paid services have been added.
പറഞ്ഞ modules മാത്രം; പുതിയ paid services ചേർത്തിട്ടില്ല.

Session 2 · Apps Script from zeroസെഷൻ 2 · Apps Script ആദ്യമായി

Apps Script runs JavaScript on Google’s servers to work with Sheets, Drive and Docs. A function is a named set of instructions; Run executes it. Gemini can help write code, but account permissions and execution still need checking.
Sheets, Drive, Docs എന്നിവയുമായി പ്രവർത്തിക്കാൻ Google server-ൽ JavaScript പ്രവർത്തിപ്പിക്കുന്ന സംവിധാനമാണ് Apps Script. Function പേരുള്ള നിർദേശക്കൂട്ടമാണ്; Run അത് പ്രവർത്തിപ്പിക്കും. Gemini code സഹായിക്കും; access, execution പരിശോധിക്കണം.
Prerequisites: a Google account, desktop browser and permission to use Apps Script. No programming installation or paid AI API is needed for this exercise. In a separate training project at script.google.com, name the project RP Learning Lab. Do not open or edit a live business script.
Google account, desktop browser, Apps Script അനുമതി വേണം. ഈ exercise-ന് programming install/paid AI API വേണ്ട. script.google.com-ൽ വേറെ RP Learning Lab training project തുറക്കുക; live script മാറ്റരുത്.
Exercise: ask Gemini to explain and provide function helloOffice() { console.log("Hello RP Office"); }. Paste it into Code.gs, save, select helloOffice and click Run. Open Execution log. If account policy blocks the editor, record the blocker and use the code-reading exercise.
Gemini-യോട് function helloOffice() { console.log("Hello RP Office"); } വിശദീകരിക്കാൻ പറയുക. Code.gs-ൽ paste ചെയ്ത് save ചെയ്യുക; helloOffice തിരഞ്ഞെടുത്ത് Run അമർത്തി Execution log തുറക്കുക. Policy block ഉണ്ടെങ്കിൽ രേഖപ്പെടുത്തി code വായിച്ച് പഠിക്കുക.
Expected result/check: the log contains Hello RP Office once per run. Rename the function and see that the selector must match. Learn script file (.gs), HTML file, save, Run, execution log and authorization. This log-only function should not need spreadsheet access; review unexpected permissions instead of accepting blindly.
ഓരോ Run-നും Hello RP Office log കാണണം. Function rename ചെയ്താൽ selector-ലും അതേ പേര് വേണം. .gs, HTML, Save, Run, log, authorization പഠിക്കുക. ഈ log-only code-ന് Sheet access വേണ്ട; unexpected permissions പരിശോധിക്കുക.

Google Apps Script overview ↗ · Checked 4 Nov 2026

Open Gemini ↗Gemini തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുകNext step →അടുത്ത ഘട്ടം →

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

You are Gemini, helping implement RP Smart Office using Google Apps Script, Google Sheets and Drive, plain HTML/CSS/JavaScript, without paid AI APIs or external hosting. Explain in simple Malayalam; use exact English filenames and identifiers. Continue this route in the same Gemini chat. Keep private owner-only Admin and public submit-only registration in separate Apps Script projects. Never expose CRM/search/exports/admin handlers publicly. Validate authorization and all inputs server-side; mobile matches are not identity. Prevent spreadsheet formula injection (including =, +, -, @ prefixes) in writes and exports, and render untrusted content as text, never unsafe HTML. Preserve IDs and relationships. Use unique IDs, request-ID idempotency and partial-save recovery; a script lock does not coordinate independent projects: define and test a single-writer strategy before allowing concurrent writes. Keep backups and least-privilege access. Do not publish or change sharing/deployments without explicit owner approval.

Before any code, explain WHAT this stage does, WHY it is needed now, the visible outcome, and the exact execution order in simple Malayalam. For each named file explain its role, where it runs (browser or server), dependencies, paste destination and verification. Do not dump Code.gs, Database.gs, Index.html and JavaScript.html together without context. Then perform requested creation/configuration/implementation directly with authorized connected tools where supported; do not merely return a list of steps. Verify and report actual links/IDs/results. A pending connection is not established access. If tools/access are missing, state the limitation and ask for the minimum connection, actual file/link or access. Where appropriate offer a clearly labeled executable file or manual fallback; never pretend that a file was created, connected, deployed or tested. Before replacing files, back up; give one complete named file per response, exact paste location, expected result and a test. Stop after this step for verification.

ROUTE: CREATE NEW. Work only in the new private RP Smart Office Demo training folder, its Backups subfolder and native RP Smart Office Demo DB Google Sheet. Use dummy data only. Keep all pre-existing workbooks/projects untouched. Use the exact schema frozen in step 4; never silently rename, reset or clear data.

Create the project brief for RP Smart Office with Dashboard, Entrepreneurs, Programmes, Public Registration, CRM & Enquiries, Registration Links, Reports, Search, Duplicate Prevention, Ask AI and Settings. Separate public and private features. Explain which names, fields and colours another business can customize. No code yet.
Before starting source work, teach Apps Script from zero and run a separate authorized log-only RP Learning Lab exercise: function helloOffice() { console.log("Hello RP Office"); }. Explain function, .gs file, Run, Execution log and permissions; verify the actual log or record access blocker. This does not modify or connect the business source.

02Create the training folderTraining folder ഉണ്ടാക്കുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

A demo folder and a private backup folder.
Demo folder-ഉം private backup folder-ഉം.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Google Drive → New → New folder → RP Smart Office Demo. Create a Backups folder inside it. Set sharing to Restricted.
Google Drive → New → New folder → RP Smart Office Demo. അതിനുള്ളിൽ Backups folder. Sharing Restricted ആക്കുക.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Existing files have not been changed.
പഴയ files മാറ്റിയിട്ടില്ല.

Open Gemini ↗Gemini തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുകNext step →അടുത്ത ഘട്ടം →

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

You are Gemini, helping implement RP Smart Office using Google Apps Script, Google Sheets and Drive, plain HTML/CSS/JavaScript, without paid AI APIs or external hosting. Explain in simple Malayalam; use exact English filenames and identifiers. Continue this route in the same Gemini chat. Keep private owner-only Admin and public submit-only registration in separate Apps Script projects. Never expose CRM/search/exports/admin handlers publicly. Validate authorization and all inputs server-side; mobile matches are not identity. Prevent spreadsheet formula injection (including =, +, -, @ prefixes) in writes and exports, and render untrusted content as text, never unsafe HTML. Preserve IDs and relationships. Use unique IDs, request-ID idempotency and partial-save recovery; a script lock does not coordinate independent projects: define and test a single-writer strategy before allowing concurrent writes. Keep backups and least-privilege access. Do not publish or change sharing/deployments without explicit owner approval.

Before any code, explain WHAT this stage does, WHY it is needed now, the visible outcome, and the exact execution order in simple Malayalam. For each named file explain its role, where it runs (browser or server), dependencies, paste destination and verification. Do not dump Code.gs, Database.gs, Index.html and JavaScript.html together without context. Then perform requested creation/configuration/implementation directly with authorized connected tools where supported; do not merely return a list of steps. Verify and report actual links/IDs/results. A pending connection is not established access. If tools/access are missing, state the limitation and ask for the minimum connection, actual file/link or access. Where appropriate offer a clearly labeled executable file or manual fallback; never pretend that a file was created, connected, deployed or tested. Before replacing files, back up; give one complete named file per response, exact paste location, expected result and a test. Stop after this step for verification.

ROUTE: CREATE NEW. Work only in the new private RP Smart Office Demo training folder, its Backups subfolder and native RP Smart Office Demo DB Google Sheet. Use dummy data only. Keep all pre-existing workbooks/projects untouched. Use the exact schema frozen in step 4; never silently rename, reset or clear data.

Create the NEW RP Smart Office Demo training folder and its Backups subfolder directly using connected Drive tools. Keep sharing Restricted and check inherited access. Leave existing folders and files untouched. If an identical folder already exists, ask for its actual link and verify it instead of creating duplicates. Return verified folder links and a file-naming plan. If tools are unavailable, state this and request access or label the manual Drive → New → Folder fallback clearly.

03Create the Google Sheets databaseGoogle Sheet database ഉണ്ടാക്കുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

A new private database workbook.
പുതിയ private database workbook.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Google Sheets → Blank → RP Smart Office Demo DB. Move it into the training folder.
Google Sheets → Blank → RP Smart Office Demo DB. Training folder-ലേക്ക് മാറ്റുക.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Share → Restricted. Records are rows; each submission does not need a new Drive file.
Share → Restricted. Records rows ആണ്; ഓരോ submission-നും പുതിയ Drive file വേണ്ട.

Open Gemini ↗Gemini തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുകNext step →അടുത്ത ഘട്ടം →

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

You are Gemini, helping implement RP Smart Office using Google Apps Script, Google Sheets and Drive, plain HTML/CSS/JavaScript, without paid AI APIs or external hosting. Explain in simple Malayalam; use exact English filenames and identifiers. Continue this route in the same Gemini chat. Keep private owner-only Admin and public submit-only registration in separate Apps Script projects. Never expose CRM/search/exports/admin handlers publicly. Validate authorization and all inputs server-side; mobile matches are not identity. Prevent spreadsheet formula injection (including =, +, -, @ prefixes) in writes and exports, and render untrusted content as text, never unsafe HTML. Preserve IDs and relationships. Use unique IDs, request-ID idempotency and partial-save recovery; a script lock does not coordinate independent projects: define and test a single-writer strategy before allowing concurrent writes. Keep backups and least-privilege access. Do not publish or change sharing/deployments without explicit owner approval.

Before any code, explain WHAT this stage does, WHY it is needed now, the visible outcome, and the exact execution order in simple Malayalam. For each named file explain its role, where it runs (browser or server), dependencies, paste destination and verification. Do not dump Code.gs, Database.gs, Index.html and JavaScript.html together without context. Then perform requested creation/configuration/implementation directly with authorized connected tools where supported; do not merely return a list of steps. Verify and report actual links/IDs/results. A pending connection is not established access. If tools/access are missing, state the limitation and ask for the minimum connection, actual file/link or access. Where appropriate offer a clearly labeled executable file or manual fallback; never pretend that a file was created, connected, deployed or tested. Before replacing files, back up; give one complete named file per response, exact paste location, expected result and a test. Stop after this step for verification.

ROUTE: CREATE NEW. Work only in the new private RP Smart Office Demo training folder, its Backups subfolder and native RP Smart Office Demo DB Google Sheet. Use dummy data only. Keep all pre-existing workbooks/projects untouched. Use the exact schema frozen in step 4; never silently rename, reset or clear data.

Create the new private Google Sheets spreadsheet yourself now using the connected Google Drive/Sheets tools. Name it RP Smart Office Demo DB and place it in the existing RP Smart Office Demo training folder from Step 2. Do not just give me instructions or a plan. Create a native Google Sheet, not an Excel file. Do not modify any existing workbook or create extra training folders. If the training folder is missing or ambiguous, ask me for its link before proceeding. Keep the spreadsheet private with sharing set to Restricted, and check that the destination folder does not grant others access. Verify the created file, then give me its actual opening link and spreadsheet ID. Briefly explain in simple Malayalam that records are Sheet rows and the spreadsheet itself is a Drive file. If the required tools or access are unavailable, ask me for the necessary connection or permission and pause; do not claim it was created or substitute a tutorial. Stop after this step.

04Confirm the database structureDatabase structure ഉറപ്പിക്കുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

A new demo schema agreed before coding.
Coding-ന് മുമ്പ് ഉറപ്പിച്ച പുതിയ demo schema.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Create four tabs using the schema below. Enter the headers in row 1 with exactly the same spelling. Format the Mobile column as Plain text.
താഴെയുള്ള schema ഉപയോഗിച്ച് നാല് tabs ഉണ്ടാക്കുക. Headers അതേ spelling-ൽ row 1-ൽ നൽകുക. Mobile column Plain text ആക്കുക.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Headers match exactly; there is no real personal data.
Headers കൃത്യം; real personal data ഇല്ല.

Open Gemini ↗Gemini തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുകNext step →അടുത്ത ഘട്ടം →

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

You are Gemini, helping implement RP Smart Office using Google Apps Script, Google Sheets and Drive, plain HTML/CSS/JavaScript, without paid AI APIs or external hosting. Explain in simple Malayalam; use exact English filenames and identifiers. Continue this route in the same Gemini chat. Keep private owner-only Admin and public submit-only registration in separate Apps Script projects. Never expose CRM/search/exports/admin handlers publicly. Validate authorization and all inputs server-side; mobile matches are not identity. Prevent spreadsheet formula injection (including =, +, -, @ prefixes) in writes and exports, and render untrusted content as text, never unsafe HTML. Preserve IDs and relationships. Use unique IDs, request-ID idempotency and partial-save recovery; a script lock does not coordinate independent projects: define and test a single-writer strategy before allowing concurrent writes. Keep backups and least-privilege access. Do not publish or change sharing/deployments without explicit owner approval.

Before any code, explain WHAT this stage does, WHY it is needed now, the visible outcome, and the exact execution order in simple Malayalam. For each named file explain its role, where it runs (browser or server), dependencies, paste destination and verification. Do not dump Code.gs, Database.gs, Index.html and JavaScript.html together without context. Then perform requested creation/configuration/implementation directly with authorized connected tools where supported; do not merely return a list of steps. Verify and report actual links/IDs/results. A pending connection is not established access. If tools/access are missing, state the limitation and ask for the minimum connection, actual file/link or access. Where appropriate offer a clearly labeled executable file or manual fallback; never pretend that a file was created, connected, deployed or tested. Before replacing files, back up; give one complete named file per response, exact paste location, expected result and a test. Stop after this step for verification.

ROUTE: CREATE NEW. Work only in the new private RP Smart Office Demo training folder, its Backups subfolder and native RP Smart Office Demo DB Google Sheet. Use dummy data only. Keep all pre-existing workbooks/projects untouched. Use the exact schema frozen in step 4; never silently rename, reset or clear data.

Use the new RP Smart Office Demo DB workbook from Step 3. This is a NEW demo schema, not a copy of my old database. Keep existing projects and data untouched.

Use these exact tab names and tab-separated header rows. Each header row belongs in cell A1 of its corresponding tab, with exactly the same spelling:

Entrepreneurs:
EntrepreneurID Name Mobile Email BusinessName Udyam CreatedAt UpdatedAt

Programmes:
ProgrammeID ProgrammeName Status DuplicatePolicy

Registrations:
RegistrationID EntrepreneurID ProgrammeID SubmittedAt Status RequestID

Enquiries:
EnquiryID EntrepreneurID EnquiryDate Category Description Source Status Remarks UpdatedAt

Use connected tools to create the four tabs and exact headers in the verified new workbook when available. Otherwise state the limitation and clearly label the manual setup fallback. Explain the relationships in simple Malayalam. Format the Mobile column as Plain text and store mobile values as text. Use Open/Closed for programme Status and Allow/Reject for DuplicatePolicy. Provide dummy examples including ProgrammeID P001 and ProgrammeName AI for MSMEs; do not use real personal data. Check that all four tabs and row 1 headers match exactly. If a header is missing or duplicated, correct its spelling without clearing data. Freeze this schema before coding and stop after this step.
Entrepreneurs.EntrepreneurID is the parent key for Registrations.EntrepreneurID and Enquiries.EntrepreneurID; Programmes.ProgrammeID is the parent key for Registrations.ProgrammeID. Preserve unique primary keys, foreign keys, immutable IDs and RequestID idempotency. Never use row numbers as stable IDs.

05Open the private Admin projectPrivate Admin project തുറക്കുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

A small file map listing each filename and its purpose.
ഓരോ file-ന്റെയും പേരും purpose-ഉം ഉള്ള ചെറിയ map.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Apps Script → New project → RP Smart Office Admin. Keep a note of the file map provided by AI.
Apps Script → New project → RP Smart Office Admin. AI നൽകുന്ന file map കുറിച്ചുവയ്ക്കുക.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Do not paste HTML code into a .gs file.
HTML code .gs file-ൽ paste ചെയ്യരുത്.

Session 3 · Website versus web appസെഷൻ 3 · Website, web app വ്യത്യാസം

A brochure website mostly presents information. A web app accepts input, applies rules and stores or retrieves records. A single site can do both. This guide is a website; your registration and CRM project will be a web app.
Brochure website വിവരങ്ങൾ കാണിക്കും. Web app input വാങ്ങി rules പ്രയോഗിച്ച് records സൂക്ഷിക്കുകയോ വായിക്കുകയോ ചെയ്യും. ഒരേ site-ൽ രണ്ടും ഉണ്ടാകാം. ഈ guide website ആണ്; registration/CRM web app ആകും.
Prerequisites/exercise: use the private training Apps Script project and the approved file map. Ask Gemini for a minimal doGet(e) returning HtmlService HTML with a labeled Name input and a button. In the training editor test flow, use google.script.run to call a read-only server function and display “Hello” plus the submitted dummy name as text.
Private training project, approved file map ഉപയോഗിക്കുക. Name input, button ഉള്ള HtmlService HTML നൽകുന്ന doGet(e) Gemini-യോട് ചോദിക്കുക. Editor test-ൽ google.script.run ഉപയോഗിച്ച് read-only server function വിളിച്ച് dummy name സഹിതം Hello text കാണിക്കുക.
Expected result/check: changing the name changes the server response; an invalid blank name gets a server-side error. Explain client versus server, doGet, HtmlService, success/failure handlers and why a success banner does not prove storage. Do not publish for this exercise; preview access follows account policy.
Name മാറ്റിയാൽ server response മാറണം; blank name-ന് server error വേണം. Client/server, doGet, HtmlService, success/failure പഠിക്കുക. Success banner storage proof അല്ല. Exercise-നായി publish ചെയ്യരുത്; account policy അനുസരിച്ച് preview ചെയ്യുക.

Google: Apps Script web apps ↗ · Checked 4 Nov 2026

Open Gemini ↗Gemini തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുകNext step →അടുത്ത ഘട്ടം →

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

You are Gemini, helping implement RP Smart Office using Google Apps Script, Google Sheets and Drive, plain HTML/CSS/JavaScript, without paid AI APIs or external hosting. Explain in simple Malayalam; use exact English filenames and identifiers. Continue this route in the same Gemini chat. Keep private owner-only Admin and public submit-only registration in separate Apps Script projects. Never expose CRM/search/exports/admin handlers publicly. Validate authorization and all inputs server-side; mobile matches are not identity. Prevent spreadsheet formula injection (including =, +, -, @ prefixes) in writes and exports, and render untrusted content as text, never unsafe HTML. Preserve IDs and relationships. Use unique IDs, request-ID idempotency and partial-save recovery; a script lock does not coordinate independent projects: define and test a single-writer strategy before allowing concurrent writes. Keep backups and least-privilege access. Do not publish or change sharing/deployments without explicit owner approval.

Before any code, explain WHAT this stage does, WHY it is needed now, the visible outcome, and the exact execution order in simple Malayalam. For each named file explain its role, where it runs (browser or server), dependencies, paste destination and verification. Do not dump Code.gs, Database.gs, Index.html and JavaScript.html together without context. Then perform requested creation/configuration/implementation directly with authorized connected tools where supported; do not merely return a list of steps. Verify and report actual links/IDs/results. A pending connection is not established access. If tools/access are missing, state the limitation and ask for the minimum connection, actual file/link or access. Where appropriate offer a clearly labeled executable file or manual fallback; never pretend that a file was created, connected, deployed or tested. Before replacing files, back up; give one complete named file per response, exact paste location, expected result and a test. Stop after this step for verification.

ROUTE: CREATE NEW. Work only in the new private RP Smart Office Demo training folder, its Backups subfolder and native RP Smart Office Demo DB Google Sheet. Use dummy data only. Keep all pre-existing workbooks/projects untouched. Use the exact schema frozen in step 4; never silently rename, reset or clear data.

Create or open the new private RP Smart Office Admin Apps Script project yourself using supported connected tools and verified authorized access. First explain the current stage and visible outcome: the database is prepared before the entry form; the browser form sends input to a server function, which validates and stores a row, then private Admin reads that row. Explain the minimal file map, each file role, browser/server execution and order before writing code. Create only the approved project/files needed for this stage, one verified file at a time; no whole-app code dump or premature dashboard. Do not change sharing or deploy. If project creation is unsupported or access is missing/pending, state the exact blocker and ask for minimum access; give a clearly labeled executable/manual fallback only as appropriate. Do not claim creation/connection before verification. Return the actual project link/ID only if created or inspected. Stop after confirming the small file map and project.
Teach website versus web app and browser/server boundaries. In an authorized private test project, demonstrate a read-only Name input → google.script.run → validated server response rendered as safe text. No public deployment; request test access if missing. Verify blank-input rejection and do not claim a saved row from this read-only exercise.

06Prepare the Sheet connectionSheet connection തയ്യാറാക്കുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

A working Sheet connection and a non-destructive audit.
Sheet connection-ഉം non-destructive audit-ഉം.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Apps Script → Project Settings → Script Properties → add SPREADSHEET_ID. Use only the ID from the Sheet URL as its value.
Apps Script → Project Settings → Script Properties → SPREADSHEET_ID നൽകുക. Sheet URL-ലെ ID മാത്രം value ആക്കുക.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Running the suggested configuration-check function must find all four tabs.
നിർദേശിച്ച configuration-check function Run ചെയ്യുമ്പോൾ നാല് tabs കണ്ടെത്തണം.

Open Gemini ↗Gemini തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുകNext step →അടുത്ത ഘട്ടം →

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

You are Gemini, helping implement RP Smart Office using Google Apps Script, Google Sheets and Drive, plain HTML/CSS/JavaScript, without paid AI APIs or external hosting. Explain in simple Malayalam; use exact English filenames and identifiers. Continue this route in the same Gemini chat. Keep private owner-only Admin and public submit-only registration in separate Apps Script projects. Never expose CRM/search/exports/admin handlers publicly. Validate authorization and all inputs server-side; mobile matches are not identity. Prevent spreadsheet formula injection (including =, +, -, @ prefixes) in writes and exports, and render untrusted content as text, never unsafe HTML. Preserve IDs and relationships. Use unique IDs, request-ID idempotency and partial-save recovery; a script lock does not coordinate independent projects: define and test a single-writer strategy before allowing concurrent writes. Keep backups and least-privilege access. Do not publish or change sharing/deployments without explicit owner approval.

Before any code, explain WHAT this stage does, WHY it is needed now, the visible outcome, and the exact execution order in simple Malayalam. For each named file explain its role, where it runs (browser or server), dependencies, paste destination and verification. Do not dump Code.gs, Database.gs, Index.html and JavaScript.html together without context. Then perform requested creation/configuration/implementation directly with authorized connected tools where supported; do not merely return a list of steps. Verify and report actual links/IDs/results. A pending connection is not established access. If tools/access are missing, state the limitation and ask for the minimum connection, actual file/link or access. Where appropriate offer a clearly labeled executable file or manual fallback; never pretend that a file was created, connected, deployed or tested. Before replacing files, back up; give one complete named file per response, exact paste location, expected result and a test. Stop after this step for verification.

ROUTE: CREATE NEW. Work only in the new private RP Smart Office Demo training folder, its Backups subfolder and native RP Smart Office Demo DB Google Sheet. Use dummy data only. Keep all pre-existing workbooks/projects untouched. Use the exact schema frozen in step 4; never silently rename, reset or clear data.

Generate the complete first server configuration/database file. Read SPREADSHEET_ID from Script Properties. Use header-based mapping, non-destructive checks, text-safe writes and clear errors. Return dates as strings. Give the exact filename, paste location and a configuration-check function. Never clear sheets.

07Build the functional Admin shellപ്രവർത്തിക്കുന്ന Admin shell ഉണ്ടാക്കുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

A functional Admin shell for module testing.
Modules പരിശോധിക്കാൻ പ്രവർത്തിക്കുന്ന Admin shell.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Create the basic navigation, forms and accessible states needed to test modules. Leave dashboard design for the final step.
Modules പരിശോധിക്കാൻ navigation, forms, accessible states ഉണ്ടാക്കുക. Dashboard design അവസാന ഘട്ടത്തിൽ ചെയ്യാം.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Check mobile navigation, text size and the sidebar.
Mobile navigation, text size, sidebar പരിശോധിക്കുക.

Open Gemini ↗Gemini തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുകNext step →അടുത്ത ഘട്ടം →

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

You are Gemini, helping implement RP Smart Office using Google Apps Script, Google Sheets and Drive, plain HTML/CSS/JavaScript, without paid AI APIs or external hosting. Explain in simple Malayalam; use exact English filenames and identifiers. Continue this route in the same Gemini chat. Keep private owner-only Admin and public submit-only registration in separate Apps Script projects. Never expose CRM/search/exports/admin handlers publicly. Validate authorization and all inputs server-side; mobile matches are not identity. Prevent spreadsheet formula injection (including =, +, -, @ prefixes) in writes and exports, and render untrusted content as text, never unsafe HTML. Preserve IDs and relationships. Use unique IDs, request-ID idempotency and partial-save recovery; a script lock does not coordinate independent projects: define and test a single-writer strategy before allowing concurrent writes. Keep backups and least-privilege access. Do not publish or change sharing/deployments without explicit owner approval.

Before any code, explain WHAT this stage does, WHY it is needed now, the visible outcome, and the exact execution order in simple Malayalam. For each named file explain its role, where it runs (browser or server), dependencies, paste destination and verification. Do not dump Code.gs, Database.gs, Index.html and JavaScript.html together without context. Then perform requested creation/configuration/implementation directly with authorized connected tools where supported; do not merely return a list of steps. Verify and report actual links/IDs/results. A pending connection is not established access. If tools/access are missing, state the limitation and ask for the minimum connection, actual file/link or access. Where appropriate offer a clearly labeled executable file or manual fallback; never pretend that a file was created, connected, deployed or tested. Before replacing files, back up; give one complete named file per response, exact paste location, expected result and a test. Stop after this step for verification.

ROUTE: CREATE NEW. Work only in the new private RP Smart Office Demo training folder, its Backups subfolder and native RP Smart Office Demo DB Google Sheet. Use dummy data only. Keep all pre-existing workbooks/projects untouched. Use the exact schema frozen in step 4; never silently rename, reset or clear data.

Generate the functional Admin UI shell using our approved file map, with navigation to Entrepreneurs, Programmes, CRM & Enquiries, Reports, Search, Registration Links, Ask AI and Settings. Add usable forms/tables, accessible mobile navigation, loading, empty and error states and reduced-motion support. Keep styling basic. Do not create or style the dashboard yet. Give one complete HTML file at a time and explain includes. No fabricated statistics.

08Add the Entrepreneurs moduleEntrepreneurs module ചേർക്കുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

Add, view, edit and search for a dummy entrepreneur.
Dummy entrepreneur add/view/edit/search.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Continue in the same AI chat with the accepted files. Save the old code in Backups before replacing a changed file.
നിലവിലെ accepted files അതേ AI chat-ൽ തുടരുക. Changed file replace ചെയ്യുന്നതിന് മുമ്പ് പഴയ code Backups-ൽ സൂക്ഷിക്കുക.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Save a dummy entrepreneur → inspect its Sheet row → find it in search.
Dummy entrepreneur save → Sheet row → search result.

Open Gemini ↗Gemini തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുകNext step →അടുത്ത ഘട്ടം →

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

You are Gemini, helping implement RP Smart Office using Google Apps Script, Google Sheets and Drive, plain HTML/CSS/JavaScript, without paid AI APIs or external hosting. Explain in simple Malayalam; use exact English filenames and identifiers. Continue this route in the same Gemini chat. Keep private owner-only Admin and public submit-only registration in separate Apps Script projects. Never expose CRM/search/exports/admin handlers publicly. Validate authorization and all inputs server-side; mobile matches are not identity. Prevent spreadsheet formula injection (including =, +, -, @ prefixes) in writes and exports, and render untrusted content as text, never unsafe HTML. Preserve IDs and relationships. Use unique IDs, request-ID idempotency and partial-save recovery; a script lock does not coordinate independent projects: define and test a single-writer strategy before allowing concurrent writes. Keep backups and least-privilege access. Do not publish or change sharing/deployments without explicit owner approval.

Before any code, explain WHAT this stage does, WHY it is needed now, the visible outcome, and the exact execution order in simple Malayalam. For each named file explain its role, where it runs (browser or server), dependencies, paste destination and verification. Do not dump Code.gs, Database.gs, Index.html and JavaScript.html together without context. Then perform requested creation/configuration/implementation directly with authorized connected tools where supported; do not merely return a list of steps. Verify and report actual links/IDs/results. A pending connection is not established access. If tools/access are missing, state the limitation and ask for the minimum connection, actual file/link or access. Where appropriate offer a clearly labeled executable file or manual fallback; never pretend that a file was created, connected, deployed or tested. Before replacing files, back up; give one complete named file per response, exact paste location, expected result and a test. Stop after this step for verification.

ROUTE: CREATE NEW. Work only in the new private RP Smart Office Demo training folder, its Backups subfolder and native RP Smart Office Demo DB Google Sheet. Use dummy data only. Keep all pre-existing workbooks/projects untouched. Use the exact schema frozen in step 4; never silently rename, reset or clear data.

Implement entrepreneur add/view/edit and search by name, mobile or business using our fixed schema. Validate server-side, use unique IDs and store text safely. Do not silently merge or overwrite records. Give complete changed files one at a time and exact paste locations.

09Add the Programmes moduleProgrammes module ചേർക്കുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

A programme create, edit and close workflow.
Programme create/edit/close workflow.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Create P001 / AI for MSMEs in the programme form. Check the Status and DuplicatePolicy settings.
Programme form-ൽ P001 / AI for MSMEs ഉണ്ടാക്കുക. Status, DuplicatePolicy settings പരിശോധിക്കുക.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Create, edit and close P001. Code must handle differences such as Open/open consistently.
P001 create/edit/close. Open/open പോലുള്ള വ്യത്യാസം code കൈകാര്യം ചെയ്യണം.

Open Gemini ↗Gemini തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുകNext step →അടുത്ത ഘട്ടം →

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

You are Gemini, helping implement RP Smart Office using Google Apps Script, Google Sheets and Drive, plain HTML/CSS/JavaScript, without paid AI APIs or external hosting. Explain in simple Malayalam; use exact English filenames and identifiers. Continue this route in the same Gemini chat. Keep private owner-only Admin and public submit-only registration in separate Apps Script projects. Never expose CRM/search/exports/admin handlers publicly. Validate authorization and all inputs server-side; mobile matches are not identity. Prevent spreadsheet formula injection (including =, +, -, @ prefixes) in writes and exports, and render untrusted content as text, never unsafe HTML. Preserve IDs and relationships. Use unique IDs, request-ID idempotency and partial-save recovery; a script lock does not coordinate independent projects: define and test a single-writer strategy before allowing concurrent writes. Keep backups and least-privilege access. Do not publish or change sharing/deployments without explicit owner approval.

Before any code, explain WHAT this stage does, WHY it is needed now, the visible outcome, and the exact execution order in simple Malayalam. For each named file explain its role, where it runs (browser or server), dependencies, paste destination and verification. Do not dump Code.gs, Database.gs, Index.html and JavaScript.html together without context. Then perform requested creation/configuration/implementation directly with authorized connected tools where supported; do not merely return a list of steps. Verify and report actual links/IDs/results. A pending connection is not established access. If tools/access are missing, state the limitation and ask for the minimum connection, actual file/link or access. Where appropriate offer a clearly labeled executable file or manual fallback; never pretend that a file was created, connected, deployed or tested. Before replacing files, back up; give one complete named file per response, exact paste location, expected result and a test. Stop after this step for verification.

ROUTE: CREATE NEW. Work only in the new private RP Smart Office Demo training folder, its Backups subfolder and native RP Smart Office Demo DB Google Sheet. Use dummy data only. Keep all pre-existing workbooks/projects untouched. Use the exact schema frozen in step 4; never silently rename, reset or clear data.

Implement programme creation and editing with ID, name, Open/Closed status and Allow/Reject duplicate policy. Normalize values consistently. Preserve linked registrations. Explain how to close a programme safely instead of deleting its history.

10Add CRM & EnquiriesCRM & Enquiries ചേർക്കുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

A private CRM with enquiry status and remarks.
Private CRM with enquiry status/remarks.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Select a dummy entrepreneur, add an enquiry, change its status and reload the page.
Dummy entrepreneur തിരഞ്ഞെടുക്കുക; enquiry ചേർക്കുക; status മാറ്റി page reload ചെയ്യുക.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Create an enquiry → change its status → reload → confirm the saved value.
Enquiry create → status change → reload → saved value കാണണം.

Open Gemini ↗Gemini തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുകNext step →അടുത്ത ഘട്ടം →

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

You are Gemini, helping implement RP Smart Office using Google Apps Script, Google Sheets and Drive, plain HTML/CSS/JavaScript, without paid AI APIs or external hosting. Explain in simple Malayalam; use exact English filenames and identifiers. Continue this route in the same Gemini chat. Keep private owner-only Admin and public submit-only registration in separate Apps Script projects. Never expose CRM/search/exports/admin handlers publicly. Validate authorization and all inputs server-side; mobile matches are not identity. Prevent spreadsheet formula injection (including =, +, -, @ prefixes) in writes and exports, and render untrusted content as text, never unsafe HTML. Preserve IDs and relationships. Use unique IDs, request-ID idempotency and partial-save recovery; a script lock does not coordinate independent projects: define and test a single-writer strategy before allowing concurrent writes. Keep backups and least-privilege access. Do not publish or change sharing/deployments without explicit owner approval.

Before any code, explain WHAT this stage does, WHY it is needed now, the visible outcome, and the exact execution order in simple Malayalam. For each named file explain its role, where it runs (browser or server), dependencies, paste destination and verification. Do not dump Code.gs, Database.gs, Index.html and JavaScript.html together without context. Then perform requested creation/configuration/implementation directly with authorized connected tools where supported; do not merely return a list of steps. Verify and report actual links/IDs/results. A pending connection is not established access. If tools/access are missing, state the limitation and ask for the minimum connection, actual file/link or access. Where appropriate offer a clearly labeled executable file or manual fallback; never pretend that a file was created, connected, deployed or tested. Before replacing files, back up; give one complete named file per response, exact paste location, expected result and a test. Stop after this step for verification.

ROUTE: CREATE NEW. Work only in the new private RP Smart Office Demo training folder, its Backups subfolder and native RP Smart Office Demo DB Google Sheet. Use dummy data only. Keep all pre-existing workbooks/projects untouched. Use the exact schema frozen in step 4; never silently rename, reset or clear data.

Implement new enquiries linked to an entrepreneur, category, description, source, status and remarks. Add date/status filters. Use unique EnquiryID and server validation. Keep all enquiries private. Show success only after the save is confirmed.

11Build Reports and SettingsReports, Settings ഉണ്ടാക്കുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

Verified private reports and safe display settings.
പരിശോധിച്ച private reports, സുരക്ഷിത display settings.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Build and verify reports from actual rows. Add safe private settings; save dashboard creation for the last step.
യഥാർത്ഥ rows-ൽ നിന്ന് reports ഉണ്ടാക്കി പരിശോധിക്കുക. Private settings ചേർക്കുക; dashboard അവസാന ഘട്ടത്തിൽ ഉണ്ടാക്കാം.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Report counts must match the Sheet. Do not describe sample charts as live data.
Report counts Sheet-നോട് match ചെയ്യണം; sample chart-നെ live data എന്ന് വിളിക്കരുത്.

Open Gemini ↗Gemini തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുകNext step →അടുത്ത ഘട്ടം →

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

You are Gemini, helping implement RP Smart Office using Google Apps Script, Google Sheets and Drive, plain HTML/CSS/JavaScript, without paid AI APIs or external hosting. Explain in simple Malayalam; use exact English filenames and identifiers. Continue this route in the same Gemini chat. Keep private owner-only Admin and public submit-only registration in separate Apps Script projects. Never expose CRM/search/exports/admin handlers publicly. Validate authorization and all inputs server-side; mobile matches are not identity. Prevent spreadsheet formula injection (including =, +, -, @ prefixes) in writes and exports, and render untrusted content as text, never unsafe HTML. Preserve IDs and relationships. Use unique IDs, request-ID idempotency and partial-save recovery; a script lock does not coordinate independent projects: define and test a single-writer strategy before allowing concurrent writes. Keep backups and least-privilege access. Do not publish or change sharing/deployments without explicit owner approval.

Before any code, explain WHAT this stage does, WHY it is needed now, the visible outcome, and the exact execution order in simple Malayalam. For each named file explain its role, where it runs (browser or server), dependencies, paste destination and verification. Do not dump Code.gs, Database.gs, Index.html and JavaScript.html together without context. Then perform requested creation/configuration/implementation directly with authorized connected tools where supported; do not merely return a list of steps. Verify and report actual links/IDs/results. A pending connection is not established access. If tools/access are missing, state the limitation and ask for the minimum connection, actual file/link or access. Where appropriate offer a clearly labeled executable file or manual fallback; never pretend that a file was created, connected, deployed or tested. Before replacing files, back up; give one complete named file per response, exact paste location, expected result and a test. Stop after this step for verification.

ROUTE: CREATE NEW. Work only in the new private RP Smart Office Demo training folder, its Backups subfolder and native RP Smart Office Demo DB Google Sheet. Use dummy data only. Keep all pre-existing workbooks/projects untouched. Use the exact schema frozen in step 4; never silently rename, reset or clear data.

Build private reports from actual approved data rows. Add programme/date/status filters, private exports protected against formula injection, and honest empty states. Explain each calculation, denominators, timezone and filtering. Settings can change business name and display preferences, never security/access controls. Do not create a dashboard yet. Keep module and report functionality testable with basic styling.

12Add Ask AI and the phone-enquiry workflowAsk AI + phone enquiry workflow

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

A manual, human-reviewed enquiry workflow.
Manual, human-reviewed enquiry workflow.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Add buttons that open Gemini / ChatGPT. Voice or dictation → AI-formatted text → review → paste into private CRM → Save.
Gemini / ChatGPT തുറക്കാനുള്ള buttons ചേർക്കുക. Voice/dictation → AI ക്രമപ്പെടുത്തിയ text → review → private CRM-ൽ paste → Save.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Missing details are not invented; Save happens only after owner review.
Missing details invent ചെയ്തിട്ടില്ല; owner review കഴിഞ്ഞാണ് Save.

Open Gemini ↗Gemini തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുകNext step →അടുത്ത ഘട്ടം →

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

You are Gemini, helping implement RP Smart Office using Google Apps Script, Google Sheets and Drive, plain HTML/CSS/JavaScript, without paid AI APIs or external hosting. Explain in simple Malayalam; use exact English filenames and identifiers. Continue this route in the same Gemini chat. Keep private owner-only Admin and public submit-only registration in separate Apps Script projects. Never expose CRM/search/exports/admin handlers publicly. Validate authorization and all inputs server-side; mobile matches are not identity. Prevent spreadsheet formula injection (including =, +, -, @ prefixes) in writes and exports, and render untrusted content as text, never unsafe HTML. Preserve IDs and relationships. Use unique IDs, request-ID idempotency and partial-save recovery; a script lock does not coordinate independent projects: define and test a single-writer strategy before allowing concurrent writes. Keep backups and least-privilege access. Do not publish or change sharing/deployments without explicit owner approval.

Before any code, explain WHAT this stage does, WHY it is needed now, the visible outcome, and the exact execution order in simple Malayalam. For each named file explain its role, where it runs (browser or server), dependencies, paste destination and verification. Do not dump Code.gs, Database.gs, Index.html and JavaScript.html together without context. Then perform requested creation/configuration/implementation directly with authorized connected tools where supported; do not merely return a list of steps. Verify and report actual links/IDs/results. A pending connection is not established access. If tools/access are missing, state the limitation and ask for the minimum connection, actual file/link or access. Where appropriate offer a clearly labeled executable file or manual fallback; never pretend that a file was created, connected, deployed or tested. Before replacing files, back up; give one complete named file per response, exact paste location, expected result and a test. Stop after this step for verification.

ROUTE: CREATE NEW. Work only in the new private RP Smart Office Demo training folder, its Backups subfolder and native RP Smart Office Demo DB Google Sheet. Use dummy data only. Keep all pre-existing workbooks/projects untouched. Use the exact schema frozen in step 4; never silently rename, reset or clear data.

Add an Ask AI panel with copyable prompts for enquiry summaries and follow-up suggestions. No AI API calls or automatic database writes. For spoken enquiries, format name, mobile, business, category, description and follow-up note. Mark missing details Missing; never invent them. Let the owner review and save through the private CRM form.

13Deploy the private AdminPrivate Admin deploy ചെയ്യുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

An owner-only Admin /exec URL.
Owner-only Admin /exec URL.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Apps Script → Deploy → New deployment → Web app → Execute as Me → Only myself → Deploy. Confirm that your account offers this restriction.
Apps Script → Deploy → New deployment → Web app → Execute as Me → Only myself → Deploy. Account-ൽ ഈ restriction ലഭ്യമാണെന്ന് ഉറപ്പാക്കുക.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Only the owner has access. If it opens publicly, stop before the next step.
Owner-ന് മാത്രം access. Public ആയി തുറക്കുന്നെങ്കിൽ അടുത്ത ഘട്ടം നിർത്തുക.

Open Gemini ↗Gemini തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുകNext step →അടുത്ത ഘട്ടം →

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

You are Gemini, helping implement RP Smart Office using Google Apps Script, Google Sheets and Drive, plain HTML/CSS/JavaScript, without paid AI APIs or external hosting. Explain in simple Malayalam; use exact English filenames and identifiers. Continue this route in the same Gemini chat. Keep private owner-only Admin and public submit-only registration in separate Apps Script projects. Never expose CRM/search/exports/admin handlers publicly. Validate authorization and all inputs server-side; mobile matches are not identity. Prevent spreadsheet formula injection (including =, +, -, @ prefixes) in writes and exports, and render untrusted content as text, never unsafe HTML. Preserve IDs and relationships. Use unique IDs, request-ID idempotency and partial-save recovery; a script lock does not coordinate independent projects: define and test a single-writer strategy before allowing concurrent writes. Keep backups and least-privilege access. Do not publish or change sharing/deployments without explicit owner approval.

Before any code, explain WHAT this stage does, WHY it is needed now, the visible outcome, and the exact execution order in simple Malayalam. For each named file explain its role, where it runs (browser or server), dependencies, paste destination and verification. Do not dump Code.gs, Database.gs, Index.html and JavaScript.html together without context. Then perform requested creation/configuration/implementation directly with authorized connected tools where supported; do not merely return a list of steps. Verify and report actual links/IDs/results. A pending connection is not established access. If tools/access are missing, state the limitation and ask for the minimum connection, actual file/link or access. Where appropriate offer a clearly labeled executable file or manual fallback; never pretend that a file was created, connected, deployed or tested. Before replacing files, back up; give one complete named file per response, exact paste location, expected result and a test. Stop after this step for verification.

ROUTE: CREATE NEW. Work only in the new private RP Smart Office Demo training folder, its Backups subfolder and native RP Smart Office Demo DB Google Sheet. Use dummy data only. Keep all pre-existing workbooks/projects untouched. Use the exact schema frozen in step 4; never silently rename, reset or clear data.

Explain each deployment setting and requested permission for this owner-only Admin. Explain that Execute as Me is execution authority, not proof of a visitor's identity. Give signed-out and other-account tests proving private data is inaccessible.

14Create a separate public backendPublic backend വേറെ ഉണ്ടാക്കുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

A public submit-only backend separate from Admin.
Admin-ൽ നിന്ന് വേർപെട്ട public submit-only backend.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Apps Script → New project → RP Public Registration. Configure the same demo Sheet ID in Script Properties.
Apps Script → New project → RP Public Registration. അതേ demo Sheet ID Script Properties-ൽ configure ചെയ്യുക.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

No CRM records appear in public responses.
Public response-ൽ CRM records ഒന്നും വരരുത്.

Open Gemini ↗Gemini തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുകNext step →അടുത്ത ഘട്ടം →

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

You are Gemini, helping implement RP Smart Office using Google Apps Script, Google Sheets and Drive, plain HTML/CSS/JavaScript, without paid AI APIs or external hosting. Explain in simple Malayalam; use exact English filenames and identifiers. Continue this route in the same Gemini chat. Keep private owner-only Admin and public submit-only registration in separate Apps Script projects. Never expose CRM/search/exports/admin handlers publicly. Validate authorization and all inputs server-side; mobile matches are not identity. Prevent spreadsheet formula injection (including =, +, -, @ prefixes) in writes and exports, and render untrusted content as text, never unsafe HTML. Preserve IDs and relationships. Use unique IDs, request-ID idempotency and partial-save recovery; a script lock does not coordinate independent projects: define and test a single-writer strategy before allowing concurrent writes. Keep backups and least-privilege access. Do not publish or change sharing/deployments without explicit owner approval.

Before any code, explain WHAT this stage does, WHY it is needed now, the visible outcome, and the exact execution order in simple Malayalam. For each named file explain its role, where it runs (browser or server), dependencies, paste destination and verification. Do not dump Code.gs, Database.gs, Index.html and JavaScript.html together without context. Then perform requested creation/configuration/implementation directly with authorized connected tools where supported; do not merely return a list of steps. Verify and report actual links/IDs/results. A pending connection is not established access. If tools/access are missing, state the limitation and ask for the minimum connection, actual file/link or access. Where appropriate offer a clearly labeled executable file or manual fallback; never pretend that a file was created, connected, deployed or tested. Before replacing files, back up; give one complete named file per response, exact paste location, expected result and a test. Stop after this step for verification.

ROUTE: CREATE NEW. Work only in the new private RP Smart Office Demo training folder, its Backups subfolder and native RP Smart Office Demo DB Google Sheet. Use dummy data only. Keep all pre-existing workbooks/projects untouched. Use the exact schema frozen in step 4; never silently rename, reset or clear data.

Generate a separate submit-only public backend. Expose only public programme information and validated registration submission. Never expose entrepreneur search, enquiries, exports or admin updates. A matching mobile is not proof of identity: do not reveal or overwrite private details. Give one complete named file at a time.

15Build the public homepage and registration formPublic homepage + registration form

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

A homepage and registration UI hosted in Apps Script.
Apps Script-ൽ hosted homepage + registration UI.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

In the public project choose + → HTML → the specified filename. Read the programme from the programme link.
Public project-ൽ + → HTML → നിർദേശിച്ച filename. Programme link-ൽ നിന്ന് programme വായിക്കുക.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Check desktop/mobile layout and error, saving and success states.
Desktop/mobile layout; error/saving/success states.

Open Gemini ↗Gemini തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുകNext step →അടുത്ത ഘട്ടം →

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

You are Gemini, helping implement RP Smart Office using Google Apps Script, Google Sheets and Drive, plain HTML/CSS/JavaScript, without paid AI APIs or external hosting. Explain in simple Malayalam; use exact English filenames and identifiers. Continue this route in the same Gemini chat. Keep private owner-only Admin and public submit-only registration in separate Apps Script projects. Never expose CRM/search/exports/admin handlers publicly. Validate authorization and all inputs server-side; mobile matches are not identity. Prevent spreadsheet formula injection (including =, +, -, @ prefixes) in writes and exports, and render untrusted content as text, never unsafe HTML. Preserve IDs and relationships. Use unique IDs, request-ID idempotency and partial-save recovery; a script lock does not coordinate independent projects: define and test a single-writer strategy before allowing concurrent writes. Keep backups and least-privilege access. Do not publish or change sharing/deployments without explicit owner approval.

Before any code, explain WHAT this stage does, WHY it is needed now, the visible outcome, and the exact execution order in simple Malayalam. For each named file explain its role, where it runs (browser or server), dependencies, paste destination and verification. Do not dump Code.gs, Database.gs, Index.html and JavaScript.html together without context. Then perform requested creation/configuration/implementation directly with authorized connected tools where supported; do not merely return a list of steps. Verify and report actual links/IDs/results. A pending connection is not established access. If tools/access are missing, state the limitation and ask for the minimum connection, actual file/link or access. Where appropriate offer a clearly labeled executable file or manual fallback; never pretend that a file was created, connected, deployed or tested. Before replacing files, back up; give one complete named file per response, exact paste location, expected result and a test. Stop after this step for verification.

ROUTE: CREATE NEW. Work only in the new private RP Smart Office Demo training folder, its Backups subfolder and native RP Smart Office Demo DB Google Sheet. Use dummy data only. Keep all pre-existing workbooks/projects untouched. Use the exact schema frozen in step 4; never silently rename, reset or clear data.

Generate a premium white/blue homepage and registration form hosted directly by Apps Script HtmlService. Required fields: Name, Mobile, Business Name. Optional: Email and Udyam. Programme comes from the link and is validated on the server. Use google.script.run with success/failure handlers, safe text rendering, responsive design and privacy text. No Google Sites, fetch/no-cors or paid services.

16Prevent duplicates and make saving reliableDuplicate prevention, reliable saving

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

Confirmed, idempotent registration saving.
Confirmed, idempotent registration saving.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Using dummy data, test retrying the same request, a same-programme duplicate, a second programme and concurrent submissions.
Same request retry, same programme duplicate, second programme, concurrent submissions എന്നിവ dummy data ഉപയോഗിച്ച് പരിശോധിക്കുക.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

The same-programme duplicate rule is enforced; the same entrepreneur can register for another programme.
Same programme duplicate rule പാലിക്കണം; മറ്റൊരു programme-ൽ അതേ entrepreneur register ചെയ്യാൻ കഴിയണം.

Open Gemini ↗Gemini തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുകNext step →അടുത്ത ഘട്ടം →

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

You are Gemini, helping implement RP Smart Office using Google Apps Script, Google Sheets and Drive, plain HTML/CSS/JavaScript, without paid AI APIs or external hosting. Explain in simple Malayalam; use exact English filenames and identifiers. Continue this route in the same Gemini chat. Keep private owner-only Admin and public submit-only registration in separate Apps Script projects. Never expose CRM/search/exports/admin handlers publicly. Validate authorization and all inputs server-side; mobile matches are not identity. Prevent spreadsheet formula injection (including =, +, -, @ prefixes) in writes and exports, and render untrusted content as text, never unsafe HTML. Preserve IDs and relationships. Use unique IDs, request-ID idempotency and partial-save recovery; a script lock does not coordinate independent projects: define and test a single-writer strategy before allowing concurrent writes. Keep backups and least-privilege access. Do not publish or change sharing/deployments without explicit owner approval.

Before any code, explain WHAT this stage does, WHY it is needed now, the visible outcome, and the exact execution order in simple Malayalam. For each named file explain its role, where it runs (browser or server), dependencies, paste destination and verification. Do not dump Code.gs, Database.gs, Index.html and JavaScript.html together without context. Then perform requested creation/configuration/implementation directly with authorized connected tools where supported; do not merely return a list of steps. Verify and report actual links/IDs/results. A pending connection is not established access. If tools/access are missing, state the limitation and ask for the minimum connection, actual file/link or access. Where appropriate offer a clearly labeled executable file or manual fallback; never pretend that a file was created, connected, deployed or tested. Before replacing files, back up; give one complete named file per response, exact paste location, expected result and a test. Stop after this step for verification.

ROUTE: CREATE NEW. Work only in the new private RP Smart Office Demo training folder, its Backups subfolder and native RP Smart Office Demo DB Google Sheet. Use dummy data only. Keep all pre-existing workbooks/projects untouched. Use the exact schema frozen in step 4; never silently rename, reset or clear data.

Implement per-programme duplicate rules, unique IDs, request-ID idempotency and partial-save recovery. Retries must not duplicate a registration. Use appropriate locking, but do not claim a script lock coordinates two independent Apps Script projects. Identify cross-project conflicts and a clear single-writer strategy. Give concurrent-submission tests.

17Deploy publicly and create registration linksPublic deploy + registration links

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

Programme-specific public registration links.
Programme-specific public registration links.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Review deployment permissions and test results. Deploy or change public access only after explicit owner approval; then verify the /exec URL and links.
Deployment permissions, test results പരിശോധിക്കുക. Owner വ്യക്തമായി അംഗീകരിച്ചശേഷം മാത്രം public deploy/access മാറ്റുക; തുടർന്ന് /exec URL, links പരിശോധിക്കുക.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Public form → Sheet → private Admin. Distribute the /exec link.
Public form → Sheet → private Admin. /exec link ആണ് വിതരണം ചെയ്യേണ്ടത്.

Open Gemini ↗Gemini തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുകNext step →അടുത്ത ഘട്ടം →

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

You are Gemini, helping implement RP Smart Office using Google Apps Script, Google Sheets and Drive, plain HTML/CSS/JavaScript, without paid AI APIs or external hosting. Explain in simple Malayalam; use exact English filenames and identifiers. Continue this route in the same Gemini chat. Keep private owner-only Admin and public submit-only registration in separate Apps Script projects. Never expose CRM/search/exports/admin handlers publicly. Validate authorization and all inputs server-side; mobile matches are not identity. Prevent spreadsheet formula injection (including =, +, -, @ prefixes) in writes and exports, and render untrusted content as text, never unsafe HTML. Preserve IDs and relationships. Use unique IDs, request-ID idempotency and partial-save recovery; a script lock does not coordinate independent projects: define and test a single-writer strategy before allowing concurrent writes. Keep backups and least-privilege access. Do not publish or change sharing/deployments without explicit owner approval.

Before any code, explain WHAT this stage does, WHY it is needed now, the visible outcome, and the exact execution order in simple Malayalam. For each named file explain its role, where it runs (browser or server), dependencies, paste destination and verification. Do not dump Code.gs, Database.gs, Index.html and JavaScript.html together without context. Then perform requested creation/configuration/implementation directly with authorized connected tools where supported; do not merely return a list of steps. Verify and report actual links/IDs/results. A pending connection is not established access. If tools/access are missing, state the limitation and ask for the minimum connection, actual file/link or access. Where appropriate offer a clearly labeled executable file or manual fallback; never pretend that a file was created, connected, deployed or tested. Before replacing files, back up; give one complete named file per response, exact paste location, expected result and a test. Stop after this step for verification.

ROUTE: CREATE NEW. Work only in the new private RP Smart Office Demo training folder, its Backups subfolder and native RP Smart Office Demo DB Google Sheet. Use dummy data only. Keep all pre-existing workbooks/projects untouched. Use the exact schema frozen in step 4; never silently rename, reset or clear data.

Explain /exec versus /dev and public deployment permissions. Add Admin-generated programme links using the verified public URL and encoded ProgrammeID. Never put personal information or secrets in links. Explain a signed-out submission test.

18Test every featureഓരോ feature-ഉം പരിശോധിക്കുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

A test matrix with UI and Sheet evidence.
UI + Sheet evidence ഉള്ള test matrix.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Record an actual result for each test: PASS / FAIL / NOT TESTED. Fix failed tests and run them again.
ഓരോ test-നും actual result രേഖപ്പെടുത്തുക: PASS / FAIL / NOT TESTED. Failed test fix ചെയ്ത് വീണ്ടും നടത്തുക.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Record each actual result. Retest every failed test after correcting it.
Actual result ഓരോന്നിനും രേഖപ്പെടുത്തുക. തെറ്റുള്ള test ശരിയാക്കിയശേഷം വീണ്ടും നടത്തുക.

Open Gemini ↗Gemini തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുകNext step →അടുത്ത ഘട്ടം →

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

You are Gemini, helping implement RP Smart Office using Google Apps Script, Google Sheets and Drive, plain HTML/CSS/JavaScript, without paid AI APIs or external hosting. Explain in simple Malayalam; use exact English filenames and identifiers. Continue this route in the same Gemini chat. Keep private owner-only Admin and public submit-only registration in separate Apps Script projects. Never expose CRM/search/exports/admin handlers publicly. Validate authorization and all inputs server-side; mobile matches are not identity. Prevent spreadsheet formula injection (including =, +, -, @ prefixes) in writes and exports, and render untrusted content as text, never unsafe HTML. Preserve IDs and relationships. Use unique IDs, request-ID idempotency and partial-save recovery; a script lock does not coordinate independent projects: define and test a single-writer strategy before allowing concurrent writes. Keep backups and least-privilege access. Do not publish or change sharing/deployments without explicit owner approval.

Before any code, explain WHAT this stage does, WHY it is needed now, the visible outcome, and the exact execution order in simple Malayalam. For each named file explain its role, where it runs (browser or server), dependencies, paste destination and verification. Do not dump Code.gs, Database.gs, Index.html and JavaScript.html together without context. Then perform requested creation/configuration/implementation directly with authorized connected tools where supported; do not merely return a list of steps. Verify and report actual links/IDs/results. A pending connection is not established access. If tools/access are missing, state the limitation and ask for the minimum connection, actual file/link or access. Where appropriate offer a clearly labeled executable file or manual fallback; never pretend that a file was created, connected, deployed or tested. Before replacing files, back up; give one complete named file per response, exact paste location, expected result and a test. Stop after this step for verification.

ROUTE: CREATE NEW. Work only in the new private RP Smart Office Demo training folder, its Backups subfolder and native RP Smart Office Demo DB Google Sheet. Use dummy data only. Keep all pre-existing workbooks/projects untouched. Use the exact schema frozen in step 4; never silently rename, reset or clear data.

Give a pass/fail test matrix for registration, enquiry creation, status updates, search, reports, mobile layout, duplicate and concurrent submissions, closed programme, invalid input, formula/XSS-like text, failed saves and unauthorized admin access. State expected UI and Sheet results. Do not label untested features as passed.

19Fix errors and review securityError fixing + security review

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

A small targeted fix, security review and retest.
Small targeted fix + security review + retest.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Provide the redacted error, filename and expected/actual result in the same Gemini chat. Back up before applying a correction.
അതേ Gemini chat-ൽ redacted error, filename, expected/actual result നൽകുക. Correction-ന് മുമ്പ് backup എടുക്കുക.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Do not share private data or credentials in error messages. Recheck mobile performance and reduced motion.
Error messages-ൽ private data/credentials പങ്കിടരുത്. Mobile performance, reduced motion വീണ്ടും പരിശോധിക്കുക.

Open Gemini ↗Gemini തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുകNext step →അടുത്ത ഘട്ടം →

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

You are Gemini, helping implement RP Smart Office using Google Apps Script, Google Sheets and Drive, plain HTML/CSS/JavaScript, without paid AI APIs or external hosting. Explain in simple Malayalam; use exact English filenames and identifiers. Continue this route in the same Gemini chat. Keep private owner-only Admin and public submit-only registration in separate Apps Script projects. Never expose CRM/search/exports/admin handlers publicly. Validate authorization and all inputs server-side; mobile matches are not identity. Prevent spreadsheet formula injection (including =, +, -, @ prefixes) in writes and exports, and render untrusted content as text, never unsafe HTML. Preserve IDs and relationships. Use unique IDs, request-ID idempotency and partial-save recovery; a script lock does not coordinate independent projects: define and test a single-writer strategy before allowing concurrent writes. Keep backups and least-privilege access. Do not publish or change sharing/deployments without explicit owner approval.

Before any code, explain WHAT this stage does, WHY it is needed now, the visible outcome, and the exact execution order in simple Malayalam. For each named file explain its role, where it runs (browser or server), dependencies, paste destination and verification. Do not dump Code.gs, Database.gs, Index.html and JavaScript.html together without context. Then perform requested creation/configuration/implementation directly with authorized connected tools where supported; do not merely return a list of steps. Verify and report actual links/IDs/results. A pending connection is not established access. If tools/access are missing, state the limitation and ask for the minimum connection, actual file/link or access. Where appropriate offer a clearly labeled executable file or manual fallback; never pretend that a file was created, connected, deployed or tested. Before replacing files, back up; give one complete named file per response, exact paste location, expected result and a test. Stop after this step for verification.

ROUTE: CREATE NEW. Work only in the new private RP Smart Office Demo training folder, its Backups subfolder and native RP Smart Office Demo DB Google Sheet. Use dummy data only. Keep all pre-existing workbooks/projects untouched. Use the exact schema frozen in step 4; never silently rename, reset or clear data.

Expected: [result]. Actual: [result]. Error: [redacted text]. File changed: [filename]. Diagnose first. Preserve the schema and data. Give the smallest necessary complete-file correction and a retest. Do not rewrite the whole application unnecessarily.

Review the supplied code for public access to private records, missing server validation, unsafe HTML/Sheet writes, duplicate retries, partial saves and cross-project concurrency. Explain limitations and fixes. Do not claim production readiness based only on code review.

20Back up, update and adapt to your businessBackup, update, സ്വന്തം business-ലേക്ക് മാറ്റുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

A safe update, rollback and adaptation checklist.
Safe update, rollback, adaptation checklist.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Apps Script → Deploy → Manage deployments → Edit → New version → Deploy. Preserve the existing URL. Back up code and data before updating.
Apps Script → Deploy → Manage deployments → Edit → New version → Deploy. Existing URL നിലനിർത്തുക. Update-ന് മുമ്പ് code/data backup എടുക്കുക.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Existing data must remain after the update. Test extra features such as email or file uploads separately later.
Update കഴിഞ്ഞും പഴയ data നിലനിൽക്കണം. Email/file-upload പോലുള്ള അധിക features പിന്നീട് പ്രത്യേകം test ചെയ്യണം.

Open Gemini ↗Gemini തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുകNext step →അടുത്ത ഘട്ടം →

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

You are Gemini, helping implement RP Smart Office using Google Apps Script, Google Sheets and Drive, plain HTML/CSS/JavaScript, without paid AI APIs or external hosting. Explain in simple Malayalam; use exact English filenames and identifiers. Continue this route in the same Gemini chat. Keep private owner-only Admin and public submit-only registration in separate Apps Script projects. Never expose CRM/search/exports/admin handlers publicly. Validate authorization and all inputs server-side; mobile matches are not identity. Prevent spreadsheet formula injection (including =, +, -, @ prefixes) in writes and exports, and render untrusted content as text, never unsafe HTML. Preserve IDs and relationships. Use unique IDs, request-ID idempotency and partial-save recovery; a script lock does not coordinate independent projects: define and test a single-writer strategy before allowing concurrent writes. Keep backups and least-privilege access. Do not publish or change sharing/deployments without explicit owner approval.

Before any code, explain WHAT this stage does, WHY it is needed now, the visible outcome, and the exact execution order in simple Malayalam. For each named file explain its role, where it runs (browser or server), dependencies, paste destination and verification. Do not dump Code.gs, Database.gs, Index.html and JavaScript.html together without context. Then perform requested creation/configuration/implementation directly with authorized connected tools where supported; do not merely return a list of steps. Verify and report actual links/IDs/results. A pending connection is not established access. If tools/access are missing, state the limitation and ask for the minimum connection, actual file/link or access. Where appropriate offer a clearly labeled executable file or manual fallback; never pretend that a file was created, connected, deployed or tested. Before replacing files, back up; give one complete named file per response, exact paste location, expected result and a test. Stop after this step for verification.

ROUTE: CREATE NEW. Work only in the new private RP Smart Office Demo training folder, its Backups subfolder and native RP Smart Office Demo DB Google Sheet. Use dummy data only. Keep all pre-existing workbooks/projects untouched. Use the exact schema frozen in step 4; never silently rename, reset or clear data.

Create a maintenance and adaptation checklist: backups, deployment versions, safe schema changes, rollback, quota monitoring and branding changes. Explain how another business can replace fields and workflows without breaking IDs or relationships. Separate tested features from optional future automation. Require explicit approval and a tested backup/rollback before schema changes; check current official quotas without promising unlimited use. Update an approved existing deployment by version while preserving its URL. Keep optional email/uploads separate and test them independently.

21Automate a Sheets workflow with GeminiGemini ഉപയോഗിച്ച് Sheets workflow automate ചെയ്യുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

A repeatable read → validate → classify → report workflow.
വീണ്ടും നടത്താവുന്ന read → validate → classify → report workflow.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Use only the new dummy workbook or an authorized test copy of the inspected existing source. Ask Gemini to implement a dry run before any writes.
പുതിയ dummy workbook അല്ലെങ്കിൽ authorized test copy മാത്രം. Write-ന് മുമ്പ് dry run Gemini-യിൽ നടപ്പാക്കുക.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Two runs give the same counts and do not change IDs, rows or formulas. Invalid and possible duplicate rows are listed for review, never automatically merged.
രണ്ട് runs-ലും counts ഒരുപോലെ; IDs/rows/formulas മാറരുത്. Invalid/possible duplicate rows review-ന് നൽകണം; auto merge വേണ്ട.

Class exercise · prerequisites, practice and safe limitsClass exercise · തയ്യാറെടുപ്പ്, പരിശീലനം, പരിധികൾ

Prerequisites: verified schema/adapter, backup and test-copy access. With permission, prepare five test records: one valid, one blank required name, two with the same mobile, and one formula-like name. Keep these out of live data; preserve the exact new-route schema.
Verified schema/adapter, backup, test-copy access വേണം. അനുമതിയോടെ അഞ്ച് test records: valid, blank name, same mobile ഉള്ള രണ്ട്, formula-like name. Live data-ൽ ചേർക്കരുത്; new-route schema അതേപടി.
Exercise: tell Gemini the input fields, validation rules and expected output before asking for code. Run the audit manually from Apps Script; compare flagged rows with your prepared cases. Approve corrections individually through the private Admin form.
Code-ന് മുമ്പ് input fields, validation rules, expected output Gemini-ക്ക് നൽകുക. Apps Script-ൽ audit manually Run ചെയ്ത് flags test cases-മായി താരതമ്യം ചെയ്യുക. Corrections ഓരോന്നായി private Admin form വഴി അംഗീകരിക്കുക.
Expected: an issue list, valid/invalid/possible-duplicate totals and zero source changes. Sheets data validation helps editing but server validation must protect every write. Record ambiguous matches; never silently merge two people.
Issue list, valid/invalid/possible-duplicate totals; source changes ഇല്ല. Sheets validation editing സഹായിക്കും; എല്ലാ writes-നും server validation വേണം. Ambiguous matches രേഖപ്പെടുത്തുക; ആളുകളെ silent merge ചെയ്യരുത്.
Check foreign keys too: a registration with an unknown ProgrammeID or EntrepreneurID must be flagged; an enquiry must link to an existing entrepreneur. Report orphan IDs without deleting rows or renumbering records.
Foreign keys പരിശോധിക്കുക: അറിയാത്ത ProgrammeID/EntrepreneurID ഉള്ള registration flag ചെയ്യണം; enquiry നിലവിലുള്ള entrepreneur-നോട് ബന്ധിപ്പിക്കണം. Rows delete/IDs renumber ചെയ്യാതെ orphan IDs report ചെയ്യുക.

Google Spreadsheet service ↗ · Checked 4 Nov 2026

Open Gemini ↗Gemini തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുകNext step →അടുത്ത ഘട്ടം →

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

You are Gemini, helping implement RP Smart Office using Google Apps Script, Google Sheets and Drive, plain HTML/CSS/JavaScript, without paid AI APIs or external hosting. Explain in simple Malayalam; use exact English filenames and identifiers. Continue this route in the same Gemini chat. Keep private owner-only Admin and public submit-only registration in separate Apps Script projects. Never expose CRM/search/exports/admin handlers publicly. Validate authorization and all inputs server-side; mobile matches are not identity. Prevent spreadsheet formula injection (including =, +, -, @ prefixes) in writes and exports, and render untrusted content as text, never unsafe HTML. Preserve IDs and relationships. Use unique IDs, request-ID idempotency and partial-save recovery; a script lock does not coordinate independent projects: define and test a single-writer strategy before allowing concurrent writes. Keep backups and least-privilege access. Do not publish or change sharing/deployments without explicit owner approval.

Before any code, explain WHAT this stage does, WHY it is needed now, the visible outcome, and the exact execution order in simple Malayalam. For each named file explain its role, where it runs (browser or server), dependencies, paste destination and verification. Do not dump Code.gs, Database.gs, Index.html and JavaScript.html together without context. Then perform requested creation/configuration/implementation directly with authorized connected tools where supported; do not merely return a list of steps. Verify and report actual links/IDs/results. A pending connection is not established access. If tools/access are missing, state the limitation and ask for the minimum connection, actual file/link or access. Where appropriate offer a clearly labeled executable file or manual fallback; never pretend that a file was created, connected, deployed or tested. Before replacing files, back up; give one complete named file per response, exact paste location, expected result and a test. Stop after this step for verification.

ROUTE: CREATE NEW. Work only in the new private RP Smart Office Demo training folder, its Backups subfolder and native RP Smart Office Demo DB Google Sheet. Use dummy data only. Keep all pre-existing workbooks/projects untouched. Use the exact schema frozen in step 4; never silently rename, reset or clear data.

Implement a beginner read-only Sheets audit workflow in the approved training source/test copy. Explain input, transformation, output and manual execution. Read data in batches using actual header mapping; normalize mobile values in memory without losing leading zeros. Flag blank required values, malformed values and possible mobile duplicates separately from proven per-programme duplicate registrations. Never treat matching mobile as identity. Produce a private review report and counts, no merges/deletes/source writes. Run twice and compare source row counts, IDs and formulas. Include tests for blank rows, malformed input, formula/XSS text, duplicate mobile with different people, duplicate same programme and a valid second-programme registration. Provide one complete named file and dry-run instructions. Do not add headers to the frozen source schema.
Audit foreign-key integrity: flag orphan Registrations.EntrepreneurID, Registrations.ProgrammeID and Enquiries.EntrepreneurID (or their approved mapped equivalents), duplicate primary IDs and missing immutable keys. Never delete or renumber to hide an error.

22Reports, notifications and remindersReports, notifications, reminders

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

A private report and a controlled reminder dry run.
Private report, നിയന്ത്രിത reminder dry run.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Start with preview-only reporting. Test notifications only to your own approved address, then add a time-driven trigger after explicit approval.
ആദ്യം preview-only report. അംഗീകരിച്ച സ്വന്തം address-ൽ മാത്രം notification test; വ്യക്തമായ approval കഴിഞ്ഞ് time trigger.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Compare totals with source rows; retry the same reminder without sending twice. Inspect execution logs and remove the training trigger at the end.
Totals source-മായി താരതമ്യം ചെയ്യുക; retry-ൽ duplicate send വേണ്ട. Logs പരിശോധിച്ച് training trigger അവസാനം നീക്കുക.

Class exercise · prerequisites, practice and safe limitsClass exercise · തയ്യാറെടുപ്പ്, പരിശീലനം, പരിധികൾ

Prerequisites: verified report functions, an owner-approved self-address and timezone. Use existing EnquiryDate/Status for a daily summary. If reminders need DueDate and it is absent, agree a separate lab dataset instead of altering the source.
Verified reports, അംഗീകരിച്ച സ്വന്തം email, timezone വേണം. Daily summary-ക്ക് EnquiryDate/Status ഉപയോഗിക്കുക. DueDate ഇല്ലെങ്കിൽ source മാറ്റാതെ വേറെ lab dataset അംഗീകരിക്കുക.
Exercise: preview today’s status counts and reminder recipients without sending. Compare with three known test rows. After approval, send one test to yourself. In Apps Script → Triggers → Add Trigger, choose the reviewed function and time-driven schedule; review the account shown as trigger owner.
Send ചെയ്യാതെ status counts, recipients preview ചെയ്യുക. മൂന്ന് test rows-മായി താരതമ്യം ചെയ്യുക. Approval കഴിഞ്ഞ് സ്വയം ഒരു test അയയ്ക്കുക. Apps Script → Triggers → Add Trigger-ൽ reviewed function, time schedule തിരഞ്ഞെടുക്കുക; owner account പരിശോധിക്കുക.
Expected/check: preview totals match; one approved email arrives; ledger records the outcome. Time triggers are not exact-time delivery and run as their creator. A send may succeed before logging fails: inspect uncertain outcomes before retrying. Check quotas and remove the trigger after class.
Preview totals ശരിയാകണം; ഒരു approved email വരണം; ledger outcome രേഖപ്പെടുത്തണം. Trigger exact-time guarantee അല്ല; creator account-ലാണ് run. Send കഴിഞ്ഞ് log fail ആകാം; retry-ന് മുമ്പ് പരിശോധിക്കുക. Quota പരിശോധിച്ച് class കഴിഞ്ഞ് trigger നീക്കുക.

Google installable triggers ↗ · Checked 4 Nov 2026

Google service quotas ↗ · Checked 4 Nov 2026

Open Gemini ↗Gemini തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുകNext step →അടുത്ത ഘട്ടം →

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

You are Gemini, helping implement RP Smart Office using Google Apps Script, Google Sheets and Drive, plain HTML/CSS/JavaScript, without paid AI APIs or external hosting. Explain in simple Malayalam; use exact English filenames and identifiers. Continue this route in the same Gemini chat. Keep private owner-only Admin and public submit-only registration in separate Apps Script projects. Never expose CRM/search/exports/admin handlers publicly. Validate authorization and all inputs server-side; mobile matches are not identity. Prevent spreadsheet formula injection (including =, +, -, @ prefixes) in writes and exports, and render untrusted content as text, never unsafe HTML. Preserve IDs and relationships. Use unique IDs, request-ID idempotency and partial-save recovery; a script lock does not coordinate independent projects: define and test a single-writer strategy before allowing concurrent writes. Keep backups and least-privilege access. Do not publish or change sharing/deployments without explicit owner approval.

Before any code, explain WHAT this stage does, WHY it is needed now, the visible outcome, and the exact execution order in simple Malayalam. For each named file explain its role, where it runs (browser or server), dependencies, paste destination and verification. Do not dump Code.gs, Database.gs, Index.html and JavaScript.html together without context. Then perform requested creation/configuration/implementation directly with authorized connected tools where supported; do not merely return a list of steps. Verify and report actual links/IDs/results. A pending connection is not established access. If tools/access are missing, state the limitation and ask for the minimum connection, actual file/link or access. Where appropriate offer a clearly labeled executable file or manual fallback; never pretend that a file was created, connected, deployed or tested. Before replacing files, back up; give one complete named file per response, exact paste location, expected result and a test. Stop after this step for verification.

ROUTE: CREATE NEW. Work only in the new private RP Smart Office Demo training folder, its Backups subfolder and native RP Smart Office Demo DB Google Sheet. Use dummy data only. Keep all pre-existing workbooks/projects untouched. Use the exact schema frozen in step 4; never silently rename, reset or clear data.

Create a training daily report and reminder workflow using approved existing fields only. First produce a dry-run report grouped by enquiry status and date, with record counts and a recipient preview. If a due-date field does not exist, ask for a separately authorized lab mapping; do not alter the frozen source schema or invent a due date. Use a separate private sidecar delivery ledger, approved before creation, keyed by record ID, reminder type and reporting period; do not add source columns. Use explicit timezone, batch reads, maximum recipient count, MailApp.getRemainingDailyQuota(), deduplication, failure logging and an off switch. Explain that email delivery and ledger writes cannot be atomically committed: an ambiguous send outcome requires review before retry, not an exactly-once guarantee. Do not create triggers or send mail until I approve the recipient and schedule. Explain installable trigger ownership, permissions, time-window variability, current quotas and how to delete it. Provide one complete file plus preview/test/disable functions. Test with one owner-approved self-address only, then prove no duplicate on rerun.

23Automate Drive and documentsDrive, documents automate ചെയ്യുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

One verified private document/PDF from a selected test row.
തിരഞ്ഞെടുത്ത test row-ൽ നിന്ന് പരിശോധിച്ച private document/PDF.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Use a private template and output folder. Preview replacements, create one document, and verify sharing and retry behavior.
Private template, output folder ഉപയോഗിക്കുക. Replacements preview ചെയ്ത് ഒരു document ഉണ്ടാക്കി sharing/retry പരിശോധിക്കുക.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

No placeholders remain; the right record ID maps to one output and retry reuses or flags it. Source/template and sharing remain intact.
Placeholders ബാക്കി ഇല്ല; ശരിയായ record ID-യ്ക്ക് ഒരു output; retry reuse/flag. Source/template/sharing മാറരുത്.

Class exercise · prerequisites, practice and safe limitsClass exercise · തയ്യാറെടുപ്പ്, പരിശീലനം, പരിധികൾ

Prerequisites: private Docs template, approved output folder and one dummy record or authorized test-copy record. In the template type the four placeholders shown in the prompt; record its real file ID and the output folder ID.
Private Docs template, approved output folder, ഒരു dummy/test-copy record വേണം. Prompt-ലെ നാല് placeholders template-ൽ നൽകുക; real template ID, output folder ID കുറിക്കുക.
Exercise: preview replacements; create one personalized programme confirmation document from a copy of the template. Optionally export that new document as PDF. Open the real output links and inspect the record ID, spelling and Share panel.
Replacements preview ചെയ്യുക; template copy-ൽ നിന്ന് ഒരു programme confirmation document ഉണ്ടാക്കുക. ആ പുതിയ document PDF ആക്കാം. Real output തുറന്ന് record ID, spelling, Share panel പരിശോധിക്കുക.
Expected/limits: one private document/PDF with no unresolved placeholders. Rerun must not create uncontrolled duplicates. Do not run reset/clear functions from samples against business data; authorization scopes and inherited folder access need review.
Placeholders ഇല്ലാത്ത ഒരു private document/PDF വേണം. Rerun അനിയന്ത്രിത duplicates ഉണ്ടാക്കരുത്. Sample reset/clear business data-ൽ നടത്തരുത്; scopes/inherited folder access പരിശോധിക്കുക.

Google Document service ↗ · Checked 4 Nov 2026

Google PDF automation sample — training reference ↗ · Checked 4 Nov 2026

Open Gemini ↗Gemini തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുകNext step →അടുത്ത ഘട്ടം →

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

You are Gemini, helping implement RP Smart Office using Google Apps Script, Google Sheets and Drive, plain HTML/CSS/JavaScript, without paid AI APIs or external hosting. Explain in simple Malayalam; use exact English filenames and identifiers. Continue this route in the same Gemini chat. Keep private owner-only Admin and public submit-only registration in separate Apps Script projects. Never expose CRM/search/exports/admin handlers publicly. Validate authorization and all inputs server-side; mobile matches are not identity. Prevent spreadsheet formula injection (including =, +, -, @ prefixes) in writes and exports, and render untrusted content as text, never unsafe HTML. Preserve IDs and relationships. Use unique IDs, request-ID idempotency and partial-save recovery; a script lock does not coordinate independent projects: define and test a single-writer strategy before allowing concurrent writes. Keep backups and least-privilege access. Do not publish or change sharing/deployments without explicit owner approval.

Before any code, explain WHAT this stage does, WHY it is needed now, the visible outcome, and the exact execution order in simple Malayalam. For each named file explain its role, where it runs (browser or server), dependencies, paste destination and verification. Do not dump Code.gs, Database.gs, Index.html and JavaScript.html together without context. Then perform requested creation/configuration/implementation directly with authorized connected tools where supported; do not merely return a list of steps. Verify and report actual links/IDs/results. A pending connection is not established access. If tools/access are missing, state the limitation and ask for the minimum connection, actual file/link or access. Where appropriate offer a clearly labeled executable file or manual fallback; never pretend that a file was created, connected, deployed or tested. Before replacing files, back up; give one complete named file per response, exact paste location, expected result and a test. Stop after this step for verification.

ROUTE: CREATE NEW. Work only in the new private RP Smart Office Demo training folder, its Backups subfolder and native RP Smart Office Demo DB Google Sheet. Use dummy data only. Keep all pre-existing workbooks/projects untouched. Use the exact schema frozen in step 4; never silently rename, reset or clear data.

Implement a private training document generator from one selected approved test record. Use a separate private Docs template with {{Name}}, {{BusinessName}}, {{ProgrammeName}} and {{RecordID}} placeholders and a verified output folder ID. First show a dry-run replacement map. Copy the template, replace placeholders with safe literal text, create an optional PDF in that folder, and keep source/template unchanged. Use a separate approved output ledger keyed by stable record ID/template version to avoid duplicate outputs; do not add source schema columns. Check inherited folder permissions and actual output access. Stop if template, folder, mapping or permissions are absent. No emailing or public links. Return verified actual document/PDF IDs and links only after tool execution; otherwise provide labeled executable Apps Script/manual fallback. Include rerun, missing field, literal special character and permission tests; offer cleanup of created test copies only with approval.

24Session 4 · Create and use a private ChatGPT pluginസെഷൻ 4 · Private ChatGPT plugin ഉണ്ടാക്കി ഉപയോഗിക്കുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

A private, tested reusable enquiry-summary workflow.
Private ആയി പരിശോധിച്ച enquiry-summary workflow.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Check Plugin Creator availability in your ChatGPT workspace, create a private instruction-only plugin and test three dummy enquiries. This is the separate Session 4 ChatGPT lesson.
ChatGPT workspace-ൽ Plugin Creator ലഭ്യമാണോ പരിശോധിച്ച് private instruction-only plugin ഉണ്ടാക്കി മൂന്ന് dummy enquiries test ചെയ്യുക. ഇത് വേറെ Session 4 ChatGPT lesson ആണ്.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Test complete, missing and conflicting input; inspect visibility and permissions. If creator access is absent, label the result a draft, not an installed plugin.
Complete/missing/conflicting input test ചെയ്ത് visibility/permissions പരിശോധിക്കുക. Creator access ഇല്ലെങ്കിൽ draft എന്ന് രേഖപ്പെടുത്തുക; installed plugin എന്ന് പറയരുത്.

Class exercise · prerequisites, practice and safe limitsClass exercise · തയ്യാറെടുപ്പ്, പരിശീലനം, പരിധികൾ

Prerequisites: a ChatGPT account with permitted plugin creation; availability depends on workspace, role and plan. Open Plugins and check whether Plugin Creator can be installed/used. Installation still requires any separate service authorization. No connector is needed for this instruction-only exercise.
Plugin creation അനുവദിക്കുന്ന ChatGPT account വേണം; workspace/role/plan അനുസരിച്ച് availability മാറും. Plugins-ൽ Plugin Creator ലഭ്യമാണോ പരിശോധിക്കുക. Install ചെയ്താലും service authorization വേറെ; ഈ instruction-only exercise-ന് connector വേണ്ട.
Exercise: start a chat with @plugin-creator and use the single prompt below. Name the plugin RP Enquiry Coach; include instructions, a dummy example and a strict Missing rule. Create/save privately using the controls actually available, then invoke the installed plugin in a new chat with dummy enquiry text.
@plugin-creator chat-ൽ താഴെയുള്ള ഒറ്റ prompt നൽകുക. RP Enquiry Coach എന്ന പേര്, instructions, dummy example, Missing rule ചേർക്കുക. ലഭ്യമായ controls ഉപയോഗിച്ച് private create/save ചെയ്ത് പുതിയ chat-ൽ dummy enquiry test ചെയ്യുക.
Expected/limits: three repeatable formatted summaries with no data writes; verify private visibility separately. A plugin bundles reusable skills and may include connected apps; a skill alone is not database access. If creation is unavailable, produce the draft and mark installation NOT TESTED rather than promising access.
Data write ഇല്ലാത്ത മൂന്ന് formatted summaries വേണം; private visibility വേറെ പരിശോധിക്കുക. Plugin reusable skills/apps ഉൾപ്പെടുത്താം; skill മാത്രം database access അല്ല. Creation ലഭ്യമല്ലെങ്കിൽ draft നൽകി installation NOT TESTED രേഖപ്പെടുത്തുക.

OpenAI: Plugins in ChatGPT ↗ · Checked 4 Nov 2026

Open ChatGPT — private plugin lesson ↗Private plugin lesson-നായി ChatGPT തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുകNext step →അടുത്ത ഘട്ടം →

Copy Prompt — take this to ChatGPTഈ prompt ChatGPT-ൽ നൽകുക

Use Plugin Creator in ChatGPT to help me create a PRIVATE instruction-only RP Enquiry Coach plugin for this separate Session 4 lesson. First check my account/workspace availability and permissions; if the creator is unavailable, give me a clearly labeled portable draft of SKILL.md/instructions and an access checklist, never claim installation. Explain plugin versus skill versus connected app. Use dummy enquiry text only. Define purpose, when to use, inputs, Malayalam explanation with English field labels, output schema (Name, Mobile, BusinessName, Category, Description, FollowUpNote), missing/conflicting detail handling, no invented facts and no automatic CRM writes, sending or external connections. Include three test inputs and expected outputs, including missing details and contradictory mobile numbers. Keep visibility private; inspect the actual sharing setting before use and do not publish. Use the current official Plugins help and tell me which account-dependent controls I actually see, rather than legacy GPT/plugin-marketplace instructions. If tools support authorized private creation, act directly and verify; otherwise clearly label draft/manual steps. Ask for minimal missing access and keep credentials and personal records out. End with exact install/use/test steps, private-access verification and actual PASS/FAIL/NOT TESTED results; do not claim a draft is installed.

25Session 4 · Gemini Skills custom assistantസെഷൻ 4 · Gemini Skills custom assistant

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

A reusable, tested enquiry-triage skill.
വീണ്ടും ഉപയോഗിക്കാവുന്ന പരിശോധിച്ച enquiry-triage skill.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Check account eligibility, create a private training skill and run the same three dummy inputs used in the plugin lesson.
Account eligibility പരിശോധിച്ച് private training skill ഉണ്ടാക്കി plugin lesson-ലെ മൂന്ന് dummy inputs test ചെയ്യുക.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Check missing/conflicting fields and identical output labels. A saved skill is reusable guidance, not a scheduled task or automatic database connection.
Missing/conflicting fields, output labels പരിശോധിക്കുക. Saved skill reusable guidance ആണ്; scheduled task/automatic database connection അല്ല.

Class exercise · prerequisites, practice and safe limitsClass exercise · തയ്യാറെടുപ്പ്, പരിശീലനം, പരിധികൾ

Prerequisites: check the official Skills page for supported account/app availability. Google currently lists signed-in access, age 18+ and Keep Activity on; review this setting before choosing the exercise. If it is unavailable or you decline that setting, use the clearly labeled reusable instruction-file fallback.
Official Skills page-ൽ account/app support പരിശോധിക്കുക. നിലവിൽ sign-in, 18+, Keep Activity on ആവശ്യമാണ്; setting പരിശോധിച്ച് തീരുമാനിക്കുക. ലഭ്യമല്ലെങ്കിൽ അല്ലെങ്കിൽ setting വേണ്ടെങ്കിൽ reusable instruction-file fallback എന്ന് വ്യക്തമായി നൽകുക.
Exercise: in Gemini web open Customize → Skills → Create if present. Define RP Enquiry Triage with the same field labels and dummy cases as RP Enquiry Coach. Save and invoke it in a fresh chat; revise the instructions when it guesses missing data.
Gemini web-ൽ ലഭ്യമെങ്കിൽ Customize → Skills → Create. RP Enquiry Coach-ലെ അതേ fields/dummy cases ഉപയോഗിച്ച് RP Enquiry Triage നിർവചിക്കുക. Save ചെയ്ത് പുതിയ chat-ൽ ഉപയോഗിക്കുക; missing data ഊഹിച്ചാൽ instructions തിരുത്തുക.
Expected/limits: complete, missing and conflicting inputs produce reviewed summaries. Account menus can differ; record the real UI and save evidence. A skill does not prove a Sheet connection, trigger execution or an installed ChatGPT plugin.
Complete/missing/conflicting inputs reviewed summaries നൽകണം. Account menu മാറാം; actual UI/save evidence രേഖപ്പെടുത്തുക. Skill ഉള്ളത് Sheet connection/trigger/ChatGPT plugin proof അല്ല.

Google: Create and manage skills ↗ · Checked 4 Nov 2026

Open Gemini ↗Gemini തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുകNext step →അടുത്ത ഘട്ടം →

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

You are Gemini, helping implement RP Smart Office using Google Apps Script, Google Sheets and Drive, plain HTML/CSS/JavaScript, without paid AI APIs or external hosting. Explain in simple Malayalam; use exact English filenames and identifiers. Continue this route in the same Gemini chat. Keep private owner-only Admin and public submit-only registration in separate Apps Script projects. Never expose CRM/search/exports/admin handlers publicly. Validate authorization and all inputs server-side; mobile matches are not identity. Prevent spreadsheet formula injection (including =, +, -, @ prefixes) in writes and exports, and render untrusted content as text, never unsafe HTML. Preserve IDs and relationships. Use unique IDs, request-ID idempotency and partial-save recovery; a script lock does not coordinate independent projects: define and test a single-writer strategy before allowing concurrent writes. Keep backups and least-privilege access. Do not publish or change sharing/deployments without explicit owner approval.

Before any code, explain WHAT this stage does, WHY it is needed now, the visible outcome, and the exact execution order in simple Malayalam. For each named file explain its role, where it runs (browser or server), dependencies, paste destination and verification. Do not dump Code.gs, Database.gs, Index.html and JavaScript.html together without context. Then perform requested creation/configuration/implementation directly with authorized connected tools where supported; do not merely return a list of steps. Verify and report actual links/IDs/results. A pending connection is not established access. If tools/access are missing, state the limitation and ask for the minimum connection, actual file/link or access. Where appropriate offer a clearly labeled executable file or manual fallback; never pretend that a file was created, connected, deployed or tested. Before replacing files, back up; give one complete named file per response, exact paste location, expected result and a test. Stop after this step for verification.

ROUTE: CREATE NEW. Work only in the new private RP Smart Office Demo training folder, its Backups subfolder and native RP Smart Office Demo DB Google Sheet. Use dummy data only. Keep all pre-existing workbooks/projects untouched. Use the exact schema frozen in step 4; never silently rename, reset or clear data.

Help me create a Gemini Apps custom skill called RP Enquiry Triage for Session 4. Check current official Skills availability and my actual UI first. Explain that skills save reusable instructions and can be explicitly selected or automatically relevant, but do not themselves grant connector access or schedule background work. Produce complete instructions/SKILL.md with purpose, use conditions, dummy examples, inputs, English CRM field labels, Malayalam explanation, Missing/conflict handling, review-before-save and no sending/database writes. Guide me through the currently available Customize → Skills → Create flow, preview/use/save checks and three dummy tests. Check eligibility and Keep Activity requirement; if unavailable or unsuitable for my account, label a reusable prompt-file fallback as a draft and ask for needed access, never claim a skill was saved. If my account still shows Gems, use the official account-specific guidance rather than assuming migration or equivalence. Keep reference material non-sensitive and private; no connected service authorization is implied. Report actual save/test evidence only.

26Session 4 · Research Kerala MSME informationസെഷൻ 4 · Kerala MSME വിവരങ്ങൾ പരിശോധിക്കുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

A source-backed scheme enquiry note with unresolved questions.
Sources, unresolved questions ഉള്ള scheme enquiry note.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Use a fictional manufacturing business and official Kerala Industries guidance. Prepare a DIC question list; do not submit an application.
സാങ്കൽപ്പിക manufacturing business, official Kerala Industries guidance ഉപയോഗിച്ച് DIC ചോദ്യങ്ങൾ തയ്യാറാക്കുക; application submit ചെയ്യരുത്.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Every scheme claim has a source/date; unsupported eligibility or subsidy is marked Unverified and confirmed with DIC.
ഓരോ scheme claim-നും source/date വേണം; unsupported eligibility/subsidy Unverified ആയി DIC-യിൽ സ്ഥിരീകരിക്കുക.

Class exercise · prerequisites, practice and safe limitsClass exercise · തയ്യാറെടുപ്പ്, പരിശീലനം, പരിധികൾ

Prerequisites: internet access or current official PDFs; fictional district, sector, investment stage and Udyam status. ESS is described by Kerala Industries as assistance for manufacturing MSMEs; that alone does not establish eligibility for a particular business.
Internet അല്ലെങ്കിൽ current official PDFs, fictional district/sector/investment stage/Udyam status വേണം. Kerala Industries ESS manufacturing MSMEs-നുള്ള സഹായമായി വിവരിക്കുന്നു; അതുകൊണ്ട് മാത്രം പ്രത്യേക business eligible ആകില്ല.
Exercise: open the official ESS page and its guidelines. Record title, source URL, version/date and a short evidence note for each condition. Ask Gemini to compare the fictional business against those conditions and draft five DIC questions, leaving one missing fact unresolved.
Official ESS page, guidelines തുറക്കുക. ഓരോ condition-നും title, URL, version/date, evidence note രേഖപ്പെടുത്തുക. Fictional business conditions-മായി താരതമ്യം ചെയ്ത് അഞ്ച് DIC questions Gemini-യിൽ തയ്യാറാക്കുക; ഒരു missing fact unresolved ആക്കുക.
Expected/limits: a traceable enquiry checklist, not a subsidy promise. Check the latest guideline and local DIC before acting; no scheme amount/deadline is asserted here. Do not upload identity documents or submit applications during the lesson.
Traceable enquiry checklist വേണം; subsidy promise അല്ല. Action-ന് മുമ്പ് latest guideline, local DIC പരിശോധിക്കുക. ഇവിടെ scheme amount/deadline ഉറപ്പിക്കുന്നില്ല. Identity documents upload/application submit ചെയ്യരുത്.

Kerala Industries: Entrepreneur Support Scheme ↗ · Checked 4 Nov 2026

Open Gemini ↗Gemini തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുകNext step →അടുത്ത ഘട്ടം →

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

You are Gemini, helping implement RP Smart Office using Google Apps Script, Google Sheets and Drive, plain HTML/CSS/JavaScript, without paid AI APIs or external hosting. Explain in simple Malayalam; use exact English filenames and identifiers. Continue this route in the same Gemini chat. Keep private owner-only Admin and public submit-only registration in separate Apps Script projects. Never expose CRM/search/exports/admin handlers publicly. Validate authorization and all inputs server-side; mobile matches are not identity. Prevent spreadsheet formula injection (including =, +, -, @ prefixes) in writes and exports, and render untrusted content as text, never unsafe HTML. Preserve IDs and relationships. Use unique IDs, request-ID idempotency and partial-save recovery; a script lock does not coordinate independent projects: define and test a single-writer strategy before allowing concurrent writes. Keep backups and least-privilege access. Do not publish or change sharing/deployments without explicit owner approval.

Before any code, explain WHAT this stage does, WHY it is needed now, the visible outcome, and the exact execution order in simple Malayalam. For each named file explain its role, where it runs (browser or server), dependencies, paste destination and verification. Do not dump Code.gs, Database.gs, Index.html and JavaScript.html together without context. Then perform requested creation/configuration/implementation directly with authorized connected tools where supported; do not merely return a list of steps. Verify and report actual links/IDs/results. A pending connection is not established access. If tools/access are missing, state the limitation and ask for the minimum connection, actual file/link or access. Where appropriate offer a clearly labeled executable file or manual fallback; never pretend that a file was created, connected, deployed or tested. Before replacing files, back up; give one complete named file per response, exact paste location, expected result and a test. Stop after this step for verification.

ROUTE: CREATE NEW. Work only in the new private RP Smart Office Demo training folder, its Backups subfolder and native RP Smart Office Demo DB Google Sheet. Use dummy data only. Keep all pre-existing workbooks/projects untouched. Use the exact schema frozen in step 4; never silently rename, reset or clear data.

Research Kerala MSME assistance for a fictional manufacturing enterprise using only current official Kerala Directorate of Industries and Commerce scheme pages and linked government guidelines/orders. Start with the Entrepreneur Support Scheme page at https://industry.kerala.gov.in/index.php/schemes-mainmenu/entrepreneur-support-scheme-schemes and inspect its linked guidelines and current application requirements. Ask for district, sector, investment stage and Udyam status without requesting personal identifiers. Build a cited eligibility-evidence matrix, document checklist, application route, exclusions/conditions and questions for the District Industries Centre. Distinguish confirmed source text, interpretation, missing facts and conflicting/stale guidance. Cite exact official URLs, publication/version where shown and date checked. Do not invent subsidy percentages, deadlines, guaranteed eligibility or approval; if web/source access is unavailable, request the actual official guideline/PDF and label conclusions provisional. Provide a simple Malayalam enquiry note for owner review, not legal/financial advice or a submitted application. Use no personal records, logins or application uploads. Test against one deliberately missing eligibility fact and show that it remains Unverified.

27Session 4 · NotebookLM document researchസെഷൻ 4 · NotebookLM document research

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

A cited comparison from two approved source documents.
അംഗീകരിച്ച രണ്ട് documents-ൽ നിന്ന് citations ഉള്ള comparison.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Create a private research notebook using two public official documents. Ask source-bounded questions and open the citations to verify the answers.
രണ്ട് public official documents ഉപയോഗിച്ച് private research notebook ഉണ്ടാക്കുക. Source-based ചോദ്യങ്ങൾ ചോദിച്ച് citations തുറന്ന് പരിശോധിക്കുക.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Verify three claims against passages and test a question absent from the sources. Record unavailable features and source freshness.
മൂന്ന് claims source passages-മായി പരിശോധിച്ച് sources-ൽ ഇല്ലാത്ത ചോദ്യം test ചെയ്യുക. Unavailable features/source freshness രേഖപ്പെടുത്തുക.

Class exercise · prerequisites, practice and safe limitsClass exercise · തയ്യാറെടുപ്പ്, പരിശീലനം, പരിധികൾ

Prerequisites: an eligible signed-in account, service enabled by the workspace if needed, and two public official source PDFs/links. Official NotebookLM help currently redirects to Gemini Notebook help; use the actual product label and controls shown in your account.
Eligible account, ആവശ്യമെങ്കിൽ workspace service enable, രണ്ട് public official PDFs/links വേണം. Official NotebookLM help നിലവിൽ Gemini Notebook help-ലേക്ക് redirect ചെയ്യുന്നു; account-ലെ യഥാർത്ഥ label/controls ഉപയോഗിക്കുക.
Exercise: create a private notebook, add both sources, record title/version/date, and ask “Which documents are needed, and where do these sources disagree?” Ask for Malayalam notes with citations. Open three cited passages. Then ask a question not answered by either source and inspect how uncertainty is handled.
Private notebook ഉണ്ടാക്കി രണ്ട് sources ചേർക്കുക; title/version/date രേഖപ്പെടുത്തുക. Required documents, sources-ലെ വ്യത്യാസങ്ങൾ ചോദിച്ച് Malayalam notes citations സഹിതം വാങ്ങുക. മൂന്ന് citations തുറക്കുക. Sources-ൽ answer ഇല്ലാത്ത ചോദ്യം ചോദിച്ച് uncertainty പരിശോധിക്കുക.
Expected/limits: verified passages support the comparison; absent information remains unresolved. Source-based answers can still need checking, and imported sources can be stale. Check current upload limits and sharing; keep identity and customer data out.
Comparison-ന് പരിശോധിച്ച passages തെളിവാകണം; missing information unresolved ആകണം. Source-based answers-ഉം പരിശോധിക്കണം; imported sources പഴയതാകാം. Current upload limits/sharing പരിശോധിക്കുക; customer/identity data ഒഴിവാക്കുക.

Google: NotebookLM / Gemini Notebook FAQ ↗ · Checked 4 Nov 2026

Open Gemini ↗Gemini തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുകNext step →അടുത്ത ഘട്ടം →

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

You are Gemini, helping implement RP Smart Office using Google Apps Script, Google Sheets and Drive, plain HTML/CSS/JavaScript, without paid AI APIs or external hosting. Explain in simple Malayalam; use exact English filenames and identifiers. Continue this route in the same Gemini chat. Keep private owner-only Admin and public submit-only registration in separate Apps Script projects. Never expose CRM/search/exports/admin handlers publicly. Validate authorization and all inputs server-side; mobile matches are not identity. Prevent spreadsheet formula injection (including =, +, -, @ prefixes) in writes and exports, and render untrusted content as text, never unsafe HTML. Preserve IDs and relationships. Use unique IDs, request-ID idempotency and partial-save recovery; a script lock does not coordinate independent projects: define and test a single-writer strategy before allowing concurrent writes. Keep backups and least-privilege access. Do not publish or change sharing/deployments without explicit owner approval.

Before any code, explain WHAT this stage does, WHY it is needed now, the visible outcome, and the exact execution order in simple Malayalam. For each named file explain its role, where it runs (browser or server), dependencies, paste destination and verification. Do not dump Code.gs, Database.gs, Index.html and JavaScript.html together without context. Then perform requested creation/configuration/implementation directly with authorized connected tools where supported; do not merely return a list of steps. Verify and report actual links/IDs/results. A pending connection is not established access. If tools/access are missing, state the limitation and ask for the minimum connection, actual file/link or access. Where appropriate offer a clearly labeled executable file or manual fallback; never pretend that a file was created, connected, deployed or tested. Before replacing files, back up; give one complete named file per response, exact paste location, expected result and a test. Stop after this step for verification.

ROUTE: CREATE NEW. Work only in the new private RP Smart Office Demo training folder, its Backups subfolder and native RP Smart Office Demo DB Google Sheet. Use dummy data only. Keep all pre-existing workbooks/projects untouched. Use the exact schema frozen in step 4; never silently rename, reset or clear data.

Prepare a beginner NotebookLM research exercise (the current official Help may label the product Gemini Notebook). Check actual account access and current official guidance first. Use two supplied public official documents, such as current Kerala ESS guidelines and an official application checklist. Ask for the actual files/links if missing. Guide creation of a private notebook, source addition, document title/version/date recording and three source-bounded questions. Request a comparison table and Malayalam briefing with source citations, plus a question whose answer is absent from both sources. Require opening each cited passage and correcting unsupported claims; no fabricated citations or eligibility conclusions. Treat source copies as potentially stale: verify current originals and re-import/update when required. Check current source limits and workspace/admin access without assuming a plan or universal feature availability. Do not upload private CRM/identity data, publish or share publicly. If tools cannot create/read the notebook, clearly label the manual workflow and do not claim it exists. Report actual citation verification results and distinguish model summary from source evidence.

28Session 4 · CustomRapid recorded demoസെഷൻ 4 · CustomRapid recorded demo

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

An evidence log of Nishin’s CustomRapid demonstration.
Nishin-ന്റെ CustomRapid demo-യുടെ evidence log.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Obtain Nishin’s own recording or approved transcript. Watch and map the demonstrated workflow; do not activate live integrations.
Nishin-ന്റെ recording/approved transcript വാങ്ങുക. കാണിച്ച workflow map ചെയ്യുക; live integrations activate ചെയ്യരുത്.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Every capability is tied to a timestamp or marked user-described/unverified. Missing recording means the viewing exercise remains NOT TESTED.
ഓരോ capability-ക്കും timestamp അല്ലെങ്കിൽ user-described/unverified label. Recording ഇല്ലെങ്കിൽ viewing NOT TESTED.

Class exercise · prerequisites, practice and safe limitsClass exercise · തയ്യാറെടുപ്പ്, പരിശീലനം, പരിധികൾ

Prerequisites: Nishin’s own approved CustomRapid recording or transcript, permission to show it, and headphones/projector. The recording has not been supplied here; ask the presenter for the actual file/link. No public video URL or live product access is assumed.
Nishin-ന്റെ approved CustomRapid recording/transcript, കാണിക്കാൻ അനുമതി, projector/headphones വേണം. Recording ഇവിടെ നൽകിയിട്ടില്ല; presenter-നോട് യഥാർത്ഥ file/link ചോദിക്കുക. Public video URL/live access assume ചെയ്യുന്നില്ല.
Exercise: pause the recording at onboarding, WhatsApp/Instagram enquiry, lead/follow-up, order, payment gateway, invoice and tax-integration discussions. Record timestamps, observed inputs/outputs and required human approval. Distinguish what was shown from what was only described; leave absent stages unverified.
Onboarding, WhatsApp/Instagram enquiry, lead/follow-up, order, payment gateway, invoice, tax discussion-ൽ pause ചെയ്യുക. Timestamp, input/output, human approval കുറിക്കുക. കാണിച്ചതും പറഞ്ഞതും വേർതിരിക്കുക; കാണാത്ത stages unverified.
Expected/limits: one evidence worksheet and five questions about access, costs, failure handling and integration availability. These capabilities are user-described demo topics, not verified product promises. No messages, live payments, invoices, tax filings or account connections are performed in class.
ഒരു evidence worksheet, access/cost/failure/integration സംബന്ധിച്ച അഞ്ച് questions വേണം. Capabilities user-described topics ആണ്; verified promises അല്ല. Class-ൽ messages/payments/invoices/tax filings/account connections നടത്തരുത്.

Open Gemini ↗Gemini തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുകNext step →അടുത്ത ഘട്ടം →

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

You are Gemini, helping implement RP Smart Office using Google Apps Script, Google Sheets and Drive, plain HTML/CSS/JavaScript, without paid AI APIs or external hosting. Explain in simple Malayalam; use exact English filenames and identifiers. Continue this route in the same Gemini chat. Keep private owner-only Admin and public submit-only registration in separate Apps Script projects. Never expose CRM/search/exports/admin handlers publicly. Validate authorization and all inputs server-side; mobile matches are not identity. Prevent spreadsheet formula injection (including =, +, -, @ prefixes) in writes and exports, and render untrusted content as text, never unsafe HTML. Preserve IDs and relationships. Use unique IDs, request-ID idempotency and partial-save recovery; a script lock does not coordinate independent projects: define and test a single-writer strategy before allowing concurrent writes. Keep backups and least-privilege access. Do not publish or change sharing/deployments without explicit owner approval.

Before any code, explain WHAT this stage does, WHY it is needed now, the visible outcome, and the exact execution order in simple Malayalam. For each named file explain its role, where it runs (browser or server), dependencies, paste destination and verification. Do not dump Code.gs, Database.gs, Index.html and JavaScript.html together without context. Then perform requested creation/configuration/implementation directly with authorized connected tools where supported; do not merely return a list of steps. Verify and report actual links/IDs/results. A pending connection is not established access. If tools/access are missing, state the limitation and ask for the minimum connection, actual file/link or access. Where appropriate offer a clearly labeled executable file or manual fallback; never pretend that a file was created, connected, deployed or tested. Before replacing files, back up; give one complete named file per response, exact paste location, expected result and a test. Stop after this step for verification.

ROUTE: CREATE NEW. Work only in the new private RP Smart Office Demo training folder, its Backups subfolder and native RP Smart Office Demo DB Google Sheet. Use dummy data only. Keep all pre-existing workbooks/projects untouched. Use the exact schema frozen in step 4; never silently rename, reset or clear data.

Help teach a recorded demo of Nishin’s own CustomRapid business automation product, referred to in this class as Rapid AI. Do not confuse it with another similarly named product. Ask for Nishin’s actual approved demo recording, local video or transcript if not supplied; no public video URL is assumed. The user-described topics are onboarding, WhatsApp/Instagram enquiries, leads/follow-ups, order processing, payment gateway, invoicing and tax integration. Treat these as discussion topics, not independently verified available features. Build a timestamped observation worksheet with columns Topic, What the recording actually shows, Input, Output, Manual approval, Connected service, Evidence and Unverified question. For each topic, mark Seen in recording, User-described only or Not shown. Ask learners to trace one enquiry → reviewed lead → follow-up → order/invoice chain only if demonstrated; do not invent missing steps. Discuss permissions, consent, duplicate events, failed payments, reconciliation, tax accuracy and rollback as questions for the presenter, not claims about implementation. No live account connection, messages, payments, orders, invoices, tax filings or third-party signup. If the recording is missing, provide the worksheet and exact request for the presenter’s file/link, mark viewing NOT TESTED and stop capability conclusions.

29Session 4 · Q&A and practical recapസെഷൻ 4 · Q&A, practical recap

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

A learner teach-back and honest evidence checklist.
Learner teach-back, actual evidence checklist.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Have each learner demonstrate one audited workflow, explain privacy boundaries and log unanswered questions before final dashboard design.
ഓരോ learner-ഉം ഒരു audited workflow കാണിച്ച് privacy boundaries വിശദീകരിച്ച് unresolved questions രേഖപ്പെടുത്തുക; തുടർന്ന് final dashboard design.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Record PASS / FAIL / NOT TESTED with evidence; disabled triggers and private test outputs are checked. Unavailable optional labs do not become completion claims.
Evidence സഹിതം PASS / FAIL / NOT TESTED; disabled triggers/private outputs പരിശോധിക്കുക. Unavailable labs complete എന്ന് പറയരുത്.

Class exercise · prerequisites, practice and safe limitsClass exercise · തയ്യാറെടുപ്പ്, പരിശീലനം, പരിധികൾ

Prerequisites: test matrix, redacted screenshots/logs, private backup/rollback note and lab evidence. Pair learners: one demonstrates, the other compares the result with the expected source rows and permission boundary.
Test matrix, redacted screenshots/logs, private backup/rollback note, lab evidence വേണം. Learners pair ആയി ഒരാൾ demonstrate ചെയ്യുക; മറ്റൊരാൾ source rows/permission boundaries-ുമായി പരിശോധിക്കുക.
Exercise: explain “What runs where?”, “Why is a mobile match not identity?”, “Why is a script lock not cross-project coordination?”, “How do we know a save occurred?” and “What happens after an uncertain email send?” Demonstrate one passing case and one rejected input, then record an unanswered question.
എവിടെ എന്ത് run ചെയ്യുന്നു, mobile match identity അല്ലാത്തത് എന്തുകൊണ്ട്, script lock cross-project അല്ലാത്തത് എന്തുകൊണ്ട്, save proof എന്ത്, uncertain email send കഴിഞ്ഞ് എന്ത് — വിശദീകരിക്കുക. ഒരു pass case, ഒരു rejected input കാണിച്ച് unanswered question രേഖപ്പെടുത്തുക.
Expected/check: a peer-reviewed evidence sheet and correction plan. Verify test triggers are disabled and outputs private; optional blocked labs remain NOT TESTED. Only after foundation/module/report/security checks are satisfied move to the final dashboard-design handoff.
Peer-reviewed evidence sheet, correction plan വേണം. Test triggers disabled, outputs private എന്ന് പരിശോധിക്കുക; blocked optional labs NOT TESTED. Foundation/module/report/security checks കഴിഞ്ഞ് മാത്രം final dashboard-design handoff.

Open Gemini ↗Gemini തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുകNext step →അടുത്ത ഘട്ടം →

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

You are Gemini, helping implement RP Smart Office using Google Apps Script, Google Sheets and Drive, plain HTML/CSS/JavaScript, without paid AI APIs or external hosting. Explain in simple Malayalam; use exact English filenames and identifiers. Continue this route in the same Gemini chat. Keep private owner-only Admin and public submit-only registration in separate Apps Script projects. Never expose CRM/search/exports/admin handlers publicly. Validate authorization and all inputs server-side; mobile matches are not identity. Prevent spreadsheet formula injection (including =, +, -, @ prefixes) in writes and exports, and render untrusted content as text, never unsafe HTML. Preserve IDs and relationships. Use unique IDs, request-ID idempotency and partial-save recovery; a script lock does not coordinate independent projects: define and test a single-writer strategy before allowing concurrent writes. Keep backups and least-privilege access. Do not publish or change sharing/deployments without explicit owner approval.

Before any code, explain WHAT this stage does, WHY it is needed now, the visible outcome, and the exact execution order in simple Malayalam. For each named file explain its role, where it runs (browser or server), dependencies, paste destination and verification. Do not dump Code.gs, Database.gs, Index.html and JavaScript.html together without context. Then perform requested creation/configuration/implementation directly with authorized connected tools where supported; do not merely return a list of steps. Verify and report actual links/IDs/results. A pending connection is not established access. If tools/access are missing, state the limitation and ask for the minimum connection, actual file/link or access. Where appropriate offer a clearly labeled executable file or manual fallback; never pretend that a file was created, connected, deployed or tested. Before replacing files, back up; give one complete named file per response, exact paste location, expected result and a test. Stop after this step for verification.

ROUTE: CREATE NEW. Work only in the new private RP Smart Office Demo training folder, its Backups subfolder and native RP Smart Office Demo DB Google Sheet. Use dummy data only. Keep all pre-existing workbooks/projects untouched. Use the exact schema frozen in step 4; never silently rename, reset or clear data.

Run a practical Sessions 2–4 recap before final dashboard design. Ask the learner to explain Apps Script/function/log/authorization, trace Gemini request → reviewed code → test, demonstrate actual-source mapping and backup, distinguish validation/duplicate candidates/idempotency, reconcile report totals, show a notification dry run and disable its training trigger, and open one private document output. Ask them to contrast a website and web app, explain separate private Admin/public registration, demonstrate a failed-save case and access denial, then compare the private ChatGPT plugin and Gemini skill without confusing instructions with connected tools. Verify a Kerala scheme citation and a NotebookLM cited passage, and inspect the CustomRapid recorded-demo evidence log without inventing missing video content. Provide a question bank with expected reasoning and a worksheet for actual PASS/FAIL/NOT TESTED, evidence links, unresolved questions and corrective retests. Mark account-unavailable plugin/skill/notebook or absent recording as NOT TESTED, not passed. Allow optional labs to be skipped with reasons while keeping app security/backup/source checks mandatory before the final dashboard step. Do not claim completion for the learner; review their evidence. No publishing, data changes or real sends during recap.

30Design the dashboard — ChatGPT → GeminiDashboard design — ChatGPT → Gemini

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

A polished dashboard implemented by Gemini on verified foundations.
പരിശോധിച്ച foundations-ൽ Gemini നടപ്പാക്കുന്ന മനോഹര dashboard.

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Copy the single prompt below into ChatGPT. Supply only a redacted module map and approved metric definitions. Copy ChatGPT’s resulting dashboard-design prompt into the same Gemini implementation chat. Gemini implements it; verify results before marking complete.
താഴെയുള്ള ഒറ്റ prompt ChatGPT-ൽ നൽകുക. Redacted module map, അംഗീകരിച്ച metrics മാത്രം ചേർക്കുക. ChatGPT നൽകുന്ന dashboard-design prompt അതേ Gemini chat-ൽ നൽകി നടപ്പാക്കുക. Result പരിശോധിച്ചശേഷം മാത്രം complete ആക്കുക.
Check the expected result below before moving to the next step.
അടുത്ത ഘട്ടത്തിന് മുമ്പ് താഴെയുള്ള expected result പരിശോധിക്കുക.

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Check dashboard metrics against reports, filters, mobile navigation, keyboard access, contrast, reduced motion, loading/empty/error states and authorization. Retest backend features; keep backups and record actual PASS / FAIL / NOT TESTED.
Dashboard metrics reports-മായി താരതമ്യം ചെയ്യുക. Filters, mobile navigation, keyboard, contrast, reduced motion, loading/empty/error, access പരിശോധിക്കുക. Backend വീണ്ടും test ചെയ്ത് actual PASS / FAIL / NOT TESTED രേഖപ്പെടുത്തുക.

ChatGPT writes the design prompt → you paste its output into Gemini → Gemini implements and tests the dashboard.

ChatGPT design prompt തയ്യാറാക്കും → ആ output Gemini-ൽ നൽകുക → Gemini dashboard നടപ്പാക്കി പരിശോധിക്കും.

Open ChatGPT for this design prompt ↗Design prompt-നായി ChatGPT തുറക്കുക

Mark completed only after verificationപരിശോധിച്ചശേഷം മാത്രം complete ആക്കുക

Copy Prompt — take this to ChatGPTഈ prompt ChatGPT-ൽ നൽകുക

You are ChatGPT. Create ONE polished dashboard-design implementation prompt for Gemini; do not implement the app yourself. This is the LAST step of the RP Smart Office Create New route. All foundations, data adapters, modules, reports, privacy boundaries, tests, backups and maintenance must already be verified; if these or the redacted module map and metric definitions are missing, request them before finalizing. Ask for no private records or secrets.

Your output must be a single complete prompt addressed to Gemini, ready for me to paste into my existing Gemini implementation chat. Ask Gemini to implement the dashboard using the approved Apps Script file map, native HTML/CSS/JavaScript and verified backend/report functions. Use a premium white/blue visual design, readable typography, responsive sidebar, subtle glass cards, accessible tables/filters and useful visual hierarchy. Derive every metric from actual authorized rows and approved report definitions; no fabricated statistics. Include keyboard/mobile navigation, contrast, reduced motion and loading/empty/error states. Preserve the exact new-demo schema and dummy-data-only workbook. Never change authentication, access, deployment settings or public/private project separation for visual design. Require backups, one complete named changed file at a time, exact paste locations, dashboard-to-report metric comparisons, regression/security tests, actual PASS/FAIL/NOT TESTED evidence and rollback. After verification, explain updating the existing deployment version while preserving its URL; redeploy only with explicit owner approval. Gemini must use authorized connected tools when supported; otherwise state limitations and request minimum access or provide clearly labeled executable/manual fallback, never claim execution. No paid AI APIs, external hosting or automatic database writes from Ask AI. Return only that one Gemini implementation prompt.

I will now take your resulting prompt to Gemini to implement, test, and verify the final dashboard.

Build your Smart Office.നിങ്ങളുടെ സ്മാർട്ട് ഓഫീസ് ഉണ്ടാക്കാം.

How would you like to start?എങ്ങനെ തുടങ്ങണം?

Create Newപുതിയത് ഉണ്ടാക്കുക

Connect Existing File/Databaseനിലവിലുള്ള File/Database ബന്ധിപ്പിക്കുക

Use one Gemini chat per routeഓരോ route-നും ഒരു Gemini chat

Foundation → modules → dashboardഅടിത്തറ → modules → dashboard

What are we automating — and in what order?എന്താണ് automate ചെയ്യുന്നത് — ഏത് ക്രമത്തിൽ?

Create Newപുതിയത് ഉണ്ടാക്കുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Session 2 · Apps Script from zeroസെഷൻ 2 · Apps Script ആദ്യമായി

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Session 3 · Website versus web appസെഷൻ 3 · Website, web app വ്യത്യാസം

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക

Verify before continuingതുടരുന്നതിന് മുമ്പ് പരിശോധിക്കുക

Copy Prompt — take this to Geminiഈ prompt Gemini-ൽ നൽകുക

Aims — what this step achievesലക്ഷ്യം — ഈ ഘട്ടത്തിൽ നേടേണ്ടത്

Actions — do these in orderചെയ്യേണ്ടത് — ക്രമത്തിൽ ചെയ്യുക