Pricing

If you’re using our REST API and you don’t have a userID because your user is anonymous, we recommend that you generate your own randomized ids using something like UUID (link resides outside IBM). If you’re using web chat and a user doesn’t have an identifier provided by you, we will generate one for your user and cookie them with the anonymous identifier in the event that they return to your site later in the month. That way you’ll only be charged once for that user.

A message that your user sent into your assistant that received a response is a meaningful interaction. Welcome messages at the beginning of a new conversation are not charged.

If messages are sent with two different userIDs then yes, you will be charged twice. We recommend either prompting users to login prior to initiating a chat or using the anonymous value for that user throughout all of their sessions.

If you’re using our REST API or web chat integrations, you need to provide us with a unique identifier (created by you) for each user that interacts with your assistant. We recommend a non-human identifiable database ID (i.e. a GUID) that doesn’t change throughout your customer lifecycle. If you’re using our Facebook, Slack or Intercom integrations, we pull the user ID from these sources automatically.

We will charge based on the session identifier automatically, meaning that if this user returns a second time within the month after their session expires, they will be treated as two MAUs.

Watson Assistant currently supports 13 languages and 1 in beta. However, support coverage differs from feature to feature. For a detailed view of the product’s support coverage by feature, go here.