Clazar POC Guide: AWS ACE Integration via CRM

Last updated: October 24, 2024

Introduction

This guide outlines the process and expectations for conducting a Proof of Concept (POC) with Clazar's AWS ACE integration via CRM. Due to AWS limitations, there are some constraints on what can be tested simultaneously with other partners. This document will help you understand what is possible during the POC and any limitations you may encounter.

What Can Be Tested

  1. Creating Opportunities

    • You can create new opportunities using the Clazar platform.

    • These opportunities will be sent to AWS ACE.

  2. Updating Existing Opportunities

    • Simple updates like changing the target close date can be performed through Clazar.

    • Note: Updates should not be made in your existing partner's platform (e.g., XYZ) during the POC to avoid conflicts.

  3. Closing Opportunities

    • You can close opportunities through Clazar if they haven't been closed via another platform.

  4. Accepting AWS Referrals

    • AWS referrals can be accepted through Clazar if they haven't been previously accepted through another platform.

  5. Viewing Opportunity Data

    • You can view opportunity data synced from AWS ACE in the Clazar platform.

Limitations and Considerations

  1. Single Active Integration

    • AWS ACE only allows one active CRM integration at a time. This means you cannot run two partners (e.g., Clazar and XYZ) simultaneously in a live environment.

  2. Existing IAM Roles

    • The POC will utilize your existing IAM roles for AWS ACE. This allows testing in your production environment without disrupting your current setup. We will share the steps to give us access to your existing IAM roles.

  3. CRM Integration Request

    • We will NOT raise a new CRM Integration request in ACE during the POC if one already exists for your current partner.

  4. Edge Cases and Complex Updates

    • Some complex opportunity updates may have limitations or unexpected behaviour due to the interaction between multiple platforms.

  5. Partner-Specific Logic

    • Any logic specific to your current partner's platform (e.g., XYZ-specific features) will not be available or testable through Clazar during the POC.

POC Setup Process

  1. Provide Access to Existing Roles

    • Grant Clazar access to your AWS ACE roles (sandbox and production).

  2. Complete AWS Co-sell Setup

    • To ensure full functionality, we recommend completing the AWS co-sell setup for the POC. We can do this in a 30-minute call.

  3. Use Clazar in Production

    • You'll be able to test Clazar directly in your production environment using your existing roles.

  4. Avoid Concurrent Use

    • Avoid using your current partner's platform during the testing period to prevent conflicts.

Important Notes

  • This POC setup allows you to test Clazar's core functionality without fully disconnecting from your current partner.

  • Be aware that some actions taken in Clazar may affect data visible on your current partner's platform.

Support and Assistance

If you encounter any issues or have questions during the POC, please contact our support team at support@clazar.com. We're here to ensure your POC experience is as smooth and informative as possible.