Chatbot lucy Icon

Build with Gupshup and get your .BOT identity faster.

New and existing customers of Gupshup now get faster access to their own .BOT domain name, letting you secure your .BOT identity and focus on building your bot.

Get a .bot domain

During Limited Registration Period 2 ("LRP2"), eligibility to register a .BOT LRP Domain Name is restricted to individuals or entities that own, operate or manage bots built using supported bot builders, as validated on AmazonRegistry.com.

Frequently Asked Questions

[1-2 line subtitle goes here]
[Body (copy or images) goes here]
.BOT is a new generic top-level domain (gTLD) from Amazon Registry Services that brands and developers can use to provide an identity and hub for their chatbots!

Yes, you can have .BOT domain for any of your bots published on these channels -

  • FB Messenger
  • Twitter
  • Hangouts Chat
  • Telegram ­
  • Skype
  • Line
  • Twilio
  • Slack

The pre-requisite is to have a bot on gupshup platform. You can use any of our developer or non-developer tools to create one. Hover on Dashboard > click on My Bots and choose your preferred method for bot creation.
Validation is the process of proving you have access rights to the bot you are using to meet validation requirements. This allows us to keep the .BOT Top Level Domain for bots and retain the domain as a community. Validation associates your bot to a specific validation token if successful. The token is then used to register a .BOT domain name.
No, there will be only one-to-one unique relationship.
As chatbots proliferate and mobile app downloads continue to decline, .BOT is poised to become for the web what Google and Apple's app stores were for apps — for bots! In addition, a .BOT domain name acts like a permanent address where your customers can find you, no matter what framework or platform you use today or tomorrow.
Amazon Registry has direct links with Gupshup and Pandorabots, but is able to validate through direct connections or manually any live bot.

[Section title goes here]

[Body (copy or images) goes here]

Why get a .BOT domain?

Identity Icon

Identity

Showcase your published bot with your .BOT domain name across multiple channels.

Stand out Icon

Stand out

Use your .BOT identity to tell the world about your bot without getting lost in the noise.

Discovery Icon

Discovery

.BOT is about bots. Use your .BOT identity to drive engagement with your users.

Join the bot community today!

Get a .bot domain

© Copyright 2018, Amazon Registry Services, Inc. Amazon, Amazon Registry, and the .BOT logo are trademarks of Amazon.com, Inc. or its affiliates.
Gupshup privacy policy


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