Connect your CRM

When you bring a new customer onto AWS, that win can be worth AWS credits — the New Client Credits (F3) program covers the first month of your new client's AWS usage. Claiming them means filling in the deal's details — company, contract length, expected spend — which already sit in your CRM. Re-typing them for every deal is slow, and the claims nobody gets around to filing are money left behind.

Connecting your CRM closes that gap: when a deal is marked won, Wring prepares the claim for you, pre-filled from the deal. You review the numbers and submit — nothing is ever sent to AWS without your review.

Supported CRMs

Setup is one-time, done by an admin, and takes a few minutes per CRM:

Your dashboard's Connect your CRM page shows which CRMs are available for your account.

How it works

The experience is the same in every CRM: your CRM fills the deal parts of the application, Wring fills the AWS parts.

1. Connect once. An admin connects your CRM from Connect your CRM in the Wring dashboard — a one-time OAuth authorization. No code, no API keys.
2. Win a deal. Mark the deal Won (or Closed Won) in your CRM, exactly as you do today. Nothing changes about how your team works.
3. Wring picks it up. The won deal reaches Wring over a secured server-to-server connection and shows up with a claim already filled in from the deal's data.
4. Review and submit. Open Credits & Funding → Drafts in your Wring dashboard, check the pre-filled claim, adjust anything that needs adjusting, and submit — usually a couple of clicks.

From there the claim follows the normal funding process — see AWS Funding Programs for how applications are reviewed and tracked.

Before you start

Three things need to be in place once, for any CRM:

1. A Wring account — you and your team sign in to the Wring dashboard.
2. A linked AWS account — connected under Credits & Funding → Linked AWS Accounts; Wring reads its usage to fill the application.
3. Connect from the right Wring account — connecting a CRM pins it to the Wring account that authorizes it, so every won deal from that CRM lands in your workspace no matter which email is on the deal. Just make sure whoever connects is signed in to the right Wring account.

What gets pre-filled

Following your claims

Every won deal carries a claim status, so you can see what's been dealt with and what hasn't:

Unclaimed → Drafting → Submitted → Credited

The page shows your most recent won deals, plus a full table of all of them and totals per CRM. For each deal you can:

• open the claim to review it, edit it inline, and submit
• correct the deal's details if something came across wrong
• archive a deal you don't intend to claim — it leaves the active list but stays in your history
• delete a deal outright
• jump straight to the same deal in your CRM

Security

• Verified at the source. Each extension authenticates inside its own CRM — OAuth connections with auto-refreshed tokens; no API keys for you to manage or store.
• Server-to-server. Won deals are relayed to Wring over authenticated server-to-server requests — never through the browser.
• Only won deals. Wring reads your won deals and sends just those deals' basics. There is no bulk pipeline sync, and nothing else in your CRM is read.
• Drafts, not submissions. A claim creates a draft in your dashboard — nothing goes to AWS without your review.

Settings

In the connection's manage dialog you can turn automatic claim drafts on or off, for the CRMs where deals are watched in the background. The won stage and the sync frequency are shown there too, but they are not adjustable yet — tell us at [email protected] if the defaults don't fit your pipeline.

Access and disconnecting

You stay in control of the connection:

• Pause and Disconnect change the state of the connection in Wring: it stops being treated as live, and a disconnected connection stays disconnected until you deliberately reconnect it.
• Neither one stops the flow of deals today. Your CRM's authorization is what makes deals arrive, and pausing or disconnecting inside Wring does not withdraw it — won deals can still reach your workspace and appear in your deal list afterwards.
• To actually stop it, remove the Wring app in your CRM's own connected-apps settings. That is what withdraws the authorization you granted, and today it is the only thing that does.

Reconnecting later is a single click, and your existing deals and claims are still there.

Common questions

A won deal didn't show up. Give it a few minutes after the deal is marked won, and check it's in your CRM's actual won stage and the connection shows as Connected on Connect your CRM. Each CRM's page lists its exact trigger and timing.

A claim landed with the wrong person, or not at all. Deals route to the Wring account that connected the CRM, not by the email on the deal — so if claims are landing in the wrong place, reconnect the CRM while signed in to the correct Wring account. (A deal-owner email is used only as a fallback for older connections made before connect-time binding.)

Can I open the original deal from Wring? Yes — every deal in Wring links straight back to your CRM: Open pipeline for the deals view, and Open in [CRM] on a deal row for that exact record. See your CRM's page.

I disconnected but deals still arrive. Disconnecting in Wring changes the connection's status but doesn't withdraw your CRM's authorization. To fully stop it, remove the Wring app in your CRM's own connected-apps settings — see each CRM's page.

A setting I need isn't adjustable. The won stage and sync frequency aren't self-service yet. Tell us at [email protected] and we'll set them for your pipeline.

Getting started

Open Connect your CRM in your Wring dashboard and pick your CRM, or write to [email protected] if you'd like us to walk through it with you — including which of your recent wins are still worth claiming.