The FollowupSales Agent pushes for followup sales via the DistributedPzn framework.

This means that there is a PznSetFacility and a PznRenderFacility for followup sales.

Following the framework, a small piece of information is passed to the set facility to indicate a that the user may wish to make an additional purchase. Say ItemICPoloBlack, or SKU1245978238, or some such.  This call is actually done by the client, but directed by information supplied by the server.

Prior to this action, areas of the site which had been using the PznRenderFacility for FollowupSales were displaying a promo for the e-commerce site.

Now that the followon sale preference has been set for this user, it changes its behavior.  Now it shows the thumbnail of the item that we are pushing for the followup sale with a link to the checkout page for that item, as well as a generic link to the commerce as usual.

Extending the design, the sales confirmation page could be made generic, in that it would not tell the agent's PznSetFacility what to promote, but only what had been purchased.

That would leave the decision as to what to promote up to the PznRenderFacility.	The PznRenderFacility would have an admin that allowed the BusinessUnit to indicate what purchases should lead to which other followup purchases -- This week purchasers of the t-shirt are steered towards the polo shirt, but next week they could be nudged towards the baseball cap.

Further, there doesn't have to be a single followup item, there could be multiples, and the renderfacility could cycle through them, etc.	The mechanism merely has to be coordinated between the two facilities of the agent.