Overall the scenario sounds good.

A few comments:

Terminology: Although leads can be manually assigned, most CRM systems have auto-lead assignment based on the criteria of the leads. The admin in these systems is usually creating the rules of assignment, rather than manually assigning leads. Related suggestions:
* instead of making a distinction between "admin client" and "client app", we could consider them as two versions of the same app - desktop Vs mobile. 
* typically the distinction on who can do what is based on the user role, rather than "admin" rights. Therefore, I'd suggest renaming "admin client" to exclude the word "admin". Perhaps call this person a "sales lead" or something.

Pitch: IMO, this demo motivates the fact that Prodoctor is able to use push notifications to ensure potential customers get immediate attention from sales. For example, if a sales agent is at a conference, and a potential lead came from a customer at the same conference, the SA is immediately notified and could utilize the opportunity to meet with the customer in person to show a demo. Talking about the end-effect of such a notification would be good. 

Related Scenario: A related scenario for future. Push notifications to get immediate approval of discount requests to close "opportunities" (a lead is typically converted into an "opportunity", once it's established to have potential for a sale). For example, a SA could get immediate approval for a discounted rate, from the division head, while interacting with the customer to ensure the opportunity is converted to a sale. 

D.

On Jun 11, 2013, at 10:45 AM, Sebastien Blanc <scm.blanc@gmail.com> wrote:

Hey !
We would like to provide, in a quite short delay (coming 2 weeks) a demo showing all the different bits of the "push" world , meaning :
 client | push server | JEE Backend App

We already have the push server (aerogear-unified-push-server) : so we need a client (iOS and maybe also Android) and a simple JEE backend application.  The backend app will mostly be scaffolded and will use the  aerogear-unified-push-java-client to send messages to the Push Server.  

Then of course, we need to think about an idea of the application itself. It needs to stay really simple, show  how we can send selectively and should be a bit "business" related.

So, I came up with an idea this morning that we can discuss here, of course if you have any other idea don't hesitate to share it.

Push Demo

Introduction

Prodoctor is a company in the health care industry, selling a revolutionary tensiometer. Their clients are doctors. Prodoctor has several sales agents all over the United States. At the headquarters, they have their "first line" sales department  doing cold calls all along the day. As soon they have a concrete lead, they use their Prodoctor Admin app to filter out available sales Agents available in the lead area. They can then send them a push notification.

The sales agent receives the notification on their mobile device that a new lead is available. The agent will handle the lead by "accepting" the notification  informing the other agents that the lead has been processed.

The client app

  1. The client consist of a list of leads : a lead can be "open" or "in process", leads "in process" of other sales are not visible.
  • optional : when the client tap a lead it appears on a map
  1. The client has a status that he can set: STANDBY | WITH_CLIENT |PTO
  2. The client has a location
  3. The client has an alias

Prodoctor Admin client

  1. The admin client can create a new lead :
  • A lead consist of a name and a location
  1. The admin client can query for Sales Agents based on :
  • Status
  • Location

  1. The admin client can assign a lead to a selection (1..n) of sales agents, this will send out the notifications.

  2. The admin client manage the Sales Agents DB.

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev