TYOP Transactional Flow

1. © 2009 Enfatico
TYOP
FLOW: Transac-onal Example
Visitor sees this (content) Visitor does this (behavior)
OA: TYOP Hero Banner
Resides on 3rd‐party website
highligh9ng specific 'Hero' and
the server they use.
Details:
Clicks on TYOP banner
Sees corresponding 'Hero'
page on TYOP site
DP 1:
Clicks link to read
detailed stories on other
'Heros'
REL 1:
Clicks link to read
detailed story about
'Hero'
REL 2:
Clicks link to learn
more details about
the server
CTA 1:
Votes on 'Hero'
CTA 3:
Calls Dell to get
quote on managed
services
CTA 4:
Selects server to
configure and
purchase
Visitor begins as not a supporter
Visitor becomes an inac-ve supporter
Visitor becomes an ac-ve supporter
Visitor is less engaged Visitor is more engaged
Task flow legend
Decision point (only path is
followed)
Interac9on node (content,
feature, or data interac9on)
Direc9on of task flow
CTA 2:
Shares server and site URL
info with boss via email link
Decision Point (DP):
1. Visitor decides that he/she is no longer
interested in 'Hero' that was presented
from OA banner, but is inclined to
explore other 'Hero' stories.
Related content (REL):
1. Visitor is interested in learning more
details of 'Hero's' story portrayed from
OA banner.
2. Visitor is interested in detailed
informa9on regarding the server shown
in the OA banner.
Calls to ac-on (CTA):
1. Visitor votes on 'Hero' story
2. Visitor shares site and server
informa9on via email link with primary
purchase decision maker.
3. Visitor calls Dell to get quote on
managed services to assist with other
servers visitor currently has.
4. Visitor selects server to begin
configure and ul9mately purchase.