iEngage
Turn existing interest into better-informed sales conversations
iEngage is designed to organise consenting audiences and relevant follow-up journeys, then hand sales the prospect's engagement context, so a salesperson continues the conversation from the interest already shown.
Does this sound familiar?
Marketing collects interest, but the follow-up is generic, inconsistent or disconnected from sales. A salesperson receives a contact without knowing what interested that person. iEngage is on the roadmap: it is designed to keep audiences, consent, follow-up journeys and the hand-off to sales on the same customer record.
What it costs the business
Interested prospects receive the same messages as everyone else, sales calls start cold, and nobody can say which campaigns started real conversations.
Built for
- Marketing leaders who work alongside a sales team
- Commercial leaders who want marketing and sales to agree on what a qualified hand-off is
- Sales managers whose team receives marketing contacts without any context
From problem to gain
What changes when the work moves into one place.
The situation
- Interested prospects receive the same messages as everyone else, sales calls start cold, and nobody can say which campaigns started real conversations.
What your team does
- Consent-based audiences
- Campaigns and journeys
- Engagement signals
What it produces
- A consenting audience for each campaign, as designed
- An engagement history for each prospect, as designed
- A proposed hand-off for a salesperson to accept, as designed
What you gain
- Follow-up that matches what interested the prospect
- Sales starts the conversation with context
- Less repeated campaign administration
The difference it makes
Follow-up that matches what interested the prospect
How
Designed to group audiences by profile and response from your customer records, and to send only where consent allows. An enquiry is never treated as marketing consent.
Sales starts the conversation with context
How
Designed to pass a proposed hand-off, with the prospect's engagement history, to a salesperson who accepts or declines it.
Less repeated campaign administration
How
Designed to plan campaign messages and follow-up journeys in one place, with the campaign and source kept on each lead.
How it fits together
What it does
- Consent-based audiences
- Campaigns and journeys
- Engagement signals
What your team gets
- A consenting audience for each campaign, as designed
- An engagement history for each prospect, as designed
- A proposed hand-off for a salesperson to accept, as designed
How your team uses it
Marketing lead
Defines a consenting audience and reviews the follow-up journey
- Output
- An approved journey for an eligible audience
- Next owner
- Marketing team
Marketing team
Reviews engagement signals and proposes a hand-off
- Output
- A proposed hand-off with the prospect's engagement history
- Next owner
- Salesperson
Salesperson
Accepts or declines the hand-off
- Output
- An accepted opportunity, or feedback to marketing
- Next owner
- The deal owner or the marketing team
Inside iEngage
Consent-based audiences
Planned: audiences built from customer records by tag, field and response, with consent and opt-outs respected. Audiences by tag and field value already exist for template broadcasts in iConnect CRM, which is in controlled rollout.
Campaigns and journeys
Planned: one place to plan campaign messages and follow-up journeys, keeping the campaign, source and keyword on every lead.
Engagement signals
Planned: deliveries, opens, clicks and replies recorded as signals of interest. Scores suggest; a person decides.
Hand-off to sales
Planned: a proposed hand-off with its engagement history, sent to the sales owner in Leads & Sales (iSales), which is in controlled rollout, to accept or decline.
Campaign-to-opportunity view
Planned: campaigns compared by the opportunities that followed them, using definitions marketing and sales agree.
Illustrative example — assumed inputs, not a customer result
What a better sales-acceptance rate would mean for one audience
Assumed inputs
- Eligible, consenting prospects
- 200
- Accepted by sales today (assumed)
- 20 of 200
- Accepted by sales with relevant follow-up (assumed)
- 30 of 200
What the assumptions give
20 versus 30 accepted hand-offs: 10 more conversations that a salesperson has agreed to take on. The improvement is an assumption, not a product result. Any extra wins need their own conversion and deal-value assumptions.
What a pilot would measure
Sales-accepted hand-offs per eligible audience, hand-off response time, opt-out and complaint rates, and the opportunities that result.
How to start / What this requires
iEngage is planned to run inside iConnect, on the customer records, consent and roles of iConnect CRM, which is in controlled rollout.
First step
Start with a tailored demoWe walk through your own workflow with you and confirm which of the requirements below apply to your team.
What needs to be in place
- Customer and audience records with consent in iConnect CRM, which is in controlled rollout. An enquiry is not marketing consent; consent is recorded separately.
- A sending account for email journeys, set up for your deployment.
- For the hand-off: Leads & Sales (iSales), which is in controlled rollout, where a salesperson accepts the opportunity.
What you gain by connecting it
Selected combinations, not every possible pair. Each connection shows how far it has been proven, so you can tell what has been shown working from what is still planned.
How to read the connection labels
- Demonstrated in testing
- Shown working in our testing, on code that is not yet released to customers.
- Configured per deployment
- Depends on setup for your deployment, such as a connected channel or approved knowledge.
- Planned
- Not built yet. Shown to explain the intended workflow.
Coordinated growth with the customer record and sales
iEngage is designed to draw consenting audiences from iConnect CRM, in controlled rollout, and to pass an accepted hand-off to the sales owner in iSales, in controlled rollout. Showing engagement on the customer timeline is not built yet.
Works with
CRM (1)Controlled rolloutiSales (2)Controlled rolloutSee the full workflowConnections
- CRMiEngage
- Eligible, consenting audience
- Demonstrated in testing
- iEngageiSales
- Sales-accepted hand-off
- Demonstrated in testing
- iEngageCRM
- Engagement on the customer timeline
- Planned
Research and coordinated growth
iGrowth, on the roadmap, is designed to research prospects and pass them through the customer record; a direct route from iGrowth into iEngage is not built yet. The iConnect Growth Engine, also on the roadmap, is designed to let an authorised person start a coordinated enrolment step into iEngage.
Works with
iGrowth (12)RoadmapGrowth Engine (14)RoadmapSee the full workflowConnections
- iGrowthiEngage
- Research signals to engagement
- Planned
- Growth EngineiEngage
- Coordinated enrolment step
- Demonstrated in testing
Suggested solutions
Complete workflows this product takes part in.
Related pages
- CRM (1)Controlled rollout
- iSales (2)Controlled rollout
- iGrowth (12)Roadmap
- Growth Engine (14)Roadmap
Good to know
We would rather you knew the current limits before a demo than after it.
- Roadmap: iEngage is planned and is not available today. Request a demo to discuss your marketing-to-sales workflow.
- Campaigns, journeys, engagement scoring, the sales hand-off and campaign-to-opportunity views are planned, not available today.
- iEngage does not publish to social networks. Social planning and publishing belong to iGrowth, which is on the roadmap.
- Scores suggest; a salesperson decides. Engagement scoring does not replace human qualification.
- An enquiry is never treated as marketing consent.
- Showing engagement on the customer timeline is planned.
Technical details
For technical evaluators: records, roles, inputs and setup, as far as current evidence supports them.
Show the technical details
- Audience source
- Customer records, tags, fields and consent in the iConnect customer record.
- Consent
- An enquiry is not marketing consent. Messages are designed to go only to contacts whose consent is recorded, and opt-outs are respected.
- Hand-off
- A proposed hand-off is designed to go to a named sales owner, who accepts or declines it.
- Boundaries
- Social planning and publishing belong to iGrowth, which is on the roadmap. iEngage connects the resulting signals to audiences and the sales hand-off.
Questions and answers
Is iEngage available now?
No. iEngage is on the roadmap. Request a demo to discuss your marketing-to-sales workflow and what is planned.
Does iEngage publish to social networks?
No. iGrowth, which is on the roadmap, researches fit and owns agreed social planning and publishing. iEngage is designed to nurture an eligible, consenting audience and prepare its engagement context for sales.
Who decides that a prospect is ready for sales?
A salesperson. iEngage is designed to propose a hand-off with the engagement history, and the salesperson accepts and manages the opportunity in Leads & Sales (iSales), which is in controlled rollout. Engagement scoring does not replace human qualification.
Does an enquiry count as marketing consent?
No. An enquiry is not marketing consent. iEngage is designed to message only contacts whose consent is recorded separately.
Discuss your marketing-to-sales workflow
Tell us how marketing passes interest to sales today. We will reply to arrange a conversation about your workflow and what is planned.