updates updates

๐Ÿš€ v2.6.4: Twilio Flex, Typing Indicators,

โœจ What's new

  1. Twilio Flex contact center integration (docs)
  2. Typing indicators for Orb and customer support integrations (docs)
  3. NLU integration (docs)
  4. Improved timeouts for APIs like Zendesk Support
  5. Improved app list view in Console
  6. Other miscellaneous bug fixes, performance and usability improvements

๐Ÿ‘ฉ๐Ÿฝโ€๐Ÿ’ป๐Ÿ”€ Twilio Flex

  • Setup guide
  • Example code
  • Seamless integration w/ complete messaging features
  • Identity: user, agent, bot names and avatars /w attribution
  • Task router: tasks, workers, task queues and more
  • Bi-directional text, media, attachments
  • Agent "slash" commands
  • Lifecycle events: start, end session that can hook into BFML

2b6c7aa-flex.gif image.png image.png

๐Ÿ”ฎ๐Ÿ’ฌ Typing Indicators

  • Guide
  • Example code
  • User, bot, agent typing indicators
  • Works with Orb, Web v1, Sunshine Conversations, Salesforce Live Agent and Zendesk Chat
  • Complete on/off control within BFML

9ad36d6-typing.gif image.png


  • Guide
  • Example code
  • Suite of triggers and components needed to add NLU to your bot
  • Multilingual support including Arabic (missing from Dialogflow)
  • Intent and entity extraction
  • Complete payloads for advanced use-cases

93f25b8-wit_intro.gif image.png image.png

๐Ÿš€ v2.6.2: Data Collection + Invites

โœจ What's new

  1. Data Collection for Orb (and Web v1) w/ fine-grained control
  2. Self-serve team member invites w/ improved permissions
  3. Support for NoteEvent sent to Customer Service Platforms (CSP): Zendesk, Front, Salesforce, etc.
  4. Improved docs:
  5. Change log in console w/ notifications of updates
  6. Misc. bug fixes and minor improvements

๐Ÿ—บ Data collection

  • Docs
  • Example code
  • Collect rich location data (city, country, lat/lng, timezone, etc.) powered by IPStack
  • Custom page context
  • Fine-grained control on what data is collected and where it is stored
  • Send data to user, thread or event scope
  • Treat collected data as sensitive



โœ‰๏ธ Team member invites


๐Ÿš€ v2.6.1: Vault + Shopify

โœจ What's new

  1. Vault UI in the console
  2. New Shopify integration
  3. Bug fixes and misc. improvements

๐Ÿ” Vault (new to Console)

  • Added Vault UI to the Console
  • Previously only supported via CLI meya vault upload|download|view
  • Observed teams permissions on vault read/write access. Allows for production app keys to be restricted to select teams
  • Team permissions also observed by CLI commands
  • Automatically populate Vault using vault.yaml in git repos when creating an app from template


๐Ÿ› Shopify

  • Authenticate users automatically on Shopify Store
  • List and get order status
  • Cancel, refund update shipping address orders
  • List and get products
  • More API calls supported, with more on the way



๐Ÿš€ v2.6.0: Sensitive Data + Twilio Voice

Meya is excited to launch v2.6 of the platform.

โœจWhat's new

We've included many new features with this release. A major highlight is the innovative approach we're taking to handle user's sensitive data that strikes a balance between privacy and utility. This is particularly important as conversational AI hits the mainstream.

Sensitive Data ๐Ÿ†•

  • automatically encrypt and decrypt sensitive user data
  • new Python encrypt and decrypt APIs
  • limit access to sensitive data in Console to privileged team members
  • Enabled using a new "Sensitive Data" integration (default off)
  • Automatically encrypt all media (images, files, etc.)
  • Automatically encrypt http and ws data. Protects auth tokens, etc.
  • Expire sensitive data after 24 hours


Usage and Metering

  • New graphs
  • New billing system for counting MAU


Zendesk Support Improvements

  • Support "On-hold" ticket status
  • Fix system user bug (current_user_id: -1)


Twilio Voice Integration ๐Ÿ†•

  • accept inbound voice calls
  • make outbound calls



  • Default to connect: false with Orb snippet
  • Fix Console BFML validation
  • Don't auto-create integration when clicking Add in Console
  • Hide user token in profile view
  • Support optional integration_id in Webhook payload
  • Improvements to meya push to tie more accurately into deployment readiness
  • Other bug fixes and minor improvements

New Twitter agent pause/unpause settings

We just released a new set of features that allow for more advance human/bot hybrid control of your Meya bot/assistant that's connected to Twitter.

โœจWhat's new:

  • support pause and timeout on human.transfer
  • support of auto-unpause on agent message that matches a regex

๐Ÿค–Existing functionality:

As a reminder what we previously support

  • support auto-pause on agent messages
  • auto-unpause on agent inactivity

Putting the new and old together your support agent have almost complete control over the bot/assistant.

  1. bot to human escalation
  2. human from bot take control
  3. human to bot pass control

