4 results found

1. Need to track "grandfathered" customers who receive PE (Partner Escalation) on GCP without being charged.

   Request for a flag for legacy clients under "partner-led premium support" who receive Partner Escalation at no cost.

   We need to track "grandfathered" customers who receive PE (Partner Escalation) on GCP without being charged as a result of having a qualifying B2B agreement. A proposed solution involves creating dummy contracts in the console for these customers and adding a flag to identify grandfathered customers.

   Core Problem: Grandfathered customers receiving PE on GCP are not being charged, but there's no clear flag to indicate this, leading to confusion for CRE teams and auditors, as they are dependent on a PLPS contract to understand whether they can escalate to Google support. There are 2 types of customers eligible for escalation, those paying for PLPS and those receive a PLPS equivalent due to the timing of when they signed their agreement.

   Proposed Solution:
   Create Dummy Contracts: For all grandfathered customers, create a dummy contract in the console for PE on GCP.

   Add a Flag/Dropdown:
   Within this PE object (contract), add a dropdown or checkbox.

   Purpose:
   To indicate that this is a "grandfathered" or "legacy account."

   Auditing:
   This flag will explain to auditors why no charge is applied (0% fee).

   Match Contract Dates:
   Use the actual contract end dates for these dummy contracts.

   AM Nudge:
   When a dummy contract is within six months of expiration, it will automatically create opportunities to remind sales reps to re-upsell the customer to paid PLPS.
   CRE

   Tool Integration:
   CRE tools look at a PE contract to determine if a CRE can escalate to Google. Using a PE object, even a dummy one, would allow the CRE team to continue their normal process without needing to find a separate flag on the individual customer.

   Future Reuse:
   The flag field could potentially be reused for future versions of partner-led support (e.g., v1, v2).

   Requirements/Next Steps:
   Create a dummy contract in the console for grandfathered customers with PE on GCP.
   Add a flag (dropdown or checkbox) to these dummy contracts to indicate they are "grandfathered" or "legacy accounts," so auditors understand why no charge is applied.
   Ensure the PE object in the console allows for a dropdown to identify grandfathered customers, with dates matching their contract end and a 0% fee.
   Potentially reuse this field for future versions of partner-led support (e.g., v1, v2).

   Request for a flag for legacy clients under "partner-led premium support" who receive Partner Escalation at no cost.

   We need to track "grandfathered" customers who receive PE (Partner Escalation) on GCP without being charged as a result of having a qualifying B2B agreement. A proposed solution involves creating dummy contracts in the console for these customers and adding a flag to identify grandfathered customers.

   Core Problem: Grandfathered customers receiving PE on GCP are not being charged, but there's no clear flag to indicate this, leading to confusion for CRE teams and auditors, as they are dependent on a PLPS contract… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Billing & Invoicing  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Planned  ·  AdminDewey (Admin, DoiT) responded

   This is will be evaluated against our CP4 work loads.

2. Adding an estimated "bill without DoiT" comparison to the Invoice Explainer to clarify savings for customers

   There is a request to add an estimated 'bill without DoiT' directly into the Invoice Explainer. Currently, customers struggle to see the value we provide because they can only view the AWS bill to DoiT and the DoiT bill to them. We also need to know how many are using the console reporting to see their savings. This lack of transparency on the invoice creates confusion, particularly around renewals, leading to the impression of overpayment and potentially jeopardizing customer trust. By including a 'bill without DoiT' comparison, we can clearly demonstrate the savings and prevent this recurring issue, ultimately improving customer satisfaction and retention. This feature was requested months ago, deemed valuable, and considered relatively easy to implement, yet it remains unaddressed, according to a stakeholder.

   I would also propose adding a column to an invoice to show savings and avoid another invoice explainer element.

   There is a request to add an estimated 'bill without DoiT' directly into the Invoice Explainer. Currently, customers struggle to see the value we provide because they can only view the AWS bill to DoiT and the DoiT bill to them. We also need to know how many are using the console reporting to see their savings. This lack of transparency on the invoice creates confusion, particularly around renewals, leading to the impression of overpayment and potentially jeopardizing customer trust. By including a 'bill without DoiT' comparison, we can clearly demonstrate the savings and prevent this recurring issue, ultimately improving… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Future Consideration  ·  1 comment  ·  Billing & Invoicing  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. GCP Project Billing Bucket Assignment Rules

   When we create projects in GCP, all projects that we create end up in the same billing bucket in the DoiT console. It would be great if we could set up some rules / configuration on the DoiT side to organize projects into different billing buckets based on the GCP project labels / tags. If that was possible, then it's easy for us to just label the projects we create appropriately in our Terraform. Lacking that, even enabling us to manage billing bucket project allocations via your REST API would be preferable to manually assigning projects.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Gathering More Feedback  ·  0 comments  ·  Billing & Invoicing  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Don't group all Marketplace spend under a single line item in GCP invoices

   Right now all Marketplace spend is grouped under a single line item on our GCP invoices but some months we have 40%+ of our bill in Marketplace spend. I'd like to be able to see all of the marketplace line items separately on the invoice.

   8 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Discovery  ·  0 comments  ·  Billing & Invoicing  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating