Skip navigation
1 20 21 22 23 24 Previous Next

Do It

517 posts

With the new lead scoring module in E10, you'll need to map a different lead scoring field in Eloqua to your CRM field.

It depends on the CRM you integrate with but you'll want to do this for the Update Contact, Update Lead and Create Lead calls.

Go to: Setup > Integration > Outbound (tab) > External Calls (tab) and update each call separately.

 

Choose the Default Scoring Model field and drag it to the Lead Rating field (or whatever you have called it in your CRM). That's it.

8-31-2012 4-40-26 PM.png

This article reviews some of the testing tools that are available for end users of Apps. Not every App that is hosted on cloudconnectors.eloqua.com has every test option outlined below. They are typically found on connectors and feeders (the difference is explained here).

 

NOTE -

This document is not for testing the DEVELOPMENT of Apps. It is meant for end users

 

Accessing the Test Tools

When you are looking at the configurtion window for an app, you will see a series of buttons along hte left hand side. Click on the "Test" button:

test tools.png

 

You will see a potential mix of different tabs, depending on the app you are looking at. The options are as follows:

 

Step Members:

step members.png

This tab shows records that are in the step in Program Builder or Canvas, and what "state" they are in. IF a record appears in a step, but is not represented here, then the Program or Canvas has not executed yet. Clicking the "Refresh counts" button will refresh the number of records in each state.

Awaiting Action - These are records that are waiting for the App to process

In Progress - The app has started processing these records

Complete - The app has finished processing these records (but they are still in the step in PB or Canvas)

 

Under the "Action area, you can select the drop down and change the state of a record to either "Awaiting Action, "In Progress" or  "Complete". You select the option that you would like, and click "Go"

 

Run Manually

Run Manually.png

Run Manually allows you to manually execute the App. It is typically used in both Connectors and Components

You have 2 options:

Dry Run - A dry run executes the call, either on the contacts in a step OR for the relevant contacts in a feeder. There MUST be records in the step within Eloqua. IT DOES NOT modify the data within Eloqua. If there is a per transaction cost with the 3rd party, this will typically NOT use those calls

Full Run - A full run executes the call, either on the contacts in a step OR for the relevant contacts in a feeder. There MUST be records in the step within Eloqua IT DOES modify data within Eloqua. If there is a per transaction cost, it will be incurred.

 

Both run modes display the information back from the third party within the screen. Both only execute off 10 records

 

 

Sample Data

Sample Data.png

Sample Data is typically used with connectors. It allows you to define a contact (which does not need to be within the step in Program Builder or Canvas).

To use, place 1 email address per line. A contact MUST exist in Eloqua with the email address that is inputed.

By default, Sample Data runs as "Dry Run" mode above (where data is displayed, but not committed to Eloqua). If you want to have the data pushed to Eloqua, click on the "Full Run" button.

Click "Test Contacts" in order to execute.

As part of the "Eloqua on Eloqua" series, I'm happy to write about how we use Eloqua to run our New Hire Onboarding.

 

Whenever a new employee joins Eloqua, they experience a timed nurturing campaign that pushes important information to them when they need it. You may be wondering how to build something similar in your organization... well wonder no more, because here's how we did it!

  • We started with defining the process: What happens when a new employee joins? In our case, the hiring manager fills out a form on our intranet and that form submission kicks off a workflow to departments like IT, HR, etc.. We first thought about integrating this form into Eloqua, but then realized the new employee wouldn't have their @eloqua.com email address just yet.
    • Once IT has created the new hire's Eloqua email, our HR department goes to a landing page with a form, hosted internally. That landing page is actually an Eloqua landing page, with the form integrated into an internal Eloqua install that we use for non-Marketing purposes. HR fills in the new hire's name, Eloqua email address, start date and department information.

New Hire - Form.jpg

  • We then designed the HR campaign: What information does every new hire need at each stage of their onboarding? Each piece of information was made into an email, or like information was grouped into one email. We then planned out the timing: Employee Handbook should get sent on Day 1, product videos on Day 10, etc.. Each link in the email went to content on our internal website portal - tracked for click-throughs of course!
    • I'm responsible for the onboarding of new sales people, so I created a parallel nurturing campaign specific to their needs and typical questions.

