Press Center

Logo

logo type1
logo type2
logo type3
logo type4

Teamchat Screenshots

Home

Home

Conversation

Conversation

Conversation 1

Conversation

Standards chatlets

Standard Chatlets

replies_on_chatlet

Replies on chatlet

Teamchat - Product Tour

Product Tour 1

Screen 1

Product Tour 2

Screen 2

Product Tour 3

Screen 3

Product Tour 4

Screen 4

Product Tour 5

Screen 5

Product Tour 6

Screen 6

Collages

Chatlet

Anatomy of a Chatlet

Infographics

Infographics

Enterprise messaging with- Popular Apps vs Teamchat

Infographics

Drowning in Message Clutter?

Infographics

E Pluribus Unum

Infographics

When Messaging Gets Smarter

Infographics

Evolution of Messaging

Infographics

Teamchat vs Other Messaging Apps

Infographics

Social Shopping through Smart Messaging

Fliers

Infographics

Leading Messaging Platform

Infographics

Omni Channel Messaging Bots

Infographics

Messaging Bots and Workflows

Infographics

Omni Channel

Infographics

Bot Store

Infographics

Chat Messaging

Infographics

Downing

Infographics

Embed SDK and Bot SDK

Infographics

IOT2

Infographics

Social Shopping

Infographics

Future of work flyer

Infographics

Chat Messaging

Infographics

Chat based commerce

Infographics

Smart SMS

Infographics

Smart Messaging Platform

Infographics

API and SDK

Infographics

API

Standees

Standees

Leading Messaging Platform

Standees

Omni Channel Messaging Bots

Standees

Messaging Bots and Workflows

Standees

Omni Channel

Standees

IoT2

Standees

Nagios

Standees

Paradigm Shift

Standees

Social Shopping

Standees

Teamchat vs Other Apps

Standees

Techcrunch

Standees

Future of Work

Standees

Chat based commerce

Standees

Smart Messaging Platform

Standees

API

Standees

IoT

For PR and content inquiries, please contact:

Richard Laermer
RLM PR
gupshup@RLMpr.com
+1-212-471-5004
OR
Email to: pr@gupshup.io

{Processing}

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 support@gupshup.io