Marketing Automation & Customer Journeys for Dynamics 365

核心功能

Visual journey/workflow designer page — chain multi-step nurture flows with wait timers, branch conditions and exit rules, all inside the Business Central client

Multi-channel steps: email via the BC email account/SMTP, plus SMS and WhatsApp through your gateway (e.g. Twilio) called from AL HttpClient

Behavior-based triggers driven by event subscribers (OnAfterInsert / OnAfterModify) on Contact, Customer, lead and opportunity records

Field-based triggers — enroll or advance contacts when a field changes (stage, country, industry, tag, custom flag)

Lead scoring and grading model that increments on opens, clicks, replies and field activity, written back to the contact record

Live segmentation engine running filtered queries over your CRM tables — segments stay current with no manual export

Job queue entries that evaluate enrollments and wait conditions on a schedule for hands-off, automatic progression

New AL tables for journeys, journey steps, enrollments and a per-message send/delivery log for full auditability

Table and page extensions that surface journey status and scores directly on the Contact and Customer cards

Dedicated permission sets separating marketer (design/run) from admin (gateway config) and read-only roles

OData / REST API endpoints exposing journeys and enrollments for Power Platform, Power BI and Dataverse integration

Deployed as a per-tenant extension — isolated to your tenant, upgradeable, and removable without touching base BC tables

按需定制，全程代劳

无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。

您下单

以一次性构建价格开始。我们在启动时与您共同确定范围。

我们构建与安装

ECOSIRE 在您的 Dynamics 365 Business Central 上构建、配置并安装。

上线 + 支持

约 2–4 周内上线，并提供上线后的支持期。

关于此产品

Affordable automation on top of Dynamics 365 — without Customer Insights licensing

Full Customer Insights – Journeys licensing is expensive and overkill if your contacts, leads and sales data already live in Dynamics 365 Business Central. Marketing Automation & Customer Journeys is a per-tenant AL extension that puts a trigger-based nurture engine directly inside your BC environment, so marketers can build multi-step journeys across email, SMS and WhatsApp against the CRM data they already own.

This is built-to-order, not an instant AppSource download. ECOSIRE develops the extension to your tenant's requirements, deploys it as a per-tenant extension (not a published AppSource app), and supports it on your environment. We do not claim a one-click marketplace install.

What it does

The extension adds table and page extensions to Contact, Customer and the lead/opportunity records, plus new tables for journeys, journey steps, enrollments, and message logs. A visual journey designer page lets marketers chain steps with wait conditions and branch logic. Event subscribers (e.g. OnAfterInsertEvent / OnAfterModifyEvent) and job queue entries evaluate behavior-based and field-based triggers, advancing enrolled contacts on schedule.

Outbound sends route through SMTP / the Business Central email account for email, and through your chosen SMS and WhatsApp Business gateway (e.g. Twilio) called via the AL HttpClient. Inbound engagement (opens, clicks, replies) feeds the lead scoring and grading model. A segmentation engine runs filtered queries over your CRM tables so a segment is always live, never a stale export.

Everything is governed by dedicated permission sets, and a clean OData / REST API surface exposes journeys and enrollments to Power Platform / Dataverse for dashboards or hand-offs. Pricing is a one-time build fee of USD 499; ongoing channel costs (your SMS/WhatsApp gateway) are billed by that provider directly.

你得到什么

Signed per-tenant Business Central AL extension (.app) built to your requirements and installed on your sandbox then production environment

Visual journey designer plus journey, step, enrollment and message-log tables wired to your Contact/Customer/lead records

Configured email channel (BC email account/SMTP) and integration to your SMS/WhatsApp gateway with your credentials stored securely

Lead scoring/grading rules and an initial set of segments configured against your actual CRM fields

Permission sets assigned to marketer, admin and read-only roles per your security model

Job queue setup for automatic enrollment evaluation, plus a documented OData endpoint for Power BI/Dataverse

Source code, deployment notes, an admin/marketer runbook and a working-session handover with your team

这是给谁的

Marketing Manager on D365 Sales

Wants trigger-based nurture across email and SMS but can't justify full Customer Insights – Journeys licensing for the contact volume they run.

Business Central Administrator

Needs automation delivered as a governed per-tenant extension with proper permission sets and job queue, not ungoverned scripts or third-party data exports.

RevOps / Sales Operations Lead

Wants lead scoring and live segments computed on the CRM data of record so sales sees scores on the contact card and dashboards stay in sync via OData.

Marketing Automation & Customer Journeys for Dynamics 365 如何比较

标准	伊科西尔	定制建造	竞争对手
Trigger-based multi-step journeys across email + SMS + WhatsApp	包含	部分支持	部分支持
Runs without Customer Insights / D365 Marketing licensing	包含	包含	部分支持
Live segmentation on your own BC CRM tables (no export)	包含	部分支持	部分支持
Built, installed and supported by ECOSIRE on your tenant	包含	不包括在内	不包括在内
Tailored to your fields, triggers and scoring rules	包含	包含	不包括在内
Delivered as a governed per-tenant AL extension (permission sets, job queue)	包含	部分支持	包含
Lead scoring/grading written back to the contact record	包含	部分支持	部分支持
OData/REST surface for Power BI & Dataverse integration	包含	部分支持	部分支持

关于Marketing Automation & Customer Journeys for Dynamics 365的常见问题

How long until it's live, and how is it delivered?

Typical delivery is about 3 to 5 weeks from requirements sign-off, depending on the number of journeys, channels and the complexity of your trigger and scoring rules. We build the extension, deploy it to your sandbox for UAT, then install it on production as a per-tenant extension. This is a build-to-order engagement — there is no instant Microsoft AppSource download; ECOSIRE builds, installs and configures it on your tenant.

Who handles ongoing support and updates after go-live?

ECOSIRE supports the extension on your environment. Because it is a per-tenant extension it upgrades cleanly alongside Business Central's monthly and major-version updates; we recompile and re-test against new BC releases as part of an optional support retainer. Bug fixes within the agreed warranty window are included; new journeys, channels or scoring logic are scoped as change requests.

Do I need a Customer Insights or Dynamics 365 Marketing license?

No. The whole point of this extension is to run trigger-based journeys on top of your existing Business Central (and optionally D365 Sales) data without Customer Insights – Journeys licensing. You will need your own SMS/WhatsApp gateway account (for example Twilio) for those channels, billed by that provider.

How are SMS and WhatsApp messages actually sent?

Email uses your Business Central email account over SMTP. SMS and WhatsApp are sent by calling your chosen gateway's REST API from AL using HttpClient — Twilio is the common choice, but we can integrate the provider you already use. Credentials are stored securely and access is restricted via permission sets. Per-message provider charges are billed to you by the gateway.

Will this interfere with Business Central upgrades or my base data?

No. It ships as a per-tenant extension using table and page extensions and event subscribers — it never modifies base Business Central tables. It can be uninstalled cleanly, and it is built to Microsoft's AL extensibility model so it survives platform upgrades. We re-validate it against each major BC release.

Can the journey and scoring data feed Power BI or Power Platform?

Yes. Journeys, enrollments and message logs are exposed through Business Central's OData/REST API, so you can build Power BI dashboards or connect via Dataverse to the broader Power Platform. Lead scores are also written back to the contact record so they appear directly on the Contact and Customer cards.