New Hire - Campaign.jpg

  • The form could be submitted at any time by HR before the new hire starts; but we wanted the first email to get sent the day the new hire arrived at Eloqua. We set up a segment that found folks who were starting within the next day and pulled them into the campaign. That segment also looked at new hires who were in Sales and pulled them into the parallel Sales campaign as well. Which means that a new Sales Rep receives messages from HR as well as messages from me about how to sell Eloqua

New Hire- Onboarding Segment.jpg

  • Once everything was built in the Landing Page editor, Segment editor and Campaign Canvas, we activated the campaign and the rest is history!

Feel free to steal any of the above for your own use. I also encourage you to attend an upcoming Road to Revenue Tour near you, where we'll be presenting this and more "non-marketing" use cases of using Eloqua.

 

... and I'd love to answer any questions about this or hear about any other nifty ways out there that you have developed to onboard your new employees!

This is a non-official post that may or may not work. I've been reviewing some old folders on my laptop and thought this material may be helpful based on some recent posts I've seen. If it doesn't work, post comments and let's work as a community to figure this out. With all that said, here we go!

 

The following post explains how Eloqua users can have content dynamically change on their event landing pages depending on whether or not the event is full. For example, if an event is full, you may want to have a message that lets web visitors know this right away (rather then sending them an email which Eloqua can be configured to do very easily).

 

