Revise WhatsApp Forms documentation and update details#578
Merged
Conversation
Updated the last updated date and modified the steps for creating WhatsApp forms, including new instructions for data storage and form submission based on the forms phase 2 implementation
Contributor
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughThis PR rewrites the WhatsApp Forms documentation to center the flow on a dedicated Form Builder, removes embedded iframe/Meta Playground steps, updates the "Last updated" to February 2026, and adds detailed guidance on field types, Option IDs, multilingual handling, lifecycle states, a creation checklist, and sending prerequisites. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
🚀 Deployed on https://deploy-preview-578--glific-docs.netlify.app |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/4`. Product Features/WhatsApp Forms.md:
- Line 46: The document uses the lowercase proper noun "google" in phrases like
"google sheet" and "google service account" (e.g., the text "add a `google
sheet` with write access to the google service account"); update these
occurrences to use the correct capitalization "Google" (e.g., "Google Sheet",
"Google service account") consistently throughout the file, including the
instances referenced at lines 46, 96, and 128.
- Around line 55-58: The doc uses two different lifecycle terms—“Submit to Meta”
(button/step label) and “published” (descriptive state); pick one term and make
it consistent across the guide and FAQs (replace occurrences of “published” with
“Submit to Meta” or vice versa), update the Form Features section lines
referencing the final step (e.g., the “Submit to Meta” button text) and the
FAQ/other sections (previously lines ~223-226 and ~239-245) so they use the
chosen term consistently, and keep the immutability note (“once the form is
submitted to meta, it cannot be changed further”) aligned to the chosen
terminology.
- Around line 42-48: The ordered step lists in WhatsApp Forms.md have skipped
numbers (e.g., 1,2,3,4,6) which breaks continuity; update each "Steps:" ordered
list so numbering is sequential and continuous (e.g., change the block that
currently reads 1,2,3,4,6 to 1,2,3,4,5) and repeat the same fix for the other
occurrences referenced (the lists around lines 61-65 and 154-156); ensure every
"Steps:" section and its items are renumbered to a consecutive sequence without
gaps so users can follow instructions linearly.
- Line 121: The emphasis contains trailing spaces ("**Implications of the id
**"); remove the extra space inside the bold markers so the text reads
"**Implications of the id**" to satisfy markdownlint MD037 and render correctly;
update the heading in the WhatsApp Forms document where the string "Implications
of the id **" appears.
Comment on lines
42
to
+48
| Steps: | ||
| 1. Go to `Quick Tools` → `WhatsApp Forms` in Glific. | ||
| 2. Click `Create Form` | ||
| 3. Go to WhatsApp Flows Playground to get a friendly interface to create your form | ||
| 4. Choose field types and design your form (text input, radio, multi-select, etc.) | ||
| 5. Click on `copy flow JSON` after completing the form design | ||
| 6. Paste the Flow JSON into the `form JSON` input field | ||
| 7. Give your form an appropriate `title`, `description` and `category` | ||
| 8. Click on `Save` | ||
| 9. This creates a draft of the form | ||
| 10. On the `WhatsApp Forms` Listing page, click on the publish icon to publish the form. | ||
| 2. Click `Create` Form | ||
| 3. Provide a form `title` and `category` | ||
| 4. For data storage, add a `google sheet` with write access to the google service account to automatically capture the responses to the form. This step is optional. A google sheet can be added before the form is `submitted to Meta` | ||
| 6. Click on Save and go to the form builder interface | ||
| <img width="568" height="386" alt="Screenshot 2026-02-24 at 3 51 24 PM" src="https://github.com/user-attachments/assets/15e81cc8-0da5-43a0-95fd-298177bb567a" /> |
Contributor
There was a problem hiding this comment.
Fix broken step numbering.
There are skipped numbers in multiple step lists (e.g., 4→6, 2→4, 1→3), which makes the instructions hard to follow. Please renumber for continuity.
Also applies to: 61-65, 154-156
🧰 Tools
🪛 LanguageTool
[uncategorized] ~46-~46: “Google” is a proper noun and needs to be capitalized.
Context: ...google sheet with write access to the google service account to automatically captur...
(A_GOOGLE)
[uncategorized] ~46-~46: “Google” is a proper noun and needs to be capitalized.
Context: ...s to the form. This step is optional. A google sheet can be added before the form is `...
(A_GOOGLE)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/4`. Product Features/WhatsApp Forms.md around lines 42 - 48, The ordered
step lists in WhatsApp Forms.md have skipped numbers (e.g., 1,2,3,4,6) which
breaks continuity; update each "Steps:" ordered list so numbering is sequential
and continuous (e.g., change the block that currently reads 1,2,3,4,6 to
1,2,3,4,5) and repeat the same fix for the other occurrences referenced (the
lists around lines 61-65 and 154-156); ensure every "Steps:" section and its
items are renumbered to a consecutive sequence without gaps so users can follow
instructions linearly.
| 10. On the `WhatsApp Forms` Listing page, click on the publish icon to publish the form. | ||
| 2. Click `Create` Form | ||
| 3. Provide a form `title` and `category` | ||
| 4. For data storage, add a `google sheet` with write access to the google service account to automatically capture the responses to the form. This step is optional. A google sheet can be added before the form is `submitted to Meta` |
Contributor
There was a problem hiding this comment.
Capitalize “Google” consistently.
Multiple instances use “google” in running text. Please capitalize the proper noun.
Also applies to: 96-96, 128-128
🧰 Tools
🪛 LanguageTool
[uncategorized] ~46-~46: “Google” is a proper noun and needs to be capitalized.
Context: ...google sheet with write access to the google service account to automatically captur...
(A_GOOGLE)
[uncategorized] ~46-~46: “Google” is a proper noun and needs to be capitalized.
Context: ...s to the form. This step is optional. A google sheet can be added before the form is `...
(A_GOOGLE)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/4`. Product Features/WhatsApp Forms.md at line 46, The document uses the
lowercase proper noun "google" in phrases like "google sheet" and "google
service account" (e.g., the text "add a `google sheet` with write access to the
google service account"); update these occurrences to use the correct
capitalization "Google" (e.g., "Google Sheet", "Google service account")
consistently throughout the file, including the instances referenced at lines
46, 96, and 128.
Comment on lines
+55
to
+58
| 1. Form Json - this allows you to toggle to the from json view, and edit things in the form json as it gets developed by adding screens and components from | ||
| 2. Save Draft - while the changes being made are auto-saved, this button is provided as a back-up. | ||
| 3. Submit to Meta - this is the final step of form creation. Click on `Submit to meta` once the form is ready to be used by over WhatsApp. Please note: once the form is submitted to meta, it cannot be changed further. To make changes, a new form will need to be created and modified. | ||
|
|
Contributor
There was a problem hiding this comment.
Align lifecycle terminology (“Submit to Meta” vs “published”).
The doc states forms must be “submitted to Meta” and then later says they must be “published.” These appear to describe the same lifecycle step; inconsistent terminology will confuse users. Please standardize on one term across the guide and FAQs.
Also applies to: 223-226, 239-245
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/4`. Product Features/WhatsApp Forms.md around lines 55 - 58, The doc
uses two different lifecycle terms—“Submit to Meta” (button/step label) and
“published” (descriptive state); pick one term and make it consistent across the
guide and FAQs (replace occurrences of “published” with “Submit to Meta” or vice
versa), update the Form Features section lines referencing the final step (e.g.,
the “Submit to Meta” button text) and the FAQ/other sections (previously lines
~223-226 and ~239-245) so they use the chosen term consistently, and keep the
immutability note (“once the form is submitted to meta, it cannot be changed
further”) aligned to the chosen terminology.
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
♻️ Duplicate comments (3)
docs/4. Product Features/WhatsApp Forms.md (3)
46-46:⚠️ Potential issue | 🟡 MinorCapitalize “Google” consistently.
Line 46, Line 96, and Line 128 use “google” in running text. Please standardize to “Google” (e.g., “Google Sheet”, “Google service account”).
Also applies to: 96-96, 128-128
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/4`. Product Features/WhatsApp Forms.md at line 46, The document uses lowercase “google” in several places; update each occurrence to use the proper capitalization: change "google sheet" to "Google Sheet", "google service account" to "Google service account", and any other instances of "google" in running text (e.g., the phrase "submitted to Meta" context) so all mentions are consistently capitalized (check the occurrences matching the diff strings "google sheet", "google service account", and surrounding text on the flagged lines).
57-57:⚠️ Potential issue | 🟠 MajorStandardize lifecycle terminology across the guide.
Line 57/131/138 use “submitted to Meta,” while Line 224–226 and Line 241/245 use “published.” Please pick one canonical lifecycle term and apply it consistently across steps, checklist, notes, and FAQs.
Also applies to: 131-131, 138-138, 223-226, 241-245
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/4`. Product Features/WhatsApp Forms.md at line 57, Choose a single canonical lifecycle term (e.g., "published" or "submitted to Meta") and replace all inconsistent occurrences—specifically the phrases "Submit to Meta", "`Submit to meta`", "submitted to Meta", and "published"—so the guide uses that one term consistently in steps, checklists, notes, FAQs and any button text; ensure casing is consistent (Meta vs meta) and update the sentence in the step that currently reads "Submit to Meta - this is the final step..." plus the checklist and FAQ entries that reference "published" to use the chosen canonical phrase.
42-47:⚠️ Potential issue | 🟡 MinorFix skipped numbering in ordered lists.
Line 47, Line 65, Line 156, and Line 243 continue lists with missing numbers. Please renumber these lists sequentially for readability and consistency.
Suggested renumbering
-6. Click on Save and go to the form builder interface +5. Click on Save and go to the form builder interface ... -4. Please note, the preview mode is not fully representative ... +3. Please note, the preview mode is not fully representative ... ... -3. Take a note of all the these form field names +2. Take a note of all these form field names ... -3. What is the published state +2. What is the published stateAlso applies to: 61-65, 154-156, 239-247
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/4`. Product Features/WhatsApp Forms.md around lines 42 - 47, The ordered lists under the "Steps:" blocks in WhatsApp Forms.md have skipped/misaligned numbers (e.g., the sequence showing "1. Go to `Quick Tools` → `WhatsApp Forms`, 2. Click `Create` Form, 3. Provide a form `title` and `category`, 4. For data storage..., 6. Click on Save..." and similar elsewhere); update each ordered list so numbers are sequential (1,2,3,4,5...) throughout the document, fixing the lists that start with the "Steps:" heading and other list blocks that include items referencing `google sheet`, `submitted to Meta`, and the form builder instructions so all list items follow correct numeric order.
🧹 Nitpick comments (1)
docs/4. Product Features/WhatsApp Forms.md (1)
50-57: Do a quick editorial cleanup pass for clarity.Several new sections have grammar/wording slips that make instructions harder to scan (e.g., Line 55, Line 57, Line 79, Line 87, Line 109, Line 123, Line 130). A brief proofread pass will materially improve readability.
Also applies to: 79-79, 87-87, 109-123, 127-131, 135-138
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/4`. Product Features/WhatsApp Forms.md around lines 50 - 57, Perform a brief editorial cleanup of the "Navigating the form builder interface." section and the other flagged blocks by fixing grammar, punctuation, capitalization, and clarity; specifically: reword the intro to be a complete sentence, normalize action names ("Form JSON" not "Form Json", "Submit to Meta" capitalization consistent), correct typos ("from json view" → "form JSON view", "over WhatsApp" → "on WhatsApp"), and simplify the Submit description to state immutability after submission and the need to create a new form for changes; apply the same proofreading rules to the other flagged sections (the blocks around lines noted in the review) to fix sentence fragments, tense/number agreement, and inconsistent styling so instructions are concise and scannable.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In `@docs/4`. Product Features/WhatsApp Forms.md:
- Line 46: The document uses lowercase “google” in several places; update each
occurrence to use the proper capitalization: change "google sheet" to "Google
Sheet", "google service account" to "Google service account", and any other
instances of "google" in running text (e.g., the phrase "submitted to Meta"
context) so all mentions are consistently capitalized (check the occurrences
matching the diff strings "google sheet", "google service account", and
surrounding text on the flagged lines).
- Line 57: Choose a single canonical lifecycle term (e.g., "published" or
"submitted to Meta") and replace all inconsistent occurrences—specifically the
phrases "Submit to Meta", "`Submit to meta`", "submitted to Meta", and
"published"—so the guide uses that one term consistently in steps, checklists,
notes, FAQs and any button text; ensure casing is consistent (Meta vs meta) and
update the sentence in the step that currently reads "Submit to Meta - this is
the final step..." plus the checklist and FAQ entries that reference "published"
to use the chosen canonical phrase.
- Around line 42-47: The ordered lists under the "Steps:" blocks in WhatsApp
Forms.md have skipped/misaligned numbers (e.g., the sequence showing "1. Go to
`Quick Tools` → `WhatsApp Forms`, 2. Click `Create` Form, 3. Provide a form
`title` and `category`, 4. For data storage..., 6. Click on Save..." and similar
elsewhere); update each ordered list so numbers are sequential (1,2,3,4,5...)
throughout the document, fixing the lists that start with the "Steps:" heading
and other list blocks that include items referencing `google sheet`, `submitted
to Meta`, and the form builder instructions so all list items follow correct
numeric order.
---
Nitpick comments:
In `@docs/4`. Product Features/WhatsApp Forms.md:
- Around line 50-57: Perform a brief editorial cleanup of the "Navigating the
form builder interface." section and the other flagged blocks by fixing grammar,
punctuation, capitalization, and clarity; specifically: reword the intro to be a
complete sentence, normalize action names ("Form JSON" not "Form Json", "Submit
to Meta" capitalization consistent), correct typos ("from json view" → "form
JSON view", "over WhatsApp" → "on WhatsApp"), and simplify the Submit
description to state immutability after submission and the need to create a new
form for changes; apply the same proofreading rules to the other flagged
sections (the blocks around lines noted in the review) to fix sentence
fragments, tense/number agreement, and inconsistent styling so instructions are
concise and scannable.
Fawas003
reviewed
Feb 25, 2026
| 2. **Media**: An image file, of type JPEG, PNG can be added upto 300kb in size. | ||
| <img width="543" height="367" alt="Screenshot 2026-02-24 at 4 42 06 PM" src="https://github.com/user-attachments/assets/5ef5b08f-6b38-4b6f-842f-bc94845d29f0" /> | ||
|
|
||
| 3. **Text answer**: A short answer, paragraph answer of date field can be captured using this type. |
Contributor
There was a problem hiding this comment.
Paragraph and date picker are different options right? this sentence may need to be rephrased
@mahajantejas
Collaborator
Author
There was a problem hiding this comment.
date picker is part of the short answer type, i have re-phrased it.
Fawas003
reviewed
Feb 25, 2026
| <img width="561" height="384" alt="Screenshot 2026-02-24 at 4 42 45 PM" src="https://github.com/user-attachments/assets/589faff4-47b8-4edb-b382-967caecc5815" /> | ||
|
|
||
| #### What are field names and how to use them? | ||
| Field name the the mandatory captions/ titles that appear above the input field in the form. This serves 2 function |
Fawas003
reviewed
Feb 25, 2026
| 1. **Titles and Captions**: Under the `Text` content, heading, subheading, captions, and texts can be added to the form. | ||
|
|
||
| <img width="1165" height="813" alt="Screenshot 2026-02-24 at 5 00 45 PM" src="https://github.com/user-attachments/assets/19b33e4a-48b5-4450-af39-976c9104dd44" /> | ||
| 2. **Media**: An image file, of type JPEG, PNG can be added upto 300kb in size. |
Contributor
There was a problem hiding this comment.
media is showing as md form in preview. this may not be an issue once it is published, i am not sure
Collaborator
Author
There was a problem hiding this comment.
this will change once it is published.
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
docs/4. Product Features/WhatsApp Forms.md (2)
219-219:⚠️ Potential issue | 🟡 MinorAlign instruction text with the actual SQL line.
The SQL uses
wf.name = 'you_form_name', but the instruction sayswf.name = form_name; this mismatch causes confusion.🧾 Proposed instruction fix
-1. Change the form name in the line `wf.name = form_name` +1. Change the form name in the line `wf.name = 'your_form_name'`🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/4`. Product Features/WhatsApp Forms.md at line 219, Update the instruction text so it matches the SQL example: change the referenced assignment to use the quoted literal used in the SQL (wf.name = 'you_form_name') instead of the unquoted variable form_name; specifically edit the line/instruction that mentions wf.name and form_name to read wf.name = 'you_form_name' to eliminate the mismatch.
189-191:⚠️ Potential issue | 🟠 MajorCorrect dataset placeholder typo in SQL snippet.
your-dateset-nameis misspelled and will mislead users copying the query.🛠️ Proposed SQL placeholder fix
- `your-project-name.your-dateset-name.whatsapp_forms` AS wf + `your-project-name.your-dataset-name.whatsapp_forms` AS wf @@ - `your-project-name.your-dateset-name.whatsapp_forms_responses` AS wfr + `your-project-name.your-dataset-name.whatsapp_forms_responses` AS wfr🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/4`. Product Features/WhatsApp Forms.md around lines 189 - 191, Typo in the SQL placeholders: replace the misspelled `your-dateset-name` with the correct `your-dataset-name` in the SQL snippet (both occurrences: `your-project-name.your-dateset-name.whatsapp_forms` and `your-project-name.your-dateset-name.whatsapp_forms_responses`) so users copying the query get the proper dataset placeholder.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/4`. Product Features/WhatsApp Forms.md:
- Around line 130-131: Fix the checklist formatting and casing in the two list
items: add a space after "3." so it reads "3. The `option ids`...", ensure
consistent casing for the platform by changing "meta" to "Meta" in "The form is
`submitted to Meta`", and tidy punctuation/spacing so both lines follow the same
checklist style (same leading number format, spacing after periods, and inline
code backticks preserved) to improve readability; locate and update the strings
"3.The `option ids` for the fields with options..." and "4. The form is
`submitted to meta`" accordingly.
- Line 55: The "Form Json" description sentence is incomplete; update the line
starting "1. Form Json - this allows you to toggle to the from json view, and
edit things in the form json as it gets developed by adding screens and
components from" to finish the thought—e.g., state the source/context such as
"from the form builder" or "from the UI editor" so it reads clearly (e.g.,
"...by adding screens and components from the form builder"); ensure the phrase
"form json" is corrected to "form JSON" for consistency if desired.
---
Outside diff comments:
In `@docs/4`. Product Features/WhatsApp Forms.md:
- Line 219: Update the instruction text so it matches the SQL example: change
the referenced assignment to use the quoted literal used in the SQL (wf.name =
'you_form_name') instead of the unquoted variable form_name; specifically edit
the line/instruction that mentions wf.name and form_name to read wf.name =
'you_form_name' to eliminate the mismatch.
- Around line 189-191: Typo in the SQL placeholders: replace the misspelled
`your-dateset-name` with the correct `your-dataset-name` in the SQL snippet
(both occurrences: `your-project-name.your-dateset-name.whatsapp_forms` and
`your-project-name.your-dateset-name.whatsapp_forms_responses`) so users copying
the query get the proper dataset placeholder.
|
|
||
| There are 3 major actions: | ||
|
|
||
| 1. Form Json - this allows you to toggle to the from json view, and edit things in the form json as it gets developed by adding screens and components from |
Contributor
There was a problem hiding this comment.
Complete the unfinished sentence in “Form Json” description.
The sentence ends with “from” and is incomplete, so readers won’t know the source/context.
✍️ Proposed text fix
-1. Form Json - this allows you to toggle to the from json view, and edit things in the form json as it gets developed by adding screens and components from
+1. Form Json - this allows you to toggle to the form JSON view and edit the JSON generated as you add screens and components from the builder.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/4`. Product Features/WhatsApp Forms.md at line 55, The "Form Json"
description sentence is incomplete; update the line starting "1. Form Json -
this allows you to toggle to the from json view, and edit things in the form
json as it gets developed by adding screens and components from" to finish the
thought—e.g., state the source/context such as "from the form builder" or "from
the UI editor" so it reads clearly (e.g., "...by adding screens and components
from the form builder"); ensure the phrase "form json" is corrected to "form
JSON" for consistency if desired.
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Actionable comments posted: 7
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
docs/4. Product Features/WhatsApp Forms.md (1)
239-255:⚠️ Potential issue | 🟡 MinorAdd missing question marks to FAQ questions.
Four FAQ questions are missing question marks at the end (lines 239, 243, 247, 255), while line 251 correctly has one. This creates inconsistency in the FAQ section formatting.
📝 Proposed fix
-1. What is the draft state of the form +1. What is the draft state of the form? Draft state of the form is when the form entity is created in Glific and it can be edited to improve the UI, but the form is not yet published with Meta, therefore it cannot be used in HSMs and it is not yet available to use via WhatsApp -3. What is the published state +3. What is the published state? Published state is when the form is published with Meta and can be used to create a WhatsApp form-linked HSM message that can be sent to users via WhatsApp. -4. What is the deactivated state +4. What is the deactivated state? Deactivated state of the form is when the form can no longer be used for future HSMs. In this state, the HSMs which have the form linked already will remain operational. 5. Why are there numbers at the beginning of the responses? The responses captured from whatsapp forms are returned along with the index of the option chosen by the user, the numbers represent the index of choice. -6. How much does it cost to send the form +6. How much does it cost to send the form?🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/4`. Product Features/WhatsApp Forms.md around lines 239 - 255, The four FAQ headings lacking punctuation should end with question marks; update the headings "What is the draft state of the form", "What is the published state", "What is the deactivated state", and "How much does it cost to send the form" to include a trailing "?" so they match the existing question style (e.g., "What is the draft state of the form?") and ensure consistent formatting across the FAQ section.
♻️ Duplicate comments (1)
docs/4. Product Features/WhatsApp Forms.md (1)
128-128:⚠️ Potential issue | 🟡 MinorCapitalize product name consistently.
"bigquery" should be "BigQuery" (the official product name capitalization).
📝 Proposed fix
-1. There is a google sheet attached to the form for ease of collecting responses. While the responses to the form are synced to your bigquery by default, having a google sheet attached will help you to see responses quickly and easily. +1. There is a Google sheet attached to the form for ease of collecting responses. While the responses to the form are synced to your BigQuery by default, having a Google sheet attached will help you to see responses quickly and easily.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/4`. Product Features/WhatsApp Forms.md at line 128, Update the product name capitalization in the sentence that mentions bigquery so it uses the official casing "BigQuery" instead of "bigquery"; locate the line in the WhatsApp Forms documentation that reads "responses to the form are synced to your bigquery by default" and change "bigquery" to "BigQuery" wherever it appears for consistent branding.
🧹 Nitpick comments (1)
docs/4. Product Features/WhatsApp Forms.md (1)
232-232: Capitalize acronym consistently."screen id" should be "screen ID" (ID is an acronym).
📝 Proposed fix
-9. It is possible to change the screen names by altering the screen id in the form json +9. It is possible to change the screen names by altering the screen ID in the form JSON.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/4`. Product Features/WhatsApp Forms.md at line 232, Change the phrase "screen id" to "screen ID" in the sentence "It is possible to change the screen names by altering the screen id in the form json" so the acronym is capitalized consistently; also scan the document for any other occurrences of "screen id" and replace them with "screen ID" to ensure uniform capitalization.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/4`. Product Features/WhatsApp Forms.md:
- Line 123: Change the misspelled compound "usecases" to the two-word form "use
cases" in the sentence "This can help with usecases where title and responses
need to be abstracted away." so the line reads "This can help with use cases
where title and responses need to be abstracted away."; update the exact
occurrence in the document "WhatsApp Forms.md".
- Line 64: Update the sentence "The preview section allows you to get glimpse of
how the form will turn out on WhatsApp." by inserting the missing article so it
reads "The preview section allows you to get a glimpse of how the form will turn
out on WhatsApp."; locate the sentence in the WhatsApp Forms documentation (the
line that starts "The preview section allows you to get glimpse") and replace
"get glimpse" with "get a glimpse".
- Line 109: Replace the lowercase "whatsapp interface" phrase with the correct
product capitalization "WhatsApp interface" in the sentence that reads "Each
option has a `title` which is text that appears to the user in the whatsapp
interface to select" so the sentence uses "WhatsApp interface" consistently;
update the same occurrence of "whatsapp" (if duplicated) within that paragraph
to "WhatsApp".
- Line 68: Replace the awkward phrase "to the in line of the Screens header"
with a clear alternative; in the sentence inside "Adding screens" change it to
say either "Use the 'Add new' button next to the Screens header to add new
screens" or "Use the 'Add new' button inline with the Screens header to add new
screens," and keep the remainder ("Screen title can be added in the `Screen
Name` entry field") unchanged.
- Line 87: Fix the subject-verb agreement in the sentence "This serves 2
function" by changing it to "This serves 2 functions" in the docs paragraph that
begins "Field names are the captions/ titles that appear above the input field
in the form."
- Line 152: Replace the awkward phrase "in the Glific" with "in Glific flows" in
the sentence describing how form responses are used; update the sentence in the
WhatsApp Forms documentation (the line that starts "The responses to the form
can be captured...") to read "...can be captured, and used in Glific flows for
taking actions such as write to google sheet or can be used in split by
logic..." and adjust surrounding punctuation/spacing so the sentence remains
grammatical.
- Line 57: Update the sentence that begins "Submit to Meta - this is the final
step of form creation..." to correct two issues: change "over WhatsApp" to "on
WhatsApp" and capitalize "Meta" in "submitted to meta" so it reads consistently
with the "Submit to Meta" button name; ensure the final sentence reads that once
the form is "submitted to Meta" it cannot be changed and a new form must be
created to modify it.
---
Outside diff comments:
In `@docs/4`. Product Features/WhatsApp Forms.md:
- Around line 239-255: The four FAQ headings lacking punctuation should end with
question marks; update the headings "What is the draft state of the form", "What
is the published state", "What is the deactivated state", and "How much does it
cost to send the form" to include a trailing "?" so they match the existing
question style (e.g., "What is the draft state of the form?") and ensure
consistent formatting across the FAQ section.
---
Duplicate comments:
In `@docs/4`. Product Features/WhatsApp Forms.md:
- Line 128: Update the product name capitalization in the sentence that mentions
bigquery so it uses the official casing "BigQuery" instead of "bigquery"; locate
the line in the WhatsApp Forms documentation that reads "responses to the form
are synced to your bigquery by default" and change "bigquery" to "BigQuery"
wherever it appears for consistent branding.
---
Nitpick comments:
In `@docs/4`. Product Features/WhatsApp Forms.md:
- Line 232: Change the phrase "screen id" to "screen ID" in the sentence "It is
possible to change the screen names by altering the screen id in the form json"
so the acronym is capitalized consistently; also scan the document for any other
occurrences of "screen id" and replace them with "screen ID" to ensure uniform
capitalization.
|
|
||
| 1. Form Json - this allows you to toggle to the from json view, and edit things in the form json as it gets developed by adding screens and components from | ||
| 2. Save Draft - while the changes being made are auto-saved, this button is provided as a back-up. | ||
| 3. Submit to Meta - this is the final step of form creation. Click on `Submit to meta` once the form is ready to be used by over WhatsApp. Please note: once the form is submitted to meta, it cannot be changed further. To make changes, a new form will need to be created and modified. |
Contributor
There was a problem hiding this comment.
Fix grammatical and terminology inconsistencies.
Two issues in this line:
- "over WhatsApp" should be "on WhatsApp" for proper usage
- "submitted to meta" should use capital "M" in "Meta" for consistency with "Submit to Meta" button name used throughout
📝 Proposed fix
-3. Submit to Meta - this is the final step of form creation. Click on `Submit to meta` once the form is ready to be used by over WhatsApp. Please note: once the form is submitted to meta, it cannot be changed further. To make changes, a new form will need to be created and modified.
+3. Submit to Meta - this is the final step of form creation. Click on `Submit to Meta` once the form is ready to be used on WhatsApp. Please note: once the form is submitted to Meta, it cannot be changed further. To make changes, a new form will need to be created and modified.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/4`. Product Features/WhatsApp Forms.md at line 57, Update the sentence
that begins "Submit to Meta - this is the final step of form creation..." to
correct two issues: change "over WhatsApp" to "on WhatsApp" and capitalize
"Meta" in "submitted to meta" so it reads consistently with the "Submit to Meta"
button name; ensure the final sentence reads that once the form is "submitted to
Meta" it cannot be changed and a new form must be created to modify it.
| 4. Please note, the preview mode is not fully representative of how the form will look on WhatsApp of your beneficiaries, as this varies a lot based on the version of WhatsApp and the device type such as android, ios etc. | ||
|
|
||
| ### Form Builder Action | ||
| 1. Adding screens: Use `Add new` button to the in line of the Screens header to add new screens. Screen title can be added in the `Screen Name` entry field |
Contributor
There was a problem hiding this comment.
Fix awkward phrasing.
"to the in line of" is grammatically incorrect. Should be "next to" or "inline with".
📝 Proposed fix
-1. Adding screens: Use `Add new` button to the in line of the Screens header to add new screens. Screen title can be added in the `Screen Name` entry field
+1. Adding screens: Use the `Add New` button next to the Screens header to add new screens. Screen title can be added in the `Screen Name` entry field.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| 1. Adding screens: Use `Add new` button to the in line of the Screens header to add new screens. Screen title can be added in the `Screen Name` entry field | |
| 1. Adding screens: Use the `Add New` button next to the Screens header to add new screens. Screen title can be added in the `Screen Name` entry field. |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/4`. Product Features/WhatsApp Forms.md at line 68, Replace the awkward
phrase "to the in line of the Screens header" with a clear alternative; in the
sentence inside "Adding screens" change it to say either "Use the 'Add new'
button next to the Screens header to add new screens" or "Use the 'Add new'
button inline with the Screens header to add new screens," and keep the
remainder ("Screen title can be added in the `Screen Name` entry field")
unchanged.
| <img width="561" height="384" alt="Screenshot 2026-02-24 at 4 42 45 PM" src="https://github.com/user-attachments/assets/589faff4-47b8-4edb-b382-967caecc5815" /> | ||
|
|
||
| #### What are field names and how to use them? | ||
| Field names are the captions/ titles that appear above the input field in the form. This serves 2 function |
Contributor
There was a problem hiding this comment.
Fix subject-verb agreement.
"This serves 2 function" should be "This serves 2 functions" (plural).
📝 Proposed fix
-Field names are the captions/ titles that appear above the input field in the form. This serves 2 function
+Field names are the captions/titles that appear above the input field in the form. This serves 2 functions:📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| Field names are the captions/ titles that appear above the input field in the form. This serves 2 function | |
| Field names are the captions/titles that appear above the input field in the form. This serves 2 functions: |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/4`. Product Features/WhatsApp Forms.md at line 87, Fix the subject-verb
agreement in the sentence "This serves 2 function" by changing it to "This
serves 2 functions" in the docs paragraph that begins "Field names are the
captions/ titles that appear above the input field in the form."
|
|
||
| #### What are Option Ids and how to use them | ||
|
|
||
| The options listed under selection type of the content - dropdown or single choice or multiple choice show up in the form json. Each option has a `title` which is text that appears to the user in the whatsapp interface to select. There is also an `id`, this id is what gets returned as the response and remains invisible to the user. |
Contributor
There was a problem hiding this comment.
Standardize WhatsApp capitalization.
"whatsapp interface" should be "WhatsApp interface" for consistency with the product name used throughout the document.
📝 Proposed fix
-The options listed under selection type of the content - dropdown or single choice or multiple choice show up in the form json. Each option has a `title` which is text that appears to the user in the whatsapp interface to select. There is also an `id`, this id is what gets returned as the response and remains invisible to the user.
+The options listed under selection type of the content - dropdown or single choice or multiple choice show up in the form json. Each option has a `title` which is text that appears to the user in the WhatsApp interface to select. There is also an `id`, this id is what gets returned as the response and remains invisible to the user.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| The options listed under selection type of the content - dropdown or single choice or multiple choice show up in the form json. Each option has a `title` which is text that appears to the user in the whatsapp interface to select. There is also an `id`, this id is what gets returned as the response and remains invisible to the user. | |
| The options listed under selection type of the content - dropdown or single choice or multiple choice show up in the form json. Each option has a `title` which is text that appears to the user in the WhatsApp interface to select. There is also an `id`, this id is what gets returned as the response and remains invisible to the user. |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/4`. Product Features/WhatsApp Forms.md at line 109, Replace the
lowercase "whatsapp interface" phrase with the correct product capitalization
"WhatsApp interface" in the sentence that reads "Each option has a `title` which
is text that appears to the user in the whatsapp interface to select" so the
sentence uses "WhatsApp interface" consistently; update the same occurrence of
"whatsapp" (if duplicated) within that paragraph to "WhatsApp".
|
|
||
| ### How the WhatsApp Form results can be used in the Glific flow | ||
|
|
||
| The responses to the form can be captured, and used in the Glific for taking actions such as write to google sheet or can be used in split by logic to create separate branches in the glific flow based on the responses received to any particular fields on the form. |
Contributor
There was a problem hiding this comment.
Fix awkward phrasing.
"in the Glific" should be "in Glific flows" for clarity.
📝 Proposed fix
-The responses to the form can be captured, and used in the Glific for taking actions such as write to google sheet or can be used in split by logic to create separate branches in the glific flow based on the responses received to any particular fields on the form.
+The responses to the form can be captured and used in Glific flows for taking actions such as writing to Google sheets or using split-by logic to create separate branches in the flow based on responses received to any particular fields on the form.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| The responses to the form can be captured, and used in the Glific for taking actions such as write to google sheet or can be used in split by logic to create separate branches in the glific flow based on the responses received to any particular fields on the form. | |
| The responses to the form can be captured and used in Glific flows for taking actions such as writing to Google sheets or using split-by logic to create separate branches in the flow based on responses received to any particular fields on the form. |
🧰 Tools
🪛 LanguageTool
[grammar] ~152-~152: Use a hyphen to join words.
Context: ...to google sheet or can be used in split by logic to create separate branches in ...
(QB_NEW_EN_HYPHEN)
[grammar] ~152-~152: Use a hyphen to join words.
Context: ...google sheet or can be used in split by logic to create separate branches in the...
(QB_NEW_EN_HYPHEN)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/4`. Product Features/WhatsApp Forms.md at line 152, Replace the awkward
phrase "in the Glific" with "in Glific flows" in the sentence describing how
form responses are used; update the sentence in the WhatsApp Forms documentation
(the line that starts "The responses to the form can be captured...") to read
"...can be captured, and used in Glific flows for taking actions such as write
to google sheet or can be used in split by logic..." and adjust surrounding
punctuation/spacing so the sentence remains grammatical.
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
♻️ Duplicate comments (8)
docs/4. Product Features/WhatsApp Forms.md (8)
57-57:⚠️ Potential issue | 🟡 MinorFix grammar and product-name casing in the final action step.
The phrase “used by over WhatsApp” is incorrect, and
Metashould be consistently capitalized in the button/state text.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/4`. Product Features/WhatsApp Forms.md at line 57, Update the final action step text to fix grammar and product-name casing: change “Submit to meta” to “Submit to Meta” and replace the incorrect phrase “used by over WhatsApp” with “used on WhatsApp” (so the sentence reads: “Click on ‘Submit to Meta’ once the form is ready to be used on WhatsApp. Please note: once the form is submitted to Meta, it cannot be changed further. To make changes, a new form will need to be created and modified.”) Ensure both occurrences of the button/state text use the capitalized “Meta”.
42-48:⚠️ Potential issue | 🟡 MinorFix non-sequential numbering in ordered lists.
Several “Steps”/FAQ lists still skip numbers, which breaks flow and makes instructions harder to follow.
✍️ Suggested fix
-6. Click on Save and go to the form builder interface +5. Click on Save and go to the form builder interface ... -4. Please note, the preview mode is not fully representative... +3. Please note, the preview mode is not fully representative... ... -3. Take a note of all the these form field names +2. Take note of all these form field names ... -3. What is the published state +2. What is the published stateAlso applies to: 63-65, 154-157, 239-247
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/4`. Product Features/WhatsApp Forms.md around lines 42 - 48, The ordered "Steps:" list under "WhatsApp Forms" has non-sequential numbering (it jumps from 4 to 6); update the ordered list so numbering is sequential (change the 6 to 5 and ensure subsequent steps continue incrementally) and scan the other lists referenced (lines around 63-65, 154-157, 239-247) to fix any skipped numbers; look for the "Steps:" header and the "Click `Create` Form", "Provide a form `title` and `category`", and "For data storage..." list items as anchors to correct numbering.
55-55:⚠️ Potential issue | 🟡 MinorComplete the unfinished “Form Json” sentence.
The sentence ends with “from” and is incomplete, so users won’t know what source/context is intended.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/4`. Product Features/WhatsApp Forms.md at line 55, Complete the unfinished "Form Json" sentence in the WhatsApp Forms doc by finishing the thought after "from" to specify the source/context (e.g., "from your application, templates, or other form builders") so readers know what can be added to the form JSON; update the sentence under the "Form Json" heading (the line starting "1. Form Json - this allows you to toggle to the from json view, and edit things in the form json as it gets developed by adding screens and components from") to a clear, complete phrase describing where screens and components are added from.
68-68:⚠️ Potential issue | 🟡 MinorRephrase the “Adding screens” instruction for clarity.
“to the in line of the Screens header” is awkward and unclear; use “next to the Screens header”.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/4`. Product Features/WhatsApp Forms.md at line 68, Reword the "Adding screens" instruction to remove the awkward phrase "to the in line of the Screens header" and clarify placement and steps: say that you should click the "Add new" button next to the Screens header to add a new screen and then enter the screen title in the "Screen Name" field (referencing the existing "Add new" button label and "Screen Name" entry field).
109-109:⚠️ Potential issue | 🟡 MinorCorrect terminology/spelling in Option Ids section.
Use “WhatsApp interface” (not “whatsapp interface”) and “use cases” (not “usecases”).
Also applies to: 123-123
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/4`. Product Features/WhatsApp Forms.md at line 109, Edit the "Option Ids" explanation line that reads about titles and ids (the sentence containing `title` and `id`) to correct capitalization and phrasing: replace "whatsapp interface" with "WhatsApp interface" and "usecases" with "use cases", preserving the existing meaning that `title` is shown to the user and `id` is returned in the response.
87-87:⚠️ Potential issue | 🟡 MinorFix subject-verb agreement in field-name description.
“This serves 2 function” should be “This serves 2 functions”.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/4`. Product Features/WhatsApp Forms.md at line 87, Update the sentence "This serves 2 function" in the field name description to correct subject-verb/number agreement: change it to "This serves 2 functions" so the text reads "Field names are the captions/ titles that appear above the input field in the form. This serves 2 functions".
46-46:⚠️ Potential issue | 🟡 MinorCapitalize “Google” consistently.
“google sheet” / “google service account” should be “Google Sheet” / “Google service account”.
Also applies to: 96-96, 128-128
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/4`. Product Features/WhatsApp Forms.md at line 46, Replace all occurrences of the lowercase terms with the correct capitalization: change "google sheet" to "Google Sheet" and "google service account" to "Google service account" in the document (examples found in the snippet containing "For data storage, add a `google sheet`..." and the other occurrences around lines referenced as 96 and 128); ensure consistent capitalization across the file for phrases "Google Sheet" and "Google service account".
57-57:⚠️ Potential issue | 🟠 MajorStandardize lifecycle terminology across the doc.
The guide mixes
Submit to Meta,submitted to meta, andpublishedfor the same state. Choose one canonical term and use it consistently in steps, notes, and FAQs.Also applies to: 138-138, 223-226, 241-245
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/4`. Product Features/WhatsApp Forms.md at line 57, Choose one canonical lifecycle term (e.g., "Submit to Meta" or "Published") and replace all inconsistent variants—specifically the phrases "Submit to Meta", "submitted to meta", and "published"—so the document uses the chosen term consistently in the step text, notes, and FAQs; update the occurrences shown in the diff and the other referenced sections (lines around the provided instances) to match the canonical wording and adjust capitalization/punctuation to be uniform across the entire "WhatsApp Forms.md" file.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In `@docs/4`. Product Features/WhatsApp Forms.md:
- Line 57: Update the final action step text to fix grammar and product-name
casing: change “Submit to meta” to “Submit to Meta” and replace the incorrect
phrase “used by over WhatsApp” with “used on WhatsApp” (so the sentence reads:
“Click on ‘Submit to Meta’ once the form is ready to be used on WhatsApp. Please
note: once the form is submitted to Meta, it cannot be changed further. To make
changes, a new form will need to be created and modified.”) Ensure both
occurrences of the button/state text use the capitalized “Meta”.
- Around line 42-48: The ordered "Steps:" list under "WhatsApp Forms" has
non-sequential numbering (it jumps from 4 to 6); update the ordered list so
numbering is sequential (change the 6 to 5 and ensure subsequent steps continue
incrementally) and scan the other lists referenced (lines around 63-65, 154-157,
239-247) to fix any skipped numbers; look for the "Steps:" header and the "Click
`Create` Form", "Provide a form `title` and `category`", and "For data
storage..." list items as anchors to correct numbering.
- Line 55: Complete the unfinished "Form Json" sentence in the WhatsApp Forms
doc by finishing the thought after "from" to specify the source/context (e.g.,
"from your application, templates, or other form builders") so readers know what
can be added to the form JSON; update the sentence under the "Form Json" heading
(the line starting "1. Form Json - this allows you to toggle to the from json
view, and edit things in the form json as it gets developed by adding screens
and components from") to a clear, complete phrase describing where screens and
components are added from.
- Line 68: Reword the "Adding screens" instruction to remove the awkward phrase
"to the in line of the Screens header" and clarify placement and steps: say that
you should click the "Add new" button next to the Screens header to add a new
screen and then enter the screen title in the "Screen Name" field (referencing
the existing "Add new" button label and "Screen Name" entry field).
- Line 109: Edit the "Option Ids" explanation line that reads about titles and
ids (the sentence containing `title` and `id`) to correct capitalization and
phrasing: replace "whatsapp interface" with "WhatsApp interface" and "usecases"
with "use cases", preserving the existing meaning that `title` is shown to the
user and `id` is returned in the response.
- Line 87: Update the sentence "This serves 2 function" in the field name
description to correct subject-verb/number agreement: change it to "This serves
2 functions" so the text reads "Field names are the captions/ titles that appear
above the input field in the form. This serves 2 functions".
- Line 46: Replace all occurrences of the lowercase terms with the correct
capitalization: change "google sheet" to "Google Sheet" and "google service
account" to "Google service account" in the document (examples found in the
snippet containing "For data storage, add a `google sheet`..." and the other
occurrences around lines referenced as 96 and 128); ensure consistent
capitalization across the file for phrases "Google Sheet" and "Google service
account".
- Line 57: Choose one canonical lifecycle term (e.g., "Submit to Meta" or
"Published") and replace all inconsistent variants—specifically the phrases
"Submit to Meta", "submitted to meta", and "published"—so the document uses the
chosen term consistently in the step text, notes, and FAQs; update the
occurrences shown in the diff and the other referenced sections (lines around
the provided instances) to match the canonical wording and adjust
capitalization/punctuation to be uniform across the entire "WhatsApp Forms.md"
file.
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Fawas003
approved these changes
Feb 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated the last updated date and modified the steps for creating WhatsApp forms, including new instructions for data storage and form submission based on the forms phase 2 implementation
Summary by CodeRabbit