Example human.transfer

        component: human.transfer
            text: "One moment while I transfer you to a live agent..."
            timeout: 10
            timeout_flow: bot

See it in action

twitter pause.gif

New settings

Screen Shot 2018-11-24 at 6.56.32 PM.png

๐Ÿš€ Features, fixes and improvements

1. DialogFlow v2 API support

  • new meya.dialogflow component
  • new dialogflow trigger
  • connect via Google OAuth as a separate integration
  • use project-id rather than api key in BFML
  • support new v2 features from DialogFlow
  • reuse same agent for multiple languages with Bot CMS
  • v1 API available using meya.api_ai component and api_ai trigger

2. Salesforce Live Agent fixes

  • handover timeout issues affecting some customers
  • other minor fixes and improvements

3. Comapi integration

  • connect your Meya bot to any of Comapi's messaging channels
  • includes: SMS, Facebook Messenger, web live chat
  • learn more:

4. Deprecate use of name field in BFML

What is affected: The required name key at the root of all BFML files is being deprecated, and should be removed from BFML. Instead, the name of the flow file itself will be set either by the UI in web dev mode or the filename in local dev mode. Note: If the name is included in BFML your bot will not break, but the name observed by nested flows, API, etc will come from the explicit name field (or filename in the case of local dev mode).

Who is affected: All bot builders in a minor way. Once the change is released, it will be recommended that developers cease to use name in new flows and remove name from old flows. It is redundant, and while it is backwards compatible, it will be ignored once a flow name is set and could result in developer confusion.


5. Limit meya.schedule to a max of 100 iterations

What is affected: In the past we have allowed for unlimited flow iterations invoked as part of meya.schedule. We will now set a default limit of the max_count to 100. Any existing flow loops running will terminate on next invocation greater than 100.

Who is affected: Anyone using meya.schedule component with max_count > 100 (or not set).


6. Other miscellaneous changes

  • increase API rate limit on meya-cli to prevent sync issues
  • fixed logging write latency issue
  • support read/delivery events from Smooch integrations

Change notice: empty strings in bot db

We'd like to notify you of a minor improvement to the core Meya platform that will be released June 20th, 2018 that may affect your development:

Correct unexpected bot database behavior for setting and getting empty strings

What is affected: Originally, due to limitations of our underlying data store, empty strings were converted to null values in bot database storage, such as flow scope data and user scope data. The subsequent read operation would return a null value rather than an empty string as you would expect. For example, self.db.flow.set("foo", "") would result in null values being returned on the next read. Specifically, self.db.flow.get("foo")would return None. We are revisiting this behaviour as a part of our ongoing effort to increase consistency and cohesion in the Meya platform, and will be supporting empty strings going forward.

Who is affected: Anyone writing empty strings to bot database and then expecting a null to be returned when read may be affected. While this was unintuitive behavior, certain cases could cause developers to create Python code or BFML that only works with the old behavior. For example, if self.db.flow.get("foo") is not None: will begin returning false. The recommend fix is to write the statement as if self.db.flow.get("foo"):. As well, in BFML, some values that previously resolved to None will now resolve to an empty string.


May 28th/2018 Release Notes

Our latest release to the Meya platform includes the following changes:

  • To expand on our multi-lingual bot development support we incorporated language detection on catchall and api_ai triggers, as well as api_ai and meya.input_string components. This enables our developers to centralize multi-lingual NLU training and configuration in a single agent.
  • To enable additional processing and data capture of DialogFLow responses we added support for the DialogFlow fullfillment webhooks feature.
  • To simplify GDPR requests Meya customers can now find their account id published in their profile page.
  • Misc. bug fixes and minor improvements.

GDPR update

In order to adhere to the General Data Protection Regulation (GDPR), coming into effect May 25, 2018, we have updated our Privacy Policy and Terms and Conditions.

We value our customers and their user's privacy choices and have taken steps to ensure we are giving you the tools needed to make yourselves fully compliant while using

In addition to the new Privacy Policy and updated Terms and Conditions, we have also taken the following steps:

  • Weโ€™ve assigned a new DPO whom you can reach at
  • We offer digitally countersigned Data Processing Agreements (DPAs) upon request
  • Provided mechanisms for you to honor your user's privacy choices such as "Request for access" and "Request for erasure"

We encourage you to read our new GDPR page which outlines how these changes will affect customers and their users.

Local dev mode + Meya CLI ๐Ÿš€

  • Bring your own text editor Develop on your local workstation with your favourite editor (Sublime, VS Code, Atom, Vim)
  • Keep multiple files open and search across your entire project
  • Manage bot source with your preferred source control system (ex. Gitlab, Bitbucket)
  • Integrate CI/CD workflows & tools (ex. Jenkins, CodeShip)
  • Snippets: quickly access many common bot building blocks, with embedded documentation and examples
  • Improved logging: real-time tailing, searchable, more detail
  • Automatic syncing: code locally with all code uploading to Meya platform in real-time
  • Read the docs -
  • pip install meya