Before starting this process, ensure that you have the necessary training from EloquaU and have access to the Events Module. This assumes that you have an advanced knowledge of Eloqua forms, landing pages, JavaScript, web data lookups and web design.

 

  1. Create an event using the Events Module - You need at least one session. Be sure to set the max number of registrants for the event.
  2. Create an Eloqua form.
  3. Add the following processing step (for events): Update Event Registration. Select the Event you created in Step 1
  4. Add the form to an Eloqua hosted landing page or to a web page that has Eloqua tracking scripts on it
  5. In order to setup a condition that will allow you to display different content if the event is full, you need to create a data card data lookup. Setup > Website > Web Data Lookup
  6. Create a new Data Look up. Make sure you select “Data Card Sets”. Select "Data Cards" from the Data Lookup Type drop down and the name of your event from the Data Card Set drop down.
  7. Once it's created, in the top right of the screen, go to Data Lookup Options > Get Data Lookup Scripts.
  8. Take the script on the lower half of the page and paste it on the web page or Eloqua hosted page (you'll need to use a Cloud Component in E10 for this). If possible, ensure the scripts are placed under the Eloqua tracking scripts.
    8-30-2012 6-47-05 PM.png
  9. You now need to customize the scripts so the Lookup will be associated with the appropriate Datacard Set (event). Within the <DataCardSet> tags, enter in the ID of the Datacard Set. You can find the ID from the scripts at the top of the page:
    8-30-2012 6-48-51 PM.png
  10. Just add in the ID so it would look like this (you can just remove the “Enter__here” between the “GroupByFieldValue” tags:
    var elqDLLookup = '<DataCardSet>48</DataCardSet><GroupByFieldValue> </GroupByFieldValue>';

    An important item to note is that one Lookup can be used for multiple Datacard sets (events). This is what it would look like: <DataCardSet>11,14,15,16</DataCardSet>

  11. Now you need to add the script that will change the content based on whether the event is full. Below is an example of the script that was added for a sample event (the code doesn't work). It displays alternative text if the event is sold out based on the limit you set in the event. For your event, ensure that you substitute the Datacard Set ID (it’s 48 below) with the correct ID. This was added in from the top section of the page.

<SCRIPT TYPE='text/javascript' LANGUAGE='JavaScript'>

if (GetElqContentPersonalizationValue('IsCourseFull48') == 'False')

{

  document.write('<p><b>Wednesday, July 11, 2017<br> Steve Miller Band</b> (Main Stage)<br> <b>Dog Power </b>(Rogers Stage)</p>'); }

else

{

  document.write('<b><span style="font-size: 11pt;">These tickets are sold out. <br> <a href="http://test.com/index.html"><u>Select an alternate date</u><img src="http://www.test.com/images/arrow-blue.gif" border="0" hspace="5"></a></b></span><br>  <br><br>');

}

</SCRIPT>

 

In a normal situation, the page will display:

Thursday, July 11, 2017

Steve Miller Band (Main Stage)

Dog Power (Rogers Stage)

 

If the event is full, the text will be substituted with:

 

These tickets are sold out.

Select an alternate date

 

EXTRA: Using JavaScript, you can get even further complicated. For example, when the page loads, you can check if the event is full and disable the form fields. Here is another code sample of a multi-city event:

 

 

<SCRIPT TYPE='text/javascript' LANGUAGE='JavaScript'><!--//

 

 

window.onload = initPage;

function initPage(){

 

  if (GetElqContentPersonalizationValue('IsCourseFull11') == 'True')

  {

  document.forms["Event_Registration_TEST"].elements["AppeonPowerBuilder_flag"].disabled = true;

  document.forms["Event_Registration_TEST"].elements["AppeonPowerBuilder_flag"].checked = false;

  }

 

  if (GetElqContentPersonalizationValue('IsCourseFull14') == 'True')

  {

  document.forms["Event_Registration_TEST"].elements["PocketPowerBuilder_flag"].disabled = true;

  document.forms["Event_Registration_TEST"].elements["PocketPowerBuilder_flag"].checked = false;

  }

 

  if (GetElqContentPersonalizationValue('IsCourseFull16') == 'True')

 

  {

  document.forms["Event_Registration_TEST"].elements["ASE_flag"].disabled = true;

  document.forms["Event_Registration_TEST"].elements["ASE_flag"].checked = false;

  }

 

  if (GetElqContentPersonalizationValue('IsCourseFull15') == 'True')

  {

  document.forms["Event_Registration_TEST"].elements["RepConnector_flag"].disabled = true;

  document.forms["Event_Registration_TEST"].elements["RepConnector_flag"].checked = false;

  }

 

}

//--></SCRIPT>

Important: This Cloud Connector/Component will be decommissioned  after March 31st 2017. Please review the App Replacement Cheatsheet for instructions

Tweet Sender

This guide will go over the installation and configuation of the "Tweet Sender" app.

The Tweet Sender app allows you to send a tweet to a contact in Eloqua. IF the twitter handle associated to a contact is follow the authorized Twitter account, a Direct Message (DM) can be sent to the Twitter handle. You can personalize the tweet with up to 2 fields from the contact.

 

It is assumed that users of this guide are comfortable with Program Builder OR Campaign Canvas. This app is supported on ALL versions of Eloqua.

As well, you will need an account on cloudconnectors.eloqua.com to use this connector. Sign up at http://cloudconnectors.eloqua.com

 

 

How to Install the App

As of the writing of this guide, this app is not available on Appcloud.eloqua.com, and must be installed from cloudconnectors.eloqua.com (please see this article to understand the difference).

Visit this URL and click on the "Install Connector" button, and follow the steps (NOTE, your Eloqua user will need to be an adminstrator user in order to install):

https://cloudconnectors.eloqua.com/StepTypeOverview.aspx?StepType=TweetSenderContact

 

Using the Connector

 

The connector is triggered off a contact. It can be triggered from either Program Builder OR Campaign Canvas.

 

Campaign Canvas:

 

The tweet sender is used the same as a regular action in Canvas. Double click or drag "Send to Cloud Connector" from the left hand navigation (under the Actions header). The step will appear. Double click the step, and select "Tweet Sender" from the list:

 

canvas component.png

Click the icon to the right in order to start configuration.

 

Program Builder:

 

The tweet sender executes as a regular action step in program builder.

Create a step in the program where you want the step to execute

Set the action of the step to: “Cloud Connector”

You will be provided with a list of Cloud Connectors that have been created. Select the correct one from the list:

list.png

Click the "Configure" button.

 

Configuring the Tweet Sender

If you are not already logged into Cloudconnectors.eloqua.com, you will be to do so:

cloudconnectors login.png

On the next screen, you will be prompted to input the information for an Eloqua user. Please ensure the user has API access:

cloudconnector login 2.png

 

On the next screen, (configuration) you will need to do 2 things:

- Authorize a twitter account (this is the account that the Tweet will be sent from)

- Define the Twitter Message.

tweet sender config.png

 

Authorize Account:

 

Click on the "Authorize Account" button. This will bring you to a Twitter login screen. Please login with the correct account, and click the "Authorize App" button.

 

Twitter Message:

Here is where you input what the message looks like. URL's will automatically be shortned (using the T.CO shortner), and message longer then 140 characters will be truncated. You have the following configuration options available:

Direct Message - To make this a Direct Message (DM) place a lowercase d at the start of the tweet.

Twitter Handle - to include someone's Twitter handle, include the following ||TwitterID||. If you want to @message them, place it as such @||TwitterID||

Personalization from Contact fields - You can include personalization from up to 2 contact fields. The fields are defined in the "Mappings Area". To include the personalization, please insert: ||Pers1|| and ||Pers2||

 

Mappings:

Under the mappings area, you will map 3 fields from the contact:

Twitter ID - this is the field the Twitter handle

Twitter Personalization Field 1 - This is the field that stores the personalization message ||Pers1||

Twitter Personalization Field 2 - This is the field that stores the personalization message ||Pers2||

 

NOTE - Although you do not need to use both personalizations, you do need to map a field into them

 

Enabling the Step:

Remember, in order for this app to be live, you need to enable both the program/canvas AND the app. To enable the app, click on the "Credentials" tab, and then click the "Enable Step" button:

enable.png

Because Cloudconnectors.eloqua.com sits outside of the standard Eloqua code base, it has a separate release structure, with releases happening in a much more frequent manner.

This post will be updated with release notes for each release. Please check back often, or follow this post for the most up to date information.

IF you have questions, please make a comment and include the release date.

 

October 27, 2012:

  • Improvement - RSS Component added validation for URL structure of feed


October 25, 2012:

  • Overall Speed Enhancements
  • Bug Fix - Static value from query string in Progressive Profiling


October 12, 2012:

  • Form Prepop now supports checkbox fields
  • Bug Fix - email address in pre pop components

 

October 6, 2012:

  • UI Improvements to Box Content app
  • String Manupulator support for large text fields
  • Bug Fix - Form Submit accepting comma

 

September 30, 2012:

  • Fixes to Brainshark feeder
  • Fixes to Survey Gizmo feeder
  • Slideshare embed released

 

September 23 2012:

  • Radian6 "Buzz Widget" available
  • Polls supported in Survey Gizmo
  • Slideshare app available
  • Upgrades to UI framework

September 15 2012:

  • Improvements to Box app UI


September 11 2012:

  • Box embed - General updates
  • Bug Fix - Wrong screen displayed intermittently when editing field mappings
    Lithium - UI Bug fix


September 7th 2012:

  • Continued increase in throughput for connectors
  • Increase in speed-to-pick-up connectors the first time a contact goes into the step
  • Box component had preview added to show live doc
  • Box file explorer added
  • On24 register connector - BUG FIX - not sending blank values
  • On24 feeders now update-but-not-create contacts if setting is set as such
  • Lithium - BUG FIX - dates fixed

 

August 24th 2012:

  • Increase in throughput for connectors for faster execution of large data sets
  • Small UI tweaks
  • Data.com connector - display fields were added (revenue, employees)
  • Progressive Profiling - Ability to upload query strings.

When using progressive profiling as part of your lead nurturing efforts, I've found capturing one high value piece of information at a time works best.  For example, if you are going to offer a case study, video or whitepaper for download, only ask for either email or social media log-in credentials and company name.  Then when a prospect responds to the next call to action in the nurturing series, ask for an additional piece of information such as industry or pain point and deliver content based upon information gathered from previous interactions.  This not only creates a personalized experience but it keeps the tone conversational.

 

In addition, you should be incorporating your lead scoring criteria into this process so subsequent interactions will boost up your prospects lead score! With any relationship, it's best built over time and there's no better way to do this then with progressive profiling.

 

As a next step, why not try out progressive profiling using Eloqua's new Cloud Component How to do Progressive Profiling in E10 Using the Cloud Component

Has anyone come up with a good way to create a form or something that allows people to register for Pod space at a meeting and once that space is filled, the option is automatically removed?

 

For example, if at Eloqua Experience, I have 5 pods to assign in 30 min. increments, the pods are assigned for 5.30 - 6.00 pm but only 3 are being used from 6.00 - 6.30 pm.  The registration for the 5.30 - 6.00 pods will close but the 6.00 - 6.30 is still open.  Ideally, this would be automatic...

This seems counter-intuitive. What's the reasoning around this not happening?

 

It would really speed up the campaign building process, especially for monthly campaigns.

 

Thoughts?

Create a data card and create a Contact and map the data from the data card onto the newly created Contact.

 

In E9, navigate to:

Evaluate > Database Management > Custom Objects > Data Card Set > Data Card Services > New Data

(if the data card services are being launched for the first time which would then enable the transfer of data from all existing data card to contact.)

1. Add Processing steps, "Save to Contact Table" and "Update existing record or Data Object"

2. For the processing step, "Update existing record or Data Object", you can then choose an existing Update Rule or create a new one--you will likely need to create a new one for the project at hand; however, if you create a new Update Rule from Data Card Services it will never give you the option to choose a database table (Contacts, Prospects, Companies, Custom Object). It will always default to the exact Data Card Set you are working in. Clearly, this will NOT work for transferring data card data to the contact table because you cannot map/align the two objects. To get around this you must visit step 3.

3. Navigate to Evaluate > Data Tools and click, "Create New Update Rule Set"

4. Create a new Update Rule and Select Contacts as the Table to update. Add the Contact Table fields you would like to update. Save.

5. Go back to your Custom Object/Data Card Set's Data card Services and open the "Update Existing Record or Data Object" process step you created and select the Update Rule you just created.

6. Map the Data Card field to Contact Field and Save and Close.

 

Repeat this process for modified data in Data Card Services, but do not place the "Save to Contact Table" step.

 

Run some tests and you will see net new contacts get created and modified ones map data card data onto their contact record.data_card_sets

I recently set up a campaign that uses the Form Submit Cloud Connector and ran into an unexpected problem. I thought I'd share my experience with everyone so you don't duplicate my error.

 

My campaign sent leads to the Form Submit Cloud Connector in order to trigger multiple actions off a "blind" form submission. When I turned on the campaign and leads started flowing through, I noticed that the same group of leads kept "submitting" the form over and over again. After several discussions with Eloqua Support, we finally figured out that my form had required fields on it, and the leads who were looping through the program were missing one of the required fields. I changed the form so none of the fields are required and now it's working as expected.

 

When setting up a Form Submit Cloud Connector make sure:

1. All of the leads running through the Connector have the required fields.

or

2. Do not make any of the form fields required.

Shared Items on Eloqua:

  1. Shared Content
  2. Shared Lists
  3. Shared Filters

   4.  Dynamic Content (can be shared)

 

  1.    Shared Content

Shared content is reusable content snippets that you can create once, then reuse in different emails and landing pages.  It allows you to ‘build once, re-use everywhere’ for your most common pieces of content. 

 

Example: Biography on a company person that speaks often at events or on webinars.

Example: “About” company information; ABC company is a global leader of …..

Example: Common product ‘blurbs’. 

 

Check this post for more info:

http://topliners.eloqua.com/groups/eloqua-product-documentation/blog/2012/05/03/shared-content-overview


2.    Shared Lists

Shared lists are a group of contacts with something in common (like a tradeshow list) and sharing the list allows others in your company using Eloqua the ability to add to this list or email to this list.

 

Example:  NA-TRADE-ABCshow-Nov2012 is a Shared Lists.  I uploaded the contacts I got from the recent tradeshow into a shared list so the marketing communication manager can send the follow up email to this list of contacts.

 

Check this post for more Info:

http://topliners.eloqua.com/message/2503#2503

 

3.       Shared Filters

Filters that are created using profile (like industry) and/or engagement (activity filter like everyone that opened this email in the last 60 days) that are shared so the whole marketing team and use them. 

 

Check this post for more info:

http://topliners.eloqua.com/groups/eloqua-product-documentation/blog/2012/05/02/shared-filters

 

4.       Dynamic Content (which can be shared!)

Dynamic content allows different email or landing page content to be substituted depending on rules and associated criteria. 

 

Example: Show a different list of training sessions based on region or city.

Check this document for more info:

  https://eloqua.box.com/s/de44dd63fe1badca1ccb

When salespeople chat with potential clients on the shopfloor or sales meetings they usually make notes either mentally or to a notepad. The information often stays silent between the ears of the salesperson or stay hidden inside the covers of the notepad. As most salespeople hate feeding stuff into CRM there should be a more friendly way to enrich data.

 

A solutions to this might be to create a custom form that a salesperson could fill out during the conversation using a pad or a smartphone. The form could be formulated to use predetermined picklists to enter the solutions, products and services the potential customer has or needs. The form could also include a budget, timeframe and other company data. Upon completion the form data would be saved to a custom object and fed to CRM. Some of the data could be updated into contact fields and then used to create a BANT score. The BANT score could then be included in the lead scoring. The data would also trigger campaigns depending on what the salesperson entered into the form. The client could be sent document packages or even quotes straight away.

 

Any thoughts on this? Has anyone ever implemented something like this? How could we gate the form page so that only authorized people could be able to enter the form page? What else could the system be used for? Any problems this kind of system might create?

Problem Statement:

Often time’s lists from clients (or internal "exclude" lists contain company names, domains, or email addresses need to be suppressed from a particular segment. This is a method of performing the match evaluation, without importing the data into the main Eloqua tables.

 

Solution Summary:

A picklist is created containing the company names (domains,or emails) to be excluded from the segment. From the segment builder, the “In List” or “Not in List” can be used to match the records.

 

Pre-Steps

Cleanse the data to be imported by narrowing it down to a two column spreadsheet. I use excel for this. One column should be the criteria you intend to suppress, and the other (I name ID) can just be a numbered list (See Below).  This step will make importing much easier. Later, the “Company” column will be mapped to the “Option Value” and the “ID” will be mapped to the “Option Name”.

cleaned list.jpg

 

Process Steps:

From the setup Menu, Select "Manage Picklists":

 

step_one.jpg

Manage Picklists Button.jpg

 

In the upper right, select "Select Lists", then "New Select List"

 

New Select List.jpg

Give the list a Name - This will be the name you look for when building the Filter in the Segmentation Tool.

 

Name the select list.jpg

 

Select Save.

 

from the upper right "Select List" button, choose the "Upload Select List" Option. This will bring up the list upload wizard.

 

Upload the Select List.jpg

Once the wizard opens, you can name the upload, and describe it. These are not needed, and will fill in automatically. The important part is selecting your file type to upload.

 

Select List Upload.jpg

Once the file type is selected, go to "Next" this will prompt the user for the data source:

 

 

 

Select file to upload.jpg

 

Browse to your file, and then "Upload and Preview Data"

 


preview data.jpg

 

Select "Next" This screen is just a preview of your data. The next step (very important) is mapping the data:

 

This screen is where you map the fields to the table in Eloqua. I map the "Company" field to "Option Value" and the "ID" field to "Option Name"

 

Option Value Revised.jpg

 

Select "Next" through the next steps (they are just 'admin / reporting' steps)... This is the window you will arrive at. If you have "Success" close the dialog window, and you can go directly into the segmentation tool.

 

success.jpg

 

Now - A list (or table) exists which you can compare values to from the segmentation tool.

 

Open the segmentation tool, place a "Filter Criteria" on the board, Select the field you want to match, and then drop down to the "In List" (or "Not in List") options:

 

final pic.jpg

 

Now the "Match Evaluation" is performed, and you will filter the contacts by whatever field matches your list. If you are trying to "Exclude" contacts from those companies, you can change the filter to "Switch to Exclude" or you could use the "Not in List" option when building the expression.

 

The maximum number of visible rows in these select lists is 2500. However, I've tested this method with over 4500 rows - the Match will still work

 

If anyone tries this, I'd love to hear feedback on this post.

 

Cheers

As we are creating a function for an online support form that would write a time stamp in local time in order to better track service response times, I started to wonder how Eloqua could help service staff to follow up on service requests and create a better experience for the client.

 

When something stops working people tend to be sensitive about the smallest details. They want to know if their request has been received and when the problem will be solved. They need to feel that their needs have been attended to and they are taken seriously. Even the smallest things, like a call from a service person two minutes after the request was made could make a huge difference and boost satisfaction and overall experience. By exceeding customer expectations the satisfaction levels could even go beyond what could be achieved if everything worked in the first place and there was no need for any service.

 

How could Eloqua reduce service response times and help to create a better service experience for example in the ICT sector.  A few ides came to mind:

  • After the customer fills out a service form the request would automatically be directed to an appropriate service person according to contact and form info and form fields. No middle men or administrative steps.
  • The service person would get an email or a text message and he could respond directly to the person who sent the form, offer support or make an appointment.
  • During the service visit, the service staff might use a mobile device to fill in a dedicated Eloqua form. The form would include customer need probing and the service person could register the visit to the system and report the problems fixed.
  • After the visit the customer would get an automated satisfaction survey regarding the visit.
  • By using custom objects and cloud components the service manager could track response times and customer satisfaction. Sales staff could get information on sales opportunities.

 

Has anyone ever implemented anything like this? How could this be done and do you have any ideas how to use Eloqua to make the service experience better for both the client and the service staff?

Filter Blog

By date: By tag: