Update Deployteq Roadmap H2 2023

In February, we gave you insight into the roadmap for 2023. We are now six months down the line, so it is high time for an update!

Looking back over the past six months

In the first half of the year, we released four major projects:

• The MFA obligation has been rolled out seamlessly. The cooperation with our partners in this was a great experience; everyone immediately recognised the benefits, and customers were well informed. The platform is now much more secure, thanks to everyone’s efforts!
• Transactional pool.  The transactional pool sends your customers’ communication with a dedicated reputation through a priority lane. The result? Messages land in the primary inbox at an expedited rate. No additional licenses apply for this, only an adjusted CPM rate of € 2.00. NEW: Especially for our partners, we have reduced this CPM by 15%, which amounts to € 1.70 per 1,000 messages sent. Meaning you can make a profit margin on this without exceeding our price.
• Analytics Events API.Thanks to this new module, there is now an accessible way to extract real-time user data from Deployteq. Ideal for powering dashboards, much more flexible and cost-effective than the old EBE exports!
• Broadcast archive improvements. The process we use for archiving messages, which is often used by large insurers, for example, has been improved. This is now arranged alongside, making it less disruptive to the performance of the sending process. With this change, we have improved the process and laid the groundwork for implementing a similar improvement in more Deployteq processes.

In addition to this, various small extras have been released, which you can find in the release notes.

What’s next?

Some items scheduled for the first half of this year have taken a little longer than expected, so a few parts of the roadmap have been delayed:

• WhatsApp Business: is currently first prior on the roadmap for the immediate future, expected to be released this summer (before September 2023!). The pricing is published but subject to change; see the price list here. In addition to a slight delay in the planning, the design has changed slightly. Where we planned to work through the interface of an intermediary partner, it has recently come to light that templates will soon be created in Meta’s own environment. A big improvement, but it also means some rework. Watch this space for more news on WhatsApp!
• We also said we would be working on a new way of assigning roles and rights, primarily at the brand level instead of the portal level, and adding ACL, with which you can grant or deny access to users at the folder level. Unfortunately, this has been halted for a while, but we expect to be able to continue with this from Q4.
• Analytics and reporting improvements. In the background, many things are being transferred to a new backend: from the old reports cluster to the new Clickhouse / Kubernetes platform. An extensive operation, but bit by bit, improve performance (speed and accuracy). Development of the new Reports front-end will follow immediately after this, and we expect to be able to deliver it in the autumn. Four functionalities are added to analytics:
  • Dashboard sharing
  • Copy widgets
  • Compare results with those of another period
  • Define KPIs and display them on a dashboard

Adjustments

Due to market developments, we must be flexible and change course on the odd occasion. A key topic at the moment is the scalability and longevity of our data model. This is a unique feature in our market which we introduced in 2015.

Our customers and partners are innovative in their use (and sometimes creative abuse? ;-)) of this functionality for all kinds of tasks. To continue to guarantee the performance of this model, we will be working on a “next-generation data model” based on the current architecture in the second half of this year.

A large package, delaying a number of other elements on the roadmap:

• Increasing the data model import speed: moved to release end of Q4. We tackle this as part of a larger ‘performance cluster’, in which we also improve the campaign event architecture (uses and speed at which the individual events within campaigns are handled).
• Usability, UI and UX have been postponed until further notice. We want to prioritise focusing on performance and completing items that have been on the roadmap for some time but have been under pressure for various reasons.

Finally, a nice piece of news: a community manager will start on 01.09.2023. Our new recruit will focus on improving the manual, release notes, feature voting and many more useful pieces of content for Deployteq users.