You are on page 1of 2

Plus!

Engage Review
Objectives:
1) Have an alignment of what PE is supposed / not supposed to be: a campaign management platform, and not a CRM / loyalty management platform
1) Benchmark PE against industry competitors
2) Perform evaluation on PE, decide if Banyan / T should use PE as a marketing + comms platform

Feature / Requirement Details Does PE have this? If NO, can PE be developed to If YES, what are its Pros / Cons Can external platforms solve this Industry Benchmark
include this? better than an internal platform?

A) Plus: 1 EDM per day, 3 EDMs per


week. PARTIAL YES.
A & C are available. B is not PROS: We have full flexibility to Probably yes. Many platforms in
Contact policy B) FP EDMs are subject to a separate available but not necessary at this N/A customise it whenever we need market have contact policy
enforcement contact policy of 1 EDM per day
C) Contact policy exceptions for certain point as FP enforces this on their to management tools.
end.
types of comms (e.g. service fulfillment)

Yes, according to Diwan. While


PARTIAL YES.
Biz rules/algorithms that determine the The existing rules have not caught PROS: We have full flexibility to this is a fairly bespoke business
Contact policy audiences allocated to all campaigns N/A customize it requirement, the back-end rules
optimization within a given day/week so that contact up with new business CONS: The business rules are still involved are not that complex and
requirements. There is an ongoing
policy is abided task force to update the rules. fundamentally "manual" market platforms may have the
ability to to offer similar features.

No, but a simple workaround is to


YES. Several segmentation PROS: Since we own the platform
Ability to segment audiences within features are available. Pipeline of we have full flexibility to build a separate front-end tool to
Segmentation & signals platform using pre-defined filter/criteria, N/A generate segmentation lists and
or via uploading a member list new signals are in roadmap customise it however & whenever upload the lists into the external
awaiting implementation we want. Generally easy to use.
platform.

Integration with loyalty User can set up bonus promo rules in Not available. The feature front Moving forward this feature may Probably not. This is a bespoke
end was enabled in PE in Oct, but continue to sit within loyalty N/A
platform to automate platform while setting up campaign, due to a bug it was never used platform instead of campaign requirement unique to our
points promotions setup avoiding SRs and Ops manual setup business
since. platform

Maybe. Our reporting


Partially. An MVP version exists requirements can be quite unique
but there are some critical issues CONS: currently buggy and not as they include sales performance
Post-campaign reporting Display campaign performance & stats in with UI, data integrity & usability YES widely adopted. See comments (e.g. conversion rate, uplift) not
a dashboard
pending fixing. Most AMs/MMs on left. just campaign comms
are not using the dashboard. performance (e.g. open/click
rates.

NO. There exist several gaps in


Data on merchant/consumer this area and much of campaign
performance data is not being fed Probably not. This is a bespoke
Data analytics attributes/behaviours for campaigns back to database to contribute to YES N/A requirement unique to our
must be fed back to LAC database to
contribute to wealth of data insights analytical insights. Some gaps are business
being identified and address but
progress tracking is slow.
Plus! Engage Review
Objectives:
1) Have an alignment of what PE is supposed / not supposed to be: a campaign management platform, and not a CRM / loyalty management platform
1) Benchmark PE against industry competitors
2) Perform evaluation on PE, decide if Banyan / T should use PE as a marketing + comms platform

Feature / Requirement Details Does PE have this? If NO, can PE be developed to If YES, what are its Pros / Cons Can external platforms solve this Industry Benchmark
include this? better than an internal platform?

Memberson, Antavo,
Advocado, Capillary,
Boxever, Emarsys

What marketing channels does the YES. Other channels are in


Only single channel (EDM) has Yes. It's a fairly hygiene feature
Channel enablement platform allow us to manage/run NO. PE only has EDM channel. roadmap: SMS, mobile app (push been enabled so far for most platforms in market.
campaigns on? & in-app), CMS, social media

Platform automatically & intelligently


decides a member should receive YES, but it's not in roadmap.
Omni-channel / Channel Yes. It's a fairly hygiene feature
optimization campaign comms from which channel(s) NO. Multi-channel enablement (see N/A for most platforms in market.
audiences, based on member's known above) needs to be rolled out first
channel preferences

Features that make it efficient for PROS: Quick to use for basic Maybe - this depends on how
Marketing to create and launch YES, insofar as basic features are straightforward execution unique our campaign operational
delivered. Additional features to
Facilitate the creation & campaigns, e.g. campaign calendar, facilitate automation & scaling are YES, on the roadmap CONS: Very inflexible features. As requirements are. Certain
execution of campaigns campaign T&Cs, audience utilisation an MVP, many features require elements like audience utilisation
forecast, execution status, approvals, not yet available, though some "creative workarounds" on the forecast, integrating promotion
are in the roadmap.
etc. part of end users setup etc. are quite bespoke.

PROS: Very easy to use


Trigger-based campaign funnels based CONS: No built-in "drip contact
Drip marketing / on user actions (i.e. YES for drip YES, canvas is on roadmap policy limit" to manage/prevent Yes. It's a fairly hygiene feature
Marketing canvas NO for canvas fore most platforms in market.
opens/clicks/conversions) members from being over-
contacted with drip comms

MAYBE. The existing Caltex trigger


engine and in-progress MOB
engine are actually built &
Automated campaigns based on more enabled by tech back-end; they Maybe - this is a more
CONS: Not a "real" platform
Advanced automated / advanced triggers/data signals, e.g. are not platform features. YES, on the roadmap feature as everything is enabled advanced/niche feature and may
trigger-based campaigns customer lifecycle funnel, Caltex trigger require procuring specialised
engine, member birthday delights We want the platform to have back end by tech platforms.
generic features to allow us to set
up automated/trigger campaigns
as & when we need to.

Set up A/B or multivariate tests, then


A/B or multivariate assign remaining audiences to the NO. Not in roadmap. YES N/A Yes. It's a fairly hygiene feature
testing for most platforms in market.
winning version

NO. PE can store pre-coded HTML


templates, but it cannot allow CONS: Highly inflexible. We're
Content: EDM templates Flexibility to create, adapt templates user to adapt layout on a YES, on the roadmap confined to whatever is coded in Yes. It's a fairly hygiene feature
that are optimised for performance WYSIWYG layout editor. Even the the HTML templates and cannot for most platforms in market.
current layout editor is difficult to modify layout easily.
use

How response & effective can vendor Partially. Mailjet's support is slow
according to user feedback, as
support us when there are technical Mailjet is not based in SG. Could Yes. Some platforms will have SG-
Vendor support issues. (note: PE runs on Mailjet back- N/A N/A
end which is still a 3rd-party email take days for issues affecting based local support.
business processes to be
delivery platform) investigated & resolved.

You might also like