From 650e0099bcadfa6dd2fd71591aa53bfe0f99b4be Mon Sep 17 00:00:00 2001
From: Tejas Mahajan <141305477+mahajantejas@users.noreply.github.com>
Date: Fri, 8 Aug 2025 13:04:39 +0530
Subject: [PATCH 1/5] Delete docs/6. FAQ/Languages Supported.md
removed languages supported section
---
docs/6. FAQ/Languages Supported.md | 16 ----------------
1 file changed, 16 deletions(-)
delete mode 100644 docs/6. FAQ/Languages Supported.md
diff --git a/docs/6. FAQ/Languages Supported.md b/docs/6. FAQ/Languages Supported.md
deleted file mode 100644
index a02c4e279..000000000
--- a/docs/6. FAQ/Languages Supported.md
+++ /dev/null
@@ -1,16 +0,0 @@
-> ### **2 minute read `Beginner`**
-
-## Languages Supported for Template Messages
-
- Message templates are supported in approximately 71 languages by Gupshup.
-
-Check out the help link for details.[Read more](https://support.gupshup.io/hc/en-us/articles/360013321939-Which-languages-are-supported-for-message-templates)
-
-Glific has offered various choices for selecting your preferred language.
-
-To access the desired language options, navigate to Settings > Organization > Supported Languages from the bottom left menu.
-
-
-
-If in case a language supported by Gupshup isn't enabled on Glific, please contact our Support Team for assistance.
-
From 6d7c6aa8a3347ddc326aabbe78f40185b24f984b Mon Sep 17 00:00:00 2001
From: Tejas Mahajan <141305477+mahajantejas@users.noreply.github.com>
Date: Fri, 8 Aug 2025 13:06:13 +0530
Subject: [PATCH 2/5] Delete docs/6. FAQ/Deduction Type of Messages on the
WhatsApp Business Platform.md
removed deduction type page as per issue https://github.com/glific/docs/issues/375
---
...sages on the WhatsApp Business Platform.md | 30 -------------------
1 file changed, 30 deletions(-)
delete mode 100644 docs/6. FAQ/Deduction Type of Messages on the WhatsApp Business Platform.md
diff --git a/docs/6. FAQ/Deduction Type of Messages on the WhatsApp Business Platform.md b/docs/6. FAQ/Deduction Type of Messages on the WhatsApp Business Platform.md
deleted file mode 100644
index 42fda04e1..000000000
--- a/docs/6. FAQ/Deduction Type of Messages on the WhatsApp Business Platform.md
+++ /dev/null
@@ -1,30 +0,0 @@
-### **3 minute read `Beginner`**
-
-
-## Deduction Type of Messages on the WhatsApp Business Platform.
-
-WhatsApp implements a billing model based on conversations rather than individual messages.A conversation refers to a continuous exchange of messages within a 24-hour period between the BOT and the end-user.
-Charges are incurred when messages sent by the BOT are successfully delivered to the end user.
-
-## Conversation Categories
-
-1) **Marketing** — Enables you to achieve a wide range of goals, from generating awareness to driving sales and retargeting customers. Examples include new product, service, or feature announcements, targeted promotions/offers, and cart abandonment reminders.
-
-2) **Utility** — Enables you to follow up on user actions or requests. Examples include opt-in confirmation, order/delivery management (e.g., delivery update); account updates or alerts (e.g., payment reminder); or feedback surveys.
-
-3) **Authentication** — This enables you to authenticate users with one-time passcodes, potentially at multiple steps in the login process (e.g., account verification, account recovery, integrity challenges).
-
-4) **Service** — Enables you to resolve customer inquiries. [Read More](https://developers.facebook.com/docs/whatsapp/pricing#Service%20Conversations)
-
-
-
-`Marketing`,`Utility`, and `Authentication` conversations can only be opened with template messages. `Service' conversations can only be opened with free-form messages. [Read More](https://developers.facebook.com/docs/whatsapp/pricing#opening-conversations)
-
-`UIC`: this is user user-initiated conversation: Whenever the user messages you then this type of conversation starts.
-
-`BIC`: Business initiated conversation: Whenever the business messages the customer/end-user then this type of conversation starts
-
-`FTC`: Free tier conversation [Read More](https://developers.facebook.com/docs/whatsapp/pricing#free-tier-conversations)
-
-
-
From 51ec0d73f5dd7064610d467dd599dffcf1875444 Mon Sep 17 00:00:00 2001
From: Tejas Mahajan <141305477+mahajantejas@users.noreply.github.com>
Date: Fri, 8 Aug 2025 13:06:58 +0530
Subject: [PATCH 3/5] Delete docs/2. Onboarding/05. Pricing, Billing &
Payment.md
removed pricing, billing as per the issue : https://github.com/glific/docs/issues/373
---
.../05. Pricing, Billing & Payment.md | 103 ------------------
1 file changed, 103 deletions(-)
delete mode 100644 docs/2. Onboarding/05. Pricing, Billing & Payment.md
diff --git a/docs/2. Onboarding/05. Pricing, Billing & Payment.md b/docs/2. Onboarding/05. Pricing, Billing & Payment.md
deleted file mode 100644
index 5f1bcc986..000000000
--- a/docs/2. Onboarding/05. Pricing, Billing & Payment.md
+++ /dev/null
@@ -1,103 +0,0 @@
-> ### **3 minute read `Beginner`**
-___
-
-**NGOs can add their billing details from their Glific account. Monthly subscription will be auto debited from Stripe integration in Glific on 1st of every month.**
-
-## Pricing
-
-- There is a monthly fee of INR 9,500 for the platform usage and a one-time setup cost of INR 15,000 for initial consulting/training/customizations.
-
-- The fee covers our operational expenses and platform costs. Messaging costs are additional and will be paid via credit card directly to Gupshup - [click here for Pricing Details](https://glific.org/pricing/). Platform development and enhancement costs are borne by philanthropic funding.
-___
-
-## Add Billing and Card Details.
-
-1. Login to your `Glific account`.
-
-2. Click on the `Settings` icon.
-
-
-
-
-
-3. Click on the `Billing` icon from the left panel.
-
-
-
-
-
-4. Add the details
-
- i) **Your** **Organisation Name** - Your organisation Name which you want on your invoice
-
- ii) **Email** **ID**- Your email address, which will be used for billings communication
-
- iii) **Card Number** - Your Credit Card details
-
-
-
-
-
-5. Click on the `Subscribe for monthly billing`button
-
-
-6. Once done you will see **You have an active subscription** message with a green tick.
-
- 
-
-___
-
-## Edit Billing Details - Card
-
-You can edit your billing details and card details on the Stripe portal
-
-1. Clink on `Visit stripe portal` link at the bottom of the billing page.
-
-
-2. Stripe portal will open up in another tab.
-
-3. Click on `+ Add payment method`
-
-
-
-4. Add the new card details and click on `Add` button
-
-
-
-
-5. Click on `Go back` button and click on `X icon` in front of old card to remove it from stripe portal.
-
-
-___
-## Edit billing details - Email, GST
-
-1. Click on `Update information` link from stripe portal under `Billing information` section.
-
-
-
-2. Enter the `email` address you want to change.
-
-3. Add the `TaxID` if you want to have it on your invoice. Select IND GST from the drop down.
-
-
-
-4. Click on `Save` button
-
-**Note** - To edit the Billing organisation name please contact Glific support team.
-___
-## View / Download invoices.
-
-You can view or download your monthly invoices from stripe portal
-
-1. Find the list of your monthly invoices under `Billing History` sections.
-
-2. Click on `Date` of the invoice.
-
-
-
-3. A new page will open up with invoice and receipt link.
-
-4. Click on `Download invoice` button to download the invoice and Download receipt button to down the receipt of the payment.
-
-
-
From 925ea825e253bd39f52488053ff13646641e3599 Mon Sep 17 00:00:00 2001
From: Tejas Mahajan <141305477+mahajantejas@users.noreply.github.com>
Date: Fri, 8 Aug 2025 13:09:59 +0530
Subject: [PATCH 4/5] Delete docs/3. Pilot Essentials.md
removed pilot essential page as per issue #371
---
docs/3. Pilot Essentials.md | 39 -------------------------------------
1 file changed, 39 deletions(-)
delete mode 100644 docs/3. Pilot Essentials.md
diff --git a/docs/3. Pilot Essentials.md b/docs/3. Pilot Essentials.md
deleted file mode 100644
index 40e690d5b..000000000
--- a/docs/3. Pilot Essentials.md
+++ /dev/null
@@ -1,39 +0,0 @@
-> ### **3 minute read `Beginner`**
-
-Designing chatbots is an iterative process, and with every launch or pilot, you learn new things and make changes. But if you are launching your chatbot for the first time with your users, here are 15 quick things you need to check. It shouldn't take you more than 15 minutes to ensure everything is in order.
-
-Disable the automated opt-in message on Gupshup. This will prevent your users from receiving additional default messages from Gupshup, which might confuse them. To do this, click on your app on Gupshup, go to the Opt-ins tab, click on the Onboarding mechanisms dropdown arrow, and scroll down to disable the toggle.
-
-
-
-The first message that a user receives upon joining the bot should be a consent message. Here are a few guidelines for designing your consent message:
-Clearly mention the name of the organization and the purpose of the bot.
-Clearly ask the user if they would like to receive messages from the bot (You can provide an interactive message with a "Yes" or 👍🏼 button).
-Users should have an option to opt out. Therefore, add the keyword in the footer through which users can opt out from the bot.
-
-
-
-Other pointers to remember-
-It is recommended to have the first message sent by the user to the chatbot, instead of you broadcasting the message to users, even if you have user details. Broadcasting messages might lead to user reporting or blocking the bot, which can affect the overall health of the bot. Unless you have obtained user consent outside the bot (on your app or manually), the first message should always be user-initiated.
-Create a separate flow for users who type "STOP" and add them to a collection for future reference.
-
-3) Update the Opt-in settings post-user consent. It is mandatory to update a contact's settings with Opt-in after their consent.
-
-
-4) Important user information collected during registration, such as Name, Language, Training group, City, etc., should be updated in the contact profile. This will be helpful for you to refer in any flow in future
-
-5) Confirm important information (like Name, Language, etc.) before updating the contact. Sometimes, users might enter incorrect information, which can impact the user experience throughout.
-
-For example, sharing a name as "My name is Krishna Priya" instead of just "Krishna Priya" can lead to the bot referring to the user with the incorrect name every time. Additionally, a user choosing the wrong language preference by mistake might discourage them from using the bot.
-
-6) Set default and new contact flows through Settings → Flows to ensure that new users receive the intended flow.
-7) Add content in all nodes for all languages, if multiple languages are used for the bot.
-8) Add users to relevant collections based on how you want to communicate with them in the future.
-9) Use interactive messages wherever you want the user to choose from given options or when answers are predictable (e.g., grade, Yes/No, Gender, etc.).
-10) If a flow is triggered from your end to the user, the first message of the flow should be an HSM message (because we don't know if the users are in the active session window or not).
-11) Add labels for both outgoing and incoming messages for all the data you want to capture and check in the future.
-12) Use appropriate names for Flows, Keywords, and Result names to make it easy to track them in the future.
-13) Use emoticons, bold, italics, and media as needed.
-14) Ensure the user does not encounter any dead ends in the bot, especially in the case of interactive messages. Make sure there is also an option for the user to send free text apart from the button options you provide, and clarify what the user is expected to do. Connect the user's response back to the main question and wait for their response so the flow can proceed.
-
-15) Testing, Testing, Testing: Test the chatbot internally with at least 3 to 5 people on mobile phones before sharing it with actual users.
From 8d7beca54cb10d4a6795dd25f735b6f8eb71271e Mon Sep 17 00:00:00 2001
From: Tejas Mahajan <141305477+mahajantejas@users.noreply.github.com>
Date: Fri, 8 Aug 2025 13:10:52 +0530
Subject: [PATCH 5/5] Delete docs/6. FAQ/14. Get upload attachment option in
Send message.md
removed the upload attachemnt page as per #369
---
...4. Get upload attachment option in Send message.md | 11 -----------
1 file changed, 11 deletions(-)
delete mode 100644 docs/6. FAQ/14. Get upload attachment option in Send message.md
diff --git a/docs/6. FAQ/14. Get upload attachment option in Send message.md b/docs/6. FAQ/14. Get upload attachment option in Send message.md
deleted file mode 100644
index dc858b890..000000000
--- a/docs/6. FAQ/14. Get upload attachment option in Send message.md
+++ /dev/null
@@ -1,11 +0,0 @@
-To get **upload attachment** option, one needs to setup GCS and make it active in Glific.
-
-### **Upload Attachment**
-
-
-
-
-
-### **Activate GCS in Glific**
-
-