WhatsApp ISV registration policy

What it means for Gupshup ISV partners

Firstly thank you so much for faith and patience in us. It is great to see you and your clients on our platform. Your suggestion and feedback help us immensely. We are constantly upgrading ourselves to ensure we can provide you the best services available.

The last couple of weeks - Gupshup has worked with WhatsApp closely to understand their new ISV registration policy and how that effects our partners/ customers on the platform. After going through the process, we are now happy to share that WhatsApp has opened up the Client ISV mechanism to ensure partners with dierent needs and solutions can all work on the same platform.

What was the story so far:

The Independent ISV mechanism
  1. The Gupshup account must be owned and operated by the end client
  2. As a consequence of 1, each client must have a separate Gupshup account
  3. Billing relationship is between Gupshup and end client
  4. Separate invoices for WhatsApp / Gupshup messaging fees and Client ISV services
  5. Full billing transparency regarding WhatsApp messaging fees and Gupshup messaging fees
  6. Payment mechanism for end client are those oered by Gupshup

Now, WhatsApp has provided more clarity on Client ISVs and hence Gupshup is oering ISVs an option to become Client ISVs

Client ISVs
  1. The Gupshup account may be owned and operated by the Client ISVs
  2. Multiple clients may be operated from the same Gupshup account
  3. Billing relationship may be between Gupshup and Client ISV on one hand and between Client ISV and end client on the other
  4. Client ISV can have consolidated invoice for WhatsApp / Gupshup messaging fees and Client ISV services
  5. Full billing transparency regarding WhatsApp messaging fees and Gupshup messaging fees
  6. Payment mechanism for end client is whatever the Client ISV supports
Steps to become Client ISVs
  1. Express interest to Gupshup and provide details
  2. Gupshup forwards details to WhatsApp and requests approval
  3. WhatsApp provides approval
  4. Client ISV signs additional terms with Gupshup
  5. Client signs additional terms with Client ISVs
If you are an Independent ISV and wish to continue to do so -
  • Please ensure that the Gupshup account is owned by the client
If you want to become a Client ISV then you can continue to do so -
  • Please follow the above steps
  • We will help you with the WA registration process and signing of WhatsApp addendum
  • You will need to ensure that all your clients sign additional terms given by WhatsApp
If you are working on a Hybrid model and wish to continue to do so -
  • Please ensure that you register as Client ISV with WA
  • Register those clients that are on a billing relationship with you with WA and get them to sign additional terms given by WhatsApp
How does registration benefit you?

We have been getting a lot of feedback that our partners would like to manage their customers end-to-end. They do not want their customers to go through the registration process, billing hassles etc. ISVs rather manage all these processes themselves and do a package billing for their customers. Well! Now you can. As long as the WA and GS component is mentioned clearly in the billing invoice, you can go ahead and manage your customers – ALL from a common account. We highly recommend that you go ahead with the registration process. This will help you cater to all kinds of customers

We are now circulating our form to gather ISV information again. Those who wish to join the registration program – please fill in your and your client details. The last date to do the same is - 25th August. Please find the form here

We will reach out to our ISV partners separately who have passed the first level of registration with the Addendum and for onward signing of terms from their respective clients. Stay tuned!

Always at your service

Team Gupshup

Please wait

Added below language support for WhatsApp,

Bot developers for Line: With the release of Line Messaging API, all BOT API Trial Accounts are scheduled to be deleted. Please republish your bot according to new Line implementation, mentioned under Publish tab in My Bots section.

New tool for non-developers- Our Flow Bot Builder helps users create their bot messaging flow with a graphical editor.

API.ai tool is now available for developing your NLP/AI bot.

Gupshup Enterprise APIs (SMS,Voice and Email) are now available directly in the APIs section.

New channels added for publishing bots- Smooch.io and your website as a web widget.

Now you can access our services including the bot builder tool using your Facebook login credentials.

Now you can delete the dummy bots created for testing from the My Bots Dashboard.

You can now access Bot specific data from your Dashboard itself.

Introducing a hassle free bot development experience for users to instantly create bots using our pre-defined restaurant templates. Check out our blog to know more.

We are removing few redundant parameters, that were being sent when a callback happens to your bot (i.e. inbound message comes to your bot).

Following is the list of parameters.

  1. sender
  2. message
  3. context

However, we will continue to send following parameters. If you are using any of the deprecated parameters, we request you to use these alternatives.

  1. senderobj
  2. messageobj
  3. contextobj

You are requested to make a note of this and do the necessary changes immediately to your bot code to keep it working. Should you need any help, please feel free to send an email to devsupport@gupshup.io