Payment setup for launch

SECTION ONE: PROCESS OVERVIEW

TITLE: What are you calling this process?

> Payment setup for launch

SUMMARY: A one-sentence description of the process.

> Bi-weekly newsletter with an overview of forum activity, to provide updates to our clients, going out every other Saturday.

WHY: Briefly explain why the process is important.

> Since the forum is growing bigger and bigger, it is really easy to miss something that is important for them. This brief overview helps others to go through the most important topics that were discussed over the last 2 weeks.

INTERVAL: How often does this process need to be complete?

> Every other Thursday (as it is checked and polished for grammar by Maria overnight and then final check on Friday by Tomas or Andrew)

SECTION TWO: PROCESS EXECUTION

STEP #1

Before the launch

• test with a dummy payment gate, CC 4111111111111111 any CVC and any expiration


• as a testing email use a new one - no tags, no history, check the permission he is given


• change payment gate to live, change amount to $1 and test live - both CC and PayPal (again - fresh email, no tags)


• tracking hotjar (heatmaps), google analytics, facebook code

STEP #2

After launch starts

• are all links working?


• wait for the first client and check the tags and sequences he was assigned to!!

SECTION THREE: REPORTING

WHO: Who should be the outcome sent to?

>

WHAT: What are you expecting to see in the outcome?

>

WHEN: When does the person reviewing the outcome want it?

>

HOW: How should the outcome be delivered?

>